Software Deployment

I packaged it awhile back for deployment in SMS. I first tried to repackage it both in Wise and in SMS Installer. It was messy to say the least. It appeared to install properly with the msi I created, however we couldn't get the client to actually connect to the server. And the uninstall was a second mess. When I ran the uninstall, either it would pull only about 10% of the files off the machine (when I packaged it in msi format) or would pull all the files but cause the machine to crash every time I tried getting to the Windows control panel (when I packaged it in exe format in).

I ulitimately used the documentation from ibm off of their ftp site (this is just for reference, it probably won't help you much). It provided a method of combining the base install and all applicable patches into a single 'image' (their term), then used an answer file with setup.exe to deploy it silently.

I ulitimately used the documentation from ibm off of their ftp site (this is just for reference, it probably won't help you much). It provided a method of combining the base install and all applicable patches into a single 'image' (their term), then used an answer file with setup.exe to deploy it silently.



I used the answer file and setup.exe -s also but when I packaged and deployed it via SMS the program requires a reboot and then tells the user that "you have to be an administrator in order to finish the installation" or something like that. How did you get around that?

I used the answer file and setup.exe -s also but when I packaged and deployed it via SMS the program requires a reboot and then tells the user that "you have to be an administrator in order to finish the installation" or something like that. How did you get around that?

Hi, I was wondering if anyone knows how to get rid of the "You have to be an administrator in order to finish the installation" issues?

I perform an install of V5r4 using the response file suggested by IBM. All works fine except the above. Wondering what might have caused it.

I MSId CA recently. IIRC, this is connected with IBM's dumb handling of DLL registration. There are a number of DLLs which require registration, but they don't have the DLLRegisterServer entry-point: you have to the IBM-supplied program,[INSTALLDIR]cwbsreg.exe, to do it. You also need to use the (free) MS utility REGTLIB to register the type libraries liberally sprinkled everywhere and lastly, run pcsws.exe with the '/regserver' switch. Other than that, pretty straight-forward. Ooh, avoid the beta IBM MSI - it's missing chunks of stuff, not the least of which is Navigator...