WTSOpenServer Windows 2000 Professional issue

[Manu]

Hi,

To get the USERNAME of all process running in local/remote system I am
using the WTSOpenServer and WTSEnumerateProcesses API's but when I invoke
the WTSOpenServer in Windows 200 Professional it s returning 1722(The RPC
server is unavailable.) error, but the same program is working fine in
Windows 2000 Advance Sever and Windows 2003.

Any idea why it is not working in Windows 2000 professional, from net in
found that Windows 2000 professional is not a "Terminal Server" but I found
in the MSDN that the above API will support in Window 2000 Professional.

Can any one can help me out..

Note : I want to get the USERNAME without WMI in both local/remote systems.

Thanks

Manu

[Willy Denoyette [MVP]]

"Manu" <di******@hotmail.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
| Hi,
|
|
|
| To get the USERNAME of all process running in local/remote system I am
| using the WTSOpenServer and WTSEnumerateProcesses API's but when I invoke
| the WTSOpenServer in Windows 200 Professional it s returning 1722(The RPC
| server is unavailable.) error, but the same program is working fine in
| Windows 2000 Advance Sever and Windows 2003.
|
|
|
| Any idea why it is not working in Windows 2000 professional, from net in
| found that Windows 2000 professional is not a "Terminal Server" but I
found
| in the MSDN that the above API will support in Window 2000 Professional.
|
|
Well, the API is supported on W2K Pro, that is, the API is there and can be
called, however, the argument must refer to a TS enabled system and W2K PRO
is not such system.

|
| Can any one can help me out..
|
|
|
| Note : I want to get the USERNAME without WMI in both local/remote
systems.
|

If you don't want to use WMI, you'll have to implement a similar
client/server architecture yourself, Windows has no API's that can be used
to query processes running on remote systems.

Willy.