Help with Comspec

[TheLug]

Trying something still related to a previous post. Previous Post

I cannot find a way to make this work... Although I think it should. The (") after the "v" is needed as part of the command line.

RunWait (@ComSpec & ' /c C:\LogFiles\Resource_Scheduler\Source\RSO1100.exe /s /v"RSBASEURL=https://url.resourcescheduler.net/RSOEFR /passive)

 

[jguinch]

" and ' are missing after /passive :

RunWait (@ComSpec & ' /c C:\LogFiles\Resource_Scheduler\Source\RSO1100.exe /s /v"RSBASEURL=https://url.resourcescheduler.net/RSOEFR /passive"')

 

[Trong]

Try:
 

RunWait(@ComSpec & ' /c "' & 'C:\LogFiles\Resource_Scheduler\Source\RSO1100.exe"' & ' /s /v "' & 'RSBASEURL=https://url.resourcescheduler.net/RSOEFR /passive"')
;ShellExecuteWait('C:\LogFiles\Resource_Scheduler\Source\RSO1100.exe', '/s /v "' & 'RSBASEURL=https://url.resourcescheduler.net/RSOEFR /passive"')

 

[TheLug]

21 minutes ago, jguinch said:

" and ' are missing after /passive :

RunWait (@ComSpec & ' /c C:\LogFiles\Resource_Scheduler\Source\RSO1100.exe /s /v"RSBASEURL=https://url.resourcescheduler.net/RSOEFR /passive"')

 

This worked like a charm thanks a lot!!! Testing if this fixes original issue now!!!

[TheLug]

Blah still doesnt work. It works when i run it manually on the machine, but not when I push it out through SCCM. I DON'T GET IT!!

[jguinch]

Try ShellExecuteWait instead  (see #3), it should work

 

[TheLug]

2 hours ago, jguinch said:

Try ShellExecuteWait instead  (see #3), it should work

 

That's not working even running manually. It pops up a run dialogue box asking to run and then runs after I click ok but then just goes away. 

[Jos]

Could it have to do with the fact that the WorkDir or the Environment variables (like Path) are different when shelled via SCCM under the System credentials?

Jos

[TheLug]

I don't think so. Looking at the script I have made the locations static. Take a look...

expandcollapse popup

#NoTrayIcon

$LogFilesDirectory = ("C:\LogFiles")
If FileExists($LogFilesDirectory) Then
   Else
      DirCreate("C:\LogFiles")
EndIf

;Install Notification
   MsgBox (48,"Resource Scheduler Outlook Client","OUTLOOK WILL CLOSE, DO NOT RELAUNCH UNTIL FINISHED",10)

;Close Outlook
   ProcessClose ("OUTLOOK.exe")

;Uninstall Resource Scheduler Outlook Client
   RunWait ("MsiExec.exe /x {7B207D64-D14A-4C05-A369-A13E914A1D34} /qb-!") ;Version 1050
   RunWait ("MsiExec.exe /x {081F2D54-90F1-4A7A-95DF-A27711BCD58B} /qb-!") ;Version 1100

;Copy Source files temporarly to LogFiles folder
   $Resource_Scheduler_Dir = ("C:\LogFiles\Resource_Scheduler")
   If FileExists ($Resource_Scheduler_Dir) Then
      Else
         DirCreate ("C:\LogFiles\Resource_Scheduler")
   EndIf

Sleep (500)

   DirCopy (@scriptDir, $Resource_Scheduler_Dir, 1)

Sleep (500)

;Install Resource Scheduler Outlook Client
   ;RunWait (@ScriptDir & '\Source\RSO1100.exe /s /v"RSBASEURL=https://url.resourcescheduler.net/RSOEFR /passive"')
   RunWait (@ComSpec & ' /c C:\LogFiles\Resource_Scheduler\Source\RSO1100.exe /s /v"RSBASEURL=https://url.resourcescheduler.net/RSOEFR /passive"')

;Completion Message
   MsgBox (48,"Resource Scheduler Outlook Client","Resource Scheduler Outlook Client - INSTALLATION COMPLETE!",10)

 

[Jos]

Understood, but that doesn't mean that for example the last runwait() will work when the WorkDir isn't the script dir. have you tried setting the workdir to the script dir with FileChangeDir(@ScriptDir) just to be sure?  

What exactly is failing of the steps you have in the script? Is it just the RunWait() or also other things?

Jos

[TheLug]

 

2 minutes ago, Jos said:

Understood, but that doesn't mean that for example the last runwait() will work when the WorkDir isn't the script dir. have you tried setting the workdir to the script dir with FileChangeDir(@ScriptDir) just to be sure?  

What exactly is failing of the steps you have in the script? Is it just the RunWait() or also other things?

Jos

The last runwait will not run when it is pushed out via sccm. It works perfectly if I right click run as admin, but if i push it out it just flashes and skips that line. All of my other apps for the last 8+ years have never had this issue.

[Jos]

I am out of ideas other than the suggestion I made to try with setting the WorkDir. 

EDIT: in  case you see the shelled screen you could replace the /c with /k to see if there is an error shown in the CMD window.

Jos 

Edited July 1, 2016 by Jos