This is Part 3 of 3
A bit of background, see http://www.myitforum.com/articles/6/view.asp?id=11240 and http://www.myitforum.com/articles/6/view.asp?id=11243
Essentially, because ITCU worked so well with deploying 9.0.47, I really wanted to continue to use ITCU for 9.0.115; but I ran into some snags, one of which was that Adobe hasn't updated their .CAB for ITCU to support 9.0.115--so I wrote my own rules (attached, extract the .cab from the .zip). If you've tested the .MSI deployment independently of ITCU and it is acceptable, here's how to import this ruleset into your ITCU; and some post-publishing of the rules steps.
Assumptions:
- You've already configured ITCU, and tested it, for Flash Player 9.0.47.0 (that's a big assumption, I know)
- You've already tested the 9.0.115 MSI, and it works exactly as you expect it to work. (possibly with a .MST and cab files, for example, following part 2 of 3)
- You do NOT have an Article ID of APSB07-020 in Adobe Systems, Inc., Adobe Flash Player 9 Section.
Assuming the above is true, this will outline the steps for importing (and customizing) the Rules to 'publish' to SMS 2003, running through the Distribute Software Updates Wizard (DSUW), and post-creation, adding files to the source, and updating distrib points.
1. Importing/Customizing the ITCU Rules
Download the attached file.
Launch “Custom Updates Publishing Wizard”.
Click “Import Update(s)”
Click “Single Catalog Import”
Browse to the downloaded .cab file, click Open, Next, next; Accept any Catalog validation, Close.
Go to +Adobe Systems, Inc. then Adobe Flash Player 9.
You will now have an Article ID of “APS07-20”
You *will* need to edit this before publishing. Right-click and Edit.
Click Next until you get to the “Select Package” section. You will need to change the “Download URL (or UNC)” to be a valid location on your network or server which contains the 9.0.115 MSI you’ve downloaded/customized from the licensing page at Adobe.
Click Finish.
You can now Set the publish flag for this update, and publish it (just like you did for 9.0.47.0).
2. Creating a new DSUW Package for this 1 update.
In your SMS Console, launch 'Distribute Software Updates'
Select an update type: (pick the Custom Update choice)
New
Package Name example: FlashPlayer
Next
Input the Organization name, rtf if you use one.
Next, Next
Choose the 9.0.115 update, Next.
Modify the Package Source Directory to match your normal Source Folder, if necessary,
Next (it will download the .msi from the folder\share you defined in step 1)
Next
Do not add DPs at this point, Next, OK
Configure Installation Agent Settings: each company is different, choose the options your company uses.
Next. Again; each company is different, choose the options your company uses. Next. Choose the options your company uses. Next. If you've already defined a Test Collection, choose to Advertise; and browse to the collection. Otherwise, Next. Finish.
Base package is now created! But it's nowhere near ready...
3. Customizing the Package source to use the .mst & .cab
The 'download' of the .MSI only downloaded the .msi, not the .CAB, nor the .MST (assuming you followed step 2 of 3 to create a transform). Copy the .cab and the .mst from where you have them, to the location specified as the source for this new Package, into the {characters} folder, the same place the .MSI is.
In Package Properties, Program, go to properties. Since during my testing I noticed IE needed to be closed, I went to the Environment tab, and changed it to "Only when no user is logged in". I also went to the Advanced tab, and picked "run another program first", and chose the Package/Program of the Custom Updates Tool (the scanner), Run this other program every time, and for this... Suppress program notifications.
Add Distribution Points to this package.
If you haven't created an Advertisement yet; do so. I strongly suggest a test collection with 1 or 2 test computers as members!
Test, test, test!
The zip containing the cab: http://myitforum.com/cs2/blogs/skissinger/Flash115CabforITCU.zip