This Question is Possibly Answered
1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
2,431 Views
12 Replies
Last post:
Apr 24, 2012 2:51 PM by
UnityGuy
anyone
some of the templates are finicky, and what I do is ensure that ALL restore points are removed. You can do this with converter. So you can convert it to VM, clone it, then use converter to remove the restore points, check disk (to ensure clean disk health) and defrag it, and remve the temp folder contents. Then reboot.
As Troy says you don't need to run sysprep before you convert it to template, you can... but if you don't let sysprep finish it completely, then you leave it in a weird state, which is probably is what is happening.
So reboot it 2 or 3 times just to make sure everything is out of there, convert the clone to template and try it out now.
the image of the template tries to run the vmware customization everytime it boots. It sits at the blue screen for a few seconds trying to start/run the customization and then skips it and goes to the logon screen. I hope this makes sense, otherwise i can screenshot it....
I've converted the template to a VM and rebooted it many times but the customization screen still appears but then doesn't run, and therefore keeps showing up everytime i reboot! 
I tries removing the AV aswell but that didn't help.
Do you think i should try a V2V and cleat the restore points and see if that helps?
Many Thanks
this is the screen that appears for a few seconds but then fails to run, therefore the customization doesn't work and i need to do it manually. This image then appears everytime i reboot.
Need to get rid of it somehow if possible?
Attachments:
-
custom_vm.JPG (14.5 K)
New here... Hope my post finds you all in a peaceful state of quiet IT smilingfulness and repose, with your Mountain Dew at your side, and Doritos in your mouths....
Virtual equipment and backstory: One XP Pro SP3 VM with 10GB HDD and 1GB RAM, all updates to 4/15/09-ish, and various applications and other bits. Trying to clone as a WORKGROUP machine to a WORKGROUP machine, though not as a template. Password set on the original VM and echoed in the customization process. Typical other settings, and generating new SID.
Had the same maddening reboot cycle after trying to customize during the cloning process. The clone would take root, permit a single login, then go into an endless loop of restarts. I spent quite some time Googling the problem and found several references requiring consistent versions of sysprep files on the installation ISO and the VMWare server. That all matched nicely, so it wasn't to be my answer.
I tried doing some troubleshooting and discovery on the VM itself by assigning an UBCD ISO image to its boot-up routine. This got me in the door to look into the sysprep files, .INI, etc. I was unable to find anything of value there.
Returning to Google, I found the 201388 thread here. Running with the Sophos idea, I went back into my original VM and disabled the Microsoft Forefront services..
1. Microsoft Forefront Client Security Antimalware Service
2. Microsoft Forefront Client Security State Assessment Service.
That cleared the problem up. I only needed to turn the services back on. (If you don't, you will receive mutterings from the Forefront process - "Application failed to initialize: 0x800106ba....") I did not take the time to hunt for the remaining component raising the complaint. (No extra credit today.)
Smiles. 
