This cmdlet needs to be run against a server that has the Hub
role installed.
The following is a list of parameters available for this cmdlet:
DomainController : Sets the DC to query.
ExcludeRecipientTest : Boolean value that if set to true ignores the recipient objects and
queries only the configuration objects for validity.
??‘
??‘
??‘
Figure 14 - 13 shows the results for the foreach script. If the $mbxname.name is omitted, the test results
will not map an index search response time to a server, and this can become messy in larger
environments.
Figure 14-13
Part III: Working with PowerShell in a Production Environment
410
MaxReportSize : Specifies how many results will be included on the report. The report
includes all objects and properties in the ADAM instance and AD that are out of sync. By default
the -MaxReportSize is 1,000 entries.
MonitoringContext : This true/false value sets whether to include the monitoring events and
performance data. This will also pass the data onto MOM if the MOM agent is installed.
Troubleshooting Unified Messaging
Connectivity
This section discusses using the Unified Messaging test cmdlet to determine UM Health:
Test-UMConnectivity
The Test - UMConnectivity cmdlet tests the UM (Unified Messaging) component of Exchange 2007.
Because Unified Messaging and telephony may be new to some Exchange administrators, this cmdlet
should provide some comfort in troubleshooting the new component.
Pages:
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565