Hi All, we are trying to isolate cloned Win7SP1 machines stuck in a reboot loop after running sysprep and cloning the hard drive. The last thing done before Win7SP1 sysprep was to install Avast 6 on the Win7SP1 patched master workstation in question. The cloned images/workstations are all stuck in a reboot loop (tried cloning with both CloneZilla and also DriveSnapShot). Logs suggest that in the past before SP1 was around that a an over-sized registry key (http://support.microsoft.com/kb/981542/) or Avira or Kaspersky were the issue (http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/f7e1a2ce-f797-4e34-ae47-529926186275). I am wondering if anyone has applied the following sysprep command to a Win7Sp1 workstation with Avast 6 installed :-
C:\Windows\system32\sysprep\sysprep.exe /generalize /oobe /shutdown
In a simple cloning scenario this is the most common way to prepare a hard drive ready for multiple machine cloning for deployment on a domain (in a VERY simple form)
Regards
Hyp
*** EDIT ***
ok, more to this… the clones all being stuck in a reboot loop - we tried various ideas…
-
Last Known Good fails - no surprise
-
Enter safe mode using F8 - system gives “you cannot start safe mode while in setup” - THEN BOOTS and Completes Sysprep OK… including SID - checked with PSGETSID…
I have no idea why, but Safe Mode got us out of trouble… all clones now booting… goto safe mode once - get an error, reboot, solved.
I would still be interested if this might in any way be related to AVAST v6
Hyp