Hello there,
any solutions to the problem?? I’m having the same problem now.

I took the WD harddisk from one of the GX745’s that worked, put it in the GX755 that has the issue, then reimaged with the same image, works fine; I then took the Seagate harddisk that was originally in the GX755 and put it in the GX745 and tried to reimage, and it works as well…go figure, am totally confused as to why FOG images the Seagate fine in the GX745, but not in the GX755…

Hi Mark
I have exactly the same problem and know for fact that it’s not the FOG service.
I finaly fix it by putting the password for account in registry under HKLM\software\microsoft\windows NT\current version\winlogon
I setup the key called DfaultUserPassword.

there is a program called windowsautologin.exe that does all that for you.
I also noticed that the password will be removed from registry after the number of autologon is over.

I appreciate if you tell mw what solution you found.
thanks

Please clarify. It works when you unicate upload/download, but not when you multicast?

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]