Sysinternals Homepage
Forum Home Forum Home > Sysinternals Utilities > PsTools
  New Posts New Posts RSS Feed: Psshutdown message and terminal services clients
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Psshutdown message and terminal services clients
 Post Reply Post Reply
Author
Message Reverse Sort Order
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
SvenBomwollen View Drop Down
Senior Member
Senior Member


Joined: 29 August 2008
Location: Germany
Online Status: Offline
Posts: 1400 		Post Options Post Options   Quote SvenBomwollen Quote  Post ReplyReply Direct Link To This Post Topic: Psshutdown message and terminal services clients
    Posted: 20 January 2009 at 11:12am
Hello, Jim.

Thanks for reporting your solution. Good to know the issue can be solved and has been solved. Smile

Kind regards,
SvenBomwollen
Back to Top
jbserck View Drop Down
Newbie
Newbie
Avatar

Joined: 18 December 2008
Location: United Kingdom
Online Status: Offline
Posts: 4 		Post Options Post Options   Quote jbserck Quote  Post ReplyReply Direct Link To This Post Posted: 20 January 2009 at 9:49am

We have solved this at last.

Psexec now works for us, after we included the "-accepteula" switch in the command line. (It runs non-interactively under the "NT AUTHORITY\SYSTEM" account.)

Thanks for your help.

Jim.
Back to Top
SvenBomwollen View Drop Down
Senior Member
Senior Member


Joined: 29 August 2008
Location: Germany
Online Status: Offline
Posts: 1400 		Post Options Post Options   Quote SvenBomwollen Quote  Post ReplyReply Direct Link To This Post Posted: 23 December 2008 at 11:15pm
Hi, Jim.

Thanks for clearing this up. It reads as if I will have to re-run my test and use a Windows 2003 Std SP2 server as a local machine as well and report back thereafter. Embarrassed

<Added>
I have just done so. I.e. local machine and remote target machine run on Windows 2003 Std SP2 64bit. psexec v1.94 used on the local machine.
Result:
Same as reported above. No access violation on either side.
</Added>

Sven



Edited by SvenBomwollen - 24 December 2008 at 11:37am
Back to Top
jbserck View Drop Down
Newbie
Newbie
Avatar

Joined: 18 December 2008
Location: United Kingdom
Online Status: Offline
Posts: 4 		Post Options Post Options   Quote jbserck Quote  Post ReplyReply Direct Link To This Post Posted: 23 December 2008 at 5:31pm

Hi Sven,

We are using psexec 1.94 on all servers including the server where the failing psexec command is entered.

The op sys is 64 bit Win 2003 Server Standard edition SP2 for the server executing the psexec command and also the target server is the same op sys.

Regards,

Jim.
Back to Top
SvenBomwollen View Drop Down
Senior Member
Senior Member


Joined: 29 August 2008
Location: Germany
Online Status: Offline
Posts: 1400 		Post Options Post Options   Quote SvenBomwollen Quote  Post ReplyReply Direct Link To This Post Posted: 22 December 2008 at 10:28am
Hi, Jim.

So I revealed that I am still using an older version of "mstsc.exe" which still understands "/console", but not "/admin". Embarrassed

Can you give two details, please, on the psexec access violation on the local machine:
+ Which psexec version? (v1.94?)
+ Which OS version? (Win2003 64bit, too?)

I have just tried to run your commandline towards one of our 64bit Windows 2003 Std SP2 servers. It worked perfectly. (Reboot aborted a few seconds after scheduling it in order not to be shot by our Windows admins.)

Local machine where the psexec commandline was typed: Windows XP Pro SP2, psexec v1.94

Kind regards,
Sven





Edited by SvenBomwollen - 22 December 2008 at 10:30am
Back to Top
jbserck View Drop Down
Newbie
Newbie
Avatar

Joined: 18 December 2008
Location: United Kingdom
Online Status: Offline
Posts: 4 		Post Options Post Options   Quote jbserck Quote  Post ReplyReply Direct Link To This Post Posted: 22 December 2008 at 9:44am

Thanks Sven,

I confirm that admin users do see psshutdown's message when they have logged on using "mstsc /admin" (previously I was mistakenly using the "/console" switch, which I think has recently been superseded by "/admin").

Our problem with psexec is that it suffers an access violation on the machine where the command is entered (not on the target). I have the Dr Watson log & dump. The command line is

psexec -u "user" -p "password" \\target shutdown.exe /s /f /t 600

The OS for all machines is 64 bit Win 2003 Server Standard SP2

Regards,
Jim.

Edited by jbserck - 22 December 2008 at 9:44am
Back to Top
SvenBomwollen View Drop Down
Senior Member
Senior Member


Joined: 29 August 2008
Location: Germany
Online Status: Offline
Posts: 1400 		Post Options Post Options   Quote SvenBomwollen Quote  Post ReplyReply Direct Link To This Post Posted: 19 December 2008 at 4:54pm
Hello, jbserck.

Sorry to say so, but to the best of my knowledge there is no way of making psshutdown display the announcement message on the desktops of all currently logged on users on a terminal server.
(The user logged on to the console via "mstsc /v:servername /console" saw the psshutdown message box and was allowed to cancel the scheduled shutdown. Have just tested it towards a Win2003 Std SP2 server, 32bit).

Anyway, this does not fulfill your requirements. So returning to the previous procedure of launching shutdown.exe remotely with the help of psexec may be the better approach. But, you write:
However we have not been able to make psexec work with 64 bit Windows Server 2003,
I wonder what exactly happened? Which error message(s) did you receive when you tried to launch shutdown.exe remotely with the help of psexec.exe?

Have just tested it here: I can successfully run remote commands on a Win2003 Std SP2, 64bit, server using psexec. Yet, as this is a production machine, I was a bit loathe to test the shutdown.exe.

Nonetheless, I would not be amazed if trying to fix the psexec issues which you experienced would bring more joy than waiting for a future release of psshutdown which might be able to replicate the behaviour of shutdown.exe.

Kind regards,
Sven
Back to Top
jbserck View Drop Down
Newbie
Newbie
Avatar

Joined: 18 December 2008
Location: United Kingdom
Online Status: Offline
Posts: 4 		Post Options Post Options   Quote jbserck Quote  Post ReplyReply Direct Link To This Post Posted: 18 December 2008 at 5:08pm

How can we make 'psshutdown -c -t 300 -m "message"' produce a message dialogue (+ cancel button) for users who are logged on as terminal services clients?

We are using psshutdown for a group of 64 bit Windows 2003 servers to shut them down when the remaining charge in a UPS batteries has become too low. The shutdown occurs after the required timeout, but the message box only appears for the user logged on to the console, not ones logged on as Remote Desktop users. Even clients connected using "mstsc.exe /console" do not see the message.

In the past, when they were 32 bit servers, we used psexec to call the MS shutdown program, which does produce a message for terminal services client users. However we have not been able to make psexec work with 64 bit Windows Server 2003, which is why we have changed to psshutdown.



Edited by jbserck - 18 December 2008 at 5:09pm
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down