Systems Deployment

right, I've got this working. I recaptured teh image locally then setup a remote site appliane in teh remote office. The image deploys ok now, just the drivers that are an issue now.

ok, this problem persists....sort of......

I can deploy the image no problems locally and remotely using the remote appliance.I sometimes get erros in the log about files existing already but that's fine as detailed in Corey's post above.

However, I've just tried to deploy to one of our newer models which is UEFI based and I've got the winload.exe missing error again.

This is a single partition win 7 image so as far as I'm aware it shouldn't make any difference if it's a UEFI or BIOS PC should it?

- See more at: http://www.itninja.com/question/deploying-win-7-single-partition-image-missing-winload-exe#answer-90198

To me it looks like the image file or the network is to blame when it is dropping bits and rereading the file.  Does it do this with other images or just this one.  If others work I would reupload the image.

ok that makes sense. I originally captured the image from a PC in our branch office, over the vpn.

I'm deploying it locally but maybe the original capture had some issues.

ok, I captured the image again, no errors this time. I can deploy it right back to the same PC no problems. This machine is on the remote network.

When I try to deploy to a different machine either on the local or remote network the image deploys successfully but there are lots of errors in the log such as....

Error in SetFileShortName for C:\......path.....Cannot create a file when that file already exisits

Can't set short name C:\.....path......because it is in use by c:\users\administrator\appdata\roaming\microsoft\protect\SID number?......

Thanks

You need to sysprep the image to use it on others.  Syspreping removes the sid and generalizes the hardware.  Also I would format the target drive instead of just over writing it.  gets rid of the crap.

it is sysprepped, sorry forgot to mention. I have 3 pre install tasks to create single partition, fortmat as ntfs and finally to create the win 7 mbr.

The image I captured only had one partition, no system partition. It turns out the PC  restored to locally boots to windows ok regardless of the errors.That's good enough for me.