Tag Info

Hot answers tagged

5

Before you capture your WIM, configure your reference computer with whatever applications you want to have pre-installed. When the WIM is applied to a target, all that is left to do is join it to the domain and apply any updates. With that said, the beauty of using MDT (and by extension, SCCM) is that you can create separate application packages that can ...


4

I found all the different places that it needs to be updated but wanted to document them here incase anybody else ever runs into a similar issue. DeploymentWorkbench > Deployment Shares > Share Name > right-click > Properties > General > Network (UNC) path DeploymentWorkbench > Deployment Shares > Share Name > right-click > Properties > Rules > Edit ...


3

The answer to 1 and 3 is "yes, but..." You may want to organize your drivers according to whether you need to use them in the boot (PE) images or the install images. Separating the drivers by model of computer can make it easier to replace the correct drivers when new versions are released. Updating the deployment share depends on where the drivers are going ...


2

We use a development DP, staging DP and production DP. We do our engineering in the dev DP, and testing from our staging. Once we're ready to support the DP, we replicate from Staging to Production. We haven't really encountered any issues so far. As for the DFS, not sure. I wanted to take a look into this but I suppose it would largely be determined if ...


2

You generate the catalogs by installing WAIK on a 32bit system and running the Windows System Image Manager on that image.


2

MDT 2010 requires and use WAIK for deploying Operating systems. MDT is a Toolkit/Workbench that brings together the Microsoft tools for image deployment into a neat intuitive package. If you plan on doing muliple, possibly repetitive deployments it is definetly the way to go. Pair MDT with WDS (Windows Deployment Services) and you can multicast/unicast ...


2

It looks like you are trying to load the registry very deep in the current registry file with this command:reg load hklm\software\microsoft\windows\currentversion\policies\system c:\mount\windows\system32\config\software Try this instead "reg load hklm\test c:\mount\windows\system32\config\software" If that completes, open regedit and navigate to hklm\test ...


2

The steps in the task sequence execute after the local administrator account has logged on and this needs to occur before. I'm not aware of a way around that within the task sequence itself. You should be able to mount your WIM file and remove those lines using regedit against the registry contained within. EDIT - I used to mount with dism and use the ...


2

Sounds like you need to add the drivers for the NIC into the Boot.WIM. I know you said you use MDT to add drivers to your WIMs but are you sure you're adding the correct ones? Dell provides a WinPE Driver pack. I created a folder under the Out-of-Box drivers called WinPE and a selection profile called WinPE that only selects that folder. For the Boot.WIM ...


2

Yes, the current thinking when using MDT is not to image them but to "deploy" them. A "deployment" consists of the base OS (thick or thin) + model specific drivers, plus any apps for the particular role you are deploying. Driver management can be as specific as you want. See this article for a video walkthru of how to deploy a system with MDT


2

To expand a little on Kieran's answer you can get driver packs that will help you out too. Dell put out drive packs on their community wiki. Also you can user Driverpacks.net too.


2

The short answer is no, you can't do what you're asking without access to the network configuration. The PXE bootstrap broadcasts a DHCPDISCOVER packet with PXE-specific options on UDP port 67, which is not normally routed. Because of this, the PXE server must be located on the same subnet unless you configure your network for forward UDP traffic. There ...


2

I just ran a test to verify adding a driver to a boot image. It has been some time since I needed to since I've moved on to SCCM 2012. First you need to add the driver to your "Out-Of-Box Drivers". You then need to right click your deployment share and select properties. Select the tab "WinPE" and make sure the second radial button (Include only drivers of ...


1

WDS provides PXE boot capacity and the the ability to capture and deploy images. MDT provides a ready way to inject drivers and execute scripted installation steps. You can use a captured WIM created by WDS in MDT - I have done so on a few occasions. My personal preference is to totally avoid using captured WIM images. While they work I have found the ...


1

WDS is interesting in that it grabs one DHCP address at PXE boot, and then grabs another one right after that after WinPE has started. What happens on some networks is that the DHCP server can't respond quickly enough to support this behavior. I have been able to remedy this exact problem on some networks by enabling portfast on the switches/switch ports ...


1

Try placing the script into the Scripts folder on your MDT server and firing the script with "cscript Z:\YourScript.vbs" as a step. EDIT: It should just be "cscript Z:\Scrupts\YourScript.vbs". The steps in MDT execute in the context of the administrator of the box being built. That account has Z: mapped to the DeploymentShare directory during the build. ...


1

This can easily be done by connecting to 2 deployment shares and dragging and dropping the "folders" from one share to the other. I have done this often and it works just fine. It does however take some time.


1

When I get this error I usually delete the the two folders created by the MDT process and start afresh. C:\Minint C:_SMSTaskSequence I boot into the system using Hiren BOOT CD and delete the folders.


1

Try wiping out the contents of the hard drive, at least by removing the partition table. I've often seen issues like this crop up when a few remnants of a previous MDT installation are present. I keep a copy of DBAN on my MDT server just in case this crops up. If you go the DBAN route you only need to let it run for about a minute.


1

You should do a Sysprep & Capture task on your golden master computer (i.e.: a clean computer that has all your software and updates installed, but is not part of the domain, etc.). That will avoid the installation process for all programs and updates.


1

There are ways of scripting the installations and post-installs right down to having your systems pre-injected in AD and auto-join and everything. Personally we've had times where things go wonky or not quite right, so the bare simplest way we use WDS is this: Create a reference system. Configure it with applications we want, updates, etc. Run the ...


1

Found the answer I was looking for http://social.technet.microsoft.com/Forums/en-US/mdt/thread/84831d92-b69a-493b-8dc8-3e0efb419242/ Example: [Settings] Priority=TaskSequenceID, Default [XP] OSDComputerName=XP SkipUserData=YES [Default] KeyboardLocale=en-us UserLocale=en-us UILanguage=en-us


1

The choice is based on the order they are listed in in your Roles tab. The first one it loads is the one that will be retained at the end of the list.


1

You can install the MDT Workbench on a workstation and then connect to a remote Deployment Share if that is what you're asking. You will have to install WAIK/PowerShell on the workstation though.


1

Create/edit the config.xml (via Deployment Workbench -> application properties -> office products tab), while specifying "Display level: None" for a silent/unattended installation. source


1

Your source CD should be a volume license copy CD. If you look at the OEM cd you should see CLG files for all of the versions. If all you have is OEM media make a copy of the sources directory and delete all of the clg files except for the one you want and try the process again. The step-by-step guide assumes you are using media specific to the edition you ...


1

It sounds like a problem with the exe installer in that the primary exe you are running isn't the main installer process, it just kicks off the real installer and exits. So the task sequence thinks the step is finished and it can move on to the next step. I could've sworn Autodesk apps have a deployment tool that can create a standard MSI deployment. If ...


1

I'm not familiar with this tool, but error 0x8007051B means the following: ERROR_INVALID_OWNER winerror.h # This security ID may not be assigned as the owner of this # object. My guess is this is related to user rights and somebody needs the SE_RESTORE_NAME privilege, but on what, I don't know.


1

BDD 2007 is the older version of the Microsoft Deployment Toolkit 2010 (which is what you should be using to deploy Windows 7). Make sure you are running MDT 2010 instead of BDD 2007 (download here: http://www.microsoft.com/downloads/details.aspx?FamilyId=3BD8561F-77AC-4400-A0C1-FE871C461A89&displaylang=en)



Only top voted, non community-wiki answers of a minimum length are eligible