VMware Horizon Community
wingnuts1979
Contributor
Contributor

View 5.3 upgrade changed persona management roaming profiles

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

Reply
0 Kudos
8 Replies
mittim12
Immortal
Immortal

Even when you rolled back to the 5.2 parent image you continued to have problems?    The rolling back would have been my first guess as it sounds like something on the parent image has gone amiss.    Do you have the same issue if you login with a new user that has never established a persona profile before? 

Reply
0 Kudos
wingnuts1979
Contributor
Contributor

So did a lot more testing today:

Test 1:

Create a new user in AD (VDITestUser1), gave user same permissions as a regular VDI user that is having problems right now after 5.3 update. Assigned VDITestUser1 to a specific linked clone (example VDI-TEST-001) in a linked clone pool (VDI-TEST) with 5.3 agent installed. Gets a temporary profile. Event Viewer reports profile errors.

Test 2:

Create a new user in AD (VDITestUser2), gave user same permissions as a regular VDI user that is having problems right now after 5.3 update. Assigned user to a specific linked clone (VDI-TEST-002) in the same pool (VDI-TEST). Before log in i uninstall 5.3 agent and remote experience 5.3 FP1, reboot and install 5.2 agent en remote experience 5.2 FP2. User logs in and user profile in C:\Users is created without any problems.

Test 3:

Use VDITestUser2, same specific linked clone (VDI-TEST-002) in the same pool (VDI-TEST). Before log in i uninstall 5.2 agent and remote experience 5.2 FP2, reboot and install 5.3 agent and remote experience 5.3 FP1. User logs in and profile brakes on Quick Start buttons in task bar, no email signature, looks like all AppData is missing. Event Viewer reports profile errors.

Test 4:

Create a new user in AD (VDITestUser3), gave user same permissions as a regular VDI user that is having problems right now after 5.3 update. Assigned user to a specific linked clone (VDI-TEST-003) in the same pool (VDI-TEST). Before log in i uninstall 5.3 agent and remote experience 5.3 FP1, reboot and install 5.2 agent en remote experience 5.2 FP2. User logs in and user profile in C:\Users is created without any problems.

Test 5:

Use VDITestUser3, same specific linked clone (VDI-TEST-003) in the same pool (VDI-TEST). Before log in i run the new CommandsPersonaManagementWin7_01062014.txt script to prepare the linked clone for maybe new Persona Management script features. User logs in and user profile in C:\Users is working without any issues, no loss of data.


Test 6:

Use VDITestUser3, same specific linked clone (VDI-TEST-003) in the same pool (VDI-TEST). Before log in i uninstall 5.2 agent and remote experience 5.2 FP2, reboot and install 5.3 agent and remote experience 5.3 FP1. User logs in and profile brakes on Quick Start buttons in task bar, no email signature, looks like all AppData is missing. Event Viewer reports profile errors.

Test 7:

Use VDITestUser3, same specific linked clone (VDI-TEST-003) in the same pool (VDI-TEST). Before log in i uninstall 5.3 agent and remote experience 5.3 FP1, reboot and install 5.2 agent en remote experience 5.2 FP2. User logs in and user profile is working correctly again.

Now you tell me, where does this go wrong. I think it's 5.3 agent that brakes something. Right now i will test it with a production linked clone pool to roll back to 5.2 agent and remote experiece 5.2 FP2.

That still leaves me with the full vdi's (FULL VM's) that a new profile is be create (firstname.lastname.domainname) and a roll back did not recover the profile.

Thnx

Reply
0 Kudos
wingnuts1979
Contributor
Contributor

I forgot to add the following warming in Event Viewer:

pastedImage_0.png

Reply
0 Kudos
bobo23
Contributor
Contributor

Did you find a solution or the cause of the issue?  I am seeing this behavior with 1 user right now.

Reply
0 Kudos
ErikTatum10
VMware Employee
VMware Employee

Hi,

Can you please send me your case number?

Thanks,

Erik

Reply
0 Kudos
wingnuts1979
Contributor
Contributor

Hey all

VMWare finally came back to us after months of research and testing. We worked together with them on this case.

You may laugh, or you may cry, but it appears there was a bug in View 5.3 with regards to Persona folder redirection. This is going to be addressed both in View 6.0, which is coming out very soon, as well as View 5.3.2, which has an expected release of some time in July.

Invalid owner on folder permissions is the problem.It's hard to determine where in the path the invalid owner comes in, but typically we see this at the top (or root) level of the share since most of the time we don't expect permissions to be pushed down through user profiles.

Bottom line: looks like this was partially a bug-related problem but at the time you opened your ticket it had not been diagnosed yet. Our Persona guy said he didn't start working on this issue until late March. We agreed that it's perfectly fine for you to stick with 5.2 Agent for now until the 5.3.2 patch is released, assuming that is an acceptable state for your VMs to remain in for another 5-7 weeks.

CASENUMBER : 14444753502

Thnx

Reply
0 Kudos
ErikTatum10
VMware Employee
VMware Employee

I am the developer who fixed the issue.  Thank you for your patience.  Analysis is correct and there are a lot of bug fixes in 5.3.2 and 6.0 related to folder redirection, this one included.  I think you will be pleased with those changes.  Let us know if you hit any other issues.

Thanks,

Erik

Reply
0 Kudos
iamxCPx
Enthusiast
Enthusiast

Hi Eric,

I just realized that I have experienced similar issue and just opened a ticket (14509281907) and we are using 5.3.2 for about a month now.

Our AppData folder is no longer updating.

Do you mind help me out on this?

I wonder if there's a new release of 5.3.2 since a month ago with the bug fixed?

Cheers.

Reply
0 Kudos