Hi,
I am wondering if anyone is using the App Volumes UIA+Profile template with UEM and if there is any benefit in doing so?
To achieve faster logon times is it better to just use UEM in conjunction with mandatory profiles?
What is considered the best current practice for profile management when focusing on fast logon times with non-persistent, linked clones?
Thanks,
Norm
We will be using UEM with Writable UIA+profile but just for 2 reasons.
1. We would like users to have their settings on both VDI and their physical machines if they switch.
2. If you have administrators on VDI with a writable volume they tend to get corrupt from time to time. I think that we need to reset about 1 or 2 writables per week from the more than 2000 we have so it depends on how much of an issue you believe this is.
And the best solution is what you want to achieve. The biggest downside to UEM (or any profile management tool) in comparison to the writable is that all info needs to be copied from a network share to the VDI. With smaller applications that's not an issue, with larger applciations (like Chrome addons or FireFox addons or people with very large background pictures) it could take a while to start up the application. Biggest downside to writable is that it is a catch all principle, which off course also is it's biggest plus. It catches all changes made by the user.
Do keep in mind that every action you execute during logon will extend logontime. Adding UEM into the equation will add a fews seconds to logon times. Adding writables will also add a few seconds onto logon time. I would not suggest creating a new profile every time a user logs in, that the slowest method. If you are going that route just make a mandatory profile.
We use UEM + Writable (UIA+profile) ONLY because that is the only method I've found that will capture Outlook Search Indexing.
However this is NOT the desired method as I would like to use UEM and Writable (UIA) only.
