MDT 2010, IE9, offlineServicing error

Came across this the other day and didn’t see anything come up in a Google search so figured I’d blog it.

If you’ve recently added Internet Explorer 9 (IE9) to your MDT deployment, and you’re getting an offlineServicing error when deploying an OS, you may want to check this out.

The problem seems to occur when:

  • You’re running Microsoft Deployment Toolkit 2010
  • You’re deploying Windows 7 with SP1 integrated
  • You’ve added IE9 in .cab format to the deployment via Packages
  • When deploying an OS, you get a fatal error saying: “Windows could not apply unattend settings during pass [offlineServicing]”

To fix the problem, I removed the IE9 .cab from Packages and instead, integrated it into the install.wim image, using these instructions: Windows 7 – Add or Remove Packages Offline

I will attempt to write up proper instructions when I can, but the above link should provide you with enough information to work it out ๐Ÿ™‚

MDT 2010 and WinPE 3.1 Reboot issue

If you’ve recently updated your WinPE from 3.0 to 3.1, you may notice an annoying reboot issue.

It looks like this: after you’ve rebuilt the .wim image, and booted from it via WDS (Windows Deployment Services), WinPE boots up and shows the Solution Accelerator background, but after a short period of time, it reboots the PC without having done anything.

This happens if:

  1. You’ve got Microsoft Deployment Toolkit (MDT) 2010 Update 1.
  2. You’ve upgraded WinPE from 3.0 to 3.1, using the supplemental update ISO.

To fix this problem, Michael Niehaus has some instructions to follow.

Fortunately we don’t use WinRE, so we can use the workaround and still make use of WinPE 3.1. Had we needed WinRE, I would have restored the backup of the WinPE 3.0 files I’d made before copying over the 3.1 files. I’ve been bitten by MDT issues too often to not make backups of stuff I’m overwriting! ๐Ÿ˜‰

Got problems deploying .Net Framework 4.0 on MDT 2010?

Recently I’ve been having really weird issues getting the Microsoft .Net Framework 4.0 to be deployed as an Application via Microsoft Deployment Toolkit.

It would install perfectly if I installed it as a local admin user with the /q /norestart command, but doing the same thing through MDT resulted in the app hanging (and thus, the entire deployment).

After a quick search, it seems I’m not alone. Check out this thread on Technet for how to solve it! ๐Ÿ˜€

Deploying Office 2010 – Prevent Activation Wizard

If you’re deploying Microsoft Office Professional Plus 2010 with a MAK key, and you want to avoid the user seeing the Microsoft Office Activation Wizard when they first start up an Office application, follow these instructions:

  1. Run the Office 2010 Customization Tool (OCT)
  2. Open up your customised MSP file
  3. Go to: Setup > Add installations and run programs > Add…
  4. Then enter the information as seen in the image below.
    1. Target:ย [SystemFolder]\cscript.exe
    2. Arguments: “C:\Program Files (x86)\Microsoft Office\Office14\ospp.vbs”ย /act
  5. Don’t forget to save your MSP!

This will activate Office immediately after it is installed, so that it won’t pop up the Activation Wizard when the user first runs Office. Think of this as either a kind of pre-activation or post-activation of Office 2010.

This guide makes the following assumptions:

  1. You know how to load OCT (Office Customization Toolkit)
  2. You are deploying 32-bit Office onto 64-bit Windows
  3. You deploy Office 2010 at Deployment time using Microsoft Deployment Toolkit (although, for this to work, you don’t have to).
  4. You deploy Office 2010 using a MAK key.
  5. You store your MSP file in the \Updates\ within the Office 2010 installation files on the MDT share (again, for this to work, you don’t have to).

I found this info after hopelessly searching around, finally coming across this page on Microsoftย Technet.

Automatically install Windows Updates / Hotfixes when installing Vista

If, like us, you run a BDD or MDT setup in order to install your Operating Systems, this might be useful ๐Ÿ™‚

If you’d like to pre-install Vista updates and hotfixes while Vista is installing:

  1. Go to your Distribution Share (C:\Distribution)
  2. Go into Operating Systems, then find your Vista OS (C:\Distribution\Operating Systems\Windows Vista Business SP1 – 32bit\)
  3. Create a new folder in this directory called “update”
  4. Copy all of your Vista Update files (.msu) into this directory
  5. That’s it ๐Ÿ™‚ The next time you run a Vista deployment, the updates will be pre-installed!
The same concept applies to installing from a Vista DVD.

Extra tip

If you’d like a list of updates released since Vista SP1, check out this site:ย