In previous OS migrations, the process for determining application compatibility was a manual one. Applications were tested and if found to have errors, put through a further testing and remediation process. This was a costly, risky, disruptive, time-consuming and ultimately a very expensive process, leading many organizations to subsequently skip OS upgrades (or delay as long as possible) due to the cost and pain of the experience.
With Windows 7 migration and the new testing tools available, the situation has improved considerably. The opportunity to pre-scan applications before testing or remediation can make the whole process significantly more efficient. Knowing which applications have issues before testing means expert resources can be applied directly to applications that need them – and only those. Applications which do not have issues can be fast-tracked through light or user testing according to importance. Time and resource planning can be based on accurate metrics rather than basic estimation, reducing the overall time to implementation.
If the process of testing and remediation is begun based on knowledge about the applications and their issues, the entire process becomes more manageable. High volumes of applications can be addressed with fewer resources. Timetables are compressed and output is more stable and thus the entire process becomes less risky for the business.
Discovering that an application has issues takes a lot less time than identifying and resolving those issues. Finding issues with an application (which may require weeks or months to resolve) late in a project can jeopardize the whole project. Therefore, early identification of issues and their causes saves more than just time. Automation of application analysis is typically more accurate than basic compatibility testing, as all files within the application can be touched and analyzed with the same degree of depth. This is not easily achieved whenever a user is required to interact with the application to perform the assessment.
Remediation can come in various forms, from modifications to the installer, shims, re-development, re-provisioning or modifications to the OS build. Knowledge of the issue types makes resolution more direct. The ability to incorporate application remediation via modifications to the OS build means that whole categories of issues, for example, missing or deprecated components, can be resolved without modification to individual applications. This level of resolution further increases stability and efficiency, but may require collaboration between application teams and OS build teams who may have previously worked in isolation.
Organizations that implement and maintain application management processes, often put in place during migrations, benefit in the long term by being more agile. Agility, in this sense, means being able to adapt to OS and technology changes more rapidly with less risk, less disruption and reduced cost.
Having an up-to-date view of applications means the portfolio size can be pruned and rationalized on an ongoing basis. Packaging of applications allows for rapid analysis and modifications. Virtualization can further increase stability and reduce testing as part of the ongoing application management cycle.
9a69b23d-faa9-4755-9d50-e0eed56ddb09|1|5.0