- Aug 28, 2001
- 52,844
- 1,049
- 126
*UPDATED - VBS help needed in my last post*
I am using psexec.exe (a command line utility that remotes to machines and outputs results to the local machine). What I am doing through a .vbs on (serverA) is kick off psexec on (serverB) an aspcommandush.exe command line exe on (serverC) which deletes machines on that serverC. FYI this is for Symantec Netbackup and serverC are the various backup servers. Ultimately, I want the delete performed, as well as logging the results to serverB... equally important.
All 3 components are required in this process since all VBS doing various things are on serverA and only serverB has the share where psexec.exe to remote and grab is, as well as where I want to store the results with the >> command. ServerC is where the delete-executable (aspcommandush.exe) and actual machines-to-delete are.
Technically I can remote to serverC (the backup servers) directly and run the aspcommandush.exe to delete machines but the point of all this is someone can delete any machine on any server by inputting the server name on the web and it's passed along thru the vbs.
The problem: The >> command to log to a text file is not working. It is performing the delete just fine but the resulting output is not logging. ServerC indeed has access to serverB to write this log file because when I remote to serverC directly and run the same delete command with >> at the end, it will perform the delete AND write the log file. But this has to be dynamic, run through the vbs.
I am using psexec.exe (a command line utility that remotes to machines and outputs results to the local machine). What I am doing through a .vbs on (serverA) is kick off psexec on (serverB) an aspcommandush.exe command line exe on (serverC) which deletes machines on that serverC. FYI this is for Symantec Netbackup and serverC are the various backup servers. Ultimately, I want the delete performed, as well as logging the results to serverB... equally important.
All 3 components are required in this process since all VBS doing various things are on serverA and only serverB has the share where psexec.exe to remote and grab is, as well as where I want to store the results with the >> command. ServerC is where the delete-executable (aspcommandush.exe) and actual machines-to-delete are.
Technically I can remote to serverC (the backup servers) directly and run the aspcommandush.exe to delete machines but the point of all this is someone can delete any machine on any server by inputting the server name on the web and it's passed along thru the vbs.
The problem: The >> command to log to a text file is not working. It is performing the delete just fine but the resulting output is not logging. ServerC indeed has access to serverB to write this log file because when I remote to serverC directly and run the same delete command with >> at the end, it will perform the delete AND write the log file. But this has to be dynamic, run through the vbs.
