Just as the title says, it gets through the process perfectly but stops at Restarting the System.

Didn’t encrypt my password finally got that figured out. Nevermind.

So after a lot of trouble getting a non-syspreped image to work, I ran into this issue changing hostnames and joining a domain.

Specifically I get this in the log.

[CODE] 11/15/2012 6:01 PM FOG::HostnameChanger Attempting to connect to fog server…
11/15/2012 6:01 PM FOG::HostnameChanger Module is active…
11/15/2012 6:01 PM FOG::HostnameChanger AD mode requested, confirming settings.
11/15/2012 6:01 PM FOG::HostnameChanger Additional non-parsable characters are at the end of the string.
11/15/2012 6:01 PM FOG::HostnameChanger at System.ParseNumbers.StringToInt(String s, Int32 radix, Int32 flags, Int32* currPos)
at System.Convert.ToByte(String value, Int32 fromBase)
at FOG.FOGCrypt.hexToByte(String hex)
at FOG.FOGCrypt.decryptHex(String hex)
at FOG.HostNameChanger.changeHostName()[/CODE]

Any ideas?

Alright, I finally managed to get it working using just fogprep and mutli-partition non-resizable. I suppose that will have to do.

Yes, I’ve tried non-VM as well, running Fog on 12.04 desktop 32-bit(supported 12.10 is not, had troubles with that aplenty.)

I don’t have anybody who will be using XP so even if that worked it would get me nowhere. I’ve tried both partitioning styles with and without 100mb partition(see first post.)

Thanks by the way for all of your help so far.

I’m doing sysprep /OOBE and /generalize, with no fanciness in the image itself, clean installation.

I did the startup repair from the windows disk to fix the MBR when it said no boot device found, I was never able to get the missing bootsector one resolved. Both of these are post-BIOS, pre-boot. I never get a W7 logo unless I manage to fix the MBR. I have a WDS server, and can capture and install with it just fine.

I really don’t know how to describe it further, it seems to me to be the simplest of setups because I’m just trying to get anything at all to work at this point. Even re-installed Ubuntu, FOG, and the Windows client from scratch, including building a custom FOG kernel to capture the VMWare SCSI drive. Maybe I should try a Linux image and see how far that gets…

I’ve monitored it to completion and it does create the NTFS partition just fine. This is a fresh install of Windows, so no other utility-esque partitions to be concerned with. If I fix the MBR or bootsector, Windows boots fine, but I can’t do this remotely of course.

I’m trying to image onto Optiplex 755s (at the moment), if it makes a difference.
My setup is pretty basic as far as the FOG-server and clients go, just a shop test at the moment. I plan to use FOG in school-lab environments.

The imaging process appears(from my little experience with FOG) to go fine. It seems the image itself is the problem.

Is there any way to run a diagnostic of some sort on the image file?

I’ve tried 3 images, before and after sysprep and a vm-image, so I doubt that its a corrupt image issue.
And they had chkdsk run before-hand.

Tried installing to 2 separate machines that had previously run Windows 7 just fine.

After imaging the BIOS says "No boot device found(bad MBR right?), or after the VM-image it said no Operating System found(bad bootsector right?).

Hi guys, I’ve been trying relentlessly just to get an image of Windows 7 to deploy.

I’ve tried single and multi-partition styles, before and after sysprep, vmware and hardware, with and without the 100mb partition.

The problem is after any deploy, either the mbr or partition’s bootsector is corrupt or wrong, and the machine won’t boot!

I’ve followed tutorials and the user guides on the wiki to no avail, any ideas?