Also you could try to specify some settings in your unattend.xml sysprep answer file:

<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
<DoNotCleanUpNonPresentDevices>true</DoNotCleanUpNonPresentDevices>

And what about the new way of activating Windows 8? Apparently new pc’s don’t come with a license key at the side of the case, Microsoft is pulling the OEM-key from the BIOS. How does Fog 0.33 handles this?

More information can be found here: [url]http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_install/where-do-i-find-the-windows-8-product-key-when-it/d4c5c0c1-825d-47f2-9bed-d9625c7e68ff[/url]

My guess is it has nothing to do with fog. It has to do with your unattend.xml file.
You have to double check it against some online tutorials.

Also, what you’re telling doesn’t add up:
By default the computer is running sysprep according to your unattend.xml and AFTER that fog is renaming the computer and is joining the domain. You’re telling the computer is joining the domain and after that sysprep is running?

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 great news, but i’m a little sceptic.
We’ve had many problems while running fog .0.29 and not using sysprep.
The cloned computers had the same CMID and the KMS server didn’t recognize them as individuals.
Because of that the license count didn’t reach 25, which causes the cloned computers to deactivate.

So i’m curious, what is it the fog service does exactly to change the CMID?
And since which version of fog has this been implemented?

Kevin, we’ve been running that kernel (1037) since feb 7th only for the 780’s and the problem seems to be solved!

Does your NAS support NFS?

I’m not sure, sorry… I allmost think you should create an unattend.xml for each pc with a unique licence key…

I would use one vlan for computers, one for wireless networks, one for IP phones…
Just place one dhcp server in each of the vlans?

You could also use VLANS, as a workaround?
I guess thats also something you should want to do, setting up your phones on a seperate VLAN…