You must be thinking do we get to see help and example for an Exchange Power Shell command. Yes, exchange 2010 gives more visibility to the commands and the usage of it. Let us now cover briefly on how to get help of any command that is at your interest. Get-help and Get-Command are the cmdlets used in Exchange 2010 Management Shell to view the help topics about exchange 2010 shell commands.
If you wanted to view the help/syntax about any cmdlet in Exchange 2010 you can use the Get-Help command, for example below combination will give the help topics about the command New-Mailbox
If you wish to see some examples on New-Mailbox cmdlet, you can append the –example parameter to the above command.
Get-Help New-Mailbox –examples
Now for instance we may want to see the list of exchange commands which has some criteria. For example, let us see how to view the list of exchange cmdlets which contains ‘Mailbox’ in it. We can use the command Get-Excommand for generating this list.
The default replication port used by the Exchange 2010 DAG is 64327. Most of us know that in Exchange 2007 it uses the port 445 for log shipping, over SMB.
You also have flexibility to change the port no used in Exchange 2010 DAG replication. To change the DAG replication port number, please follow the steps below.
Execute the cmdlet Set-DatabaseAvailabilityGroup from the Exchange Management Shell, by specifying the new port number.
Syntax: - Set-DatabaseAvailabilityGroup -Identity DAGID –ReplicationPort
You can specify any number between 1 and 65535 as the port number. You may also have to modify your Windows firewall to allow the DAG replication port, if not you will face issues. If you plan to modify the port no, please do plan the firewall rules to avoid any outage.
Know your exchange 2010 ports, see more Exchange Network Port Reference
As you all would know the interesting features of Exchange 2010, and the improvements that are brought by introducing the Service Pack 1(sp1). Let us now see some really helpful improvement about database repair with Exchange 2010 SP1.
The functionality provided by ISInteg in 2003 or 2007 exchange server is now rolled into two Exchange Management Shell commands in Exchange 2010 SP1, which are
Looking at the above cmdlets you can make out that the commands will be executed against the mailboxes, and with the databases. This new approach removes the need of dismounting the database when we run the ISInteg cmdlets.
This is one of the much talked about subjects in earlier version of exchange. Now with Exchange 2007 and Exchange 2010 you can achieve it easily. Follow the below simple steps to configure OWA authentication to use only "Username" and "Password", instead of using "Domain\user name" and "password"(default setting).
Let us have a look at how the Outlook Web App Login page before we do any modification.
Complete the below steps to configure OWA login without domain.
Microsoft has introduced a new feature called Administrator Audit Logging in Exchange 2010. You can use administrator audit logging to log when a user or an administrator runs a cmdlet. This helps you to track the changes that are done, and the person who done the changes etc. Cmdlets are logged that are run directly on Exchange Management Shell(EMS), or when an actions executed in Exchange Management Console(EMC), or when an operation performed using the Exchange web management. Because regardless where these actions are performed it all run cmdlets in background.
Get commands are not logged, also if there are errors during the operation performed those may also be not logged. The log files are stored in a mailbox. So that the log can be accessed anywhere and it does not demand for the access to a logfile path.
Do you know the list of cmdlets in Exchange 2010, if not refer - Exchange 2010 Cmdlets
OWA does not stands for Outlook Web Access anymore! It stands for Outlook Web App from Exchange 2010. Yes I know, no one gives much care for what it stands for, whereas we all cares what's new in it, isn't it?
Microsoft brought new features, functionalities and lot more in Exchange 2010, one of these feature is discussed here. The Exchange Control Panel.