I was wondering if anyone else has started to see this issue pop up with the new 5.50 version...
During testing of the 5.40 version in our environment, we tested encrypting a machine, reimaging it (with a ghost image), then re-encrypting it. Despite there being a KB article (#66372) that advises against this due to a chance that the new machine key may not get copied to the database if the machine name is the same (they are with our imaging system), it worked fine in our 5.40 environment. I have a laptop that was reimaged several times during testing, and each time it was re-encrypted, the old machine key was moved to "Inactive Keys" and a new machine key created successfully.
Then...I upgraded the server and our client install to 5.50 and this sequence no longer works. Oddly enough, there is a KB article (#110597) that says that the issue from #66372 has been fixed in version 5.50! Another odd thing I have found is that this sequence of events will now cause an XP machine to become unusable (you can't log into POA and you can't do a challenge/response because the new machine key never got copied to the database, which also means the data on the encrypted drive is NOT recoverable), but it works fine on a Windows 7 machine!
I already have a ticket open that's been bumped up to the engineering team, but I thought I would bring this up here to see:
1) If anyone else has run into this with the new 5.50 version
2) As a warning to others to be careful reusing machine names, even in the 5.50 version
This thread was automatically locked due to age.
