Answer here: [url]http://fogproject.org/forum/threads/support-for-efi-gpt-systems.150/#post-2086[/url]

I’d rather not- it contains a lot of things like server names, ip addresses etc that relate to my organisation and it would take me ages to strip them all out. Sorry.

What I’ve already posted should be plenty to go on- it contains all the relevant information. You can see that in my configuration, the extendospartition happens during the ‘specialize’ pass, but from what I understand it can be run in some of the other passes too if for some reason that suited you better.

The technet link I posted mentions the component that contains the setting in Windows System Image Manager, which allows you to add the extendosparition to your unattend.xml

Found out how to have the partition extended to cover the whole disk via this thread:

[url]http://fogproject.org/forum/threads/resizing-partition-with-windows-7-image.250/[/url]

This is the guide I use to sysprep and it has served me very well.

[url]http://brianleejackson.com/sysprep-a-windows-7-machine-–-start-to-finish-v2[/url]

My thought would be that because the hardware is not exactly the same the image would push fine but the NIC drivers are not exactly the same so when you do login as administrator then Windows updates the new driver (which i would assume at this point it has it built it) and upon reboot it now has networking capabitlity…
Thats just my thought 🙂

[quote=“David, post: 1293, member: 495”]I have a minor problem. I can get fog to join computers to AD in an OU if they do not exist in that OU; however, if they exist in that OU, it gives me this error ( Error 2224 )

Once, I delete the computer from the OU in AD, and restart the fog service, it joins AD again and the OU just fine. I also noticed, that if I don’t assign an OU, I do not have this problem, it will join the domain again after a reimage…even if it is already in AD.

Has anyone else ran into this.[/quote]

i went through that when i first started using fog to join my computers…but i learned to delete or un-join my computers before re-fogging them

No problem.

I’ll also point you to the updated version of oemscan which is just about perfect in my opinion - [url]http://siginetsoftware.com/forum/showthread.php?541-OEMSCAN_ADDON_MULTIOEM-v1.8[/url]

I’ve worked on that project with mr. Smartiepants to some degree testing it out. It works great as a batch script or an SFX package.

Good luck, and if you need more help let us know.

And permissions? have 192.168.2.5:/media/FOG-Images 777 permissions? The error is “Permission denied”.

David, that process does work but I beleive the folder name is just Default and its a hidden folder as well. Also if you need to lock down some settings abit more you can always run “gpedit.msc” on each computer but this would be fairly time consuming. In Windows 7 you can also set up a network printer IP as a local printer and it will be available to all users on that computer (much easier than copying to default user profile the XP way).

Hi there Russell, if you were talking to me then I’ve figured out my problem, it was related to a badly written program that changes the startup sound for windows 7. I never should have put in it was only for a laugh, and was meant to take it out. I figured it out by rebuilding the image one things at a time, process of elimination. I got it on the 3rd or 4th time as I had a feeling it was the culprit.

Try one of the newer kernel’s. I think the older kernels don’t support the change right after imaging.

enjoy! and here i just got to work …

Or you could just try and set the Scopes on the machine itself and see if it works ? i know i have tried this before but "upper leve: setting took preference … but hey its worth a try 🙂

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.