I use a User Environment Management (UEM) or other “Roaming Profile” tool like fsLogix Profile Containers.

I use a User Environment Management (UEM) or other “Roaming Profile” tool like fsLogix Profile Containers.

I use a User Environment Management (UEM) or other “Roaming Profile” tool like fsLogix Profile Containers.

User Environment Management tools do a great job at two things:

  • They make logging on faster because user’s whole roaming profiles aren’t downloaded all at once and
  • They trap users’ changes so they can cleanly roam from machine to machine (VDI to real, desktop to laptop, etc.) and keep the settings that users have changed themselves.

Great goals — and, PolicyPak doesn’t try to do either of those two things. PolicyPak is different: PolicyPak delivers, enforces and remediates the settings that you know are important business and IT settings.

Said another way:

  • UEM tools help roam the settings that the user cares about (and speed up login times).
  • PolicyPak delivers, enforces and remediates IT and security settings that you (the administrator) care about

PolicyPak and UEM tools have a fantastic “better together” story. As an example of one tool, here’s our video with PolicyPak + Microsoft U-EV: https://www.policypak.com/integration/microsoft-user-experience-virtualization-ue-v-enhanced-by-policypak.html

And here’s our “better together story” with the FSLogix profile containers. https://www.policypak.com/integration/policypak-fslogix.html

But similar user state virtualization (ie: Settings & Profile roaming) tools will work with PolicyPak in the same way.