Let me publish my script which tests and gathers information directly from Exchange server 2010 (Windows 2008). It is my little helper in case of patching or troubleshooting. Basically it is nothing special, but let’s look at its help:
.DESCRIPTION Test-ExchangeServer2010.ps1 - filip.kasaj@tieto.com - v1.180714 This script performs test cmdlets and gathers information from Exchange Server 2010 (Windows Server 2008) into own txt log. It can be used only directly on the Exchanger server (the server role is chosen automatically). Only get and test cmdlets are used for this type of health check. Run-space: PowerShell 2.0 or Exchange Management Shell. Prerequisite: new-TestCasConnectivityUser.ps1 Tests and information: ---------------------- Always: - Get-WMIObject (Operating System, Volumes) - Get-ExchangeServer - GCM Exsetup - Test-ServiceHealth - Get-ExchangeCertificate - IIS Status - Test-PowerShellConnectivity - Test-FederationTrust - Server Services - Bad Application Events - Bad System Evenets - Top processes - CPU,MemorySize - Server Performance Mailbox role: - Get-MailboxDatabaseCopyStatus - Get-DatabaseAvailabilityGroup - Cluster /quorum - Cluster group /stat - Cluster /prop - Test-Mailflow - Test-MAPIConnectivity - Test-ReplicationHealth CAS role: - Test-OwaConnectivity - Test-ActiveSyncConnectivity - Test-WebServicesConnectivity - Test-OutlookWebServices - Test-OutlookWebServices - Test-OutlookConnectivity - Test-EcpConnectivity - Test-ImapConnectivity - Test-PopConnectivity HUB role: - Test-SmtpConnectivity - Get-Queue .EXAMPLE Test-ExchangeServer.ps1 # It performs test cmdlets and gathers information into txt log generated in C:\temp. .EXAMPLE Test-ExchangeServer.ps1 -ShowOutputLog # It performs test cmdlets and gathers information into txt log generated in C:\temp and opens the log in notepad at the end. .EXAMPLE Test-ExchangeServer.ps1 -OutputLogPath "D:\Report\ExchangeServerLog.txt" # It performs test cmdlets and gathers information into the specified log file. .EXAMPLE Test-ExchangeServer.ps1 -ShowOutputLog -OutputLogPath "D:\Report\ExchangeServerLog.txt" # It performs test cmdlets and gathers information into the specified log file and opens the log in notepad at the end.
How to use it?
Just copy the script to your Exchange server and go ahead:
Output log as its result:
How to compare logs (i.e. check the state before/after patching)?
For example via Total Commander:
Download: Test-ExchangeServer2010.ps1 – http://1drv.ms/1wI2eS4
