Tag Info

Hot answers tagged

6

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

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 ...


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

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 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

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

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 ...


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

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


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

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 ...


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 ...


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

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

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

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

Based on my experience and research, Role settings are applied on a first assignment wins basis, and the order of the roles in the MDT UI has no bearing on the order in which evaluation occurs. Instead, RoleSettings (the MSSQL view that returns these settings) is queried with the following syntax: SELECT * FROM RoleSettings WHERE ROLE IN ...


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

Vista SP2 media is available... on MSDN, at least. Anyway, have you tried installing SP2 on a vista SP1 computer and capturing an image of it using the "Sysprep and capture" MDT task sequence?


1

Use WAIK to integrate your language pack into Vista SP2 English media and set it as default language. You can easily find language packs around or download them from VL, MSDN etc. I'm pretty sure you can find them from Microsoft Update catalog, but i didn't bother to check myself. I have repeadedly used this method to create custom images (3 languages etc). ...


1

Look into MDT 2010. It has builting functionality to boot into WinPE and Query a SQL Database (based on the computers Mac address) for pretty much anything you want and populating this into unattend.xml before the install runs. Lots of options. Takes a little while to get the hang of it, but it's pretty logical. IP Address specifiation was a bit troublesome ...


1

It sounds like you want a WDS server. WDS is Windows Deployment Services, replacing the older Remote Installation Services (RIS). And uses answer files, can name systems within a naming convention, and can be installed through a network boot. Here is a very cool article on how 2500+ notebooks were simultaneously installed with Windows 7 at the TechEd ...


1

If you can mount a VHD you can just use: [UserData] ComputerName = <computer name> in C:\SysPrep\sysprep.inf file. As for IP there is a NetSet tool which is able to set up IP. But just using DHCP with static assignments will be much better - easier and more flexible.


1

Solved the ActiveX Problem. ActiveX is already installed in Windows 7. It can be found in the services menu. This may be the cause for this error. I have fixed it by only changing the startup type through the command line in the applications menu in MDT 2010. Following command will do the Job sc config AxInstSV start= auto As for the errors that are ...


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