I had a long discussion with one of my customers this morning about Sequencing Best Practices. As part of our conversation, I referred to the Microsoft Application Virtualization 4.5 Sequencing Guide as a great reference and the Sequencing Best Practices KB article, but then we went further. In particular, we talked about the Installation (monitoring) phase when you run an application and knowing where to click to perform the "Top 10" user actions for an application you do not typically use.
From my experience as a Support Engineer, I have seen that Sequencing is sometimes handed off as just some tedious task with a pile of installation media. These are the applications that your business will run on so I'm making the suggestion that Sequencing applications is a vitally important task and that it should be taken as seriously as any other engineering related task you may undertake. Overall, this will keep your helpdesk calls down and your business running more smoothly.
The sequencing guide suggests this as a best practice:
It is recommended that you familiarize yourself with the installation and execution of the application prior to sequencing. Be sure to read all installation instructions associated with the application. It is also recommended that you learn how the application runs and the components of the application the user will need. To improve the process of sequencing an application, one should document step by step the installation and post-configuration procedures for the application. Step-by-step documentation will ensure that no unnecessary troubleshooting occurs during the sequencing process since no important steps will be skipped. Items to document include:
In reality, that best practice can be a tall order and can't be met by clicking "Begin Monitoring" and then "Setup.exe". It is also unrealistic to expect someone, or even a group of people, to be that familiar with the hundreds of applications that might be used in your environment. The bullet points above all lead to effective sequencing, so what can a Sequencing Engineer do to meet these needs?
To use a movie analogy, consider this work your Pre-Production. Pre-Production is all the tasks and planning that has to be completed before the cameras even get their lens caps off. Effective pre-production always pays off in making movies and the same can be said for Sequencing.
Steve Bucci | Senior App-V Support Engineer
PingBack from http://www.ditii.com/2009/04/03/effective-sequencing-starts-before-you-launch-sequencer/
Steve, a great read; is there anthing out there that goes deeper into what's a good use case or bad use case for App-V packaging. Here's one for you to consider MS Online BPOS (with the SSO, Office Communicator, Live Meeting and the audio/vidio that goes with it) - would we be mad to try it? or could this be viable.