Does anyone else have a better process in place?
I would like to know if I can have drivers for different workstations built in to a single image and once imaging has completed to let the workstation install the drivers that it needs. I am aware of the different MB models, CPUs, IRQs, HD, modesl etc., but I am thinking would it be possible with universal chipsets or very similar workstations to implement something like this?
I think that would be more effective and I read somewhere that it was possible, but has anyone actually done it ??

Possible solutions:

Check if the client configuration is well. IP FOG Server During the client instlallation process, you set the client to enable restart PC service? In the server configuration, you have enabled restart PC Service?

I, for one, can’t see any way that PXE or FOG could cause this situation.

Was the NIC actually working in the 2K box prior to capturing the image? Not knowing how it is used, I could imagine a situation where the NIC had been down for some time, you image it, someone notices the NIC isn’t working, and since you touched it, you own it (in their mind), even though there isn’t a way FOG or PXE couldn’t have changed things.

I might check the network cable, especially if a different cable was used for capturing the image. Or the pins on the NIC, wall jack, hub/switch/whatever else it’s connected to. I’ve seen pins pop out, get crossed, and other strangeness.

You could also try a safe-mode boot and see if that gets you anywhere as far as being able to log on. Or even an Ubuntu LiveCD. If you’re getting network connectivity there with the same cables, etc., I’d guess it is a driver issue.

Only other possibility I can think of (and this is pure speculation) is there might be a damaged bit of the hard disk where the NIC driver (or other files) live and aren’t able to be read. Perhaps the activity on the disk pushed it over the edge, but it would have failed sometime soon anyway in that case. Short of being able to log onto the 2K installation, I don’t see how you’d be able to troubleshoot this one.

You’ve demonstrated the NIC still functions, FOG doesn’t change anything on your computer when capturing an image (as I understand it), and you had no way of logging onto the computer to change anything.

Maybe my input might help here because i have had the same issues as some listed here
This is my process start to finish (Single partition NTFS only, Resizable)

I install Windows 7 from a CD, when i get to the point where i see the partitions listed i delete all partitions and click next ( At this point you do have a option to create a partition first but i dont because i have had issues before)
Once windows is installed i make sure all drivers are installed and the machine has ran Windows updates, i then install my software till i feel the machine is ready for Upload

Now at this point i have my XML file already configured and copied to the Sysprep folder
So all i do is run the FogPrep
Run the command prompt with Elevated rights and type in the following command and also assuming you are in the c:/
cd windows/system32/sysprep/
sysprep.exe /generalize /oobe /reboot /unattend:%windir%\system32\sysprep\unattend.xml “press enter”
at this point the sysprep is now running and upon reboot ( at this point you should have set the server to upload this machine) it will connect to the fog server and upload

If a machine is not sysprep’d correctly it will 90% of the time break before it even started up
[COLOR=#ff0000]“Whether I run fogprep or sysprep or neither, FOG is breaking my master boot record somewhere along the way. I created a bare bones image from a clean install, uploaded it and tried deploying it and it fails”[/COLOR]
Now Fogprep and Sysprep is totally different, so make sure when you run the Sysprep you do it with elevated rights ( it does make a difference)

Hope this helps…

[quote=“Icak_newton, post: 620, member: 249”]You can burn multiple ipxe cd’s and let the pc’s boot from them :)[/quote]
Yeah… I could. But i’m not 😉

As it turns out, I am able to use the FOG service to reboot when there is a pending task. It all works pretty well now.

[QUOTE]Because the data has been scattered around the disk and FOG needs to read all of the empty data between the real data. Defrag before uploading and this will be fixed (as long as all data can be moved to the front of the disk)[/QUOTE]
We have defragmented the PC several times and the problem is still there.

[QUOTE]A good tradesman never blames his tools.[/QUOTE]
I don’t want to blame the tool, but after working and trying for hours and days it could be a problem with the tool.

[QUOTE]Your problem looks like a failing hard drive. [/QUOTE]
I don’t think so, because it was a factory new PC and we tested it on more than that one machine. The error postet in [url]http://fogproject.org/forum/threads/fog-converts-hdd-in-raw-format.132/[/url] appears after I deleted the 100mb-Windows-Recovery/Boot-Partition. And I tried that only because the image size was wrong.

Thank you guys for the trailhead. Looks like I have some studying to do! This is probably one of those things that seems intimidating from the onset but once in the thick of it or when done, it isn’t too bad.

It’s probably not advisable to be using the domain administrator account, better to delegate local admin rights to another AD account and then use that to install software.

It uploads it via FTP, the file is not locally copied.

This is done for flexibility; The TFTP server does not need to be on the FOG server.

Please follow this guide on trouble shooting an image upload.

[url]http://fogproject.org/forum/threads/wiki-troubleshooting-an-image-upload.21/[/url]

The screenshot looks like it’s failing on the ‘ntfsresize’ command. This is where it will probably error or break.

Generally if the NTFS resize fails, there is some sort of file system issue that has to be fixed with chkdsk.

Any errors, or anything odd should be reported here.

Great to hear you got it all working.

I’m not sure if a trailing slash is meant to be there or not.

I will look into the standards and hopefully have a change for 0.33. By the sounds of it, the trailing slash should not be there.