This past Wednesday, we hosted a webinar with StackSafe on "The Influence of application selection on Testing and Change Management."
In this session, Dennis Powell, StackSafe's Senior Product Manager, and Shahzad Hussain, a Senior Systems Engineer with Ecora Software, discussed the following:
- Three main organizational approaches to change management and testing
- Why change management adoption can be more difficult in high stress environments
- The positive role downtime expenses play in the adoption of testing and change management processes
- The types of organizations that tend to have the most "laissez-faire" attitude towards change management
- How multiple operating systems can nearly double the cost of unplanned downtime
Today, Dennis shared more of his thoughts from this presentation in a post called, "IT's About Uptime."
If you'd like to see the presentation in its entirety, you can register and download it here.
While much of the presentation focused on environments where applications are actually developed, there are also plenty of challenges related to the deployment or third-party applications or upgrades that should be considered. In the latter portion of the presentation, Shahzad gives some examples of the types of configuration reports you'll want to be able to generate to ensure that any application, patch or service pack are upgraded on every appropriate system in your environment and how to ensure that the upgrade didn't cause additional, unanticipated changes that could render other applications inoperable because they share common dll files, as an example, that were removed when the application or upgrade was deployed.
If you are looking for this type of solution, or need a way to ensure your test environment is accurately configured to reflect your production environment, request a personal demonstration of Ecora Auditor Pro and see if will answer your configuration audit or compliance reporting questions.
Contributed by Mark Tordoff
Comments