RE: Spam:Spam:RE: Terminal Services Namespace Problem

Unfortunately I do know this. Thanks for your help. An easy way to see this is to use WinOBJ (www.sysinternals.com/ntw2k/freeware/winobj.shtml) to view kernel namespace objects while on a console and while in a terminal server session. If you look at the ‘??’ or global namespace object list and then plugin a Pnp device, the new Pnp device will show up in the console session, but not in the terminal server session (when using 2000).

If you log off the terminal server session then log in, and look again in WinOBJ, the new device will show up in the list.

In 2003 Server, the device is immediately in the list.

Thanks again,
Marc

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Ceri Coburn
Sent: Tuesday, July 06, 2004 10:22 AM
To: Windows System Software Devs Interest List
Subject: Spam:Spam:RE: [ntdev] Terminal Services Namespace Problem

Hi,

I do know that kernel object in XP (fast user switching, remote desktop) and in NT , 2000, etc…(Terminal Services) need a Global\ prefix in front of the name when creating the object to make it accessible to all user contexts on the system. As opposed to Local\ which is the default if omitted I think.

Regards,
Ceri


From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Marc Zapf
Sent: 06 July 2004 15:07
To: Windows System Software Devs Interest List
Subject: [ntdev] Terminal Services Namespace Problem

Hello all, ?

I am having an issue with the kernel namespace in Windows 2000.? If a PnP device becomes on a Terminal server, any logged in users cannot access the device.? Even if the device manager list is refreshed so that the device is shown in each session’s device manager, the device’s kernel object name is not in any of the terminal server sessions kernel namespace (while the console’s kernel namespace does contain the device’s kernel object name).? If a new user logs in, the kernel namespace for that session will contain the device’s kernel object name.

This is not the case in Windows 2003.? As device’s become available, logged in user’s see the device and each session’s kernel namespace is updated with the new device’s kernel object name.

Does anyone know how to refresh or update a terminal server session’s kernel namespace object list programmatically?? It seems that in Windows 2000, a user would be forced to log out and log in to do this simple task.

Marc


Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@first4internet.co.uk
To unsubscribe send a blank email to xxxxx@lists.osr.com


This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email



This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email



Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: mzapf@go-eol.com
To unsubscribe send a blank email to xxxxx@lists.osr.com