Well a mac address is individualistic, meaning it is unique to the board… this is why Fog uses it for tracking and cataloging.
We use the DMI info and register our computer names based off of the serial number, as well as name them in AD based off the serial #.
Most deployment solutions use the mac address, and truth-be-told I still think that this is the best way. Acronis / Altiris / etc. all use Mac addresses as the single unified primary method of identification. >_<
I really don’t know of a way around what you are trying to do, other than what you’ve already listed above.
You can’t install XP over PXE in the traditional sense of booting off the .iso This is due to the way memdisk / ramdisk.sys and the legacy microsoft product’s don’t play nice with each other. Same can be said for BartPE and memdisk (based off of server 2003). You can’t PXE boot bartpe either (without some crazy fan-gangling)
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
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
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).