Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1248
  • Last Modified:

Windows 7 WIM Deployment

Hi.

Recently I have been researching deployment methods for Windows 7 in order to speed up our installs. To start with, this is what I have done so far...

- Set up a 'base' system. Installed Windows 7 Professional 64-bit with all Windows Updates, additional programs, runtimes etc. Ran Sysprep with oobe and generalize and shut down.

- Created a Windows PE disk with Imagex on. Booted this on the 'base' system and captured a WIM file.

- Obtained an ISO of Windows 7 Professional 64-bit and extracted it with 7-zip. Removed the install.wim file from the sources folder and replaced it with my custom wim - also called install.wim

- Used ImgBurn to create a new iso (also tried using a bootable USB).

Booting from this all seems to go well at first.
- Copying Files
- Expanding files
- Installing features
- Completing installation
All of this completes, then it restarts the system. Upon restarting it gets to "setup is starting services" then throws the below error message.

"Windows could not finish installing the system. To attempt resume configuration, restart the computer."

Restarting the computer just re-creates the error again and again.


I'm stuck as to what is causing this error. Any ideas? Can you spot anything I have done incorrectly?
0
KTBerwick
Asked:
KTBerwick
  • 5
  • 3
  • 2
  • +1
2 Solutions
 
Gabriel CliftonCommented:
Could be sysprep corruption, sysprep did not completely before shutdown or something not configured correctly in the unattend.xml. On the base system where you created the image and ran the sysprep from, what does it do if you boot it up normally?
0
 
KTBerwickAuthor Commented:
For some unknown reason it never came to mind to boot up the base system and see if it actually works. Such an obvious thing to check as well!

Unfortunately I can't check until tomorrow since I'm not in the same building any more.

Is it essential to create an unattend.xml file? I did not create one during this process.
I don't mind inputting the Username, time zone, update preferences etc manually so I left it out (for now anyway). Didn't want to add more complications in something I already know little about.
0
 
Gabriel CliftonCommented:
The sysprep uses the unattend.xml to help make it generic again.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
KTBerwickAuthor Commented:
In that case I will definitely look into making the unattended.xml file.

An very odd development...

If I reboot the system into safe mode it gets to the same stage and tells me the installation cannot be completed in safe mode, as you would expect. When I reboot again, normally this time, it opens this Windows Installation screen back up:
- Copying Files
- Expanding files
- Installing features
- Installing updates
- Completing installation

They are all marked as completed apart from the last entry. After about 30 seconds it reboots the computer and the installation completes! All my installed programs and updates are there, everything seems as expected.

Done another fresh install (in a VM) and exactly the same thing happened. Seems like something is getting stuck and going into safe mode dislodges it.

So I guess I'm getting to where I wanted but in a very weird way.
0
 
Gabriel CliftonCommented:
That is strange considering that I cannot think of anything in safemode that will "dislodge" the final step.
0
 
KTBerwickAuthor Commented:
Me neither. Very strange indeed but hey it works.

I'l try creating another image in the next few days and see how that goes. I need a Home Premium image anyway.
0
 
Adam LeinssCommented:
Why not use MDT 2012 from Microsoft?  It's all wizard driven and includes everything you need "in-the-box".
0
 
KTBerwickAuthor Commented:
Thank you very much for suggesting MDT. I used it to create another WIM of Win 7 Home Premium and it was a LOT easier.

I have figured out the cause of this error message and a solution.

It was nothing to do with capturing and deploying the image. Sysprep was not completing fully because of AVG Antivirus that I had installed. I uninstalled AVG and replaced with MSE before running Sysprep again. This time it went without a hitch.


 I used this method to find out what was causing the error...


This issue is caused by certain registry keys that are either:

a) Larger than 8kb

b) Set with incorrect permissions

c) Corrupt in some way


When you see the error message, do the following:

1.) Push Shift+F10 to get to a command prompt

2.) Navigate to C:\windows\Panther

3.) Find the Setup.etl file and find a way to copy this file off of the system (I copied it to the D:\ partition and used Ghost to gather that partition and get the file off)

4.) Copy the setup.etl file from the corrupted system to another computer that has Windows 7.  Put it on the root of C:\ for easiest access.

5.) Open a Command Prompt on the Windows 7 computer.

6.) Navigate to the root of C:\ (or wherever you saved the file)

7.) Type "tracerpt setup.etl -o logfile.csv"

8.) Close the command prompt and open up logfile.csv in your text editor of choice.

9.) Look through the log file (towards the end probably) for messages that say "Failed to process reg key or one of it's decendants"  For me, the exact eror looked like this: "Failed to process reg key or one of its descendants: [\REGISTRY\MACHINE\SOFTWARE\ESET\ESET Security\CurrentVersion\Plugins\01000200\Profiles\@My profile]"  If you search for "reg key" or "failed to process" you should find the failure.

10.) Remove this software from your image, or find out how to get the registry key that is failing to work properly.

Credit to Jeff Harrison on TechNet for this solution.
0
 
Adam LeinssCommented:
Interesting!  I added that to my notes.
0
 
Mike TLeading EngineerCommented:
Hi,

You've pretty much got there on your own with help from Jeff, so well done.

For anyone reading the solution in future, there were two uneccessary steps: 1 - the bait and switch with install.wim, 2 - putting apps in the original image.

Unfortunately antivirus products wreak havoc with OS deployment, so avoid installing until the OS is done.

Using MDT instead is by far the easiest, quickest way to achieve all the above, as you've found. Checkout the customsettings.ini file for serious automation if you need it.

Mike
0
 
KTBerwickAuthor Commented:
It fixed my problem.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 5
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now