Try putting in a * and windows will give it a random name, and after that fog will rename it accordingly

I know it has been a little while but I had to shelve this project temporarily. I was able to correct the issue by setting the image type to “Multiple Partition Image - Single Disk (Not resizeable)”

Thanks,

Kyle

After doing some more testing i found that i get this error on Seagate Barracuda ST3250312AS drives which have the 4k advance format (Note: there is something also called Western Digital Advanced Format and Dell Advanced Format) From my testing it seems Windows Vista or Windows 7, disk alignment is correctly forced by the OS and for windows xp you will need to create an image on for this drive type Align the disk with an alignment tool (For example the Paragon Alignment Tool, a third party product, has been used by many) then Sysprep the image. The release of 0.33 fog should resolve this when ever released. Microsoft has also developed a patch for this [URL=‘http://support.microsoft.com/kb/982018’]here http://support.microsoft.com/kb/982018 [/URL]

Yeah, the FOG log on the client (C:/fog.log by default) would probably tell you why the client was rebooting the computer. You can also check if forcerestart=1 in C:\Program Files\FOG\etc\config.ini.

Reboot options can be set several ways in the FOG manager too:

[B]Auto logoff[/B]
[LIST]
[][B]FOG Configuration > Auto Log Out[/B] or
[][B]Other Information > FOG Settings > FOG Service - Auto Log Off[/B] or
[*][B]Group Management > [I]myGroup[/I] > Service Settings[/B]
[/LIST]
Remember that “Auto logoff” reboots the client computers after it times out.

[B]Task reboot[/B]
[LIST]
[][B]FOG Configuration > Task Reboot[/B] or
[][B]Other Information > FOG Settings > FOG_SERVICE_TASKREBOOT_ENABLED > 1[/B] or
[][B]Group Management > [I]myGroup[/I] > Service Settings[/B]
[/LIST]
[B]Shutdown/Reboot[/B]
[LIST]
[][B]FOG Configuration > Green FOG[/B] (Only if no user is logged in) or
[*][B]Group Management > [I]myGroup[/I] > Service Settings[/B]
[/LIST]

That error you’re having has to do with the rights. You have to give the proper rights to the user/group fog is using to write to the image directory.

This is how I do it, but everyone is different;

[url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url]

please use the CODE tags.

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)

Look here for more info - [url]http://sanbarrow.com/phpBB2/viewtopic.php?t=1695[/url]

glad it worked out well for you. 😃

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]