Persistent Device Drivers in Reference Image

We needed to keep the Intel USB 3.0 drivers in a Windows 7 reference image.

  1. Import the drivers into MDT and create a selection profile.
  2. Edit the TS and update the Injected Drivers step to point to the selection profile.
  3. Open and edit Unattend.xml. Add the component called Microsoft-Windows-PnpSysprep to Step 3 Generalize.
  4. Edit the PersistAllDeviceInstalls option to be true.
  5. Save the Unattend.xml file and close.

More information here: http://technet.microsoft.com/en-us/library/ff716298.aspx

Windows 7 Pre-Provision Bitlocker Not Working

After updating Configuration Manager 2012 R2 and adding the Windows 10 ADK, task sequences will no longer pre-provision BitLocker

Reason:

With WinPE 10 it uses the AES-CBC 128-bit encryption method.

Solution:

Add the following Run Command Line steps after Format and Partition and before Pre-provision BitLocker.

  1.  Set EncryptionMethodWithXtsFdv – reg add HKLM\SOFTWARE\Policies\Microsoft\FVE /t REG_DWORD /v EncryptionMethodWithXtsFdv /d 3 /f
  2. Set EncryptionMethodWithXtsOs – reg add HKLM\SOFTWARE\Policies\Microsoft\FVE /t REG_DWORD /v EncryptionMethodWithXtsOs /d 3 /f
  3. Set EncryptionMethodWithXtsRdv – reg add HKLM\SOFTWARE\Policies\Microsoft\FVE /t REG_DWORD /v EncryptionMethodWithXtsRdv /d 3 /f

Available Encryption Methods in WinPE 10

  1. Value Data: 3 (Description: AES-CBC 128-bit)
  2. Value Data: 4 (Description: AES-CBC 256-bit)
  3. Value Data: 6 (Description: XTS-AES 128 bit)
  4. Value Data: 7 (Description: XTS-AES 256-bit)

CScript Error: Can’t find script engine “VBScript” for script

During a OSD task sequence in Configuration Manager, we ran into an error with a VBS script that has worked previously.

The error in the SMSTS.LOG file was: CScript Error: Can’t find script engine “VBScript” for script

The problem appears to be caused by a changed registry value: HKEY_LOCAL_MACHINE\Software\Microsoft\COM3\REGDBVersion

After some searching on the internet the solution was to add the modify the REGDBVersion to a value of hex:01,00,00

Add to task sequence via a Command Line: REG ADD HKLM\Software\Microsoft\COM3 /v REGDBVersion /t REG_BINARY /d 010000 /f

Profit!

best practices

Some light reading for the bus ride home:

Download Whitepaper on Top 10 Best Practices on Windows 10 OSD with SCCM ConfigMgr

Re: Install Application Step fails in Task Sequence

Great blog post about a similar issue we were having in production.

Instances where application will not install after a reboot. Even when the logs say they installed correctly. We found this was more likely to happen on devices with SSD compared to SATA drives.

Looks like a know bug, but nothing a sleep command can solve: http://www.bctechnet.com/install-application-step-fails-in-task-sequence/

MDT Installing Office 365 – Check license and the correct Product ID

Always good to make sure you have the correct Product ID in you configuration file when installing Office 365. An easy way to do this is to check you license in the Office 365 Portal.

  1. Login to the Office 365 Admin Center and click Billing then Licenses.
    Capture
  2. Then go to the TechNet page: Product IDs that are supported by the Office Deployment Tool for Click-to-Run
  3. The page lists all the Product IDs that are supported by the Microsoft Office Deployment Tool for Click-to-Run
    Capture
  4. Ensure you select the right one when downloading and install the appropriate Office application.
    In my example I would use:

    <Product ID="O365BusinessRetail">

Reference for Click-to-Run configuration.xml file

 

Failed to run the action: Use Toolkit Package – Error: 80070002; Source: Windows

Error:

Failed to run the action: Use Toolkit Package.
The system cannot find the file specified. (Error: 80070002; Source: Windows)

Use Toolkit Package Error 80070002

Environment:

System Centre 2012 R2 CU5 Integrated with MDT 2013. Deployment Windows 7 SP1 with Office 2013.

Cause:

If the Drive Letter task sequence variable is configured to True. This does not occur if it is configured to False.

Solution:

To work around this issue, create the following two Task Sequence variables at the very top of the Task Sequence:

SMSTSDownloadRetryCount = 5
SMSTSDownloadRetryDelay = 15

Place them immediately after the Execute Task Sequence group.

Troubleshooting OSD – Now where are those logs again?

When troubleshooting you’re OSD, it is always good to know those log locations. Here is a quick list of the smsts.log and it’s locations during the deployment:

  • WindowsPE, before HDD format: x:\windows\temp\smstslog\smsts.log
  • WindowsPE, after HDD format: x:\smstslog\smsts.log
  • Windows, SCCM agent not installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
  • Windows, SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.log
  • Windows x64, SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
  • Task Sequence completed: c:\windows\system32\ccm\logs\smsts.log
  • Task Sequence completed x64: c:\windows\sysWOW64\ccm\logs\smsts.log

Are you PXE booting?

Better have this log file in you favourites; \\DPServer\D$\SMS_DP$\sms\logs\SMSPXE.log. It records details about the responses to PXE boot clients and details about expansion of boot images and boot files.

Document a Configuration Manager 2012 Task Sequence

After sometime I was able to document a Configuration Manager 2012 Task Sequence using the tsDocumentorv2.xsl file that was previously used for MDT Task Sequences.

  1. In Configuration Manager 2012 export the TS to a zip file.
  2. Extract the zip file.
  3. Navigate to SMS_TaskSequencePackage\{packageid}.
  4. Copy tsDocumentorv2.xls into the SMS_TaskSequencePackage\{packageid} folder.
  5. Open the file object.xml and search for CDATA
  6. Copy everything between <VALUE><![CDATA[ and ]]></VALUE>
  7. Paste it into a new text file. The contents should start with <sequence version=”3.00″> and finish with </sequence>.
  8. Add the following text to the top of the new file <?xml-stylesheet type=”text/xsl” href=”tsDocumentorv2.xsl”?>.
  9. Save the new file with a .xml file extension into SMS_TaskSequencePackage\packageid folder.
  10. Start Internet Explorer and open the newliy created xml file.
  11. Hit F12 and enable Compatability View browser mode.

Michael Niehaus Notes from TechEd North America

As we were going through our TechEd North America deployment pre-conference today, we showed a lot of links for pages of interest.  Here is a list of those (at least the ones I remembered):

Also, be sure to look for the session slides on http://deploymentbunny.com.