Nope, you do not need to upgrade them. The client they are running will work with your FOG server.

What version of the client? (legacy, or the new beta)

@ch3i said:

21/08/2015 09:34 Middleware::Communication Unknown Response: Failed to decrypt data

That tells me the server keys are incorrect (specifically the public / private key pair). Whatever you do, do not regenerate the CA key, as this will require a re installation of all clients.

@Tom-Elliott should be able to tell you how to regen the authentication key pair.

The second log you posted, did you edit it at all? Some things are happening in it that just aren’t possible with v0.9.4.

@Matthieu-Jacquart , @Wayne-Workman is correct about the new style of AD password. A brief overview of how the AD password is handled for the new client:

1. When the user enters it into the settings field, on-the-fly AES 256 is done on it using a new key each time. Granted if someone can breach your database then they would still be able to retrieve it (there is nothing we can do about that).
2. When the client requests the ad information, the server decrypts the password, and re-encrypts it along with all other data being sent using an AES key established during the client’s handshake (I won’t get into that).

As for the problem you are describing, I am baffled. It should not be possible for the beta client to do rename-joinAD out of order. Could you post the log of a client that does this? (please take the log right after it finishes renaming / ad joining).

What version did you upgrade from?

What version are you on? (Look at the cloud in the upper left). Also, did you use git or svn?

Are these 2 different images? If so what is the compression level at?

Include dashes. As for caps, that doesn’t matter but I would as windows product keys tend to be all caps.

That means the server is out of sync of the client for encryption. My recommendation is to click the “Reset Encryption Data” on the host doing this.

I know for a fact windows 8.1 does auto update. Are you sure there is not something else going on? Or perhaps it actually did update?

@ITSolutions To revert to a specific commit in git, do

git checkout COMMIT_HASH .

Do not forget the “.” on the end, it is very important.
You can find the commit hashes here:
https://github.com/FOGProject/fogproject/commits/dev-branch

https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk#Git

You must update the server. Each server is marked with a compatible version which deployed clients will upgrade to. If you upgrade your server then all deployed clients will update themselves to the compatible version.

@Psycholiquid said:

ice, with updating the client now neither computer renames but it still joins one of them to the domain. I cant tell which one though since they are both using the name from the Unattended which is only a temp

You are running 0.9.0 but 0.9.4 is the latest.

6 weeks? I threw together my golden image in 2 days… Yours was definitely more well documented and probably supported more computer models though as mine only had to work on about 5 different models ^^

I agree with @sudburr on the approach, however testing all drivers is not always needed. For example when making a golden image I just dumped a ~3 GB driver pack onto the machine and it worked perfectly on all hardware I was using. No extra configuration was needed.

SVN has just been updated with v0.9.3

Thought so. Its a bug with some debug code I had…

v0.9.3 fixes this, however SVN is not yet updated to include this version. For now can you download it from here: https://github.com/FOGProject/fog-client/releases/tag/0.9.3 and see if it fixes your issue?

Is AD disabled on this host?

Do these problems still persist in the latest rev?