prime_id2
Enthusiast
Enthusiast

New View session does not login to View desktop with AD credentials

Hi,

We are experiencing a problem that we can't find any answer for yet.

We have View 5.3.1 with Windows 8.1 x64 Update 1 on a floating linked clone pool.

When the users log off the desktop, the desktop is deleted immediately as configured in the pool configuration.

We use Windows roaming profiles, since View 5.3.1 doesn't support Persona management on Windows 8.1.

When a standard AD user connects to View with View Windows client, they normally just log on and nothing is wrong.

But in scenarios when the user needs to rapidly log off and on again we are experiencing two issues.

1. When the user try to log on to after just logged off from another session/desktop we get this message:

viewagentreports.JPG

Is it possibly to avoid this message and confuse users?

2. After the users waits approx 2 minutes, he/she can log on again, but sometimes View doesnt log on the user to the new desktop assigned to the user. Instead the user get the standard local administrator user and wants you to type the password for this account.

We have also disabled restart and shutdown buttons in Windows by GPO, but these functions are available when this happens. This is because the users doesnt get policies from a GPO in the user OU. It seems that View try log on the user with local administrator account instead of the normal AD user.

Is this something with the roaming profile not synced properly in the logoff procedure ?

Please help:)

Reply
0 Kudos
mittim12
Immortal
Immortal

1:  As you noted this is strictly a timing issue.   The desktop is probably logging off, syncing profile, and then going through the process of deleting.   Perhaps these all processes that need to be complete before the user's session is lifted and they can get a new desktop.

2:   Did you note if maybe they are getting connected into the same desktop that was rebuilt?

Reply
0 Kudos
bbmark
Enthusiast
Enthusiast

Try ping from the client to VM or connection server, and check if the latency is poor.

Reply
0 Kudos
prime_id2
Enthusiast
Enthusiast

The latency is not poor and if its a timing issue then I think this solution will have been doomed. Because latency in original timing when testing will change drastically in working hours etc.

Anyone who have implemented this kind of solution before and experienced the same issues?

Can this be fixed in someway by "locking" the user profile until its finished synchronizing on log off and not allow new connections until it has finished?

Also we see that the desktop the user logged off is deleted after log off and the user get assigned a new computer, but this computer doesn't "forward" the user credentials and automatically log in to the new desktop.

Or will this work better with persona management? anyone?:smileyconfused:

Reply
0 Kudos
Rorus
Enthusiast
Enthusiast

For 1: Can you post a screenshot of that pool's config, and perhaps the log? It sounds like it is trying to give that user the same VM (as if it were a dedicated pool instead of a floating).

For 2: Do you do any GINA chaining software? I've found previously that products that alter the default GINA can affect VMware View's ability to perform SSO.

Reply
0 Kudos