VBscript/Wscript - MS DOS Help - retrieving error code from PSEXEC, equivalent of "runwait"?

Posted on 2007-04-10
Last Modified: 2009-01-09
This is yet another question related to previous questions I posted. I have a script that removes symantec from a specified list of computers. Symantec is removed using the PSEXEC tool from Microsoft.
The way the script works is like this:
I have a list of computers in computer.txt. This is stored in an array.
I also have a list of Uninstall keys for Symantec stored in an array. The reason I have multiple uninstall keys is because some client computers have different versions of symantec installed on their computer. To uninstall them, I need to set the UninstallPW key to false. I also need the specific uninstall key to remove it. So for each computer, run the PSEXEC command for each key:

psexec \\" & strComputer & " MsiExec.exe /norestart /q /x " & strSymantecKey & " REMOVE=ALL

This somewhat works. The first problem is it doesn't seem to perform like a "runwait".. where it waits until the uninstall is done before executing the next command. It basically just runs right after the other without waiting for it to be done. I'm afraid this could cause problems during the uninstall.

The second problem is that when this runs, the command prompt opens for a split second and closes. I would like to have one continuous command window open at all times until the script is completely done. Is there a way to do this?

The third problem is this. When the psexec command finishes, it returns an error code in the command line. I would like to keep track of this in a log. But I don't know how to RETRIEVE the error code from the command line back to VBscript. Can anyone help me figure out how to retrieve the error code, and if the error code is 0 (successful) then exit out the for loop and go to next computer?

My main concern right now is retreiving the error and logging. Thanks!

Here is my code:

'Remove Symantec Remotely and Silently
'Results are stored in a log file: symantec.log

'--------------- Create Log File ----------------

'Open up the path to save the information into a text file
Dim Stuff, myFSO, WriteStuff, timeStamp
timeStamp = Time()

Set myFSO = CreateObject("Scripting.FileSystemObject")
Set WriteStuff = myFSO.OpenTextFile("symantec.log", 2, True)

Dim objShell: Set objShell=CreateObject("Wscript.Shell")

Dim startMsg
startMsg = "STARTING SCRIPT, YO!" & vBCrLF & "You do not neet to click OK until it is done." &_
           vbcrlf & "When the script is done, it will say DONE, YO! Check symantec.log for results."

objShell.Popup startMsg, 3
'WScript.Echo startMsg

WriteStuff.WriteLine("Starting Script, yo!" & vbcrlf)

'-------------------- Grab computer names from Computer.txt and store in array ----------------

strComputers = ""

On Error Resume Next

'Initialize global constants and variables.
g_strHostFile = "computer3520.txt"

'Read computer names for install from text file.
Set objFSO = CreateObject("Scripting.FileSystemObject")

If objFSO.FileExists(g_strHostFile) Then
  Set objTextStream = objFSO.OpenTextFile(g_strHostFile, FOR_READING)
  WScript.Echo "ERROR: Input file " & g_strHostFile & " not found."
End If

'Loop through list of computers and perform tasks on each.
Do Until objTextStream.AtEndOfStream
  readingInComputer= objTextStream.ReadLine
'  Wscript.Echo VbCrLf & readingInComputer
 strComputers = strComputers + readingInComputer +","


arrComputers = Split(strComputers , ",")

'----------------------------- Symnantec Piece---------------------------------
'Pre condition:  arrComputers must be populated from Computer.txt

'------- Insert all Available Keys Here-------------------
Dim strSymantecKeys
Const HKEY_LOCAL_MACHINE = &H80000002

arrSymantecKeys = Split(strSymantecKeys, ",")

For Each strComputer in arrComputers

