Thursday, December 6, 2012

New Enhancement in Exchange Server 2013 Recipients Management


New Enhancement in Exchange Server 2013 Recipients Management              


Author,
Arun Chaudhary    
MCP, MCTS, MCITP
(Exchange 2010)
Exchange Administrator, Book writer,
 Freelancer trainer of Exchange Server

About me: I am working as an Exchange Administrator & also a freelancer trainer of Exchange & other Microsoft Servers; I have 6+ years experience in Microsoft servers. I have written many articles on different – different topics & given Exchange Server training for more than 250 Indian & Inter national clients.

***************

In this article, I am going to discuss with you the enhancements for managing recipients in Exchange 2013.
           
As we know that Microsoft have already launch the beta version of Exchange Server 2013 & I have posted few articles on Exchange Server 2013 on my blog,



In this article, I am going to introduce you about the new enhancements in Exchange Server 2013 Recipients Management functionality; these are the following new enhancements in Exchange Server 2013.

Group naming policy: This feature allow administrators to create a Group Naming Policy by using Exchange Administration Centre (EAC), using this policy administrator can manage the names of distribution groups, which was created by users in your Exchange organization. You can require a specific prefix and suffix be added to the name for a distribution group when it's created, and you can block specific words from being used. So the major advantage of this policy, you can now block the inappropriate words in group names.

 ow to create Group Naming Policy: you can perform these simply steps to create a Group Naming Policy in your organization.

  1. In the EAC, select Groups | More | Configure group naming policy.
  2. Under Group Naming Policy, configure the prefix by selecting either Attribute or Text in the pull-down menu.
·             Attribute   Select the attribute and then click OK.
·             Text   Type the text string and click OK
Notice that the text string that you typed or the attribute you selected is displayed as a hyperlink. Click the hyperlink to change the text string or attribute.
  1. Click Add to add additional prefixes.
  2. For the suffix, in the pull-down menu, select either Attribute or Text, and configure the suffix.
  3. Click Add to add additional suffixes.
    After you add a prefix or suffix, notice that a preview of the group naming policy is displayed.
  4. To delete a prefix or suffix from the policy, click RemoveDelete.
  5. Click Blocked Words to add or remove blocked words.
·             To add a word to the list, type the word to block and click AddAdd symbol for excluded folders in email migration.
·             To remove a word from the list, select it and click Remove.
·             To edit an existing blocked word, select it and click Edit.
  1. When you are finished, click Save.

Make Sure that your policy is working fine, follow these simple steps:

      In the EAC, select Groups > More > Configure group naming policy.
On the Group naming policy page, the group naming policy that you defined is displayed under Preview of policy.

Use following cmdlets to verify the policy in EMS:

Get-OrganizationConfig | FL DistributionGroupNamingPolicy

Auditing Reports: Exchange Administration Centre (EAC) also have a new feature that called Auditing, so using this you can run the reports or can export the mailboxes audit logs.
These are the following benefits of this functionality:
  1. This can help you determine who has accessed a mailbox and what they have done.
  2. The administrator audit log records any action, based on an Exchange Management Shell cmdlet, performed by an administrator.
  3. This can help you troubleshoot configuration issues or identify the cause of problems related to security or compliance. 
Message Tracking: One more exiting feature of EAC, using the message tracking, you can track the message sent & received delivery report of the users. To perform this action, just select any user mailbox and then search for messages sent or received by a user. You can also make search customized by using the specific words in the subject line.
The major advantage of this feature is that you can easily find out any user messages status that message has been delivered, pending or not delivered.
Batch Moves: One more new feature of Exchange 2013 server, the new move architecture is built on top of MRS (Mailbox Replication service) moves with enhanced management capability these are the following features of batch move.
  1. You can move multiple users’ mailboxes in large batches.
  2. Email notification during move with reporting.
  3. Automatic retry and automatic prioritization of moves.
  4. Primary and personal archive mailboxes can be moved together or separately.
  5. Option for manual move request finalization, which allows you to review a move before you complete it.
  6. Periodic incremental syncs to migrate the changes.

If you find this article is valuable for you, please leave a comment & to get the new articles, please subscribe my blog & make your knowledge up to date.

                                                ***********************
                                                            Thanks
                                          Arun Chaudhary

Source: http://technet.microsoft.com/en-us/library/jj150540.aspx#BKMK_Mail

How to move File Server Witness (FSW) in Exchange Server 2010 DAG





How to move File Server Witness (FSW) in Exchange Server 2010 DAG

Author,
Arun Chaudhary
MCP, MCTS, MCITP
(Exchange 2010)
Exchange Administrator, Book writer,
 Freelancer trainer of Exchange & Windows Servers

About me: I am working as an Exchange Administrator & also a freelancer trainer of Exchange & other Microsoft Servers; I have 6+ years experience in Microsoft servers. I have written many articles on different – different topics & given Exchange Server training for more than 250 Indian & Inter national clients.

In this article, I am going to discuss with you that how to move a FSW in Exchange 2010 DAG, when any server fails in DAG scenario.
As we know that DAG in Exchange 2010 Server required File Server Witness (FSW), FSW is used to create the Majority in case of server failure in the DAG. And as we know that DAG is managed from the EMC & EMS also but it still required the fail-over clustering binaries under the hood. And the DAG is built on top of a Majority node set cluster, but we don’t use Windows fail-over cluster feature for managing the DAG. The FSW server can be any Exchange Server (recommended is HT) with a file share, which is required for the DAG members. We can also use any windows server machine as a Files Server witness, but we have to add this server in the Exchange Trusted Subsystem Universal Security Group to the local Administrators Group on the FSW Server, without installing any more service.
When we configure DAG, that time we have to provide the FSW Server information.
These are the following commands, which can help you to create the DAG, FSW & also verification of DAG & FSW.
 Run the following command to create the DAG
New-Database AvailabilityGroup -Name DAG-test -WitnessServer HT-1 -WitnessDirectory C:\FSW_DAG-test
To verify the DAG configuration, run the following commands:
Get-DatabaseAvailabilityGroup
To make the changes in FSW option in DAG-test, use the following CMDLets:
Set-DatabaseAvailabilityGroup -Identity DAG-test | Set-DatabaseAvailabilityGroup -WitnessServer HT-1
To verify the FSW options in DAG, sue this CMDLets:
Get-DatabaseAvailabilityGroup -Identity | Select Wi*
If this article makes help you to configure & move the FSW in DAG, please leave your valuable comments.
                                                            Thanks
                                                       Arun Chaudhary