Reimaging with OEM licenses

I came across a TechNet blog post on Microsofts site the other day that taught me something new I thought I would pass along in case it would help someone out.  If you don’t have software assurance with Microsoft but are a volume license customer you can deploy volume license media providing you have keys and the edition of the OEM OS and the Volume License match.  This means you don’t have to be purchasing volume licenses to reimage provided you do have at least a few volume licenses of the software you are trying to deploy.  The below blog posts provide more info.  Guess you learn something new every day.

https://blogs.technet.microsoft.com/volume-licensing/2014/02/13/licensing-how-to-reimaging-rights-top-5-questions/

http://www.aidanfinn.com/?p=14534

 

Advertisements

SCCM 2012: dynamic app install Policy download failed

I had an issue the other day with an application not installing that I had been installing for a long time through the UDI wizard with the MDT Integration with SCCM 2012.  Suddenly it had stopped installing and I got the below error in the SMSTS.log.

Make sure the application is marked for dynamic app install Policy download failed, hr=0x80004005. The operating system reported error 2147500037: Unspecified error

While this error can be caused by symbols such as a comma or ampersand in the application name for me it was because I had changed the application name to a more user-friendly name which in turn broke the UDI as it doesn’t dynamically update application names.  I simply went into the UDI and removed and re-added the application and it started working again.

 

 

NVMe drivers

Just a quick note incase someone else is having this issue.  I was working on using SCCM to image a Dell 7710 laptop and it has a Samsung M.2 PCIe NVMe SSD which I couldn’t seem to ever find  the right storage drivers to get it to see the hard disk.  It was a one time deal so I resorted to having the onsite tech manually load the machine (which was an endeavor in itself as he had to find the right storage driver to load windows 10 and if you wanted to do windows 7 you had to have USB 3.0 drivers slipstreamed into the windows installer). Upon trying to image another machine pxe would stop part way and display the below error message.

File: \Windows\system32\DRIVERS\nvme.sys

Status: 0xc0000359

Info: Windows failed to load because a critical system driver is missing, or corrupt

Turned out just like it says nvme drivers I had loaded caused it to completely not load the pxe boot image which I hadn’t seen occur before in adding drivers to a boot image.  Pretty straight forward but figured it might help someone that gets this error especially if you didn’t add the drivers or forgot that you had added them.

MDT 2013 Update 2 UDI Wizard – domain join credentials issue

I recently upgraded to MDT Update 2 integrated with SCCM 1602.  Previously I used to install Windows 7 using MDT UDI (2013 I think?) and configured the OSDJoinDomain and OSDJoinPassword variables as collection variables on the collections I had the task sequence.  But after the 2013 update 2 install, on my new task sequence for Windows 10 they would show up like the below and it wouldn’t join the domain.

Capture3.PNG

So thanks to some help on this TechNet forum we were able to come up with a workaround.

  1. Create two custom variables and place them just before the UDI Wizard step in your task sequence.  One will be the account used to join the domain and the other the accounts password.Capture4.PNGCapture5
  2. Then open up the UDI Wizard Designer and on the new computer details page under “domain join credentials” put in the custom variables you setup into the default value boxes (remember to use %% around your task sequence variables).Capture6
  3. Then simply save your changes and update your MDT Toolkit package in SCCM.  Then you should be all set.

 

MDT UDI Wizard won’t update

Well I finally got a good image of Windows 10 with my custom settings yesterday so now it was on to iron out my deploy task sequence for SCCM integrated with MDT 2013.  I was working on getting my existing UDIWizard_Config.xml files from my MDT 2013 toolkit files for Windows 10 to work with MDT 2013 Update 2.  Why create an entire new file when you can simply reuse my wizard settings as I have a lot of custom settings for OU’s and such.  It seemed that no matter what I did it held onto the old settings and wouldn’t update.  Finally through a mention in a technet forum I discovered that the applications in the install programs page in the wizard caused it to fail and use the old UDIWizard_Config.xml from before.  So I simply deleted all my software in the wizard and re-validated the site settings with configuration manager and then went in and clicked update distribution points.  Eureka, upon pxe booting all my new settings were there. Goes to show what I get for reusing UDI Wizard settings.  So yes you can reuse your UDI wizard settings from previous MDT Versions but proceed with caution.

snip_20160524102205

Windows PE initialization fails with error code 0x80220014

I’ve continued to fight a bunch of issues trying to get imaging to work the way I want it in SCCM 1511/1602.  Well another issue I was running into was when capturing from an SCCM capture disc I would get Windows PE initialization failed with error code 0x80220014.  Well what I discovered is this Microsoft Hotfix fixes the issue and is still an issue in SCCM Current Branch 1602.

 

snip_20160523163222

I have been integrating MDT with SCCM for a long time and followed the below steps from Microsoft to fix the initializing issue when capturing using my MDT boot image. Below are the steps from Microsoft with a few notes and changes on how to do this with an existing MDT Boot image This must be done on a machine with Windows ADK for Windows 10 is installed.

Step 1: Preparation

  1. Extract the contents of the hotfix. For example, extract the contents to the %userprofile%\downloads folder.
  2. Start an elevated “Deployment and Imaging Tools Environment” command prompt.

snip_20160523154044

Step 2: Prepare Windows PE

Create the Windows PE customization working directory, and then mount the image file. To do this, type the following commands, and then press Enter after each command:


dism /mount-wim /wimfile:”E:\Sources\Imaging\OS\MDT Boot images\MDT Boot image W10 64bit SP2\Winpe.wim” /index:1 /mountdir:E:\mount

Note: Point the /wimfile parameter to the winpe.wim you have been using that is having the boot problem.  There will be an second WinPE.packagenumber.wim that SCCM creates from the winpe.wim.  Leave it alone it will get updated when we update the distribution points.  For the /mountdir parameter just create an folder somewhere as the mount directory, here I just created an mount folder at the root of E.

Step 3: Save schema.dat state

Back up the permissions that are applied to the existing schema.dat file before you replace it. To back up the file, type the following command, and then press Enter:

icacls E:\mount\Windows\System32\schema.dat /save “%temp%\AclFile”

 

Step 4: Update the schema.dat file

To replace the schema.dat file that has the updated version, you must take ownership of the file and grant permissions to the local administrators group. To do this, type the following commands, and then press Enter after each command:

takeown /F E:\mount\Windows\System32\schema.dat /A

icacls E:\mount\Windows\System32\schema.dat /grant BUILTIN\Administrators:(F)

xcopy “%userprofile%\Downloads\schema-x64.dat” E:\mount\Windows\System32\schema.dat /Y

Note: the Xcopy is assuming you extracted the hotfix in the downloads folder.

Step 5: Reset permissions and ownership

When the schema.dat file is replaced, the permissions saved in step 5 must be restored by running the following commands:

icacls E:\mount\Windows\System32\schema.dat /setowner “NT SERVICE\TrustedInstaller”

icacls E:\mount\Windows\System32\ /restore “%temp%\AclFile”

 

Step 6: Commit Windows PE changes

Commit the changes to the winpe.wim file. To do this, type the following command, and then press Enter:

dism /unmount-wim /mountdir:E:\mount /Commit

Step 7: Update Distribution points

Click update distribution points on the MDT boot image and then wait for drivers to be injected into your fixed boot image.

snip_20160523155257

Step 8: Recreate capture media

If your doing this like me and using capture media make sure and recreate it so it uses your new boot image.