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


Sunday, October 28, 2012

Some Common Issue of Outlook User’s



Some Common Issue of Outlook User’s


Error 1: Profile name is already exists:

When you create and delete a profile for the same user several times, you might end up by getting an error message saying “The profile name you entered already exists. Enter a different profile name.” even though you can’t see the profile in the Control Panel.
This is caused by Outlook not completely removing the profile information from the system, more specifically from the Registry. To fix this, navigate to
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles

              And delete the key with the name matching the user that you are trying to create a profile for!

Error 2:
Ø  When I delete an e-mail from the shared mailbox I manage, the e-mail goes into my Deleted Itemsfolder instead of the folder in the shared mailbox;
Ø  When I send an e-mail as (SendAs) the shared mailbox I manage, the e-mail goes into my Sent Itemsfolder instead of the folder in the shared mailbox

If you ever get users complaining about any of the following cases, please note that to resolve it all you have to do is add/update a registry key on the user's PC:
The following applies to Outlook 2007:

Change the Sent Behavior

1.        Open the Registry and navigate toHKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Preferences\
2.        Look for the DelegateSentItemsStyle DWORD (if it doesn’t exist, create it)
3.        Set the value to 1
4.        Restart Outlook

 Now any e-mails sent from that shared mailbox (again, when using SendAs permissions) will go into theSent Items folder of the shared mailbox.

IMPORTANT: After you set the DelegateSentItemsStyle registry value to 1, the functionality is only available when the Exchange account is set to Use Cached Exchange Mode. The DelegateSentItemsStyle registry value will not work consistently on an Exchange account that is configured in Online mode...

 Change the Deleted Behavior

1.        Open the Registry and navigate to    HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\General
2.        Look for the DelegateWastebasketStyle DWORD (if it doesn’t exist, create it)
3.        Change its value to
a.        8 - Stores deleted items in your folder
b.        4 - Stores deleted items in the shared mailbox folder
4.        Restart Outlook

 Now any e-mails deleted from that shared mailbox will go into the Deleted Items folder of the shared mailbox.

IMPORTANT: make sure that the delegate user has at least Author level rights for the Deleted Items folder of the owner's mailbox. If the delegate does not have these rights, and this registry option is set to 4, then either the item is deleted permanently or the user receives an error message

Error 3: Troubleshoh@gmail.comoting Outlook Calendar Problems

If your users are experiencing issues with their Outlook Calendar, Microsoft recently released a tool to help administrators in these situations, the Calendar Checking Tool for Outlook (also known as CalCheck).
This is a command-line tool that opens an Outlook profile on the local machine, opens the Outlook Calendar and checks permissions, free/busy information and auto booking, for example. The tool then checks each item in the calendar for any problems.
The calendar to by analyzed must reside on an Exchange Server and this tool does not work with IMAP, POP3 or any other non-Exchange mail servers.

DOWNLOAD: To download the simply,

Instructions

Instructions for how to use this tool:

After you install this download, open a Command Prompt window in the directory that contains the CalCheck.exe file. To obtain detailed instructions, type the calcheck /? command in the Command Prompt window, and then press Enter. 



Here is a list of command-line switches for CalCheck.exe:

CalCheck [-P
 <Profile name>] [-M <Mailbox name>] [-S <Server name>] [-O<path>] [-A] [-F] [-R] [-V] [-No]
CalCheck -?

If you found this information valuable, please leave your comments for me.


                                                                      Thanks
                                                              Arun Chaudhary
                                                 Email me: arunkalagarh@gmail.com 
                              

Very Useful Exchange Cmdlets


                                
Some useful EMS Cmdlets to get the valuable information from Exchange Server 2010, as per your Organization requirements:

Number of E-mails Sent and Received by one User

This is very powerful script used to check the Send & Receive Emails by a user:


[Int] $intSent = $intRec = 0
Get-TransportServer | Get-MessageTrackingLog -ResultSize Unlimited -Start “10/01/2012” -End “11/01/2012” -Sender " arun@excEvehangeby-arun.com" -   EventID RECEIVE | ? {$_.Source -eq "STOREDRIVER"} | ForEach { $intSent++ }
Get-TransportServer | Get-MessageTrackingLog -ResultSize Unlimited -Start “10/01/2012” -End “11/01/2012” -Recipients " arun@exchangeby-arun.com" -EventID DELIVER | ForEach { $intRec++ }



                                Get Recoverable Items folder size per Database

This script is used to get the size of recoverable items of per Mailbox-Database:

Get-MailboxFolderStatistics nuno –FolderScope RecoverableItems | Select Identity, FolderAndSubfolderSize
[Int] $total = 0
(Get-Mailbox -Database MDB16 -ResultSize Unlimited) | ForEach {$total += (Get-MailboxFolderStatistics $_ -FolderScope RecoverableItems | ? {$_.Identity -match "Recoverable Items"}).FolderAndSubfolderSize.ToMB()}
$total




