Windows NT What rights needed to see process info in TSADMIN?

[Jim]

Hi,

I want to give one TS user rights to see process information under
tsadmin connections so that he can remote control and close open
programs if necessary. Does he have to be a local admin or is there
another group/rights assignment I can make? As a regular user he can't
see processes listed under other users.

TIA

 

[Vera Noest [MVP]]

I have tested it, but I believe that it is sufficient to give the
user the proper rights on the rdp-tcp connection.

Here are the details (applies to 2003 as well):

243554 - Explanation of RDP-TCP Permissions in Windows 2000
http://support.microsoft.com/?kbid=243554

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Jim <nospam@any.time> wrote on 22 aug 2007 in
microsoft.public.windows.terminal_services:

> Hi,
>
> I want to give one TS user rights to see process information
> under tsadmin connections so that he can remote control and
> close open programs if necessary. Does he have to be a local
> admin or is there another group/rights assignment I can make? As
> a regular user he can't see processes listed under other users.
>
> TIA

 

[Jim]

Hi,
Thanks for the link but it doesn't seem to apply. The remote desktop
group already has full access to the RDP connection according to the TS
configuration tool but the user cannot see processes.

Vera Noest [MVP] wrote:
> I have tested it, but I believe that it is sufficient to give the
> user the proper rights on the rdp-tcp connection.
>
> Here are the details (applies to 2003 as well):
>
> 243554 - Explanation of RDP-TCP Permissions in Windows 2000
> http://support.microsoft.com/?kbid=243554
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> Jim <nospam@any.time> wrote on 22 aug 2007 in
> microsoft.public.windows.terminal_services:
>
>> Hi,
>>
>> I want to give one TS user rights to see process information
>> under tsadmin connections so that he can remote control and
>> close open programs if necessary. Does he have to be a local
>> admin or is there another group/rights assignment I can make? As
>> a regular user he can't see processes listed under other users.
>>
>> TIA

 

[Helge Klein]

I am afraid you will have to grant admin rights to a user on Server
2003 to enable him to see other user's processes. I have not tested
this, though.

Helge

On 22 Aug., 21:59, Jim <nos...@any.time> wrote:
> Hi,
> Thanks for the link but it doesn't seem to apply. The remote desktop
> group already has full access to the RDP connection according to the TS
> configuration tool but the user cannot see processes.
>
> Vera Noest [MVP] wrote:
> > I have tested it, but I believe that it is sufficient to give the
> > user the proper rights on the rdp-tcp connection.
>
> > Here are the details (applies to 2003 as well):
>
> > 243554 - Explanation of RDP-TCP Permissions in Windows 2000
> >http://support.microsoft.com/?kbid=243554
>
> > _________________________________________________________
> > Vera Noest
> > MCSE, CCEA, Microsoft MVP - Terminal Server
> > TS troubleshooting: http://ts.veranoest.net
> > ___ please respond in newsgroup, NOT by private email ___
>
> > Jim <nos...@any.time> wrote on 22 aug 2007 in
> > microsoft.public.windows.terminal_services:
>
> >> Hi,
>
> >> I want to give one TS user rights to see process information
> >> under tsadmin connections so that he can remote control and
> >> close open programs if necessary. Does he have to be a local
> >> admin or is there another group/rights assignment I can make? As
> >> a regular user he can't see processes listed under other users.
>
> >> TIA

 

[Vera Noest [MVP]]

Mmm, I was a bit afraid of this. See now that I also made a typo,
meant to write "I haven't tested this, but...".

But the users should be able to logoff or reset other users's
sessions, correct? Just not kill individual processes.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Jim <nospam@any.time> wrote on 22 aug 2007 in
microsoft.public.windows.terminal_services:

> Hi,
> Thanks for the link but it doesn't seem to apply. The remote
> desktop group already has full access to the RDP connection
> according to the TS configuration tool but the user cannot see
> processes.
>
> Vera Noest [MVP] wrote:
>> I have tested it, but I believe that it is sufficient to give
>> the user the proper rights on the rdp-tcp connection.
>>
>> Here are the details (applies to 2003 as well):
>>
>> 243554 - Explanation of RDP-TCP Permissions in Windows 2000
>> http://support.microsoft.com/?kbid=243554
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> Jim <nospam@any.time> wrote on 22 aug 2007 in
>> microsoft.public.windows.terminal_services:
>>
>>> Hi,
>>>
>>> I want to give one TS user rights to see process information
>>> under tsadmin connections so that he can remote control and
>>> close open programs if necessary. Does he have to be a local
>>> admin or is there another group/rights assignment I can make?
>>> As a regular user he can't see processes listed under other
>>> users.
>>>
>>> TIA

 

[Jim]

Yes, they could logoff or reset but in this case a certain process being
present implies that the user has left open database files that could be
damaged if the application is not cleanly closed. It definitely works if
the user is local admin so that's the way it will have to be

Thanks for the input.

Vera Noest [MVP] wrote:
> Mmm, I was a bit afraid of this. See now that I also made a typo,
> meant to write "I haven't tested this, but...".
>
> But the users should be able to logoff or reset other users's
> sessions, correct? Just not kill individual processes.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> Jim <nospam@any.time> wrote on 22 aug 2007 in
> microsoft.public.windows.terminal_services:
>
>> Hi,
>> Thanks for the link but it doesn't seem to apply. The remote
>> desktop group already has full access to the RDP connection
>> according to the TS configuration tool but the user cannot see
>> processes.
>>
>> Vera Noest [MVP] wrote:
>>> I have tested it, but I believe that it is sufficient to give
>>> the user the proper rights on the rdp-tcp connection.
>>>
>>> Here are the details (applies to 2003 as well):
>>>
>>> 243554 - Explanation of RDP-TCP Permissions in Windows 2000
>>> http://support.microsoft.com/?kbid=243554
>>>
>>> _________________________________________________________
>>> Vera Noest
>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>> TS troubleshooting: http://ts.veranoest.net
>>> ___ please respond in newsgroup, NOT by private email ___
>>>
>>> Jim <nospam@any.time> wrote on 22 aug 2007 in
>>> microsoft.public.windows.terminal_services:
>>>
>>>> Hi,
>>>>
>>>> I want to give one TS user rights to see process information
>>>> under tsadmin connections so that he can remote control and
>>>> close open programs if necessary. Does he have to be a local
>>>> admin or is there another group/rights assignment I can make?
>>>> As a regular user he can't see processes listed under other
>>>> users.
>>>>
>>>> TIA