Before PowerShell, performing an automated install would have required knowledge of
batch scripts, Visual Basic, and a hodgepodge of unattended files and still would not have provided the
same result as using PowerShell. Using PowerShell in conjunction with system and application
commands provides for an easier, more efficient use of scripts to perform common administrative tasks.
The power of having .NET functionality built in allows for manipulation of variables, objects, and data
that is more robust and has a better framework.
(continued)
Troubleshooting
Exchange Issues
This chapter deals with troubleshooting Microsoft Exchange Server 2007 through the use of
cmdlets. Microsoft has created several test cmdlets that allow the system administrator to
programmatically test various Exchange roles and services. These cmdlets are built into Exchange.
No longer do you need to write cumbersome multilanguage test scripts! This chapter covers
the following:
Determining server health
Determining Exchange system health
Testing anti - spam functions
Troubleshooting Client Access Server Role functions
Testing Web Services
Troubleshooting MAPI connectivity
Testing Mailflow
Testing the Exchange Search service
Troubleshooting edge synchronization
Troubleshooting Unified Messaging connectivity
Using Get-EventLog
Using Get-Message
Tracking messages
Working with event log levels
??‘
??‘
??‘
??‘
??‘
??‘
??‘
??‘
??‘
??‘
??‘
??‘
??‘
??‘
Part III: Working with PowerShell in a Production Environment
390
To receive the greatest benefit from these cmdlets, a fully configured Exchange environment is required.
Pages:
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538