Perpetual loop of Windows after image is deployed

[Migration User]

Hello, I am deploying images to a group of Dell Optiplex machines which includes models: SX280, 745, 755, 760, and 780. I have taken an image of an Optiplex 780 and have deployed it correctly to all models except the SX280. For whatever reason, after Configuration completes successfully in the deploy process and just before it begins the task “To target operating system”, the SX280 enters a perpetual loop. The system enters Windows and logs in, but before it is able to load the Windows desktop the machine reboots. This process continues into the loop which, up until now, I’ve only been able to remedy through formatting. And even after formatting, I try to deploy an image the same machine (or the same model, different machine) to no avail. I’ve even tried creating a new Optiplex 780 image to deploy, but that only yields the same result. My next step is to try creating an image of a SX280 and deploying it to my farm of computers to see what effects that delivers. It would be interesting to see if a SX280 image sends a 780 into a loop. Though with Ghost’s DeployAnywhere utility, would hardware differences even matter regarding the image? Any thoughts on what may be the problem would be greatly appreciated. >>Korey

[Edward Tippelt]

I have seen this sort of behaviour before, where a machine keeps rebooting, and if I recall correctly, it was due to an incorrect driver for the mass storage device. If you have IDE compatibility mode on the SX280, try enabling that instead of using AHCI and see if it makes any difference.

[Migration User]

I agree with EdT, Please change the mode to IDE and this will definitely solve the issue.

[Migration User]

Hello,

First off, thanks for the help.

While the problem exists on the machine, I changed the drive settings in the BIOS to IDE, but it still didn't alleviate the situation. I will try formatting the machine then deploy an image again to remove any question regarding the state of the HDD in the BIOS.

>>Korey

[Edward Tippelt]

Is the problem occurring when you try and deploy your image to a factory built DELL that has their original operating system on it?
If so, then I suspect a reformat of any new machine before imaging to remove existing partition structures would always be a good move.
Manufacturers use all sorts of different structures to support system recovery and maintenance partitions and these can also play havoc with a deployed image that assumes it is in a specific partition, eg the first on the drive.
You don't mention which O/S you are deploying, is it XP?  If so, does the boot.ini reference information match the hard disk partition structure on the target machine?

[Migration User]

EdT,

Sorry about not mentioning the OS. Yes, we are using XP Pro SP3. And we make it a point to reformat every Dell machine we get in. The image I am deploying was made with a clean install of XP along with whatever miscellaneous programs we use at my company. And yes, the boot.ini is referencing the hard disk partition structure.

I just finished reimaging the SX280 with the updated HDD BIOS settings, but the problem is still there. No changes to the problem either; it's the same scenario as described in my original post.

Could the problem be with the DeployAnywhere storage drivers? Maybe the utility cannot find the appropriate drivers for the SX280, so it installs a driver it believes would work which causes it to fail? Could installing the appropriate storage driver in the utility remedy my situation?

I have yet to alter any driver settings in the DeployAnywhere utility, so I will wait for a response on the subject from people who know better than I before I go ahead with any actions.

>>K

[Edward Tippelt]

If you boot a working image on an SX280 and then check the PNP ID for the storage device (SATA chipset I would most likely expect here),
This gives you a reference point to work from.
After that, once you have imaged a machine that keeps rebooting, boot WinPE or mount the hard disk as a slave in another machine, then trawl through the c:\windows\inf folder searching the INF files for a matching PNP ID.
The inf file will give you a list of driver files required by the hardware, so you can then look for them on the hard disk, and compare them with a freshly downloaded DELL driver for the hard disk chipset on the SX280, and see if the files are different.
You could also try replacing the INF with the one from the downloaded drivers, and also replace the driver files, and try booting again. This does not always work as there may also be difference in the registry requirements, but if it now does boot, you at least know that the drivers for the SATA chipset need adding to DeployAnywhere.

[Migration User]

EdT,

Thanks for the suggestions. I'll try them out, see what I come up with, and report back later with any info I get.

>>K