I am working on a Omnissa Horizon project. The cu...
# _general
t
I am working on a Omnissa Horizon project. The customer has nothing but persistent desktops. This is the first customer I've worked with that went all persistent.
e
Interesting. Was it a conscious choice due to some idiosyncracy or constraint/requirement?
t
I think it boiled down to administrative experience.
👍 1
s
I have a mix of persistent and nonpersistent CVAD desktops. Persistent tends to be our higher end users who need a custom app, or tools, etc. Not just "because" :)
💯 1
t
This particular customer went only persistent desktop. I haven't work with persistent desktops as a standard deployment since the VMware View 4.6 days.
👍 1
e
admin (in)experience was gonna be my next guess, though there are some use cases that make sense for persistent desktops (though rarely for the entire organization)
t
It's very interesting for sure. I got nostalgic for a moment when I saw all of the persistent desktops.
🤘 1
r
i once had a customer that was treating linked clones as if they were persistent desktops, that was fun.
r
I learned that in the US they do more persistent than non-persistent.. I was baffled when I first heard that, why would you do that.
now I'm used to it but still think non-persistent is the way to go for any desktop.. they should be disposable, created on the fly, context aware, tuned to the employee..
s
@Rob Beekmans in my case (which is a mix of persistent and non) we have groups that require specific apps and/or drivers (foot pedals for dictation, sessions that need to run for days because of a report they are running) that having it refresh each reboot caused problems. So we created pools of persistent and manage them with ConfigMgr as any other desktop. I also have people doing accounting/billing tasks that nonpersistent is perfect for as we do not want anything stored. It's not solely one solution or another.... it's a mix. Maybe the person in question had lack of experience... but that doesn't mean there isn't a good use case for persistent.
r
yeah that sounds like a good use case, those I would 100% do with persistent desktop.. In the change we see towards UEM managing persistent desktops as well, my resistance is going away.. my main issue was always management, I don't see SCCM as a proper tool to manage anything virtual, not designed for it and not flexible enough. with UEM taking over that role, now we are talking.
s
I have not had any issues with ConfigMgr\SCCM to persistent desktops. Or at least not any more than physical desktops lol :)
😂 1