This took care of it... I have tested a Windows XP client and it can
now see the session properties. Thanks for that. I had started to
think this may just be a limitation, since I noticed that Qwinsta, and
terminal services manager were not able to get this information
either. Now they can all access the info.
Have you noticed that if a local user is logged into the machine you
get some inconsistent data? It seems some of the properties report
correctly and some report incorrectly.
I am trying to figure out if there is a way to determine whether the
user is logged in locally, or remote using any of the available data.
If this isn't something you have already determined... I'll figure out
if it's possible. It may be a limitation in the Remote Desktop
Services API.
Thanks,
On Jun 13, 9:04 pm, Dan Ports <
danpo...@gmail.com> wrote:
> Mathew,
>
> Just to clarify: you're trying to invoke .GetRemoteServer(some XP/Vista/7
> machine).GetSessions() and you're getting an access denied error, right?
>
> On client versions of Windows, this is often caused by the AllowRemoteRPC
> registry entry<
http://technet.microsoft.com/en-us/library/ff710472(WS.10).aspx>not
> being set appropriately. Windows XP will require a reboot for changes
> to
> that registry key to be effective; Vista and 7 should not.
>
> Does that help?
>
> Dan
>