Share via


Run the Exchange 2010 UM Troubleshooting Tool on Windows 7 or Windows Vista

 

Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

The Microsoft Exchange 2010 UM Troubleshooting Tool is an Exchange Management Shell cmdlet named Test-ExchangeUMCallFlow. You can use the cmdlet to diagnose configuration errors specific to call answering scenarios and to test whether voice mail is functioning correctly in both on-premises and cross-premises Microsoft Exchange Server 2010 Service Pack 1 (SP1) UM deployments. You can use this cmdlet in deployments with Microsoft Office Communications Server 2007 R2 or Microsoft Lync Server 2010 or in UM deployments with IP gateways or IP PBXs.

Prerequisites

Run the UM Troubleshooting Tool on Windows 7 or Windows Vista

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "UM server" entry in the Unified Messaging Permissions topic.

  1. Click Start > All Programs > Accessories > Windows PowerShell.

  2. Right-click Windows PowerShell, and from the pop-up menu select Run as administrator.

  3. At the PowerShell command prompt, go to the folder where the UM Troubleshooting Tool was installed and run the following.

    C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -psconsolefile .\Microsoft.Exchange.UM.TroubleshootingToolsnapin.psc1 -noexit -command ". '.\Microsoft.Exchange.UM.TroubleshootingTool.ps1' "
    
  4. If you're running the UM Troubleshooting Tool on Windows 7, at the PowerShell command prompt, run the following:

    Set-ExecutionPolicy RemoteSigned
    
  5. Open the Microsoft Exchange 2010 UM Troubleshooting Tool from the Start menu.

  6. In the Microsoft Exchange 2010 UM Troubleshooting Tool window, at the prompt, type the following and press Enter.

    $cred=Get-Credential
    
  7. In the Windows PowerShell Credential Request window, type the domain\user name and password and click OK.

  8. In the Microsoft Exchange 2010 UM Troubleshooting Tool window, specify the necessary cmdlet parameters to test for call flow. For example:

    Test-ExchangeUMCallFlow -Mode SIPClient -CallingParty tonysmith@contoso.com - CalledParty jamiestark@contoso.com NextHop ocsfe.contoso.com -Credential $cred
    

Other Tasks

After you set the credentials for the UM Troubleshooting Tool, you may also want to:

 © 2010 Microsoft Corporation. All rights reserved.