John Twilley Posted July 3 Share Posted July 3 I'm looking for clarification on KB 1000590 --> The View virtual machine is not accessible and the View Administration console shows the virtual machine status as Already Used (1000590) (omnissa.com) We are having random issues where a user cannot connect to a non-persistent desktop. When investigated, the desktop state is "already used". The pool is already set with the pae-DirtyVMPolicy=2: Automatically refresh virtual machines. The KB mentions adding some timeout values that I'd never seen published before. cs-suspendpolltimeout=90000 and cs-suspendpolltime=1000 Has anyone added these values before? This does not happen very often, but when it does, it involves the Clinical worker calling the Support Desk to delete the VM and causes disruption. I'd like the VM to just automatically delete as per the DirtyVMPolicy. Quote Link to comment Share on other sites More sharing options...
Gerard Strouth Posted July 9 Share Posted July 9 I have not added anything other than pae-DirtyVMPolicy=2 Quote Link to comment Share on other sites More sharing options...
John Twilley Posted July 12 Author Share Posted July 12 That's all I ever add as well. That's why that KB article confused me, as I'd never heard of adding Polling timeouts. And I cannot find ANY other mention of those polling values anywhere on the Internet. Quote Link to comment Share on other sites More sharing options...
John Twilley Posted July 16 Author Share Posted July 16 I'll open a Support ticket and share my findings. Quote Link to comment Share on other sites More sharing options...
jr1983 Posted Thursday at 09:35 PM Share Posted Thursday at 09:35 PM Hi John or anyone else, Did you ever get any response on this issue from the support. Our users have been encountering this a lot recently and the pae-DirtyVMPolicy=2 doesn't appear to help. From what I'm reading the here https://kb.omnissa.com/s/article/1000590 the DirtyVM policy will only apply to Refresh On Logoff "The pae-DirtyVMPolicy values provide these options for the Refresh on logoff policy:" but I am using Instant Clones and here https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-virtual-desktops/GUID-0359DB4C-4517-4535-8EBC-BD4F27C764F3.html it states that "For instant-clone desktops, the machine is always deleted and recreated after logoff." So it wouldnt, or atleast doesnt appear to apply. What I can see is that the "Already Used" are disappearing from the Problem Center VMs section but the actual end user effect/issue is still occurring. The users are unable to relog on to a session that is still leased to them. Thanks Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.