Silent Install

[Guest.Visitor]

Hi, We have CA installed on a network drive and then perform silent installs to new PC's, this works fine. But, when we get a service pack we then have to do asilent install of the service pack to each pc. Is there a way to install the service pack onto the network version of CA - this will then give us only 1 silent install - instead of a possible 2. TIA Carl

[Guest.Visitor]

Should it be any different when you're trying to install CAE, silently, from the AS/400? We are trying to get a silent migration to work, and we keep getting the error message -- "A device attached to the system is not functioning." Our silent migration command looks like the following -- \as400qibmproddataca400expressinstallimagesetup.ex e s2f1=\as400qibmproddataca400expressinstallsilentst age2.iss s2f2=c:stage2.log XD1 -s -f1\as400qibmproddataca400expressinstallsilentstage 1.iss -f2c:stage1.log We are trying to do this from the Start -> Run command.

[Guest.Visitor]

In working with the folks at IBM, (mailto:rchexp1@us.ibm.com), they have asked me to use a batch file to run the particular silent install command. I still get the same error: "A device attached to the system is not functioning." Has anyone run the silent install command through a batch file? Any "gotchas" to consider?

[Guest.Visitor]

Yes we have - but we run the upgrade from our server. We use the same syntax as you tho...

[Guest.Visitor]

Joe (& Carl) - Have you tried 'silent install' rather than 'silent migration' to determine if the error message appears? (I know it's not what you want to do but it might help in problem determination.) I can do 'silent install' with no problem but haven't tried 'silent migration'. HTH, Steve

[Guest.Visitor]

We use the silent install - and it works fine. My 'problem' is with the service pack. I have to install the service pack on each client, Why can't I install the service pack on my server version, and then when a new client appears I just have one install to do and not 2. Carl

[Guest.Visitor]

Carl, I know it doesn't address your current problem, but I believe that the capability to silently Install and Service Pack before re-booting is coming in V5R1. Bil

[Guest.Visitor]

Silent install work? Yes.

[Guest.Visitor]

When you say that you run the upgrade from "your server" -- do you mean an NT network server, or the AS/400 through NetServer?

[Guest.Visitor]

Silent Migrations do work. Unfortunately, they're like watching grass grow! According to the folks at IBM, my bat file problem with the silent install command may be related to the parm size (the parm being everything from "s2f1" on)... I had this long thing -- \qas400qibmproddataca400expressinstallimagesetup.e xe s2f1=\qas400qibmproddataca400expressinstallsilents tage2.iss s2f2=c:stage2.log XD1 -s -f1\qas400qibmproddataca400expressinstallsilentstag e1.iss -f2c:stage1.log Was told to -- * Shorten the stage1 and stage2 names to s1 and s2 respectively. * Move files s1 and s2 up a few directories. New thing looks like -- \qas400qibmproddataca400expressinstallimagesetup.e xe s2f1=\qas400qibmproddataca400s2.iss s2f2=c:s2.log XD1 -s -f1\qas400qibmproddataca400s1.iss -f2c:s1.log

[Guest.Visitor]

I forgot to mention that IBM stated -- "Your problem seems to be the length of the command line parameters passed in to setup.exe. With V4R4, we used InstallShield 5.1, which was a 16-bit setup.exe. With V4R5 and V5R1, we use InstallShield 5.5, which has a 32-bit setup.exe." Make sense?

[Guest.Visitor]

Furthermore, IBM's documentation on the web suggests bootoption=0 over bootoption=3. Bootoption=3 tells the system to perform an automatic reboot of the PC. Bootoption=0 tells the system not to reboot after a completed setup stage. With bootoption=0, you can wait a long time unless you know when each stage of a setup is done. With bootoption=3, a reboot at least gives you an indication that a setup stage has completed. IBM tells me, generously, -- "We are looking into a silent install progress indicator (maybe something in the task tray that a user can click to see more detailed status)." In the meantime, during a Client Access install, file instlog.txt does get updated at particular points of the installation process. This file and path is -- c:program filesibmclient accessinstlog.txt. Thank you IBM guys.