Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Batch to roll out nav msi, managed not AD!

Status
Not open for further replies.

Auger282

MIS
Sep 27, 2003
978
I'm having some trouble with the switches for my batch file. I'm trying to roll out this msi file for corp 10 via a novell login script. I can get it to install the msi file silently but I cant figure out how to configure it to be managed mode or identify the correct server (via script).

---second problem
When I toss this msi to my current clients (upgrade) it uninstalls their version and then reinstalls.. is there any way to create an upgrade package to send out?

Thanks!
 
I normally have clients map to the parent servers vphome share and run the setupo directly from there which will put it in managed mode automatically. This is with windows though, so I cant help to much with Novell

HTH - Stiddy
 
Results of running symantec antivirus.msi /?

######################################
Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
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
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
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
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
Remove update(s) for a product
Repair Options
/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
[PROPERTY=PropertyValue]

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.





HTH - Stiddy
 
For your #1 I've always done as Stiddy suggests. In the login script create a drive mapping and then execute \vphome\win32\setup.exe from there.

For #2, symantec has always insisted on an Uninstall then Install for me.
 
BTW, IF SYMANTEC is already installed, you need just copy the right grc.dat file to each machine for it to switch between unmanaged to managed

HTH - Stiddy
 
just because I like passing info this is the command I came up with...


\\SERVER NAME\vol1\nav\nav_10_client\setup.exe /S /v"REBOOT=ReallySuppress /qn"

runs like a charm.. I still dont have the warm and fuzzys about 10.0.2... but its onward and upward
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top