I have a properly functioning customized network installation point for deploying Office 2007 using the Office Customization Tool. I'm trying to configure a "post install" installation of Microsoft's "SaveAsPDF" add-on for Office 2007. I've unpackaged the EXE file and have a working SaveAsPDF.MSI file (tested as a standalone installation on a seperate computer). In OCT, I'm using the "Add installations and run programs" section and added the following command:
"L:\Workstations\Office200
7\Updates\
Custom Programs\saveaspdf.msi /quiet"
Everything actually works fine with this syntax, but my problem is if I decide to move the setup files to a different subdirectory I have to remember to go into the OCT program and update the command to reflect the new structure.
How can I specify a system environment variable instead of the explicit directory structure so that the command is more dynamic or portable? The OCT comes with several useful "targets" for specifying some system variables already such as [INSTALLLOCATION], [WindowsFolder], and [CommonProgramFiles], but they don't have one with something like [SetupDirectory] or [DeploymentDirectory]. I tried the following command, but it doesn't work:
"%setupdir%\Updates\Custom
Programs\saveaspdf.msi" /quiet
Any ideas?
Start Free Trial
