CAS, Hub, and Mailbox roles are required for tests in this chapter. Also, Internet connectivity is
recommended so the test cmdlets can retrieve updates from Microsoft.
Determining Server Health
This section covers the following cmdlets:
Test-ServiceHealth
Get-ExchangeServer
The Test-ServiceHealth cmdlet queries the targeted Exchange server ??™ s roles and then checks to make
sure that the required services are running. The account that runs this cmdlet must be a member of the
Exchange Server Administrators Group as well as a local administrator on that computer. By using
the Server parameter, a remote server can be queried. If the Server parameter is not used, the cmdlet
runs the health check locally. The domain controller to query can be set via the DomainController
parameter, as well as the AD timeout value ActiveDirectoryTimeout , 15 seconds by default. This
cmdlet can be run in a monitoring mode by setting the MonitoringContext to $true . This allows the
cmdlet to pull events and performance counters. When Test-ServiceHealth is run against the local
machine, the output by default will look like Figure 14 - 1 .
??‘
??‘
Figure 14-1
Chapter 14: Troubleshooting Exchange Issues
391
W3Svc is stopped. This is particularly bad for a server with the CAS role installed.
Pages:
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539