This script is used to update or modified the IP Address on Exchange Receive Connector:

# Get Receive Connectors to update
$recCons= Get-ReceiveConnector | Where {$_.Name -match"Unauthenticated SMTP"}
ForEach ($recConin$recCons)
{
      Write-Host"Updating", $recCon.Identity
       $recCon.RemoteIPRanges -="10.101.74.10"
      $recCon.RemoteIPRanges -="10.102.34.12"
       Set-ReceiveConnector $recCon -RemoteIPRanges$recCon.RemoteIPRanges
}




This script is used to create a Transport Rule in Exchange Serve 2010:

New-TransportRule “Block Non Delivered e-mails from Nuno” -Comments ”Prevent Nuno from forwarding NDRs e-mails” -From “nuno@letsexchange.com” -SentToScope “NotInOrganization” -SubjectContainsWords “FW: There was an error sending your mail”, “FW: Mail delivery failed”, “FW: failure notice” -RedirectMessageTo “quarantine@letsexchange.com”-Enabled $True



This script is used to check the full access permissions to any other User-Mailbox:

Get-Mailbox -Resultsize Unlimited | Get-MailboxPermission -User | ? {$_.AccessRights -match "FullAccess" -and$_.IsInherited -eq $False} | Select Identity
ForEach ($mbx in (Get-Mailbox -Resultsize Unlimited | Select Identity)) {Get-MailboxPermission $mbx.Identity -User | ? {$_.AccessRights -match "FullAccess" -and $_.IsInherited -eq $False} | Select Identity}



This script is used to make the comparisons between the Primary & Secondary IP Address:

[String] $strPrimaryAddress
[String] $strSIP
[Array] $arrCollection = @()

ForEach ($mbx in (Get-Mailbox -ResultSize Unlimited))
{
       # Initialize object to hold all the information
       $mbcomb = "" | Select "Display Name", "Primary SMTP Address", "SIP"
      
       # Reset variables
       $strPrimaryAddress = $strSIP = $NULL

       # Check all the e-mail aliases the user has
       $mbx.EmailAddresses | ForEach {
              If ($_.IsPrimaryAddress -and $_.Prefix -match "SMTP") { $strPrimaryAddress = $_.SmtpAddress }
              If ($_.PrefixString -eq "sip") { $strSIP = $_.AddressString }
       }
      
       # Compare the primary SMTP with the SIP address
       If ($strPrimaryAddress -ne $strSIP)
       {
              $mbcomb."Display Name" = $mbx.DisplayName
              $mbcomb."Primary SMTP Address" = $strPrimaryAddress
              $mbcomb."SIP" = $strSIP
             
              $arrCollection += $mbcomb
       }
}

# Print or export all the results
$arrCollection | FT
#$arrCollection | Export-Csv D:\Scripts\"SMTPvsSIP_$(Get-Date -f 'yyyyMMdd').csv" -NoType




get-mailbox | where {$_.UseDatabaseQuotaDefaults -ne $true}


Get-Mailbox Database Statics

This command is used for get the Mailbox Database statics:

[PS] C:\>Get-MailboxDatabase 
Name                           Server          Recovery        ReplicationType                                        
----                           ------          --------        ---------------                                        
Mailbox Database 0020849825    Exchangeby-Arun-Ex001  False           Remote                                                 
Mailbox Database 2       Exchangeby-Arun-Ex-02  False           Remote                                                 


If you like these scripts, please leave your comments here.

                                                    Thanks
                              Arun chaudhary
                             Email me: arunkalagarh@gmail.com

Manage-GroupManagmentRole.ps1



            Manage-GroupManagmentRole.ps1




# Script for creating a Role that can manage distributions groups but can't create new ones



#################################################################################



# Parameter to get a different name than default for the new Role
Param([string]$name="MyDistributionGroupsManagement",[string]$policy="Default Role Assignment Policy",[switch]$creategroup,[switch]$removegroup)

# Help Function
Function Show-Help {

"
This script is will create or manage a management role designed to allow users to modify groups that they already own
but not create or remove any new distribution groups.

Switches:
-name           Name of the managment role you want to create or modify
                    Defaults to: `"MyDistributionGroupsManagmenet`"
                   
-policy         Name of the Role Policy you want to assign the role to
                    Defaults to: `"Default Role Assignement Policy`"
                   
-creategroup    Adds or Removes the ability of the Role to Create DLs

-removegroup    Adds or Removes the ability of the Role to Remove DLs

Examples:
--------------------------------------------
This will Use the default names and Policy and will create a role that cannot
Create or remove groups but can still modify them.  If the role already exists
It will modify it by removing or adding the abiltity to create and remove groups
based on the current state.

Manage-GroupManagementRole -CreateGroup -RemoveGroup

"


}



