Archive

Archive for the ‘Microsoft Deployement Toolkit (MDT)’ Category

Why I think DISM is awesome…

August 5, 2011 2 comments

Have you ever run into a situation where a NIC driver just will not install from a driver package in a ConfigMgr task sequence? The NIC driver works when you use it in WinPE. It will install in the full OS outside of the imaging process without issue (i.e. via Device Manager). It just will not install from “Auto Apply Drivers” or a “Apply Driver Package” in the task sequence. I have to say this can be really frustrating. This happened to me with Windows 7 32-bit and some Intel drivers. No version difference would help.

But, I used DISM (Deployment Image Servicing and Management) to install the drivers in the image that I captured and the NIC drivers installed without issue using that new image in the same task sequence. In fact I used the same drivers from the driver package that didn’t work in the task sequence. Nothing different other than installing them into the offline .WIM file of the captured OS.

That is why I think DISM is awesome!

Source: http://technet.microsoft.com/en-us/library/dd744355(WS.10).aspx

Advertisements

Creating a custom SCCM boot image wizard

February 6, 2011 Leave a comment

Assumption 1: you have MDT 2010 Update 1 installed and understand the basic principles of MDT and boot images in a WIM format
Assumption 2: you have configured MDT integration with SCCM
Assumption 3: you understand how to create and edit SCCM Task Sequences within SCCM Operating System Deployment

  1. Create a file structure for your image management (I like to create [Drive]:\Install\OSD with the following subdirectories – “BootImage”, “ISO”, “MDT2010Files”, “OperatingSystem”, and “USMT”)
  2. Share “Install” (you can decide on permissions – I only allow Domain and Local Administrators with a few functional roles as discretionary additions)
  3. Create a subfolder in ““[Drive]:\Install\OSD\BootImage\” named “PreExecutionServerx86” or “PreExecutionClientx86” and “Mount”
  4. Create a subfolder in ““[Drive]:\Install\OSD\BootImage\” named “Serverx86” or “Clientx86”
  5. Copy all of the files from “[InstallDrive]:\Program Files\Microsoft Deployment Toolkit\SCCM” to “[Drive]:\Install\OSD\BootImage\PreExecutionServerx86” OR “[Drive]:\Install\OSD\BootImage\PreExecutionClientx86”
  6. Copy all of he files from “[Drive]:\DeploymentShare\Scripts” to “[Drive]:\Install\OSD\BootImage\PreExecutionServerx86” OR “[Drive]:\Install\OSD\BootImage\PreExecutionClientx86”
  7. Open “WizardEditor.exe” from “[Drive]:\Install\OSD\BootImage\PreExecutionServerx86” OR “[Drive]:\Install\OSD\BootImage\PreExecutionClientx86”
    image
  8. Click on “File” and then “Open” in the “Microsoft Deployment Toolkit Wizard Editor”
    image
  9. Select “Deploy_SCCM_Definition_ENU.xml” and click “Open”
    image
  10. Create your wizard – below are a couple of examples I am using…
  11. “OSType”
    image

    image

    image

  12. TimeZoneSelect
    image

    image

    image

  13. Once you have created all of your wizard settings click on “File” and then “Save”
    image
  14. Close the wizard editor
  15. You will need to crate a custom MDT boot image within the SCCM console
  16. Within the SCCM console go to Computer Management – Operating System Deployment – Boot Images and click on “Create Boot Image using Microsoft Deployment”
    image
  17. Type the UNC path for the location to store your boot image and click “Next” (i.e. “\\SERVER\Install\OSD\BootIMage\Serverx86”)
    image
  18. Provide a name, version, and any comments and click “Next” (I name mine “Server Deployment Boot Image (x86)”)
    image
  19. Put a check next to “Add media hook files to enable the Deployment Wizard for this boot media” and click “Next”
    image
  20. Click “Next” with defaults for the rest to finish it out
  21. Once the custom boot image appears add it to a SCCM Distribution Point (DP)
  22. Open the “Deployment Tools Command Prompt” with elevated privileges
    image
  23. Type either “imagex /mountrw [Drive]:\Install\OSD\BootImage\Serverx86\WinPE.wim 1 [Drive]:\Install\OSD\BootImage\Mount” OR “imagex /mountrw [Drive]:\Install\OSD\BootImage\Clientx86\WinPE.wim 1 [Drive]:\Install\OSD\BootImage\Mount”
    image
  24. The image will be mounted to the temporary location of “[Drive]:\Install\OSD\BootImage\Mount”
    image
  25. Copy “Deploy_SCCM_Definition_ENU.xml” from “[Drive]:\Install\OSD\BootImage\PreExecutionServerx86” OR “[Drive]:\Install\OSD\BootImage\PreExecutionClientx86” to “[Drive]:\Install\OSD\BootImage\Mount\Deploy\Scripts”
  26. Type “imagex /commit [Drive]:\Install\OSD\BootImage\Mount”
    image
  27. The change will commit in the temporary location
    image
  28. Type “imagex /unmount [Drive]:\Install\OSD\BootImage\Mount”
    image
  29. The image with the changes committed will unmount and copy to either “[Drive]:\Install\OSD\BootImage\Serverx86” OR “[Drive]:\Install\OSD\BootImage\Clientx86”
    image
  30. In the SCCM console update the custom boot image that you create and optionally create a bootable CD/DVD or USB drive
  31. If you do not have a “Task Sequence” (TS) created for an OS deployment yet create one
  32. An example you can follow is to edit your TS and create a group for an OS version – in this case I used “Microsoft Windows Server 2008 SP2 Ent (x86)”
  33. In the group “Options” you should add a condition “If All the conditions are true:” and specify the appropriate TS Variable
  34. The TS variable comes from the wizard that was created – in this case if the option for Windows Server 2008 SP2 (x86) was selected the TS variable is “WinSvr2k8SP2Entx86”
    image
  35. You can use these variables to beef up your TS and empower those imaging to customize the deployment without having to mess with the SCCM console or add steps afterward

MDT 2010 Update 1 VM CPU Validation Error

December 1, 2010 Leave a comment

If you try to use MDT 2010 Update 1 to deploy a build or an image when using Virtual PC you are likely to run into a problem with validation.  For some reason the virtual machine CPU comes back as really slow.  To fix this you can edit the ZTIVALIDATE.WSF file.  The code is around line 179 and should be changed to:

If (CSng(oEnvironment.Item("ProcessorSpeed")) < iProcessorSpeed and CSng(oEnvironment.Item("ProcessorSpeed")) > 33) then ‘ Allow for rounding/"creative math"

Found at: http://social.technet.microsoft.com/Forums/en/mdt/thread/b885a71c-2d3f-4e91-b044-5906b8fe3912

MDT 2010 – Setup a new database

October 20, 2010 Leave a comment
  1. Open the MDT Workbench
    image
  2. Assuming you have created a deployment share right click on “Database” found under “Advanced Configuration” and click on “New Database”
    image
  3. Provide a SQL server name and instance if necessary and click “Next”
    image
  4. In the “Create a New Database” field type the name of the database you want to create (I usually do MDT_COMPANY) and then click “Next” 
     image
  5. Provide a SQL share so you can access it using Windows PE for a HTA front-end (I usually just use DeploymentShare$) and click “Next”
    image
  6. Click “Next”
    image
  7. The database will be setup
    image
  8. Click “Finish”
    image 
%d bloggers like this: