Does the Streets and Trips setup.exe file allow for the /admin command? Thats how I push out Office 2007 upgrades here locally. Run the setup.exe with that /admin command, set all the options I want to use, then save it as a office.msp in the same directory as setup.exe.
Then its easy, just a one line script to call setup.exe /adminfile office.msp from the share and the the installtion runs like a champ.
Just an idea ...
I have tried this. I did have to do this for the Office2007 which works fine.
But this one i am a little lost on.
What would I run??
There is a data.msi file but that is located here.
The CD where the files for ST2009 is, is called.
st2k9/streets/MSMap/ and then the data.msi
Windows ® Installer. V 3.01.4000.3959
msiexec /Option <Required Parameter> [Optional Parameter]
</package | /i> <Product.msi>
Installs or configures a product
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Quiet mode, no user interaction
Unattended mode - progress bar only
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
Do not restart after the installation is complete
Prompts the user for restart if necessary
Always restart the computer after installation
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
Equivalent of /l* <LogFile>
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
Remove update(s) for a product
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.