On Error Resume Next
       '---- If computername is blank then exit loop ---
        If strComputer = "" Then
           exit for
        End If
 '----------- Set Uninstall Password & LockUnloadSvcs Registry Key Values-------

 Set objReg = GetObject("winmgmts:\\" & strComputer & "\root\default:StdRegProv")

 'objShell.Popup "Error = " & err.number & "!!!", 1

 ' ----If getObject fails, server is offline or doesn't exist -------------
 If err.number <> 0 then

        objShell.Popup "ERROR: "& strComputer & " is offline or access is denied", 1
      'wscript.echo "ERROR: "& strComputer & " is offline or access is denied"
      'write to log file
      WriteStuff.WriteLine(timeStamp & "  " & strComputer & " - ERROR! It is offline or doesn't exist.")
      On Error GoTo 0

 '------ Else GO ahead and remove Registry Keys ---------------------
   On Error GoTo 0

'   strKeyPath = "SOFTWARE\INTEL\LANDesk\VirusProtect6\CurrentVersion\AdministratorOnly\Security"
'   ValueName = "LockUnloadServices"

'   objReg.GetDWORDValue HKEY_LOCAL_MACHINE, strKeyPath, ValueName, strValue

'   If strValue<>0 Then
'      objReg.setDWORDValue HKEY_LOCAL_MACHINE, strKeyPath, ValueName, 0
      'WScript.Echo strComputer & ": LockUnloadServices set to: " & strValue
'   End If

'   ValueName = "UseVPUninstallPassword"

'   objReg.GetDWORDValue HKEY_LOCAL_MACHINE, strKeyPath, ValueName, strValue

'   If strValue<>0 Then
'     objReg.setDWORDValue HKEY_LOCAL_MACHINE, strKeyPath, ValueName, 0
     'WScript.Echo strComputer & ": UninstallPW set to: " & strValue
'   End If

   '----- Run MSIEXEC to remove Symantec -------------

  For Each strSymantecKey in arrSymantecKeys

     ' "%comspec% /k psexec \\" & strComputer & " MsiExec.exe /norestart /q /x " & strSymantecKey & " REMOVE=ALL", 8, true "psexec \\" & strComputer & " MsiExec.exe /norestart /q /x " & strSymantecKey & " REMOVE=ALL", 8, true
     'objShell.Run "%comspec% /k rem "

  'Print to log file
   WriteStuff.WriteLine(timeStamp & " - " & strComputer & " - Symantec Removed.")

  'objShell.Popup strComputer & " - Symantec Removed", 1
  'WScript.Echo strComputer & " - Symantec Removed"

 End If

SET objReg=Nothing

'Write to log file and close it
WriteStuff.WriteLine(vbcrlf & "Script is Done, yo!
SET WriteStuff = NOTHING
SET objShell = NOTHING

'Let user know the script is done!
WScript.Echo "SCRIPT IS DONE, YO!!!"
Question by:ThinkPaper
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 65

Accepted Solution

RobSampson earned 500 total points
ID: 18886941

As far as catching the error code goes, I would probably suggest running a batch file using
wshShell.Run "cmd /c pathtobatchfile.bat"
with the batch file having the following:
rem ==========
@echo off
psexec \\d23rbb1sring ipconfig /all > F:\Temp\ipc.txt
echo %errorlevel% > Error.txt
type Error.txt
rem ==========

You could then use vbs to open the Error.txt and read the error code.  Using a batch file
like this would also allow you to use one continuous command prompt for your commands.

As far as having PSExec act like a Run...Wait command goes, I have done something similar
to this by using a process monitoring script:
Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & "." & "\root\cimv2")

boolStillRunning = True

Do While boolStillRunning = True
      Set colProcess = objWMIService.ExecQuery ("Select Name from Win32_Process")
      boolStillRunning = False
      For Each objProcess in colProcess
            If objProcess.Name = "msiexec.exe" Then
                  boolStillRunning = True
            End If
      Wscript.Sleep 5000

Then you could run the next command, but this could get tricky if you do put
all of the commands in the same batch's kind of like switching between
vbs and batch files alot....

Hope that helps.

LVL 16

Author Comment

ID: 18917230
Thanks for the info. Unfortunately I wasn't able to put it to good use, since our SRR started, but this'll help me in the future. =)

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When asking a question in a forum or creating documentation, screenshots are vital tools that can convey a lot more information and save you and your reader a lot of time
Windows 10 Creator Update has just been released and I have it working very well on my laptop. Read below for issues, fixes and ideas.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…

724 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question