Training
Module
Use Microsoft Dynamics 365 Customer Service queues to manage case workloads - Training
Learn about using Microsoft Dynamics 365 Customer Service queues to manage case workloads.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
In Exchange Server, you can use the Queue Viewer in the Exchange Toolbox or the Exchange Management Shell to manage queues. For more information about queues, see Queues and messages in queues.
This topic describes how to perform the following procedures on queues:
For procedures on messages in queues, see Procedures for messages in queues.
Estimated time to complete each procedure: 5 minutes
To find and open the Exchange Toolbox, use one of the following procedures:
Windows 10: Click Start > All Apps > Microsoft Exchange Server <Version> > Exchange Toolbox.
Windows Server 2012 R2 or Windows 8.1: On the Start screen, open the Apps view by clicking the down arrow near the lower-left corner or swiping up from the middle of the screen. The Exchange Toolbox shortcut is in a group named Microsoft Exchange Server <Version>.
Windows Server 2012: Use any of the following methods:
When the shortcut appears in the results, you can select it.
To learn how to open the Exchange Management Shell in your on-premises Exchange organization, see Open the Exchange Management Shell.
For more information about using filters and identity values in the Exchange Management Shell, see Find queues and messages in queues in the Exchange Management Shell.
You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Queues" entry in the Mail flow permissions topic.
For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.
Tip
Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection.
To view queues, use the following syntax.
Get-Queue [-Filter <Filter> -Server <ServerIdentity> -Include <Internal | External | Empty | DeliveryType> -Exclude <Internal | External | Empty | DeliveryType>]
This example displays basic information about all non-empty queues on the server named Mailbox01.
Get-Queue -Server Mailbox01 -Exclude Empty
This example displays detailed information for all queues on the local Exchange server that contain more than 100 messages.
Get-Queue -Filter "MessageCount -gt 100" | Format-List
For more information, see Get-Queue and Find queues and messages in queues in the Exchange Management Shell.
The Get-QueueDigest cmdlet provides a high-level, aggregate view of the state of queues on all servers within a specific scope (for example, a DAG, an Active Directory site, a list of servers, or the entire Active Directory forest).
By default, the Get-QueueDigest cmdlet displays delivery queues that contain ten or more messages, and the results are between one and two minutes old. For instructions on how to change these default values, see Configure Get-QueueDigest.
Notes:
To view summary information about queues on multiple Exchange servers, run the following command:
Get-QueueDigest <-Server <ServerIdentity1,ServerIdentity2...> | -Dag <DagIdentity1,DagIdentity2...> | -Site <ADSiteIdentity1,ADSiteIdentity2...> | -Forest> [-Filter <Filter>]
This example displays summary information about the queues on all Exchange 2013 or later Mailbox servers in the Active Directory site named FirstSite where the message count is greater than 100.
Get-QueueDigest -Site FirstSite -Filter "MessageCount -gt 100"
This example displays summary information about the queues on all Mailbox servers in the database availability group (DAG) named DAG01 where the queue status has the value Retry.
Get-QueueDigest -Dag DAG01 -Filter "Status -eq 'Retry'"
For more information, see Get-QueueDigest.
When you retry a delivery queue, you force an immediate connection attempt and override the next scheduled retry time. For more information about the schedule retry time for queues, see Message retry, resubmit, and expiration intervals.
Notes:
In the Exchange Toolbox, in the Mail flow tools section, double-click Queue Viewer to open the tool in a new window.
In Queue Viewer, click the Queues tab. A list of all queues on the server that you're connected to is displayed.
Click Create Filter, and enter your filter expression as follows:
To retry queues, use the following syntax.
Retry-Queue <-Identity QueueIdentity | -Filter QueueFilter [-Server ServerIdentity]>
This example retries all queues on the local server with the status of Retry.
Retry-Queue -Filter "Status -eq 'Retry'"
This example retries the queue named contoso.com on the server named Mailbox01.
Retry-Queue -Identity Mailbox01\contoso.com
To verify that you have successfully retried a queue, use either of the following procedures:
In Queue Viewer, verify the values of the Status, Next Retry Time, and Last Error properties.
In the Exchange Management Shell, replace <QueueIdentity> with the identity of the queue, and use the following syntax to verify the property values:
Get-Queue -Identity <QueueIdentity> | Format-Table -Auto Identity,Status,LastRetryTime,NextRetryTime
Resubmitting a queue sends all messages in the queue back to the Submission queue for the categorizer to process. For more information about the categorizer, see Mail flow and the transport pipeline.
Notes:
To resubmit queues, use the following syntax:
Retry-Queue <-Identity QueueIdentity | -Filter "Status -eq 'Retry'" -Server ServerIdentity> -Resubmit $true
This example resubmits all messages located in any delivery queues with the status of Retry on the server named Mailbox01.
Retry-Queue -Filter "Status -eq 'Retry'" -Server Mailbox01 -Resubmit $true
This example resubmits all messages located in the Unreachable queue on the server Mailbox01.
Retry-Queue -Identity Mailbox01\Unreachable -Resubmit $true
For more information, see Retry-Queue.
To verify that you have successfully resubmitted a queue, use either of the following procedures:
In Queue Viewer, verify the properties of the queue.
In the Exchange Management Shell, replace <QueueIdentity> with the identity of the queue, and run the following command to verify the property values:
Get-Queue -Identity <QueueIdentity>
A special case for resubmitting messages is the poison message queue. You can't resubmit the poison message queue like other queues, but you can resubmit individual messages in the poison message queue.
Notes:
To resubmit a message from the poison message queue, perform the following steps.
Find the identity of the message by running the following command on the local server.
Get-Message -Queue Poison | Format-Table Identity
Use the identity of the message from the previous step in the following command.
Resume-Message <PoisonMessageIdentity>
This example resumes a message from the poison message queue that has the message Identity value of 222.
Resume-Message 222
For more information, see Resume-Message.
To verify that you have successfully resubmitted a message from the poison message queue, use either of the following procedures to verify that the message is no longer in the queue:
In Queue Viewer, view the poison message queue where you attempted to resubmit the message.
In the Exchange Management Shell, run the following command:
Get-Message -Queue Poison
If the message you resubmitted was the only message in the poison message queue, and the queue is no longer visible, that's also an indication of a successful message resubmission.
You can suspend a queue to stop mail flow, and then suspend one or more messages in the queue. For more information, see Suspend messages in queues.
Notes:
To suspend a queue, use the following syntax:
Suspend-Queue <-Identity QueueIdentity | -Filter "QueueFilter" [-Server ServerIdentity]>
This example suspends all queues on the local server that have a message count equal to or greater than 1,000 and that have a status of Retry.
Suspend-Queue -Filter "MessageCount -ge 1000 -and Status -eq 'Retry'"
This example suspends the queue named contoso.com on the server named Mailbox01.
Suspend-Queue -Identity Mailbox01\contoso.com
For more information, see Suspend-Queue.
To verify that you have successfully suspended a queue, use either of the following procedures:
In Queue Viewer, verify the queue has the Status value of Retry.
In the Exchange Management Shell, replace <QueueIdentity> with the identity of the queue, and run the following command to verify the Status property value:
Get-Queue -Identity <QueueIdentity>
By resuming a queue, you restart outgoing message delivery from a queue that has a status of Suspended.
Notes:
In the Exchange Toolbox, in the Mail flow tools section, double-click Queue Viewer to open the tool in a new window.
In Queue Viewer, click the Queues tab. A list of all queues on the server that you're connected to is displayed.
Click Create Filter, and enter your filter expression as follows:
Click Apply Filter. All queues on the server that are currently suspended are displayed.
Select one or more queues from the list, right-click, and then select Resume.
To resume queues, use the following syntax:
Resume-Queue <-Identity QueueIdentity | -Filter "QueueFilter" [-Server ServerIdentity]>
This example resumes all queues on the local server that have a status of Suspended.
Resume-Queue -Filter "Status -eq 'Suspended'"
This example resumes the suspended delivery queue named contoso.com on the server named Mailbox01.
Resume-Queue -Identity Mailbox01\contoso.com
For more information, see Resume-Queue.
To verify that you have successfully resumed a queue, use either of the following procedures:
In Queue Viewer, verify the queue doesn't have the Status value Suspended (for example, Active, Connecting, or Ready).
In the Exchange Management Shell, replace <QueueIdentity> with the identity of the queue, and run the following command to verify the Status property value:
Get-Queue -Identity <QueueIdentity>
Training
Module
Use Microsoft Dynamics 365 Customer Service queues to manage case workloads - Training
Learn about using Microsoft Dynamics 365 Customer Service queues to manage case workloads.