# Function to modify a role by removing or adding Role Entries
# If no action is passed we assume remove
# $roleentry should be in the form Role\Roleentry e.g. MyRole\New-DistributionGroup
Function ModifyRole {
 Param($roleenty,$action)
   
    Switch ($action){
        Add {Add-ManagementRoleEntry $roleenty -confirm:$false}
        Remove {Remove-ManagementRoleEntry $roleenty -confirm:$false}
        Default {Remove-ManagementRoleEntry $roleenty -confirm:$false}
    }
}

If (($creategroup -eq $false) -and ($removegroup -eq $false)){
    Show-Help
    exit
}


# Test if we have a role that already has that name
If (([bool](Get-Managementrole $name -erroraction Silentlycontinue)) -eq $true){
    Write-Warning "Found a Role with Name: $name"
    Write-Warning "Trying to Modify Existing Role"
}
Else {
    # Create the new Management Role
    Write-Host "Creating Managmenet Role $name"
    New-ManagementRole -name $name -parent MyDistributionGroups
}

# Determine if we have the New and Remove Role Entries on the Role Already
$create = [bool](Get-managementroleentry $name\New-DistributionGroup -erroraction Silentlycontinue)
$remove = [bool](Get-managementroleentry $name\Remove-DistributionGroup -erroraction Silentlycontinue)

# If we have the switch CreateGroup add or remove the RoleEntry for New-DistributionGroup
If ($creategroup -eq $true){
    If ($create -eq $true){ModifyRole $name\New-DistributionGroup Remove;Write-Host "Removing ability to create distribution Groups from $name"}
    elseif ($create -eq $false) {ModifyRole $name\New-DistributionGroup Add;Write-Host "Adding ability to create distribution Groups to $name"}
}

# If we have the switch RemoveGroup add or remove the RoleEntry for New-DistributionGroup
If ($removegroup -eq $true){
    If ($remove -eq $true){ModifyRole $name\Remove-DistributionGroup Remove;Write-Host "Removing ability to create distribution Groups from $name"}
    elseif ($remove -eq $false) {ModifyRole $name\Remove-DistributionGroup Add;Write-Host "Adding ability to create distribution Groups to $name"}
}

# Test if we have the assignment for the Role and Policy
# If we do ... write a warning
# If not create a new assignment
If (([bool](get-managementroleassignment $name-$policy -erroraction SilentlyContinue)) -eq $true){
    Write-Warning "Found Existing Role Assignment: $name-$policy"
    Write-Warning "Making no modifications to Role Assignments"
}
Else {
    # Assign the Role to the Role Policy
    Write-Host "Creating Managmenet Role Assignment $name-$policy"
    New-ManagementRoleAssignment -name ($name + "-" + $policy) -role $name -policy $policy
}




If you feel this is usefull for you, leave a comment for me

Thanks
 Arun Chaudhary
Email me: arunkalagarh@gmail.com

Set-DistributionGroupOwners (Script)




             Set-DistributionGroupOwners



This script is used to set the Distribution-Group Owners, this script is develop by-Microsoft.

#################################################################################


Param($DistributionGroup = $null,$GroupOwner = $null)

# Sets all users in the DL listed in $dn_storage as managing the DL they are listed in
Function SetUserAsOwners {
Param ([string]$DistributionGrouptoSet)

# Handle single DG vs Processing everything
if ($DistributionGrouptoSet -eq ""){

# Get a list of all groups that we need to manipulate
$Groupstoset = Get-distributiongroup -filter "($dn_storage -like 'CN*')"

}
# Set our Grouptoset to just the single group that was passed into the function
else { $Groupstoset = Get-distributiongroup $DistributionGrouptoSet }

# Process each group
$Groupstoset | foreach {

# Seting the array of users to null so that it doesn't keep adding to the array with each loop
[array]$DNOfUserstoset = $null

# Setting CheckedUserstoSet to Null to ensure we don't continue building the array over time
[array]$CheckedUserstoset = $null

Write-Host "Setting Members of" $_.($dn_storage) "as owners on" $_.identity

# Get a list of the users that need to be listed as managers of the DL
# This will preform this search recursively
$Userstoset = Get-ADGroupMember $_.($dn_storage) -recursive

# Convert the output from get-adgroupmember into an array of DNs
$Userstoset | foreach { [array]$DNOfUserstoset = $DNOfUserstoset + [string]$_.distinguishedname }

# Verify that each of the users in the array is a mailbox
# This eliminates any nested groups / contact / or users and just leaves us with the mailboxes
$DNOfUserstoset | foreach {

If (Get-mailbox $_ -erroraction silentlycontinue){[array]$CheckedUserstoset = $CheckedUserstoset + $_ }
else {}
}

# Throw any duplicates out of the $checkedUsersToSet
$CheckedUserstoset = $CheckedUserstoset | Select-Object -Unique

# Set that list of mailboxes as owners of the DL
# Throw a warning if we didn't get any valid objects returned
if ($CheckedUserstoset -eq $null){Write-warning "Didn't Find any valid objects in Owning Group"}
else { Set-distributiongroup $_.identity -managedby $CheckedUserstoset -BypassSecurityGroupManagerCheck }

}

}

