Database Search

match allmatch any Look in all areasLook in current areas Check all datesPrevious dayPrevious 3 daysPrevious weekPrevious fortnightPrevious monthPrevious 2 monthsPrevious 3 monthsPrevious half-yearPrevious year

TechHome

• !!NEWSFLASH!!
• Availability of Terminal Services
• Detect if Session is Locked
• Determine Active Window In A Citrix Session
• How to Detect WTS
• Identify Citrix Server
• Memory leak in wtsQuerySessionInfo
• NT4 Citrix server and Error 116
• Run Terminal Extender on Non Terminal Service Machine
• Shadow Terminal Server User
• UDF to get Citrix Session Information
• wtsEnumProcesses Error 107
• wtsSendMessage and Win7
• wtsShutdownSystem

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

wtsSendMessage and Win7

 Keywords: wtsSendMessage Win7 RPC Server Unavialable Terminal Services Remote Desktop Services msg.exe psexec.exe

---

Question:

I see that Microsoft has removed the Messenger service in Win7. I would like to send a message to a remote system. Does anyone have any tips on how to use the Terminal Service, wtsSendMessage on Windows 7? When I try and query a Win 7, it fails with Error 103, Unable to open terminal server handle. If I click on More Error Info I get : 6BA "WTSOpenServerAX() : WWWTS_OpenServer().

Answer:

Terminal Services has been renamed Remote Desktop Services. Reference: http://msdn.microsoft.com/en-us/library/windows/desktop/dd979766(v=vs.85).aspx.

The extended error 6BA is the Hex equivalent of the error 1722. The Windows System error 1722 indicates:

1722 The RPC server is unavailable.  RPC_S_SERVER_UNAVAILABLE 

This error is returned if a remote computer was specified in the lpServer parameter and the RPC server is not available.

By default remote RPC is disabled on Windows 7. It can be enabled by setting the 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server' value 'AllowRemoteRPC' to 1. However, this will only get you another error - 0x721 - which I am guessing is caused by Windows 7 not allowing 'nul' user access. There are several possible ways around this problem but I haven't tried any of them. One approach would be to add credentials from remote machines to the credential cache on the sending machine but I don't know how practical that is. There may be a way to allow 'nul' user access but that is probably not a good idea either.

For what it is worth, one reported solution is to use syteminternal's psexec.exe and the built-in msg.exe command line tool to display message on the remote system. It does have the advantage of circumventing the RPC issue but I don't know that it would not just generate its own set of annoyances.

User Reply:

It was the AllowRemoteRPC key change to 1.

---

Article ID:   W17608

Filename:   wtsSendMessage and Win7.txt

File Created: 2013:01:15:10:23:40

Last Updated: 2013:01:15:10:23:40