SPSS 1802 patch silent deployment
Anyone managed to successfully deploy this silently: e.g.
MsiExec.exe /i "c:\spss1802\PASWStatistics18.0.2Patch.msi" /qn /L*V "c:\spss1802.log"
I use Novell Console One to deploy the MSI via running a batch file as above in unsecure system mode. If a non-privileged user deploys the application, they get an error when trying to run up the SPSS 1802 software.
Error message: 'c:\program files\spssinc\paswstatistics18\paswstat.exe
The application has failed to start because the application configuration is incorrect.
Reinstalling the application may fix this.'
If the non-privileged user logs out and a privileged user just logs in and then logs out, then the non-privileged user can run SPSS1802. (It seems that the MSI install is being completed after the restart by the privileged user looking at MSIEXEC running under task list when privileged user logs in)
If a privileged user does the deployment and reboots at the end as requested, then when he logs in again and runs SPSS 1802 too quickly, he gets the same error. In task list, it indicates MSIEXEC to be running so that needs to complete what it is doing after reboot before the privileged user can run up the software.
Same behaviour if I just simply run the batch file with the above command line as the privileged user.
Both the privileged user and non-privileged can install and run the software using the original PASWStatistics_1802_win32_Patch.exe (but this is not silent installation unfortunately).
Any one got similar behaviour?
Paul
MsiExec.exe /i "c:\spss1802\PASWStatistics18.0.2Patch.msi" /qn /L*V "c:\spss1802.log"
I use Novell Console One to deploy the MSI via running a batch file as above in unsecure system mode. If a non-privileged user deploys the application, they get an error when trying to run up the SPSS 1802 software.
Error message: 'c:\program files\spssinc\paswstatistics18\paswstat.exe
The application has failed to start because the application configuration is incorrect.
Reinstalling the application may fix this.'
If the non-privileged user logs out and a privileged user just logs in and then logs out, then the non-privileged user can run SPSS1802. (It seems that the MSI install is being completed after the restart by the privileged user looking at MSIEXEC running under task list when privileged user logs in)
If a privileged user does the deployment and reboots at the end as requested, then when he logs in again and runs SPSS 1802 too quickly, he gets the same error. In task list, it indicates MSIEXEC to be running so that needs to complete what it is doing after reboot before the privileged user can run up the software.
Same behaviour if I just simply run the batch file with the above command line as the privileged user.
Both the privileged user and non-privileged can install and run the software using the original PASWStatistics_1802_win32_Patch.exe (but this is not silent installation unfortunately).
Any one got similar behaviour?
Paul
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
The simplest route here is to take a gap capture between the non-privileged and privileged log-ins. You can use a lightweight snapshot tool like InstallWatch or In Control for that.
If it turns out to be changing a registry entry or some data in an INI/XML/whatever file, you may need to permission it to allow non-privileged users to update it, depening on its location.
If it turns out to be changing a registry entry or some data in an INI/XML/whatever file, you may need to permission it to allow non-privileged users to update it, depening on its location.
Posted by:
bearbonez
13 years ago
I got a silent install by creating a mod (mod-SPSSv18-0-2) in console one that runs the following line as "unsecure system user"
%*WINSYSDIR%\msiexec.exe /i %SOURCE_PATH%\PASWStatistics18.0.2Patch.msi /NORESTART /qb
And a line in Distribution scripts > run after disribution
c:\windows\system32\xcacls.exe "C:\Program Files\SPSSInc\PASWStatistics18" /T /E /G users:F
(and calls xcacls as a dependancy)
to open permissions to the install directory
(%SOURCE_PATH% being a zenworks variable you can declare in COMMON>Macros>ADD>String Value
which in my case points to where the msi is stored on the server ie. \\fs_zfdbuildmr\apps\testapps\SPSS-patch-18-0-2)
The above was called as a dependancy by the parent app "SPSSv18-0-2" which is run as "secure system user"
and has the following line in Distribution scripts > run after distribution
regsvr32 /s C:\WINDOWS\system32\csseqchk.dll
and script engine location - %*WINSYSDIR%\cmd.exe /c
and places an icon on the desktop. (note windows variables require the %* at the begining)
Couldn't for the life of me get "SPSSv18-0-1" to install properly and SPSS support were next to useless :-/
so we skipped that update.
We find doing this one app calls another gets round the "privileged user and non-privileged user" dilema
Hope this helps ;)
%*WINSYSDIR%\msiexec.exe /i %SOURCE_PATH%\PASWStatistics18.0.2Patch.msi /NORESTART /qb
And a line in Distribution scripts > run after disribution
c:\windows\system32\xcacls.exe "C:\Program Files\SPSSInc\PASWStatistics18" /T /E /G users:F
(and calls xcacls as a dependancy)
to open permissions to the install directory
(%SOURCE_PATH% being a zenworks variable you can declare in COMMON>Macros>ADD>String Value
which in my case points to where the msi is stored on the server ie. \\fs_zfdbuildmr\apps\testapps\SPSS-patch-18-0-2)
The above was called as a dependancy by the parent app "SPSSv18-0-2" which is run as "secure system user"
and has the following line in Distribution scripts > run after distribution
regsvr32 /s C:\WINDOWS\system32\csseqchk.dll
and script engine location - %*WINSYSDIR%\cmd.exe /c
and places an icon on the desktop. (note windows variables require the %* at the begining)
Couldn't for the life of me get "SPSSv18-0-1" to install properly and SPSS support were next to useless :-/
so we skipped that update.
We find doing this one app calls another gets round the "privileged user and non-privileged user" dilema
Hope this helps ;)
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.