Quantcast
Viewing all articles
Browse latest Browse all 5983

Linked Clone Pools & "forcibly disconnect users"

Maybe I am Googling the wrong words, but, can someone clarify this for me?

 

Within View there's the setting "forcibly disconnect users". Obviously this boots users off at a certain time, or when a certain time is met, regardless of whether the user is using a VM or not. I had thought this to be an odd setting, since it kicks someone off even if they're busy on the VM. However, I had heard that this is really a crucial setting specifically in a linked clone pool, as, if a user is not booted off the VM, the delta can just grow and grow and thus slow done the VM.

 

For clarification: A. is this the primary reason for the setting. And B. is there a best practice for this?

 

I'd love to get granular if it's something we should put in place. We had previously been a full clone shop but have now jumped into the linked clone world. In a perfect world I'd like to force this to happen after says 5 days of login time, or a few hours of idle time, whichever came first. Not sure that it's doable or if there's an even better alternative, but, I'd love to hear about it.

 

We're a Hospital/University shop utilizing Epic Hyperspace. I never loved the idea of a Doctor being in the middle of a chart and the VM logging him/her off, so, I'd be interested to hear what people in a similar situation are doing.

 

Thanks in advance.

Image may be NSFW.
Clik here to view.

Viewing all articles
Browse latest Browse all 5983

Trending Articles