I was asked by my company to create a 2-day training for SWV for an end user company. The training needed to enable the end user company to make simple packages, clean them and deploy them.
That got me thinking... what do you actually do when creating a package. Explaining to the IT people of the company to simply "install, but first turn on recording" would be a little to easy and lazy. Is that really what we do when packaging?
Then again... Isn't it really what we do?
So this is how I build up the training:
- Day 1 morning: Theory about packages: What do they contain. Why Read Only and Read Write, registry and files (a nice four segmented diagram helps here). What does an installation actually attempt to do and what does Symantec SWV do with it? Version control on packages.
- Day 1 afternoon: Practical use: Make some packages. Let them test amongst each other. Simple but neat packages, like FireFox, Notepad ++, nothing conflicting or needing any cleaning, just to get some hands on.
- Day 2 morning: More theory: What do you clean, how do you clean and how do you deploy packages? Some helpful tips (packaging from command line, global capture and why not to use it and so on. OnEvents of course, package dependencies, the "harder" theory.)
- Day 2 afternoon: Practical use: Production packages by the customer, troubleshooting, proper testing (different machines, snapshoting VMs and so on) and the harder packages (Office 2010 for instance).
The course helped three different companies so far and counting.
So if you face the challenge of creating a course: use this guide freely and create your own content for it. This just describes a "global" design.
Enjoy and good luck!