Some Exchange Administrators do the
perfect job with the combination of cmdlets on Server, that’s why Microsoft is
increasing the new cmdlets in Exchange server with the every new release. There
are 187 Powershell cmdlets in Exchange Server 2013 alone. With the latest
product release of 2012-2013 cycle, Microsoft has added lot of new Powershell
cmdlets in Exchange 2013 to help Administrators. So if you’re an Exchange
Administrator who is planning to deploy an Exchange 2013 Server, these 10 newly
added Powershell commands you should definitely need to know about-
1.
Get-ExchangeServerAccessLicense
By running this cmdlets you can get
the licensing report information of Exchange Server. You will receive both
reports by running Get-ExchangeServerAccessLicense
command, Enterprise and Standard edition, and CAL license for Exchange Server
2013.
2.
Get-HealthReport
You can check the health report of the
any component of Exchange 2013. For example, run the below cmdlets to determine the health report of OWA-
Get-HealthReport
–InputEntries OWA –InputObject Maintenance
This command will return you OWA
health report by exporting different information.
3.
Redirect-Message
Messaging in queue is the very usual
problem in Exchange Server that resides on users mailboxes. If you’re getting
this with a mailbox server, you can run Redirect-Message
Powershell to remove queue from the current mailbox server and add the
pending queue to another queue on a healthy Exchange mailbox server.
You only need to source and
destination server names to execute this shell command-
Redirect-Message
–Server –Target
4.
Test-MigrationServerAvailability
Exchange Server is aimed to work as larger
distributed application, so businesses might have cloud mailboxes, on-premises
mailboxes, and mailboxes which reside in external AD forests. The Test-MigrationServerAvailability command
helps to confirm that current Exchange version can communicate with external
server before trying a migration process.
5.
Get-MobileDevice
By running the command, an Exchange
administrator can make a list of all mobile devices which are associated with
the current mailbox. E.g. run the below cmdlets to get the list of mobile
devise associated with THOMAS mailbox.
Get-MobileDevice
–Mailbox "Thomas"
6.
Get-MobileDeviceStatistics
Now Administrator can identify the issue
with Exchange Active Sync, and can retrieve mobile device log files for
analysis.
Simply run the below Powershell script
to identify mobile device statistics for THOMAS mailbox.
Get-MobileDeviceStatistics
–Identity Thomas
7.
Get-PartnerApplication
Execute the command to see the list of
all registered partner application. SharePoint is the best example of partner
application, as Exchange 2013 has introduced the concept of partner
applications in Exchange server.
8.
Get-ServerHealth
Rather than check the health of
selective competent in Exchange Server, Get-ServerHealth
cmdlets helps to check the overall health of Exchange Server. You only need to provide
the name of domain controller for recognize the Exchange server which you want
to analyze. Below is the syntax for that-
Get-ServerHealth
–Identity –DomainController
9.
Set-ServerMonitor
You can monitor individual server by
simply specifying the name of server and monitor.
E.g. Run the below cmdlets to enable
the Maintenance monitor for Exchange server RXZ1
Set-ServerMonitor
–Name Maintenance –Server RXZ1
10.
New-PublicFolderMigrationRequest
If you’re upgrading to Exchange 2013
from previous version, Microsoft suggests you to migrate the public folders to
Exchange Server 2013. For execute this cmdlets you only require source database
and the .CSV file which contains exported public folder figures. (Run Export-PublicFolderStatistics.ps1 cmdlet
to create .CSV file). Below is the syntax to execute the command-
New-PublicFolderMigrationRequest
–SourceDatabase PF1 –CSVData (Get-Content C:\Data\CSVData.csv –Encoding Byte)
That’s it. However there are 200 newly
added cmdlets in Exchange 2013 which helps administrator to make their job
easier and faster, but these 10 you should definitely pay attention to if
you’re an Exchange Administrator.
Good Luck,
No comments:
Post a Comment