Installing Applications via the Configuration Manager 2012 Task Sequence Takes A Long Time

Lately I’ve been working on a Windows 7 SOE solution which is being deployed via System Center 2012 Configuration Manager.

The Windows 7 SOE design consists of a thin-image (captured using Configuration Manager – with all Critical, Important, Low Updates as well as IE9). I experienced nothing but good performance when capturing the image so was a bit surprised to discover when testing the end-to-end deployment of the Windows 7 SOE with Applications (deploying applications in the Task Sequence using the the new Install Application step (which I use variable instead of specifying each application), on some devices the time it would take to complete an Application Installation could take quite literally hours. Take the Adobe Flash Player installation as an example – it would normally be a case of blink and you miss it, but in some cases I found it could take a good 20 minutes.

The hardware I’m working with varies, but in nearly all cases it’s one of the various HP SFF’s or USDT’s. The client has been running a Windows XP image (deployed by Acronis – a solution built by the client’s internal IT department). Because the people who built the XP image struggled to get the Intel Storage Drivers working, they switched the BIOS Storage configuration to Legacy mode instead of AHCI. Doing this prevented the XP systems from Blue-screening due to missing storage driver.

I wondered what would happen if flicked that setting back to AHCI. So I did….

hp-bios-sata-ide

hp-bios-sata-ahci

The build time on a HP 8000 Elite SFF and a DC7900 SFF has basically halved and most notably, the application installations are now installing as quickly as you would expect.

The HP 8000 Elite went from 2:05hr down to 0:41m.

The deployment includes:

  • Windows 7 Enterprise SP1 x86 image
  • Adobe Flash
  • Adobe Reader
  • Adobe Shockwave Player
  • Microsoft Office 2010
  • Microsoft Visio Viewer 2010
  • Oracle Java Runtime 1.7
  • McAfee Framework Package

 

I don’t know if it will work for everyone, but give it a go and see what happens.

 

Ben Fisher

Connect with me on LinkedIn: http://au.linkedin.com/in/fisherben

Follow me on Twitter: http://twitter.com/ben__fisher

Join my System Center 2012 LinkedIn Group: http://www.linkedin.com/groups?gid=3752127

email

Written by , Posted .
  • http://myITforum.com/myitforumwp/community/members/baatch/ Iceee

    Is there any way to detect and change this with script in the task sequence?

  • http://rickmahn.com/ Rick Mahn

    With HP systems, you can program the BIOS from the TS. There is an HP tool that does it, but requires a config file for the particular model you’re running it on (they’re not all identical). The catch is that it needs to be run from the Full OS and not WinPE, so if you start your imaging TS as a Deployment to an existing system, you can change the BIOS settings before booting into WinPE and imaging the system.