Very good, I confirm, resolved 😉

For information, I’ve just deployed 24 computers and 2 of them need to reset encryption data (if not, invalid security token in fog.log)

Then I’m going to solve the thread. As far as I can tell, all of the sources of reports of this horrendous problem are no more occurring on current trunk.

Thank you all for your patience with this.

@midas1989 Your logs indicate this is for the legacy client. Mind posting this in a new thread?

Ok thanks

I have software to deploy software (GPO or I prefer PDQ deploy), but I don’t know the tips to remove it, I’m going to search 😉

@el-psycho the new client can only be used with the development versions of fog. This is because the new client was coded along side the development versions. And believe me there are a lot of changes to make it work. The compatibility of legacy and new clients is still present, but 1.2.0 will NOT work with the new client.

ok great, everything is ok, thanks !

Resolve in new svn, thanks

Thanks for your answer and all your job !
I’ll test this tomorrow

@Matthieu-Jacquart the bzImage file has absolutely nothing to do with how snapins, printers, or the rest of the client’s operations work

Oh, my fault, read to fast…
I’ll try this today, thanks