I ran into this issue as well, but it's no longer an issue with version 5.3. We removed the options to shutdown or restart the desktops, that seemed to cause the issue, instead we made the user use the log off button. See this: Solution for "Already Used" state
Thank you! I will test with having the users just log off and see if it helps. Is there somewhere to remove the options for Shutdown and Restart? I think I remember seeing it somewhere but can't think of where.
We use group policy: User Config > Policies > Admin Templates > Start Menu and Taskbar > Change Start Menu Power button and Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands
Great! Thank you!
Sounds timing related - 5.1.3 subscribes to an additional notification from Windows to be sure that logoff has fully completed before passing the ENDED notification back to the broker, as in 5.1.0 it was found that a long profile sync could sometimes be interrupted if we start the shutdown process too early. As nzorn says, if that's the case then not allowing users to shutdown but instead only logoff may help alleviate the issue.
I'm interested in the below statement in your original post, could you clarify what the exact reason is? There shouldn't really be any reason to not move to the latest 5.x View release even if you keep the same vSphere version for hosting the VMs.
"We cannot upgrade higher than 5.1.3 because our storage won't support it at this time. Anyone have any ideas?"
I set the group policy for one of my pooled users to test the log off suggestion. And so far (only a day) the machines haven't gone into the already used state except for one. In this particular pool, I have a max number of 8 desktops, 3 always powered on, and 5 provisioned. So when one user signs on a machine another attempts to become available. That machine that was supposed to come out of the provisioned state to the available state is what went directly into an already used state.
So the log off only option may help for the users signing off and the machine refreshing better but this creates another situation where the machine gets stuck. You can see the event information of the machine in the attached image. I can make all of the machines available instead of powered off I suppose.
But to answer your question I was told that we had to stay on the same level of View as vSphere. Thank you for questioning it because now I see we should be fine going 5.3
I have encountered this in the past and was able to resolve it by adjusting a few key configuration settings in the ADAM database. VMware now has a KB Article (1000590) outlining almost these changes:
Hopefully this will be useful for your situation.-=Alex
Alex St. Amand | Principal Solutions Architect, VCP
Data Intensity, LLC. | 22 Crosby Drive, Bedford, MA 01730
My only solution was "Remove" the VM from the pool, nothing else "Reset, Recompose, Log off/Disconnect session" worked for me!