Recently, well I say recently it was actually back in Sept 2019 I was asked by a client to investigate a solution for one of their vendors whom for no better reason than they have ‘legacy’ iLOs that they need to connect to with IE 8.
We all know there are ways to deliver this but all of these will eventually come up against something that Microsoft will not support or allow. Unsupported OS, disallow multiple versions of IE on the same Kernel.
This is where http://www.dropletcomputing.com comes in; two container options based on XP or W7 kernel stripped back to the bare essentials to provide backward compatibility … think XP/W7 core and you won’t be far from the truth but the container has been pen-tested by nccgroup for added security when running these containers.
This solution has allowed me to enable not only IE8/IE9 but I see it becoming very useful when used in conjunction with VMWare NSX to provide a solution for some Huawei software that another client wishes to be secured (for obvious reasons).
- Legacy application support
- Works with RDS and WVD to accelerate our migrations (we’ve been working with droplet to enable RDS/CVAD)
- Works with MacOS
- Other clients in the pipeline
The downside; I’d like to say there isn’t one but each user will require their own container, currently 2-4GB. If this is on the network then I would make sure you put it on a share that benefits from De-dupe; if local then this is less of an issue. I also envisaged that the use of these legacy kernels would be an issue but due to the ‘zero inbound connection’ design there is no need to maintain patches. This means patch Tuesdays is not going to be an issue for droplet.
If you’d like to see it in action with your own environment then please get in touch. If you require us to sign an NDA to ensure you exposure to legacy software remains confidential then this is not a problem