About ESM
1. Inventory
ESM uses a third party source to provide inventory data (a global application list), typically including applications that are not of interest but are found by the commonly used inventory tools; e.g. Microsoft Application Compatibility Toolkit (default and free), Microsoft SCCM, Altiris inventory Solution, LANDesk.
Application can be grouped together and a level of interest or plan assigned to them; For example, they can be ignored, mapped to a replacement or put into a planning queue (Remediation, Procurement, Discovery, etc)
2. Remediation
When applications are identified as current and it is desired they should stay in the estate in their current configuration they can be assigned to the remediation queue. A number of automated tests can then be run against the packages with automated fixes also available for a Windows 7 Migration scenario.
3. Procurement
Frequently applications within the inventory will be identified as obsolescent and therefore rather than invest time to remediate and test them it is more effective to upgrade or replace them. When this is the case they are assigned to the Procurement queue, enabling the work to be assigned to people with procurement skills and information to be captured and reported.
4. Request & Discovery
A major challenge within OS migration projects is the ability to assemble all the required application setup and configuration details in advance of the packaging process. Once applications have been identified as required within the new environment they can be assigned to discovery where a, typically junior, technical resource can assemble all required files and configuration documentation to ensure the desired configuration is understood.
5. Approval
The Approval queue is a workflow checkpoint stage. Its purpose is to ensure the request to expend effort packaging has management or business approval.
6. Packaging
ESM integrates with a number of application packaging tools in order to streamline the packaging process; for example Wise Package Studio, MS App-V Sequencer, Symantec WVS (formerly SVS), InStead.
7. QA
ESM brings structured approach and efficiency to Quality Assurance by automating the creation of testing environments, capturing test outcomes online and providing an audit trail.
8. UAT
Once most applications have passed QA testing and are considered ready by the technical team they will require a functional User Acceptance Test by every day user(s) with a relevant understanding of the application’s businesses purpose.
Depending on the desired workflow setup, applications are typically sent to a UAT deployment OU/container/group so that the UAT can be performed using the live GPO and deployment tool settings (i.e. they go to a UAT Deployment queue first and then UAT). Again creation of the UAT environment can be automatically triggered by ESM.
9. Sign Off
The Sign-Off stage is another workflow checkpoint stage, this is typically completed by the application owner or application technical owner. Once Sign-Off is completed it is inferred that an application package delivers what has been set out within its Discovery stage.
10. Live
Once completed packages are deployed into the environment they remain with a live status within ESM. At its core ESM is an Application Estate Management product and live packages can be cycled through the system again to account for patches, upgrades and other desired additions and changes.
11. On Hold
When exceptions or obstacles are encountered within the Discovery, Packaging or other stages and issues are logged, the request is typically placed On Hold. All information within ESM is entered into a journal feature, which (along with all other fields) is accessible via Web Services Interface; enabling a service management tool (for example Remedy or ITSM) to seamlessly access the latest available information.
12. Retired
Once packages are decommissioned from Live their history is retained by keeping them with a Retired queue.
13. Deployment
ESM has a number of Service Connector Extensions that enable packages to be published in an automated and structured way into a systems management suite. Supported products include Microsoft SCCM, LANDesk and Altiris.