Correct, upgrade to 3738 (or higher), and then download the new client from your server.

There is nothing we can do about it; the legacy client is depreciated (It hasn’t been worked on for quite a few years, minus my product key addition way back when). If you upgrade to SVN you can try out the new client and see if the problem is fixed.

See https://forums.fogproject.org/topic/5243/kernel-panic-with-svn-3553-and-virtual-esxi-image

This is server 2012, meaning esxi treats it like windows 8. You will need to use the 3.0.1 kernel.

Legacy or beta client?

Fixed in v0.9.1.

Confirmed joining AD fails. I will work on this tonight and release a patch ASAP.

Just confirmed that hostname changing works as intended. It may be an issue with AD joining in combination with hostname changing though. Can I teamviewer into a machine having this issue (PM me if you are willing)?

If you manually reboot the computer does is the named changed?

I’ll look into it later, its an issue with volatile registry keys… not fun at all.

Ew…

Yes they can. I made sure v0.9.0 could still auto upgrade itself. Simply upgrade your server and all deployed clients will be auto upgrade to v0.9.0

If you can, the beta client. Try and break that thing (I just released v0.9.0 and I think its about ready for an official v1.0 release).

Tom means that this problem is now fixed in 3685. Update your svn copy and upgrade the server.

It does nothing. It was a plugin needed to make FOG 1.3.0 compatible with the new client, but we removed the need for it.

I just finished talking with Tom and we may have found a fringe case that would cause the issue you are seeing. As for why it happens ever 5 re-images we have no idea, but we are hoping its caused by this fringe case. Tom will push out a patch when he has time.

Its an issue with the beta client which is fixed in my v0.9.0 nightly builds.

Can you give me the log files from each of the 5 re-images (that is log file from post-image #1, #2, …)?

On the machine, open up task Schedular and manually create a folder “FOG” and see if that helps.

Thanks for the notification Wayne. @Psycholiquid I will attempt to reproduce this issue in my vms. Is there anything special you are doing to the image? E.G. sysprepping?