I too am having trouble to deploy images wit UEFI images. Each time I deploy the computer boots into recovery.

If the machine was in the domain before you reimaged, then you’ll need to reset the computer account or delete the computer account before you can add it back as the same name.

If you have computers in specific OU’s, then you can just reset the computer accounts and the domain adds should work.

Awesome! Thanks for posting. I’ll take a look at it as soon as I get a chance.

Honestly, the reason I’m interested in it is - just because. Haha. The extra reboot certainly isn’t the end of the world. I would technically save a bit of time, but it’s more an excuse for me to learn more about how FOG works, and how PHP works, so I’m just playing with it when I have extra time (which isn’t very often). I don’t actually use snapins to deploy software - I have a lot of VBS that pulls info from active directory and deploys software from a networked drive based on that information.

Lee, I actually have been working on your post – I don’t have it in production yet, but I still have to fiddle around with buildroot. Although, I’m not sure I’ll need to - I think sed is actually included in whatever build of init.gz I have.

Sysprep is working fine. I made another image and this time around it worked. Not sure what changed.

Now I’m trying to make a new base image and FOG will not allow me to upload it, but that’s another thread…

You might try some of the newest kernels from this post.
[URL=‘http://fogproject.org/forum/threads/dell-2330-all-in-one-network-issue.1054/’]http://fogproject.org/forum/threads/dell-2330-all-in-one-network-issue.1054/htt[/URL]

if you map a network drive under audit mode it will be part of the default profile aslong as you specify in your unattend.xml to copyprofile. Every profile change you make will be captured in audit mode, i think the idea of audit mode is so that nothing machine specific is copied over which and makes it easier to handle licensing and to skip oobe and have un-needed personalisation.

Did you PXE boot it?

I believe I figured out the problem. FOG uploads the script <FOG install dir>/tmp/ since I used the default path, <FOG install dir> equates to \program files\fog, assuming that FOG sends the full path to the executing command, there will be a space in the script name, which would cause (powershell at least) it to croak. I uninstalled and reinstalled into \FOG and that seems to have fixed my issue…

With the help of Michael’s thread here

[url]http://fogproject.org/forum/threads/solved-task-is-complete-within-seconds-problem-with-gpt-mbr.1172/[/url]

I finally was able to solve my problem. In my case it seems as if the GUID partition table and the MBR were confusing each other, so the Linux-FOG-Kernel couldn’t find any partitions.

Here is what I did:

[B]Please note:[/B]
Since my computer was just a testing machine to create an image I did not backup anything before doing this. As recommended on the Fixparts webpage you should certainly do a backup (of MBR, system and data, or in other words everything ;-), if you’re going to do the following steps on an important machine/system.

Download Fixparts for Windows from here:

[url]http://www.rodsbooks.com/fixparts/[/url] (look for the link “download page”)

Unzip the file and execute it with administration privileges. A command window will now pop up.

Type in “0:” (this command is just for Windows!) to define your first (and in my case only) HDD to be the one to analyse.

Now the tool suggests to delete the GPT signatures and asks you to confirm. If you want to use Linux as well as Windows on your disk you probably should not delete those signatures. But in my case I only want to use Windows, so I say yes.

After that exit the tool by typing “w” (write changes to disk and quit). Restart your computer to check if it still works.

Sysprep the OS and upload the image to FOG.

I used the custom kernel written by yogipaolo, found here:
[url]http://fogproject.org/forum/threads/lenovo-x130e.587/#post-2813[/url]

Works like a charm - booting the kernal seems to take a while but otherwise perfect.

Having the same issue here as well. I will keep you posted. Thanks!

Little late to the party, but I am also seeing this type of issue on our main Windows XP image. After sysprep is done, fog services will not fire. Fog.log shows the following:

[CODE]
8/8/2012 9:40 AM FOG::GreenFog Starting green fog…
8/8/2012 9:40 AM FOG::GreenFog Attempting to connect to fog server…
8/8/2012 9:41 AM N/A Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
8/8/2012 9:41 AM FOG::SnapinClient Sleeping for 497 seconds.
8/8/2012 9:41 AM N/A Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
8/8/2012 9:41 AM N/A Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
8/8/2012 9:41 AM FOG::AutoLogOut Unable to continue, MAC is null!
8/8/2012 9:41 AM FOG::UserTracker Unable to determine MAC address, exiting…
8/8/2012 9:41 AM FOG::TaskReboot Attempting to connect to fog server…
8/8/2012 9:41 AM N/A Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
8/8/2012 9:41 AM FOG::HostnameChanger Host name was not found in the database.
[/CODE]

A temporary solution I have is to tell sysprep to run the net stop “Fog Service” and net start “Fog Service” commands on first login after the imaging is done, but this still fails when trying to join the domain. So my current solution would be to add a batch script that runs any time the computer logs in to restart the service.

Worked like a charm!

Thanks!

You got this right on target !! Thanks a lot !

Now my server is working I was able to upload and deploy images. I have my images in XP.
Now I have to try doing my Windows 7 Image. Hope not to face any issues.
Again, thanks you so much for the help ! Cheers !

Hmmm, interesting. I haven’t had any problems using a single resizable partition. I wonder if that’s because all of our machines still have the 100mb partition still in place when they are imaged, and perhaps the image just replaces the OS partition instead of the system reserved.

Our machines are all typically the Dell Latitude series (couple of Precisions, but they work too), and the master image came from a modified e6510 build (it’s been converted to a VM, since).

Thank you very much for this! Now with this being said…is there anyway to enact this with Group Policy to all clients? Let me know. Thanks a bunch!

I have to ask, why would you want to go to XP? Application compatibility?

astrouga