image column in TSAdmin

[Guest Remko]

When I look on the processes tab in TSAdmin it seems to me that the image

name of processes is cut off when longer than 15 or 18 characters.

 

Some examples:

1) run tsadmin on windows xp, look at local processes

veryveryverylongfilename.exe is displayed as veryveryverylongfi

frameworkservice.exe is displayed as frameworkservice.e

 

So the names are cut off at 18 chars.

 

2) run tsadmin on windows xp, look at remote windows 2003 server:

amagentassist.exe is displayed as amagentassist.e

lockdownmgrsrv.exe is displayed as lockdownmgrsrv.

 

So the names are cut off at 15 chars.

 

If I run TSAdmin on the windows 2003 server the processnames are displayed

correctly. Could this be a Windows XP bug?

[Guest Soo Kuan Teo [MSFT]]

Re: image column in TSAdmin

 

If possible, please try (1) with task manager. Do you see the same issues

with task manager?

 

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"Remko" <Remko@discussions.microsoft.com> wrote in message

news:78CE96BA-1018-4FE4-81DA-1C373E629793@microsoft.com...

> When I look on the processes tab in TSAdmin it seems to me that the image

> name of processes is cut off when longer than 15 or 18 characters.

>

> Some examples:

> 1) run tsadmin on windows xp, look at local processes

> veryveryverylongfilename.exe is displayed as veryveryverylongfi

> frameworkservice.exe is displayed as frameworkservice.e

>

> So the names are cut off at 18 chars.

>

> 2) run tsadmin on windows xp, look at remote windows 2003 server:

> amagentassist.exe is displayed as amagentassist.e

> lockdownmgrsrv.exe is displayed as lockdownmgrsrv.

>

> So the names are cut off at 15 chars.

>

> If I run TSAdmin on the windows 2003 server the processnames are displayed

> correctly. Could this be a Windows XP bug?

[Guest Remko]

Re: image column in TSAdmin

 

> If possible, please try (1) with task manager. Do you see the same issues

> with task manager?

I already did, Taskmanager shows correct size. I do remember though that

taskmanager on Windows 2000 had the same issue (not sure if this was fixed in

one of the service packs).

[Guest Soo Kuan Teo [MSFT]]

Re: image column in TSAdmin

 

thanks for the info. One more question: what service packs do you have on

your XP?

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"Remko" <Remko@discussions.microsoft.com> wrote in message

news:E08E3F0C-D44D-46BF-87DE-A06B7A3C9348@microsoft.com...

>> If possible, please try (1) with task manager. Do you see the same issues

>> with task manager?

> I already did, Taskmanager shows correct size. I do remember though that

> taskmanager on Windows 2000 had the same issue (not sure if this was fixed

> in

> one of the service packs).

[Guest Remko]

Re: image column in TSAdmin

 

Windows XP with SP2 (English langauge) and up to date with Microsof Updates.

 

"Soo Kuan Teo [MSFT]" wrote:

> thanks for the info. One more question: what service packs do you have on

> your XP?

>

> --

> This posting is provided "AS IS" with no warranties, and confers no rights.

>

> "Remko" <Remko@discussions.microsoft.com> wrote in message

> news:E08E3F0C-D44D-46BF-87DE-A06B7A3C9348@microsoft.com...

> >> If possible, please try (1) with task manager. Do you see the same issues

> >> with task manager?

> > I already did, Taskmanager shows correct size. I do remember though that

> > taskmanager on Windows 2000 had the same issue (not sure if this was fixed

> > in

> > one of the service packs).

>

>

[Guest Soo Kuan Teo [MSFT]]

Re: image column in TSAdmin

 

This is very interesting. I'm not able to locate this issue internnally or

externally. Great find! I'll send this issue to the appropriate team. Can

you please share how critical is this issue to you? Does this stop you from

performing anything you need to do?

Can you also tell us which version of adminpack did you install?

 

Thanks for sharing.

Soo Kuan

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"Remko" <Remko@discussions.microsoft.com> wrote in message

news:B0FADB8F-CF8F-430B-A64B-304C100B5329@microsoft.com...

> Windows XP with SP2 (English langauge) and up to date with Microsof

> Updates.

>

> "Soo Kuan Teo [MSFT]" wrote:

>

>> thanks for the info. One more question: what service packs do you have on

>> your XP?

>>

>> --

>> This posting is provided "AS IS" with no warranties, and confers no

>> rights.

>>

>> "Remko" <Remko@discussions.microsoft.com> wrote in message

>> news:E08E3F0C-D44D-46BF-87DE-A06B7A3C9348@microsoft.com...

>> >> If possible, please try (1) with task manager. Do you see the same

>> >> issues

>> >> with task manager?

>> > I already did, Taskmanager shows correct size. I do remember though

>> > that

>> > taskmanager on Windows 2000 had the same issue (not sure if this was

>> > fixed

>> > in

>> > one of the service packs).

>>

>>

[Guest Remko]

Re: image column in TSAdmin

 

I'll give you the version numbers:

TSAdmin.exe: 5.2.3790.1830

winsta.dll: 5.1.2600.2180

rpcrt4.dll: 5.1.2600.3173

 

As far as I can see TSAdmin calls either WinStationGetAllProcesses or

WinStationEnumerateProcesses from winsta.dll. Winsta.dll calls

RpcWinStationGetAllProcesses/RpcWinStationEnumerateProcesses, Rpc functions

call NdrClientCall2. When the Rpc call arrives at Terminal Server it uses

WinStationGetAllProcessesWorker -> NtQuerySystemInformation to obtain process

information.

 

Please note that this is a blocking issue, our service desk staff has no

permissions to log onto the server. So they need TSAdmin to kill processes

from their workstations. In some cases they cannot see which process they

need to kill because the first part of the filename is identical! In these

cases they forward the calls to senior staff (which means that 1st call

resolution is not possible and senior staff is busy performing tasks they

shouldn't handle).

 

Thank you for cooperation.

[Guest Soo Kuan Teo [MSFT]]

Re: image column in TSAdmin

 

I see. Letting your service desk to have remote logon permissions to your

windows 2000/2003 may be the work around. Is there any reasons for your

service desk to have the permissions to query and kill other processes (I

assume they have permissions to logoff other sessions too), but not able to

logon remotely?

 

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"Remko" <Remko@discussions.microsoft.com> wrote in message

news:CFF6FA57-DAC7-471E-916D-19B060E0BF86@microsoft.com...

> I'll give you the version numbers:

> TSAdmin.exe: 5.2.3790.1830

> winsta.dll: 5.1.2600.2180

> rpcrt4.dll: 5.1.2600.3173

>

> As far as I can see TSAdmin calls either WinStationGetAllProcesses or

> WinStationEnumerateProcesses from winsta.dll. Winsta.dll calls

> RpcWinStationGetAllProcesses/RpcWinStationEnumerateProcesses, Rpc

> functions

> call NdrClientCall2. When the Rpc call arrives at Terminal Server it uses

> WinStationGetAllProcessesWorker -> NtQuerySystemInformation to obtain

> process

> information.

>

> Please note that this is a blocking issue, our service desk staff has no

> permissions to log onto the server. So they need TSAdmin to kill processes

> from their workstations. In some cases they cannot see which process they

> need to kill because the first part of the filename is identical! In these

> cases they forward the calls to senior staff (which means that 1st call

> resolution is not possible and senior staff is busy performing tasks they

> shouldn't handle).

>

> Thank you for cooperation.

[Guest Remko]

Re: image column in TSAdmin

 

Yes, it's company policy because the service desk staff is not considered to

be skilled enough to remote control a server. And besides they would consume

one of the available terminal session.