Hi,

I am having an issue while deploying package through SCCM, the package is going for reboot without user intervention.This is setup.exe and it has .iss file. Manually testing is working fine but through SCCM package is going for reboot. Here is my .iss file

[{89B44DBB-9F91-4541-839F-67024172CCF0}-DlgOrder]
Dlg0={89B44DBB-9F91-4541-839F-67024172CCF0}-ZSdShared_CountryDlg-0
Count=4
Dlg1={89B44DBB-9F91-4541-839F-67024172CCF0}-AskYesNo-0
Dlg2={89B44DBB-9F91-4541-839F-67024172CCF0}-ZSdShared_DestPath-0
Dlg3={89B44DBB-9F91-4541-839F-67024172CCF0}-ZSdShared_Finish-0
[{89B44DBB-9F91-4541-839F-67024172CCF0}-ZSdShared_CountryDlg-0]
szCountry=United States
Result=0
[{89B44DBB-9F91-4541-839F-67024172CCF0}-AskYesNo-0]
Result=1
[{89B44DBB-9F91-4541-839F-67024172CCF0}-ZSdShared_DestPath-0]
szACT=C:\Program Files\ACT\Act for Windows
szSQL=C:\Program Files\Microsoft SQL Server
Result=1
[{89B44DBB-9F91-4541-839F-67024172CCF0}-ZSdShared_Finish-0]
bOpt3=0
Result=1

Please let me know if you any ideas.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
On the SCCM program, on the general tab, you can configure the behavior after running the program. Set the after running action to "no action required".
Hope that helps.
Answered 01/09/2012 by: jocken
Yellow Belt

Please log in to comment
0
On the SCCM program, on the general tab, you can configure the behavior after running the program. Set the after running action to "no action required".
Hope that helps.
Answered 01/09/2012 by: jocken@sah.com
Yellow Belt

Please log in to comment
0
Take a capture of the install and find out why it's rebooting. My guess would be that it adds to the System PATH. If you like, you can then use the resulting MSI - suitably edited, of course - instead of the legacy installer.
Answered 01/10/2012 by: VBScab
Red Belt

Please log in to comment
0
It appears that you are working on Sage ACT application.
In that case, you may already have a MSI installer available in the source.
Instead of capturing/using setup.iss, why not use the MSI installer?
Answered 01/10/2012 by: SandeepPanat
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity