timallen
Well Known Member
I know this is a topic that has been gone over before, but I've just had such a successful experience with doing silent installations from the command line that I felt that I should advocate it a little.
We have a client with 120 installation licenses on OneWorld Xe (*not* named licenses or any of the other sales, um, confusion JDE sprays at their customers: 120 real installations possible). They have a Novell system where they can launch programs on their client machines. They wanted to do these 120 first-time installations over a period of a couple of days. I started imagining sleepless unshaved nights doing monkey work.
I got the KG document OTM-00-0067 "Installing Packages from the Command Line". We found we were able to use this to do the installations, and I have become a new silent install disciple because:
1) The silent installation went faster
2) We had control of the level of detail in the installation log
3) I didn't have to go point and click on 120 machines.
There were a couple of caveats, though (on Xe at least):
1) Although the document says it's for Pre-Xe, Xe, and ERP 8.0, the command line still refers to "\\<deployment server>\b733\...". This should be B7333 for Xe.
2) The -t command line option causes the installation to fail. It's not necessary anyway (it marks the default behavior of installing development objects)...
2a) The -c command line option, which selects to *not* install development objects, causes a warning ("CSetupApp::InitInstance: Setup was passed the unrecognized option '-c'."), but still does its job.
3) The user has to have READ/WRITE permission to B7333 on the deployment server.
Here was the command line which worked so well for us:
"\\DEPLOYMENT_SERVER\b7333\OneWorld Client Install\Setup.exe" -d c:\b7 -p PY7333F001 -s -e H -c
-d : drive and path to install to
-p : package name
-s : silent (-v for verbose)
-e H : full logging (-e I information, -e W warnings, -e E errors)
-c : compact (don't install development objects-- put no option to install them).
Hope this is helpful.
(Ignore the configuration in my tag line, this one is:
Update 6 SP19.1 Windows 2000 ES & DS, SQL Server)
We have a client with 120 installation licenses on OneWorld Xe (*not* named licenses or any of the other sales, um, confusion JDE sprays at their customers: 120 real installations possible). They have a Novell system where they can launch programs on their client machines. They wanted to do these 120 first-time installations over a period of a couple of days. I started imagining sleepless unshaved nights doing monkey work.
I got the KG document OTM-00-0067 "Installing Packages from the Command Line". We found we were able to use this to do the installations, and I have become a new silent install disciple because:
1) The silent installation went faster
2) We had control of the level of detail in the installation log
3) I didn't have to go point and click on 120 machines.
There were a couple of caveats, though (on Xe at least):
1) Although the document says it's for Pre-Xe, Xe, and ERP 8.0, the command line still refers to "\\<deployment server>\b733\...". This should be B7333 for Xe.
2) The -t command line option causes the installation to fail. It's not necessary anyway (it marks the default behavior of installing development objects)...
2a) The -c command line option, which selects to *not* install development objects, causes a warning ("CSetupApp::InitInstance: Setup was passed the unrecognized option '-c'."), but still does its job.
3) The user has to have READ/WRITE permission to B7333 on the deployment server.
Here was the command line which worked so well for us:
"\\DEPLOYMENT_SERVER\b7333\OneWorld Client Install\Setup.exe" -d c:\b7 -p PY7333F001 -s -e H -c
-d : drive and path to install to
-p : package name
-s : silent (-v for verbose)
-e H : full logging (-e I information, -e W warnings, -e E errors)
-c : compact (don't install development objects-- put no option to install them).
Hope this is helpful.
(Ignore the configuration in my tag line, this one is:
Update 6 SP19.1 Windows 2000 ES & DS, SQL Server)