In a previous post, I gave an overview of what the product could do and why you would benefit from using it.
One of my colleague and good blogger, Chris Halstead, wrote a good post on how to set this up. Check it out here.
Now, on the second part of the series, I wanted to go over actual use cases for the solution.
I recorded a few quick videos on setup and configuration, you can find them on YouTube:
– The first video is the technical overview of the solution.
Then, I go in a 6 part series where I cover different aspect of the solution.
Part 1 goes into setting the back-end file shares required for the configuration files for UEM and the User directories where user configuration are kept. You will see that this solution is extremely simple to install and configure. I did not go into granular security permissions but if you need to do this, you can find the information in the UEM documentation, now online, here.
Part 2 goes into how you can personalize the environment from an application perspective. The good thing about the solution is that the administrator can predefine settings for his users, in a lot of cases, the organization will want to have fix settings for applications and make sure that users don’t modify those settings. But, in other cases, the administrator will setup initial settings and let the user customize to his/her look and feel. The solution enables you the flexibility to do both. In more advance scenarios, you might even want to have some fix settings (like the language) but other would be up to the users. You can even have 1 single application settings but multiple configurations for it, for example, have specific conditions when users are part of a certain Active Directory group, set it one way but if they are part of another AD group, set it a different way.
Part 3 covers how different application can have different configuration and how specific triggers happen when those applications execute. For example, when Adobe Reader opens, a user might require access to a specific network drive or a specific printer, well, why not make these resources available when the application actually opens. Why would we need to map those resources at user login? Doing this at login, slows down the login process and the user actually doesn’t need those resources until he actually uses those applications. Adobe Reader is just a small example but you might do the same for other apps, like Microsoft Word or Powerpoint. You might also have different triggers depending where you are actually located (physical IP). This way, when you open Word from the office, you would get a specific set of printers mapped to you but when you open Word from home, you might get a different set of resources.
Part 4 goes into settings related to the users. This is a pretty straightforward one and some of those settings can be done from the Microsoft GPMC but the UEM solution gives you more choices and more ways to actually configure those settings for the users. The conditions which you can set in the UEM console are, from my perspective, what makes this solution very unique from the others.
Part 5 covers Application setting migrations. How you can go from a specific version of Office for example and retain all your settings when upgrading to a newer version. Going from Office 2010 to 2013 and keeping all the user settings. This, of course, can be done for any application migrations, it’s up to the administrator to configure the proper targets in the environment.
Finally, Part 6 covers the dynamic desktop configuration and how the different triggered tasks change the desktop look and feel. Adding shortcuts, mapping drives and printers and all this, how a user locking and unlocking his desktop. Think of this scenario has something that would be very useful in the Desktop Virtualization space with Citrix or VMware where you have a user connected in the office, then he goes home and reconnects to his/her desktop.
Hope you enjoy those videos, I tried to keep them short and to the point, let me know what you think!