Ease Software Installations in a CDI

One feature I like about Kasm’s containerized virtual infrastructure is that the docker images are constantly checking for an update from docker hub. This keeps the base OS and software patched and the software up to date.

Just a few lines of code to install software which runs at build.

Time Consuming, Error Prone and Stale Software Install in legacy VDI

In the last page we briefly mentioned software packaging and how time consuming it can be even if you are using an image management solution because you have to follow a wizard before “sealing” the layer. Then repeat for every application you have, and then repeat again to keep them updated. Ouch!

I clicked an EXE to start the installation but to start the installation click next. LOL!
Custom will make you chose different variations. How will your team know which one to use?
Right…..
Once again, I agree to the EULA to install so I will do another click to install. LOL!
In a custom installation you either document or hope that the next person knows what to chose.

Software distributors have agents (middle man) on the target endpoints to invoke the command line and run an msi with a silent switch like the example below. The executable is often outdated because it was downloaded from the vendor’s site and placed on a network share to distribute to endpoints.

VDAWorkstationCoreSetup.exe /quiet /controllers "Contr-East.domain.com" /enable_hdx_ports /noreboot

In the next page we will cover another VDI challenge which is right sizing and cost and how a containerized desktop infrastructure helps the case.

Pages: 1 2 3 4 5 6