# Setup a DL as "owner" of another DL
# This will place the DN of DistributionGroupOwner into the $dn_Storage file of the Distribtiongroup
Function SetDNofGroupOwner {
Write-Host "Setting" $GroupOwner "as the owner of" $DistributionGroup

# Build and Execute the command that we need to make this change
$commandtorun = "Set-Distributiongroup -identity `'" + $DistributionGroup + "`' -" + $dn_storage + " `(get-adgroup `'" + $GroupOwner + "`'`)`.distinguishedname"
Invoke-Expression $commandtorun
}

# Main Body
# ===============================

# Attribute to use for storing DN of group owner
# !!!! --- Change this to the correct attribute for your Organization --- !!!! #
$dn_storage = "CustomAttribute5"

#Check the OS Version
if ([system.environment]::OSversion.Version.Major -eq 6 -and [system.environment]::OSversion.Version.Minor -ge 1 -and (get-wmiobject Win32_OperatingSystem -comp .).Caption.Contains("R2")  ) {}
else {
Write-Error "The Operating System requirements are not met, you must be running at least Windows 2008 R2"
exit
}

# Check to see if the Exchnage snapin is loaded, if not load it
if ((Get-PSSession | where {$_.configurationname -eq "Microsoft.Exchange"}) -eq $null) {
Write-Host "Loading Exchange Shell"

# Load up Exchange Powershell so we have the Exchange cmdlets
# !!!! --- You will need to change this Path if your Exchange Install is not in the Default Location --- !!!! #
. 'c:\Program Files\Microsoft\Exchange Server\v14\Bin\RemoteExchange.ps1'
Connect-ExchangeServer -auto
}

# Import the AD management Module
Import-Module ActiveDirectory

# If no parameters passed process all Distribution groups
If (($GroupOwner -eq $null) -and ($DistributionGroup -eq $null)){ SetUserAsOwners }

# If we have a Distributiongroup but not an owner then just process that DL
elseif (($GroupOwner -eq $null) -and ($DistributionGroup -ne $null)){ SetUserAsOwners -DistributionGrouptoSet $DistributionGroup }

# If we have DL owner and don't have a DL then we need to generate an error
elseif (($DistributionGroup -eq $null) -and ($GroupOwner -ne $null)) {Write-Error "Incorrect Syntax"}

# If none of the above then we should have both DL and DLOwner so set the DL owner attribute
else { SetDNofGroupOwner }


If you feel this is valuable, please leave your comments for me.
                                             
                                                 Thanks
                                        Arun Chaudhary
                               Email me:arunkalagarh@gmail.com

Monday, October 22, 2012

Exchange Server 2010 Data center switch over trouble-shooter



Exchange Server 2010 Data center switch over trouble-shooter


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.

 


Exchange 2010 has a very good feature that called Data centre Activation Coordination (DAC) mode, which is designed to prevent split brain at the database level during switchback procedures that are being performed after a data centre switchover. The major advantage of enabling the DAC feature is that you can use built-in recovery cmdlets to perform the data centre switchover and switchback.

But before going to run the built-in cmdlets you should have to understand properly these factors.

  • Are all Exchange Servers available in Primary data centre?
  • Is network connectivity available between the primary and remote data centre?
  • Is Exchange deployed in a topology with a single Active Directory site or multiple sites?

When you got the required information regarding above points, now you can plan what command will be run & where will be run.

Now Administrator can run the built-in cmdlets but he required some more information like;

·        How do I verify that stop-databaseavailability group was successful?
·        How do I verify that restore-databaseavailabilitygroup performed the correct steps?
·        When is it appropriate to run start-databaseavailailitygroup?

Each of these required a different set of verification steps, before you start.






Data centre Switchover Tool: this is a very good tool to perform the data centre switch over, it’s a kiosk-based power point application that allows administrators to work on the following steps.

  • What commands to run and where to run them
  • How to verify the commands completed successfully.
  • How to walk through a Data centre Switchover from the Mailbox server / database availability group perspective.

Thanks
                             Arun Chaudhary
            Read my Books:
1.      “The complete guide from Exchange Server 2003 to Exchange Server 2010 migration”
2.      “Open Source Email Servers