Has anyone had this happen before?  This is the first time I have tried a scripted installation.  The method I used was:

 

1.  Uploaded the most recent source CD directly from MSDN

2.  Preinstallation Task- Create Single Partition

3.  Scripted Installation

4. Postinstallation Task (Windows Environment)

        --Disable UAC

        --Install Office 2010 using setup.exe /adminfile office.msp

 Update:  Right after I posted this, the computer finally rebooted.  It had stayed on that same screen for 45 minutes....

When I left the office, the rest of my windows environment post installation tasks were running.  Is there any way to speed this up?

 

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2

Just thought I'd share my experiences - I use scripted installs for WinXP and Win7, including multiple apps (anywhere from 10 - 15, including MS Office & Adobe Acrobat) and WSUS Offline (which copies ~2GB of updates down & installs them) and my scripted installs take ~1.5 hours to complete for everything.  A little slower to deploy than an image (from what I've read), but much faster than reloading systems by hand and much easier to maintain than images.

Something I have run into on several occassion is scripted installs getting stuck on certain screens (especially before Windows starts loading).  I've found the typical "fix" to be to delete the deployment task for the machine and then redeploy to it - this typically fixes this issue.  A couple of times I fixed another issue with hangs by rebuilding the scripted install from scratch.

I haven't had any of these issues for a while, and typically just duplicate existing working scripted installs using them as a baseline for new ones (adjusting postinstall tasks as necessary).

John

Answered 05/22/2012 by: jverbosk
Red Belt

Please log in to comment

Answers

0

I have not seen this specific behavior.

My understanding is that scripted installs are slower than imaging. It has to run the install rather than just laying down files.

You will get some speed increases out of making sure to use a gigabit network. Client resources also impact how long it will take.  IE. Slow laptop drives take much longer than 10K RPM desktops.

If you have updates running, that can vary the time it takes before completing.  Certain drivers also take longer.

Answered 05/18/2012 by: philologist
Red Belt

  • Thanks Philologist. The scripted images do take forever, from what I have seen. Now, I did create a .wim of this laptop and attempted to deploy that, however, there are problems occurring with that as well. If I cannot sort through it, I will make a new post.
Please log in to comment
Answer this question or Comment on this question for clarity