(same guy, different account)
Using task to run a command like this would run as a batch file on the remote system. Getting a return of 9009 would mean that the path/file does not exist on the target system. If this is the only command being run, it would mean the target system does not have this path/file. I'm wondering why its returning 9009.
Can we do a couple of things?
- In the Task, add this as the first line: ECHO.>C:\test.tag
This will place a file called test.tag on the C: drive (assuming there is a C drive) allowing us to make sure the task is making it correct system. We've seen issues where NetBIOS/FQDN provide an IP address, but it belongs to a different system.
- Copy the contents of the Task to a file called Test.cmd on the expected target system. Then run it manually.
Keep track of: What happens? Did the test.tag file get created? Was there an error?
I should change my name to Curious George for this conversation. :)