We are pleased to announce that the beta versions of Microsoft Application Virtualization (App-V) 5.0 and a new MDOP product Microsoft User Experience Virtualization (UE-V) are now available for download fromMicrosoft Connect.
UE-V is an enterprise-scale user state virtualization solution that delivers a user’s personal Windows experience across devices, is simple for IT to deploy, and easily integrates with existing management tools.
Some of the main features of UE-V are:
Some of the new features in the App-V 5.0 Beta are:
These products will be part of a future version of the Microsoft Desktop Optimization Pack (MDOP). If you want to learn more about App-V 5.0 and UE-V now, check out the Windows for your Business Blog were we have posted even more information about the products.
Does UE-V completely remove the need for Roaming Profiles or should we be combining with something like a mandatory profile in order to provide a fast, but customised logon?
Thanks for the question. UE-V can be used instead of a roaming profile to provide a consistent experience across devices. If you are looking to create an experience that the user can change but not save, then mandatory profiles would be a better solution. As UE-V allows users to sync settings to an SMB share, it expects to have read/write access to this share in order to copy any changes made.
Thanks AJ. I suppose the point I am trying to make is that even if one is to use UE-V there is still a need for a profile of some sort. If I use a roaming profile then I am doubling up and still suffer from the pull down of the whole profile at logon. If I use local profiles only and UE-V then when a user changes computer their logon will take a long time whilst Windows builds the user a profile. So it seems like combining a mandatory with UE-V might give a fast logon but still allow customization to roam.
You are right that you need some sort of profile. For roaming profiles, I would agree that this would not be a good idea and we don’t recommend using these. With local profiles you have a good point that you will need wait for the profile default profile to be created if this the first time the user was on the machine, but this is one time cost (assuming you don’t delete the profile). On the topic of mandatory profiles, we don’t support using these with UE-V but I would love to understand your use cases for this so we can consider supporting this in the future.
For me the issue is that I have a very large environment where users roam often. Logon times is always an issue and I was hoping that UE-V could be the answer. We have many public IT areas and in these areas we delete copies of profiles from machines at log off as we could easily have 50+ unique users use a machine in 24 hours. I guess if we can optimize the default local profile to minimise the creation time there could be some value in this. Roaming profiles do work but login times are long and we have quite a support overhead because they often corrupt.
In an academic environment where we have 30,000+ users. They currently all have roaming profiles. We do not cache profiles onto local disk because users move between many computers with high frequency. Therefore we are completely reliant on the roaming profile. The profile has a small limit, make for long logon times and are prone to corruption, so we would like to use something else. UE-V has some great features and if we could combine with with a mandatory profile that would allow the user to logon at speed, then any changes to registry/profile folders can be captured by UE-V then reinstated when they logon elsewhere. The fact that you can put your UE-V within your home folder also means another set of shares we could retire where we currently host all those roaming profiles.