In Installation Script for Mass Rollout of Duet Client (Part 1) I talked about a new sample script, which can be used as a template for your mass rollout of the Duet Client Component. Today I will provide more detail on how to prepare the script for your environment.
What do I need to do before using the script?
1. First create the following subfolders within your root directory:
- HotFix (including subfolders KB899587, KB907417, KB945430, KB941275) - optional
- Office_2003_SP3 - optional
- Office_2007_SP1 - optional
- Scripts
- Source
Your folder structure should look like this:
2. Next you need to place the following files within these folders:
Folder Scripts:
- File: DuetInstallationScript.vbs
This is the file, which you downloaded from Microsoft's website earlier.
Folder Source:
- Files: CD Microsoft Installation Files OBA Client Setup Files en
Copy these files from the Duet CD to the Source folder. (Choose the proper language folder for your desired language.)
Folder Office_2003_SP3:
Folder Office_2007_SP1:
Folder HotFix / KB899587:
Folder HotFix / KB907417:
Folder HotFix / KB945430:
Folder HotFix / KB941275:
3. Next you need to make adjustments to the script. Open the script in an editor and make the following changes:
- READSERVICE_URL
Set the variable READSERVICE_URL to the correct URL of your Duet Read Service. - DUET_SCRIPT_LOG
Variable DUET_SCRIPT_LOG determines where the log of the installation script should be stored. Specify a path that will exist on all operating systems. - DUET_SETUP_LOGGING
Parameter DUET_SETUP_LOGGING lets you specify where the log of the Duet Installation (setup.exe) should be stored.
4. Read through the script and modify where necessary. Turn off features not applicable to your environment. Here some areas you should pay attention to:
- Support Packages
Modify functions DetectAndInstallOfficeSP3() and DetectAndInstallOffice2007SP1() if you do not want the script to install service packs. - Hotfixes
Determine if it is necessary to rollout hotfixes. They might be already available on your company's computers. Revise function DetectAndInstallHotfixes() as necessary. - Group Policies
If your script is executed by an administrator (instead of the end user) then group policy settings might not be available to the administrator. In this case, you should turn off function ValidateGroupPolicies().
Error handling
Once the script determines that a prerequisite is not met, then the script will do the following:
- Stop the installation process
- Create a log entry with a specific error message
- Return an error code, which can be captured by your software distribution system (e.g. Microsoft SMS)
If errors are encountered, desktop support should start manual resolution.
Script test
Perform a thorough test of your script. Choose a small test group in your production environment for a final test prior to starting the mass rollout.
Using script in your software distribution system
Depending on your company's software distribution system (e.g. Microsoft's SMS), now create the software distribution package which includes your new script. Allow the package to execute with administrative rights, as required by the Duet Installer. Also consider forcing a user log off, because the Duet System Tray will only start upon next logon of the user.
Usage of this sample script should significantly reduce the time and work involved in preparing for the mass rollout of the Duet Client Component.
