Hey everyone
Last Tuesday evening we upgraded the view composer server, view security servers and view connection servers to 5.3.
Then last Wednesday we upgraded the VCenter server for our view environment to version 5.5.
The hosts were upgraded on Thursday to version 5.5.
Over the weekend we recomposed our linked clone pools to view agent 5.3, remote experience 5.3 feature pack 1, new hardware version and new vmtools.
We tested this big time before we released the vdi updates, no issues.
Today users started to log in to view and came back with the following error:
Windows could not load your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you log off. Windows could not load your profile because a server copy of the profile folder already exists that does not have the correct security. Either the current user or the Administrators group must be the owner of the folder.
In case of our linked clone users a temp folder is created on the vdi's.
Our full vdi users (full vm's) are getting a second profile. Before the upgrade the profile name was firstname.lastname. Now they are getting firstname.lastname.domainname. This happens as well on our file servers where the profiles are stored.
Persona Management was working for before the update. We did not touch our file servers during the upgrade or changed permissions.
We tried to roll back for a few users to view agent 5.2 and remote experience 5.2 feature pack 2 but probably the damage was already done.
Any ideas where to look? I opened a case with VMWare but so far no answers.
Let me know.
Thnx