I had to try assign a desktop to a user, but View shows error that the desktop is assigned to a user and user has a desktop on the pool,
But I couldn't find his virtual machine by searching his username,
When I checked events, I saw, the virtual machine was assigned to the user and assigned automatically to another user (This wasn't in events).
Details is same as this example:
User A and user B have two different desktops, C and D, after moments, C and D assigned to A and View server saying B has desktop on the pool, but B can't logon.
What was happened?
It's second time that this problem happened on my connection server.
It sounds like you have automatic assignment enabled for the pool so when a user logs in to a desktop they get assigned a desktop that hasn't been given to someone else yet. I assume you have multiple connection servers replicating their ADAM databases which means there is a slight delay for all of the servers to register manual changes you make. What could happen in this case is that while you are making a manual assignment on one connection server a user is authenticating to a different connection server and grabbing the desktop you are assigning. Then basically the ADAM databases try to figure it out with some odd results occasionally.
My suggestion would be to use either manual assignment or automatic assignment but never both to avoid this problem. I tend to use automatic assignment if all the machines are basically the same (i.e. Linked Clones) before the users start customizing them and manual assignment if the pool consists of different builds logically organized into a pool. Hope that helps.
Thank you Eric, but "Auto Assignment" is disabled on my pools.
Anyway, if you know another way that I can check my View LDAP database, please share with me.