Home
Connecting to WebSphere MQ using Terminal Services
If you are connecting using Terminal Services to a machine running one of:
- Windows 2000 with service pack 4 or later
- Windows XP with service pack 2 or later
- Windows 2003
and you have problems creating or starting a queue manager this might be because of the introduction of a new user right, "Create global objects", in these operating systems.
The "Create global objects" user right limits the users authorized to create objects in the global namespace. In order for an application to create a global object, it must either be running in the global namespace, or the user under which the application is running must have the "Create global objects" user right applied to it.
When you connect using Terminal Services, applications run in their own local namespace. If you attempt to create a queue manager using the WebSphere MQ Explorer or the crtmqm control command, or attempt to start a queue manager using the strmqm control command, it will result in an authorization failure. This will create a WebSphere MQ FDC with Probe ID XY132002.
Starting a queue manager using the WebSphere MQ Explorer, or using the amqmdain control command, will work correctly because these commands do not directly start the queue manager. Instead the commands send the request to start the queue manager to a separate process running in the global namespace.
If we need to create or start a queue manager when connected via Terminal Services have the "Create global objects" user right. To get this right your administrator must do the following:
- Open the control panel.
- Double-click Administrative Tools. The Administrative Tools panel opens.
- Double-click Local Security Policy.
- Expand Local Policies.
- Click User Rights Assignment.
- Add the new user or group to the "Create global objects" policy.
Administrators have the "Create global objects" user right applied by default, so if you are an administrator you will be able to create and start queue managers when connected via Terminal Services without altering your user rights.
Parent topic:
WebSphere MQ security
fa12840_
Home