Streamlined migrations and installations
Use Cases and Deployment Scope
We used Desktop Containers until recently to allow us to run applications within their own containers during migration to another operating system. We had a large number of employees we needed to migrate, and using this allowed us to do so with confidence. Users still had access to their applications before, during and after migration -- there was no interruption. We used it for a period of time following the migration as well, because we found our anti-virus caught fewer intrusions with the containers in operation (web browsers run within the containers were isolated, and if an attack occurred, we could easily remove the container and create a new one).
Pros
- It allowed us to isolate applications so that they did not adversely interact with other applications.
- They served as a virtual machine while we managed the migration to a new OS.
- They helped us decrease malicious attacks because web browsers operating within a container could be terminated if an attack occurred.
- They allowed us to quickly deploy applications across a diverse, global organization.
Cons
- Container access and restrictions were a bit cumbersome to set up.
- We would frequently have users report containers failing to work properly due to file size.
- There was very little documentation we could provide to users during onboarding
Likelihood to Recommend
It is very well suited to large, diverse organizations looking to quickly deploy applications virtually to its employee base. They give immense control to system
Admins and allow users to more easily install the applications they need. They also allow users quick access to their applications, even during migration.
