Oracle 11g R2 Client - SCCM
Hi Guys,
Long-time reader – first-time poster
I’m trying to install Oracle 11g R2 via the task sequencer in SCCM when deploying PCs. I’m using VBScript as wrapper but can’t for the life of me get it work within SCCM.
When running the script manually everything works just fine.
Here is the script I’m trying to use:
Set WshShell = WScript.CreateObject ("WScript.Shell")
strPath = WshShell.CurrentDirectory
strCommand = "cmd /c setup.exe -waitforcompletion -nowait -responseFile " & strPath & "\Install_Oracle11gR2_Client.rsp -force -silent -noconsole"
returnCode = WSHShell.Run (strCommand,1,True)
Wscript.Quit(returnCode)
As you can see I’m passing the path to the rsp file. I’ve also tried copying the file to c:\windows\temp before initiating the install in the script and then hardcoding the path in the command line. No luck. As I mentioned, everything works fine when running the script manually.
From a lot of research I found that some people needed to add the cmd /c in front of the .exe or the install would stall and eventually time out. This was true for me too. One I added the cmd /c the install no longer stalled and timed out, but rather failed immediately. I get exit code 1 returned from the installer.
Any advice on this would be greatly appreciated. I’ve been chasing my tail for a couple of days now.
Long-time reader – first-time poster
I’m trying to install Oracle 11g R2 via the task sequencer in SCCM when deploying PCs. I’m using VBScript as wrapper but can’t for the life of me get it work within SCCM.
When running the script manually everything works just fine.
Here is the script I’m trying to use:
Set WshShell = WScript.CreateObject ("WScript.Shell")
strPath = WshShell.CurrentDirectory
strCommand = "cmd /c setup.exe -waitforcompletion -nowait -responseFile " & strPath & "\Install_Oracle11gR2_Client.rsp -force -silent -noconsole"
returnCode = WSHShell.Run (strCommand,1,True)
Wscript.Quit(returnCode)
As you can see I’m passing the path to the rsp file. I’ve also tried copying the file to c:\windows\temp before initiating the install in the script and then hardcoding the path in the command line. No luck. As I mentioned, everything works fine when running the script manually.
From a lot of research I found that some people needed to add the cmd /c in front of the .exe or the install would stall and eventually time out. This was true for me too. One I added the cmd /c the install no longer stalled and timed out, but rather failed immediately. I get exit code 1 returned from the installer.
Any advice on this would be greatly appreciated. I’ve been chasing my tail for a couple of days now.
0 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.