Share via

Managing queues

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Managing queues

The Computer Management snap-in or the Active Directory Users and Computers snap-in is used to manage and administer queues. For more information, see Administration overview.

Creating queues

There may be certain restrictions on creating queues on computers that are determined during Message Queuing Setup. For more information, see Access control for Message Queuing.

For information on how to create, delete, or find a queue, see Create queues, Delete queues, and Find queues.

Viewing queues

The operation of viewing the contents of a queue from the same computer on which the queue is located is called local reading. The operation of accessing the contents of a queue from a computer other than the one on which the queue is located is called remote reading.

You can view the contents of only those queues that you have sufficient permissions to open. Therefore, there can be public queues whose contents are not visible in the snap-ins. For more information, see Access control for Message Queuing.

By default, any user with the Get Properties permission for the msmq object can view the queue status of local outgoing queues. To limit this default, you can do either of the following:

  • Change users' Get Properties permissions for the msmq object.

  • In the registry, add the dword RestrictAdminAPI with a registry value of 1, under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Msmq\Parameters. This restricts the ability to view the queue status of active outgoing queues to local administrators, regardless of security permissions for the msmq object.

    Caution

    • Incorrectly editing the registry may severely damage your system. It is recommended that you back up any valuable data on the computer before making changes to the registry.

  • After setting the registry, restart the Message Queuing service for the changes to take effect.

Viewing internal private queues and outgoing queues

There are certain internal private queues that are used exclusively for internal operation, and the Active Directory Users and Computers and Computer Management snap-ins do not display any internal private queues. For more information, see Internal private queues and outgoing queues.

Outgoing queues on a computer are used to store messages temporarily before the messages are sent to their destinations. Outgoing queues are visible only when using the Computer Management snap-in. However, transactional messages in outgoing queues cannot be viewed from Computer Management.

Pausing and resuming queues

You can pause and then later resume the operation of a local outgoing queue, thereby deferring the sending of messages from that queue to the corresponding destination queue. This way, you can send all pending messages to a destination queue at a later time. For information on how to pause or resume an outgoing queue, see Pause or resume an outgoing queue.

You can also take Message Queuing offline from the network. When you take Message Queuing offline from the network, you pause the operation of all outgoing queues on the local computer. This is useful when you communicate over a slow, expensive connection and want to defer sending messages in all outgoing queues on the computer to a later time. For information on how to take Message Queuing offline from the network for a computer, see Take outgoing queues offline.

Managing queues with triggers

When you delete a queue, the triggers associated with that queue are not deleted. If you later re-create a queue of the same name, any existing triggers will be used by this queue. However, this re-created queue will not be monitored by the Message Queuing Triggers service until the computer is restarted, or the associated triggers disabled and then enabled again. For instructions on setting the enabled or disabled property for a trigger, see View or change properties of triggers and rules for triggers.