you do not need to specify the Reseal in your xml file as that’s what the switches do - by having this in your unattend file it conflicts with the switches you pass to sysprep. just remove this section all together from your unattend file and it should stop the issue.

Cloud windows 8 is more functional than a disk management software like partition magic: [url]http://www.partition-magic.org/[/url]

[quote=“danuel, post: 9573, member: 628”][url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url][/quote]

danuel, that guide is where I got some of the information but it is an incomplete guide. Also There is the SAD2 part which bloats the install to way to big a size for storing and transferring over a WAN or even a LAN at some points. That is why I wrote this one.

Something perhaps to do with fixed lease addresses and corresponding DNS entries on the windows side perhaps? Just a thought.

After restarting FOG service, it worked…
No more information in the log… I don’t know why it needed a restart of the service while it did not work this night.

That is a ridiculously simple and awesome solution, thanks!

the default username is set under WindowsNT/Winlogon in the registry, for more info just google display last user registry (make sure your GPO doesn’t disable this)

OK…thanks…everything appears to be clean and working as expected!

A backup recovery software can help solve more questions, so you need to have one like: [url]http://www.partition-magic.org[/url]

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…