Dealing with legacy applications
Legacy applications refer to software older than the current ‘official’ release. In any IT environment, there are legacy applications that cannot be replaced. To combat this, companies use legacy management tools or ‘thick clients’, but this can cause a number of issues…
Legacy applications all have dependencies, be it their own Dynamic Link Library (DLL)’s, or versions of .NET and Java. Furthermore, it can be tricky or even impossible to have multiple versions of some management tools concurrently installed.
SysAdmins are forced to work across different versions of management tools, or install specific versions on jump boxes and access those. Resource intensive and a security risk, jump boxes are only accessible via a dedicated desktop, often shared by team members.
Applications are presented on the user's desktop alongside their other applications.
Secure environment for running legacy applications.
No need to ensure the user's desktop has all the necessary supporting libraries for each legacy application.
Credentials are injected in the mapped application and never revealed to the user.
IT has control over who has access to which applications and the credentials that are used.
multiple versions of management applications to be available to SysAdmin or DevOps desktop without any dependencies at the workstation.