Using Windows 7 host & remotes.
Some proprietary software I use has a bug that prevents me from managing some remote computers from that software's admin console. I can re-establish my ability to manage a remote if I logon to the remote, then logoff. I could wait for them to fix their bug, but history shows me that it will take a few weeks - if they consider my problem to be critical - which it is, but they don't see it that way.
I have some choices:
PSEXEC \\remotename cmd
That gets me a cmd window on the remote. However, it doesn't actually logon as a user. Since no one is logged on, SHUTDOWN -l errors out with error code 1.
PSEXEC \\remotename some legal command
That does a fantastic job of executing some remote commands, but I haven't found any that do what I need in this situation, i.e., logon & logoff
PSSHUTDOWN \\remotename -o
That "logs off" whoever is logged on, but I haven't figured out a way to logon to the remote from a script (or batch file) - so no one is logged on.
I can easily reboot remotely ( SHUTDOWN -r -m \\remotename), but a reboot doesn't register with this software as a logoff. Note: SHUTDOWN -l only works locally; it cannot be used to logoff a remote user. Besides, there is no one logged on to the remote.
By the way, TELNET is turned off on all of our non-admin computers.
If I could, using a batch file, pass username and password with MSTSC /v:remotename I would truly log on, and could then logoff using 3rd-party software or using PSSHUTDOWN \\remotename -o
So.... I'm open to ideas - or even facts. The key to this is that I have to "fix" several hundred computers, so the solution has to involve a batch file (or script). A batch file is best, because my understanding of PowerShell is very limited ... I couldn't debug a PowerShell script if my life depended on it.
Some proprietary software I use has a bug that prevents me from managing some remote computers from that software's admin console. I can re-establish my ability to manage a remote if I logon to the remote, then logoff. I could wait for them to fix their bug, but history shows me that it will take a few weeks - if they consider my problem to be critical - which it is, but they don't see it that way.
I have some choices:
- physically logon/logoff each affected machine in the WAN, which covers several hundred computers over a 50-square mile area.
- use remote control software to logon/logoff at each workstation
- the best way - I think - is to figure out a way to do the remote logon/logoff using a script or batch file
- there is another option, but it involves a long drive, and the likelihood that I would wind up on the 5 o'clock news ;)
PSEXEC \\remotename cmd
That gets me a cmd window on the remote. However, it doesn't actually logon as a user. Since no one is logged on, SHUTDOWN -l errors out with error code 1.
PSEXEC \\remotename some legal command
That does a fantastic job of executing some remote commands, but I haven't found any that do what I need in this situation, i.e., logon & logoff
PSSHUTDOWN \\remotename -o
That "logs off" whoever is logged on, but I haven't figured out a way to logon to the remote from a script (or batch file) - so no one is logged on.
I can easily reboot remotely ( SHUTDOWN -r -m \\remotename), but a reboot doesn't register with this software as a logoff. Note: SHUTDOWN -l only works locally; it cannot be used to logoff a remote user. Besides, there is no one logged on to the remote.
By the way, TELNET is turned off on all of our non-admin computers.
If I could, using a batch file, pass username and password with MSTSC /v:remotename I would truly log on, and could then logoff using 3rd-party software or using PSSHUTDOWN \\remotename -o
So.... I'm open to ideas - or even facts. The key to this is that I have to "fix" several hundred computers, so the solution has to involve a batch file (or script). A batch file is best, because my understanding of PowerShell is very limited ... I couldn't debug a PowerShell script if my life depended on it.