Exchange Knowledge

Exchange Powershell Script

2012-11-22T03:28:00.002-08:00

Exchange Control Panel (ECP):
Get-EcpVirtualDirectory | fl *url*, ide*

Set-EcpVirtualDirectory –Identity “TLCAS01\ecp (Default Web Site)” –ExternalUrl https://mail.testlabs.se/ecp

Autodiscover:

Get-ClientAccessServer | fl *uri*

Set-ClientAccessServer –Identity TLCAS01 –AutoDiscoverServiceInternalUri https://autodiscover...utodiscover.xml

Exchange ActiveSync (EAS):

Get-ActiveSyncVirtualDirectory | fl *url*, ide*

Set-ActiveSyncVirtualDirectory –Identity “TLCAS01\Microsoft-Server-ActiveSync (Default Web Site)” –ExternalUrl https://mail.testlab...rver-ActiveSync

Exchange Web Services (EWS):

Get-WebServicesVirtualDirectory | fl *url*, ide*

Set-WebServicesVirtualDirectory –Identity “TLCAS01\EWS (Default Web Site)” –ExternalUrl https://mail.testlab...S/Exchange.asmx

Offline Address Book (OAB):

Get-OabVirtualDirectory | fl *url*, ide*,pol*

Set-OabVirtualDirectory –Identity “TLCAS01\OAB (Default Web Site)” –ExternalUrl https://mail.testlabs.se/OAB –PollInterval 60

Outlook Web App (OWA):

Get-OwaVirtualDirectory | fl *url*, ide*

Set-OwaVirtualDirectory –Identity “TLCAS01\OWA (Default Web Site)” –ExternalUrl https://mail.testlabs.se/OWA

PowerShell:

Get-PowerShellVirtualDirectory | fl *url*, ide*

Set-PowerShellVirtualDirectory –Identity “TLCAS01\PowerShell (Default Web Site)” –ExternalUrl https://mail.testlabs.se/powershell

Enable Outlook Anywhere:

Enable-OutlookAnywhere –Server TLCAS01 –ExternalHostname mail.testlabs.se –InternalHostname tlcas01.testlabs.se –ExternalClientAuthenticationMethod Basic –InternalClientAuthenticationMethod Ntlm –IISAuthentication Ntlm –SSLOffloading:$false

Get-OutlookAnywhere –Server TLCAS01
Get-AcceptedDomain
New-AcceptedDomain –Name testlabs.com –DomainName testlabs.com –DomainType Authoritative
Get-EmailAddressPolicy
Get-EmailAddressPolicy | fl

Send & Receive Connector

Get-ReceiveConnector
Get-ReceiveConnector | fl
Set-ReceiveConnector –Identity “TLCAS01\Default Frontend TLCAS01” –MaxMessageSize 30MB
Get-ReceiveConnector | fl ide*,maxmes*
Get-SendConnector
Get-SendConnector| fl

New-SendConnector –Name “Outbound” –AddressSpaces ‘*’ –SourceTransportServers TLMB01 –MaxMessageSize 30MB

New-SendConnector –Name “Outbound” –AddressSpaces ‘*’ –SourceTransportServers TLMB01 –

MaxMessageSize 30MB –DNSRoutingEnabled:$false –SmartHosts “10.10.10.10”

New-SendConnector –Name “Outbound” –AddressSpaces ‘*’ –SourceTransportServers TLMB01 –

MaxMessageSize 30MB –DNSRoutingEnabled:$false –SmartHosts “10.10.10.10” –FrontEndProxyEnabled:$True

Get-SendConnector| fl ide*,maxmes*

Globaladdresslis

Get-Globaladdresslist | update-Globaladdresslist
Get-Addresslist | Update-Addresslist
New-GlobalAddressList -Name "gal" -RecipientFilter {(MemberOfGroup -eq 'cn=<GROUP NAME>,OU=Exchange Groups,DC=ggncloud,DC=internal')}

Update-GlobalAddressList -Identity "gal"

update-AddressList -Identity '\All Contacts

Move Request

New-MoveRequest -Identity 'tony@alpineskihouse.com' -TargetDatabase DB01 –WhatIf
New-MoveRequest -Identity 'tony@alpineskihouse.com' -TargetDatabase DB01 -BadItemLimit 100
New-MoveRequest -Identity 'tony@alpineskihouse.com' -TargetDatabase DB01 -BadItemLimit 200 -AcceptLargeDataLoss
New-MoveRequest -Identity 'Kweku' -PrimaryOnly -TargetDatabase "DB01" -BadItemLimit 100 –AcceptLargeDataLoss

Get-MoveRequest –MoveStatus queued |Get-MoveRequestStatistics | ft -auto alias,Status,TotalMailboxSize,PercentComplete,TargetDatabase,TotalInProgressDuration

Suspend-MoveRequest -Identity Shaji_John@abc.com -SuspendComment "Resume suspended request.after @12 PM Today"

Get-MoveRequest -MoveStatus queued | Suspend-MoveRequest -SuspendComment "Resume suspended request.after completion Domino & Cadista"

Get-MoveRequest -MoveStatus suspended | Resume-MoveRequest

Get-LogonStatistics -Database DB-MBX-2

Get-LogonStatistics -Identity shiva_prasad@abc.com

Get-MoveRequest -MoveStatus failed -TargetDatabase DB-mbx1

Get-MoveRequest –MoveStatus Rajesh_Kajalkar@xyz.com

Get-MoveRequest -TargetDatabase DB-MBX-M8 | Suspend-MoveRequest -SuspendComment "Resume @ 12 PM."

Suspend-MoveRequest -TargetDatabase DB-MBX-M8 -SuspendComment "Resume @ 12 PM."

(Get-MoveRequest –MoveStatus queued).count

(Get-MailboxStatistics -Database DB-MBX-3).Count

Get-Mailbox -Database DB-MBX-G7 | Get-MailboxStatistics | Select-Object DisplayName, ServerName, Database,
TotalItemSize, ItemCount, StorageLimitStatu

MailboxStatistics

Get-MailboxStatistics -Server ggncloud | Where {$_.DisconnectDate -ne $null} | Format-Table DisplayName,Database

Get-MailboxStatistics -Server HNLMBX01 | Where {$_.DisconnectDate -ne $null} | Format-Table DisplayName,DisconnectDate

Get-MailboxStatistics -Server HNLMBX01 | Where-Object {$_.DisconnectDate

-gt (Get-Date).AddDays(-7)} | Format-Table displayName,ServerName,
DatabaseName, TotalItemSize -Autosize

Get-MailboxStatistics -Database db3 | where {$_.LastLogonTime -lt
(Get-Date).AddDays(-7)}} | Format-Table displayName,lastlogontime,
lastloggedonuseraccount,ggncloud

Get-MoveRequestStatistics -database db3
Get-Mailbox -Database db3 | New-MoveRequest -TargetDatabase db4
Get-LogonStatistics -Server ggncloud

TransportRule

New-TransportRule -Name 'TS Rule1' -Comments 'transportrule' -Priority '0' -Enabled $true -From 'shailendra@corp.mld' -DeleteMessage $true -ExceptIfFrom 'john@corp.mld'

DatabaseAvailabilityGroup

Restore-DatabaseAvailabilityGroup –Identity DAG1 –ActiveDirectorySite ggncloud
Remove-DatabaseAvailabilityGroupServer -MailboxServer 'RAKESH' -Identity 'DAG2
Get-MailboxDatabase -Status | Sort-Object name | Format-Table Name, DatabaseSize, AvailableNewMailboxSpace
Get-MailboxDatabase -Identity databasename -Status | Format-Table Name, DatabaseSize, AvailableNewMailboxSpace
Get-DatabaseAvailabilityGroupNetwork -Identity DAG2 | fl name, MapiAccessEnabled
Suspend-MailboxDatabaseCopy -Identity DB1\MBX2 -ActivationOnly

Resume-MailboxDatabaseCopy -Identity DB1\MBX2

Set-MailboxServer -Identity MailboxServer–DatabaseCopyAutoActivationPolicy
Set-MailboxServer -Identity MailboxServer–DatabaseCopyAutoActivationPolicy

DynamicDistributionGroup

New-DynamicDistributionGroup -Name "All Research" -IncludedRecipients ‘MailboxUsers’
-ConditionalDepartment ‘Research’ -OrganizationalUnit ‘its’-Alias ‘AllResearch’

new-DynamicDistributionGroup -Name 'DDG-ITS' -RecipientContainer 'corp.mld/ITS' -IncludedRecipients 'AllRecipients' -OrganizationalUnit 'corp.mld/ITS' -Alias 'DDGits'

Set-DynamicDistributionGroup -Name "All Research" -MaxReceiveSize 75KB

New Mailbox

New-Mailbox -Name "System Administrator" -FirstName "System" -LastName "Administrator" -DisplayName "System Administrator" -Alias "sysadmin" -SamAccountName "sysadmin" -organizationalUnit "Test" -Database "MBXDB3" -UserPrincipalName sysadmin@test.com

New-Mailbox -Name:'Help Desk' -OrganizationalUnit:'corp.mld' -Database:'DB01' -UserPrincipalName:'helpdesk@corp.mld' -Shared

Import-CSV "c:\CreateTest.csv" | ForEach-Object { New-Mailbox -Lastname $_.”LastName” -Name $_."DisplayName" -FirstName $_.”FirstName” -Alias $_.”Alias” -SamAccountName $_.”SamAccountName” -organizationalUnit "OU=Test,OU=Departments,DC=test,DC=ac,DC=in" -Database "MBXDB3" -UserPrincipalName $_.”UserPrincipalName” -Password (ConvertTo-SecureString $_.password -AsPlainText -Force)}

FirstName	LastName	DisplayName	Alias	SamAccountName	Password	UserPrincipalName
System	Administrator	System Administrator	sysadmin	sysadmin	nKP5Z6Bz	sysadmin@test.com

Installing the Exchange Server 2013 Preview on Windows Server 2012

2012-11-20T00:53:00.001-08:00

In case you haven’t heard, this week Microsoft unveiled preview editions of Exchange 2013, SharePoint 2013, Office 2013, Lync Server 2013, and the new version of Office 365. As you could imagine, there are a slew of new features in each product. From an Exchange point of view, we’re left with only two core server roles; Client Access Server and Mailbox Server. With this new architecture there are some changes to the deployment process. In this post we’ll walk through the installation of the Exchange Server 2013 Preview on Windows Server 2012. Keep in mind that this is preview only, and some of the screens, along with the technical details, are subject to change. The lab environment I’ll be using looks like this:

Active Directory Requirements & Prerequisites

Your Schema Master can still run Windows Server 2003, but your global catalog servers need to be running 2008 or higher. As before, your forest/domain functional levels should be at 2003 or higher. And of course, since this is a new installation of Exchange, the AD schema will need to be extended. For the purposes of this walk-through, this will be done over the wire from the Exchange server during setup. As a prerequisite for this, I’ve installed the RSAT-ADDS tools by issuing the following PowerShell command: Install-WindowsFeature RSAT-ADDS. For more details on the AD requirements, see the Network and directory servers topic under the Exchange 2013 System Requirements in the TechNet documentation.

Server Prerequisites

Two of the main prerequisites are the Windows Management Framework 3.0 (which includes PowerShell v3) and the .NET Framework 4.5. Both of these are already installed on Windows Server 2012.

The remaining operating system prerequisites can be installed by issuing the following command from PowerShell. This will install the OS prerequisites for both the CAS and Mailbox roles:

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

Unified Communications Managed API 4.0 (Preview) Runtime

After you’ve installed the Desktop Experience feature as part of the previous step and have rebooted your servers, you’ll need to install the Unified Communications Managed API 4.0 runtime. Make sure you install this component on both the CAS and Mailbox servers. Once installed, remove/uninstall the Visual C++ 11 Beta Redistributable (x64) – 11.0.50531 from each server.

Office 2010 FilterFilter Pack

Make sure you install the Office 2010 Filter Pack and the Office 2010 Filter Pack SP1 packages on the Mailbox server.

o Microsoft Office 2010 Filter Pack 64 bit

o Microsoft Office 2010 Filter Pack SP1 64 bit

Installing the prerequisites is much easier on Windows Server 2012. There’s more steps involved in installing it on Windows Server 2008 R2. For full details, see Exchange 2013 Prerequisites on TechNet.

Graphical Install – Mailbox Server Role

The Client Access Server role is truly a front-end/proxy for the backend, which is the Mailbox Server role (sound familiar?). So we’ll start off by installing the back-end first, because with only a front-end, there is nothing to proxy to.

Initially setup.exe will check for updates

Next we get into the installation. If you’ve done a few Exchange 2010 installations, the options throughout the rest of the wizard will be very familiar.

Accept the License Agreement and click next

Specify your Error Reporting preference and click next

Some prerequisite checks will be performed. If any issues were found (missing prerequisites, etc.) this should let you know

Make you Server Role Selection and click next

Specify an installation path and click next

Since we’re installing into a clean forest, a new organization needs to be created as part of the Active Directory prep

Malware scanning, which is brand new in 2013. I’ve chosen NOT to disable it, so it will be turned on by default. You can read more about this under Anti-Spam and Anti-Malware Protection in the TechNet documentation.

Select an option for the Customer Experience Improvement Program and click next

Some final readiness checks will be made

Depending on the server resources in your lab, this next step can take a bit of time to complete. In my lab, this took at about 15-20 minutes on a VM with 4 vCPUs and 4GB of RAM.

Windows Firewall Configuration – CAS Server

Before installing your CAS, you need to modify the Windows Firewall to allow Exchange to access the registry of the Client Access server. When splitting the servers roles like this (CAS and Mailbox on independent servers) you’ll need to make sure that the Windows Firewall on the CAS server allows TCP port 139 inbound. On the CAS, perform the following steps:

o Open Control Panel\Windows Firewall

o Click Advanced Settings

o Click Inbound Rules

o Click New Rule…

o Select Port and then Next

o Select TCP and in Specify local ports, type 139. Click Next

o Select Allow this connection and click Next

o Click Next again to accept the default selections

o Enter a name and description for the new rule and flick Finish

Command Line Install – CAS Server Role

Command line installations have changed a bit as well. Now that we’ve got the Mailbox Server role installed with the GUI, lets deploy the CAS using a command line installation. To perform the install, use the following command from an elevated prompt:

Setup.exe /mode:Install /role:ClientAccess /IAcceptExchangeServerLicenseTerms

Unlike previous versions of Exchange, setup.com is not used, and we can now use setup.exe to perform the install from the command line. Alot of the previous switches, such as mode, and role, still work, as shown above. The most interesting addition is the /IAcceptExchangeServerLicenseTerms switch which automatically accepts the Exchange 2013 Preview licensing terms. For full details, check out Install Exchange 2013 in Unattended Mode in the TechNet documentation.

Post Installation

After the installation is complete, you can manage Exchange 2013 with the shell, or through the Exchange Administration Center (EAC), which is a new web based management tool. The Exchange Management Console is no longer part of the product in Exchange 2013. To run the EAC, navigate to http://cas_server_name/ecp

Many of the configuration screens are very similar to what you would see in EMC. If you’re familiar with Exchange 2010 then you should be able to find your way around in here quite well.

Accessing a Mailbox from Outlook Web App

After the installation is complete, you’ll want to head over to OWA and send yourself an email to make sure your Exchange Server 2013 Preview is fully functional. You’ll still navigate to the CAS for this, e.g. http://cas_server_name/owa

As you can see from the screen shot, OWA has been completely overhauled. The user interface now supports the use of touch screens, enhancing the experience with tablets and smartphones. You can even go “offline” with OWA and access your mail without a connection to the server.

There’s so much more to talk about with Exchange Server 2013. Keep your eye on this blog and follow me on twitter for updates. To get started with Exchange 20103 and build your own lab, head over to the TechNet Evaluation Center and Download the Microsoft Exchange Server 2013 Preview.

Exchange Server 2013

2012-11-20T00:06:00.004-08:00

Exchange Server 2013 comes with a number of new features as well as improvements on existing features that are already familiar to those who have worked with Exchange Server 2010.

Here are a few of the highlights:

Reduction in server roles to just two; Client Access server and Mailbox server
New streamlined Outlook 2013 and Outlook Web App user interfaces, and offline access for OWA
No more Exchange Management Console, all administration is now performed using the new web-based Exchange Administration Center and the Exchange Management Shell (using PowerShell 3.0)
Improvements to high availability features and manageability
Public folders are now stored in mailbox databases and can take advantage of Database Availability Groups for replication and high availability
Data loss prevention capabilities that can be integrated into Transport Rules

Getting Started with Exchange Server 2013

The Exchange 2013 Preview has been publicly released so that you can try it yourself. Note that it is not supported to run Exchange Server 2013 Preview in production environments (in fact it currently has no co-existence support with previous versions).

Explore some of the features of Exchange Server 2013:

New Features in Exchange Server 2013

2012-11-20T00:04:00.005-08:00

Here's a list from Microsoft of some of the new Exchange Server 2013 features:

Offline support in OWA: Emails and actions are automatically synced the next time connectivity is restored.

Site Mailboxes bring Exchange emails and SharePoint documents together

Outlook Web App offers three different UI layouts optimized for desktop, slate, and phone browsers

Ability to customize Outlook and OWA by integrating apps from the Office marketplace. (Yes, this is a reference to the Agaves add-ins that Microsoft and partners will be making available via the new Office Store.) The new "Napa" tools and/or HTML5 are Microsoft's preferred ways to developers to build these.

Replacement of the Exchange Management Console by a Web-based Exchange Administrative Center (EAC)

Support for up to 8 TB disks and multiple databases per disk via Data Availability Group (DAG) management

Built in basic anti-malware protection, with ability for administrators to configure and manage settings from inside EAC. (Note: this feature can be turned off, replaced or "paired with premium services such as Exchange Online Protection for layered protection.")

New Data Loss Prevention (DLP) capabilities for identifying and protecting "sensitive data." DLP policies are based on regulatory standards, including PII and PCI. Also: new policy tips in Outlook 2013 can be set to inform users about potential policy violations.

In-Place eDiscovery can be run across Exchange, SharePoint, and Lync from a single interface

Here are some more new Exchange 2013 features, courtesy of Michael Van Horenbeeck, a member of the Pro-Exchange community and consultant/trainer with Xylos:

A reduction in the number of available roles to two: a Client Access Server and a Mailbox Server role. The result: These two roles are now "loosely coupled," as Microsoft explains it. More from the Softies on this architectural change:

The Mailbox server includes all the traditional server components found in Exchange 2010: the Client Access protocols, Hub Transport service, Mailbox databases, and Unified Messaging. The Mailbox server handles all activity for a given mailbox. The Client Access server provides authentication, redirection, and proxy services. The Client Access server itself doesn't do any data rendering. The Client Access server is a thin and stateless server. There is never anything queued or stored on the Client Access server. The Client Access server offers all the usual client access protocols: HTTP, POP and IMAP, and SMTP."
FAST Search now integrated into Exchange 2013 managed store to provide a more consistent (across Microsoft servers) indexing and searching experience

Inclusion of a "Managed Store," with is the name of the rewritten information store processes, which are now written in C#

Create User Through Script

2012-08-31T17:00:00.000-07:00

Import-CSV "c:\create.csv" | ForEach-Object { New-Mailbox -Lastname $_.”LastName” -Name $_."Name" -FirstName $_.”FirstName” -Database "DB3" -UserPrincipalName $_.”UserPrincipalName” -Password (ConvertTo-SecureString $_.password -AsPlainText -Force)}

FirstName

LastName

Name

UserPrincipalName

Password

PrimaryEmailAddress

SecondryEmailAddress

Rakesh

Kumar

Rakesh Kumar

RakeshK@corp.mld

P@ssword123

RakeshK@corp.mld

RakeshK@ggncloud.corp.mld

Powershell Command

2012-08-31T16:55:00.000-07:00

    Address Powershell Command
   ----------------------------
         Add-AvailabilityAddressSpace
         Disable-AddressListPaging
         Enable-AddressListPaging
         Get-AddressList
         Get-AvailabilityAddressSpace
         Get-EmailAddressPolicy
         Get-GlobalAddressList
         Get-OfflineAddressBook
         Move-AddressList
         Move-OfflineAddressBook
         New-AddressList
         New-EmailAddressPolicy
         New-GlobalAddressList
         New-OfflineAddressBook
         Remove-AddressList
         Remove-AvailabilityAddressSpace
         Remove-EmailAddressPolicy
         Remove-GlobalAddressList
         Remove-OfflineAddressBook
         Set-AddressList
         Set-EmailAddressPolicy
         Set-GlobalAddressList
         Set-OfflineAddressBook
         Update-AddressList
         Update-EmailAddressPolicy
         Update-GlobalAddressList
         Update-OfflineAddressBook
        Get-GlobalAddressList
         New-GlobalAddressList
        Remove-GlobalAddressList
        Set-GlobalAddressList
        update-GlobalAddressList
----------------------------------------------------------------------------------------------------------

Mailbox PowerShell Command
---------------------------------------------------
         Add-MailboxDatabaseCopy
         Add-MailboxFolderPermission
         Add-MailboxPermission
         Clean-MailboxDatabase
         Connect-Mailbox
         Disable-Mailbox
         Disable-RemoteMailbox
         Disable-UMMailbox
         Enable-Mailbox
         Enable-RemoteMailbox
         Enable-UMMailbox
         Export-MailboxDiagnosticLogs
         Get-ActiveSyncMailboxPolicy
         Get-CASMailbox
         Get-Mailbox
         Get-MailboxAuditBypassAssociation
         Get-MailboxAutoReplyConfiguration
         Get-MailboxCalendarConfiguration
         Get-MailboxCalendarFolder
         Get-MailboxDatabase
         Get-MailboxDatabaseCopyStatus
         Get-MailboxFolder
         Get-MailboxFolderPermission
         Get-MailboxFolderStatistics
         Get-MailboxJunkEmailConfiguration
         Get-MailboxMessageConfiguration
         Get-MailboxPermission
         Get-MailboxRegionalConfiguration
         Get-MailboxRestoreRequest
         Get-MailboxRestoreRequestStatistics
         Get-MailboxServer
         Get-MailboxSpellingConfiguration
         Get-MailboxStatistics
         Get-ManagedFolderMailboxPolicy
         Get-OwaMailboxPolicy
         Get-RemoteMailbox
         Get-UMMailbox
         Get-UMMailboxPIN
         Get-UMMailboxPolicy
         Move-ActiveMailboxDatabase
         New-ActiveSyncMailboxPolicy
         New-Mailbox
         New-MailboxAuditLogSearch
         New-MailboxDatabase
         New-MailboxFolder
         New-MailboxRepairRequest
         New-MailboxRestoreRequest
         New-ManagedFolderMailboxPolicy
         New-OwaMailboxPolicy
         New-RemoteMailbox
         New-UMMailboxPolicy
         Remove-ActiveSyncMailboxPolicy
         Remove-Mailbox
         Remove-MailboxDatabase
         Remove-MailboxDatabaseCopy
         Remove-MailboxFolderPermission
         Remove-MailboxPermission
         Remove-MailboxRestoreRequest
         Remove-ManagedFolderMailboxPolicy
         Remove-OwaMailboxPolicy
         Remove-RemoteMailbox
         Remove-StoreMailbox
         Remove-UMMailboxPolicy
         Restore-Mailbox
         Resume-MailboxDatabaseCopy
         Resume-MailboxExportRequest
         Resume-MailboxRestoreRequest
         Search-MailboxAuditLog
         Set-ActiveSyncMailboxPolicy
         Set-CASMailbox
         Set-Mailbox
         Set-MailboxAuditBypassAssociation
         Set-MailboxAutoReplyConfiguration
         Set-MailboxCalendarConfiguration
         Set-MailboxCalendarFolder
         Set-MailboxDatabase
         Set-MailboxDatabaseCopy
         Set-MailboxFolderPermission
         Set-MailboxJunkEmailConfiguration
         Set-MailboxMessageConfiguration
         Set-MailboxRegionalConfiguration
         Set-MailboxRestoreRequest
         Set-MailboxServer
         Set-MailboxSpellingConfiguration
         Set-ManagedFolderMailboxPolicy
         Set-OwaMailboxPolicy
         Set-RemoteMailbox
         Set-UMMailbox
         Set-UMMailboxPIN
         Set-UMMailboxPolicy
         Suspend-MailboxDatabaseCopy
         Suspend-MailboxRestoreRequest
         Update-MailboxDatabaseCopy
--------------------------------------------------------------------------------------------------------

Database Powershell command
--------------------------------------------------
         Add-DatabaseAvailabilityGroupServer
         Add-MailboxDatabaseCopy
         Clean-MailboxDatabase
         Dismount-Database
         Get-DatabaseAvailabilityGroup
         Get-DatabaseAvailabilityGroupNetwork
         Get-MailboxDatabase
         Get-MailboxDatabaseCopyStatus
         Get-PublicFolderDatabase
         Mount-Database
         Move-ActiveMailboxDatabase
         Move-DatabasePath
         New-DatabaseAvailabilityGroup
         New-DatabaseAvailabilityGroupNetwork
         New-MailboxDatabase
         New-PublicFolderDatabase
         New-PublicFolderDatabaseRepairRequest
         Remove-DatabaseAvailabilityGroup
         Remove-DatabaseAvailabilityGroupNetwork
         Remove-DatabaseAvailabilityGroupServer
         Remove-MailboxDatabase
         Remove-MailboxDatabaseCopy
         Remove-PublicFolderDatabase
         Restore-DatabaseAvailabilityGroup
         Resume-MailboxDatabaseCopy
         Set-DatabaseAvailabilityGroup
         Set-DatabaseAvailabilityGroupNetwork
         Set-MailboxDatabase
         Set-MailboxDatabaseCopy
         Set-PublicFolderDatabase
         Start-DatabaseAvailabilityGroup
         Stop-DatabaseAvailabilityGroup
         Suspend-MailboxDatabaseCopy
         Update-MailboxDatabaseCopy
--------------------------------------------------------------------------------------------------

Group Poershell command
------------------------------------------
         Add-DatabaseAvailabilityGroupServer
         Add-DistributionGroupMember
         Add-RoleGroupMember
         Disable-DistributionGroup
         Enable-DistributionGroup
         Get-DatabaseAvailabilityGroup
         Get-DatabaseAvailabilityGroupNetwork
         Get-DistributionGroup
         Get-DistributionGroupMember
         Get-DynamicDistributionGroup
         Get-Group
         Get-RoleGroup
         Get-RoleGroupMember
         Get-RoutingGroupConnector
         Get-UMHuntGroup
         New-DatabaseAvailabilityGroup
         New-DatabaseAvailabilityGroupNetwork
         New-DistributionGroup
         New-DynamicDistributionGroup
         New-RoleGroup
         New-RoutingGroupConnector
         New-UMHuntGroup
         Remove-DatabaseAvailabilityGroup
         Remove-DatabaseAvailabilityGroupNetwork
         Remove-DatabaseAvailabilityGroupServer
         Remove-DistributionGroup
         Remove-DistributionGroupMember
         Remove-DynamicDistributionGroup
         Remove-RoleGroup
         Remove-RoleGroupMember
         Remove-RoutingGroupConnector
         Remove-UMHuntGroup
         Restore-DatabaseAvailabilityGroup
         Set-DatabaseAvailabilityGroup
         Set-DatabaseAvailabilityGroupNetwork
         Set-DistributionGroup
         Set-DynamicDistributionGroup
         Set-Group
         Set-RoleGroup
         Set-RoutingGroupConnector
         Start-DatabaseAvailabilityGroup
         Stop-DatabaseAvailabilityGroup
         Update-DistributionGroupMember
         Update-RoleGroupMember
--------------------------------------------------------------------------------------------------------

Get MailboxStatistics

2012-08-31T16:42:00.002-07:00

$Results = @()

$mbx = Get-mailbox -ResultSize "Unlimited"
foreach ($mb in $mbx)
{
$Srv = New-Object PSObject
$stat = Get-mailbox $mb.Alias | Get-MailboxStatistics
$usr = Get-User $mb.Alias

$Srv | Add-Member -MemberType NoteProperty -Name UserName -Value $mb.Name
$Srv | Add-Member -MemberType NoteProperty -Name FirstName -Value $usr.FirstName
$Srv | Add-Member -MemberType NoteProperty -Name LastName -Value $usr.LastName
$Srv | Add-Member -MemberType NoteProperty -Name DisplayName -Value $stat.DisplayName
$Srv | Add-Member -MemberType NoteProperty -Name Title -Value $usr.Title
$Srv | Add-Member -MemberType NoteProperty -Name Department -Value $usr.Department
$Srv | Add-Member -MemberType NoteProperty -Name Office -Value $mb.Office
$Srv | Add-Member -MemberType NoteProperty -Name Fax -Value $usr.Fax
$Srv | Add-Member -MemberType NoteProperty -Name City -Value $usr.City
$Srv | Add-Member -MemberType NoteProperty -Name State -Value $usr.State
$Srv | Add-Member -MemberType NoteProperty -Name CountryorRegion -Value $usr.CountryorRegion
$Srv | Add-Member -MemberType NoteProperty -Name PostalCode -Value $usr.PostalCode
$Srv | Add-Member -MemberType NoteProperty -Name PrimarySmtpAddress-Value $mb.PrimarySmtpAddress
$Srv | Add-Member -MemberType NoteProperty -Name TotalItemSize -Value $stat.TotalItemSize
$Srv | Add-Member -MemberType NoteProperty -Name IssueWarningQuota -Value $mb.IssueWarningQuota
$Srv | Add-Member -MemberType NoteProperty -Name ProhibitSendQuota -Value $mb.ProhibitSendQuota
$Srv | Add-Member -MemberType NoteProperty -Name ProhibitSendReceiveQuota -Value $mb.ProhibitSendReceiveQuota
$Srv | Add-Member -MemberType NoteProperty -Name ItemCount -Value $stat.Itemcount
$Srv | Add-Member -MemberType NoteProperty -Name LastLogonTime -Value $stat.LastLogonTime
$Srv | Add-Member -MemberType NoteProperty -Name LastLogoffTime -Value $stat.LastLogoffTime
$Srv | Add-Member -MemberType NoteProperty -Name AssociatedItemCount -Value $stat.AssociatedItemCount
$Srv | Add-Member -MemberType NoteProperty -Name DeletedItemCount -Value $stat.DeletedItemCount
$Srv | Add-Member -MemberType NoteProperty -Name DisconnectDate -Value $stat.DisconnectDate
$Srv | Add-Member -MemberType NoteProperty -Name LastLoggedOnUserAccount -Value $stat.LastLoggedOnUserAccount
$Srv | Add-Member -MemberType NoteProperty -Name ObjectClass -Value $stat.ObjectClass
$Srv | Add-Member -MemberType NoteProperty -Name TotalDeletedItemSize -Value $stat.TotalDeletedItemSize
$Srv | Add-Member -MemberType NoteProperty -Name MoveHistory -Value $stat.MoveHistory
$Srv | Add-Member -MemberType NoteProperty -Name IsQuarantined -Value $stat.IsQuarantined
$Srv | Add-Member -MemberType NoteProperty -Name IsArchiveMailbox -Value $stat.IsArchiveMailbox
$Srv | Add-Member -MemberType NoteProperty -Name IsMoveDestination -Value $stat.IsMoveDestination

$Results += $Srv
}
$Results | Export-CSV "C:\Result18.csv" -notype

Managing Distribution List using Shell Command

2012-08-31T16:37:00.002-07:00

This post contains the information on how to manage distribution list in Exchange server 2010. In exchange server 2010, only the universal distribution or the security group can be mail enabled. No other scopes like Local or Global Distribution Groups are supported in Exchange Server 2010. Below are the distribution groups that can be created

Mail enabled Universal Distribution Group
Mail enabled universal Security Group
Dynamic Distribution Group

Now we will have a look at some of the topics related to managing distribution list in exchange server 2010.

How to create a Distribution Group in Exchange Server 2010

New-DistributionGroup -Name “Name of the Distribution Group” -OrganizationalUnit “DomainName.Com/Exchange Distribution Lists” -SAMAccountName “DIstributionGroupAlias” -Type “Distribution”

How to add owner to a distribution group
Set-Group -Identity “DL Group Name” -ManagedBy “Domain Name\UserName”

How to add Permission to distribution group for Owner After adding Managedby user on a distribution group, better to give read and write access permission for Owner
Add-ADPermission -Identity “DL Group Name” -User “DomainName\user” -AccessRights ReadProperty, WriteProperty -Properties ‘Member’

How to change the owner of a distribution group
Set-DistributionGroup -Identity “DL Group Name” -ManagedBy “DomainName\NewOwnerUser”
Add-ADPermission -Identity “DL Group Name” -User “DomainName\NewOwnerUser” -AccessRights ReadProperty, WriteProperty -Properties ‘Member’

How to add a second or additional owner for a distribution group Giving read and write access permission at active directory level will allow the other user to function as a co owner for a Distribution Group
Set-DistributionGroup -ManagedBy ‘New Onwer Name’,'Old Owner Name’ -Identity ‘Distribution Group Name’

Add-ADPermission -Identity “DL Group Name” -User “DomainName\SecondOwner” -AccessRights ReadProperty, WriteProperty -Properties ‘Member’

How to remove additional owner from a distribution group
Remove-ADPermission -Identity “DL Group Name” -User ” DomainName\SecondOwner ” -AccessRights ReadProperty, WriteProperty -Properties ‘Member’

How to rename a Display name and Alias Name for a Distribution Group

Set-DistributionGroup -Identity ‘Distribution Group Name’ -DisplayName ‘Enter New Name’ -Alias “New_Alias”

How to export the members list from a Distribution Group

Get-DistributionGroupMember -Identity ‘Distribution Group Name” | FL Name

How to add a New Member to the distribution Group
Add-DistributionGroupMember -Identity “Distribution Group Name” -Member “UserName’

How to disable or remove a Distribution Group Disable-DistributionGroup -Identity “Distribution Group Name”
Remove-DistributionGroup -Identity “Distribution Group Name”

How to mail enable or mail disable a security group If we have an active directory security group available and if we want to mail enable that security group, we can use the below shell command and email address will be created for that security group
Enable-DistributionGroup –Identity “DL Display Name”

Disable-DistributionGroup –Identity “DL Display Name”

How to allow external users to send email to the distribution list
Set-DistributionGroup -Identity ‘Distribution Group Name’ -RequireSenderAuthenticationEnabled $True

How to allow owners to approve or restrict member to join or to leave a Distribution Group Set-DistributionGroup -MemberJoinRestriction ‘ApprovalRequired’ -MemberDepartRestriction ‘Closed’ -Identity ‘Distribution Group Name’

How to allow only few users to send email to distribution list
Set-DistributionGroup -AcceptMessagesOnlyFromSendersOrMembers ‘User Name 1’,’User Name 2′ -RequireSenderAuthenticationEnabled $True -Identity ‘Distribution Group Name’

How to restrict few users to send email to distribution list
Set-DistributionGroup -AcceptMessagesOnlyFromSendersOrMembers “All Users” -RequireSenderAuthenticationEnabled $True -Identity ‘Distribution Group Name’ -RejectMessagesFromSendersOrMembers ‘User Name 1’,’User Name 2′

How to set a Message Moderator to allow emails and to bypass approval from few users Set-DistributionGroup -ModerationEnabled $true -ModeratedBy ‘Moderator User Name’ -BypassModerationFromSendersOrMembers ‘User don’t require approval’ -Identity ‘Distribution Group Name’

How to hide a distribution group from Gloabll Address List
Set-DistributionGroup -Identity ‘Distribution Group Name’ -HiddenFromAddressListsEnabled $true

How to add additional email address to a distribution list Set-DistributionGroup -Identity ‘Distribution Group Name’ -EmailAddresses ‘SMTP:existingemailaddress’,'smtp:Newemailaddress’

How to create a dynamic distribution list
New-DynamicDistributionGroup -Name “Name of DDG” -Alias “Alias_Name” -IncludedRecipients “MailboxUsers,MailContacts” -OrganizationalUnit “DomainName.com/Users” -ConditionalDepartment “DepartmentName1″,”DepartmentName2″ -RecipientContainer “DomainName.com”

Exchange Server 2010 Mail Flow diagram

2012-08-31T16:34:00.000-07:00

Email to the Hub Transport Server are submitted in 3 ways, they are

Through SMTP submission,
From the Pickup directory and
When a user inside the organization sends a message

Those emails submitted to the Hub transport server is picked up from the user’s Outbox by the store driver. The store driver is a software component of the Hub Transport server that delivers inbound messages to Exchange stores, the databases that contain public folder and mailbox stores

Messages that are sent by users in your organization are picked up from the sender’s Outbox by the store driver and are put in the Submission queue on a server that runs the Hub Transport server role. When messages are submitted to the Hub Transport server, they’re processed by the categorizer.

Categoriser: The categorizer is a component of Exchange transport that processes all inbound messages and determines what to do with the messages based on information about the intended recipients.
In Exchange 2010, the Hub Transport server uses the categorizer to expand distribution lists and to identify alternative recipients and forwarding addresses. After the categorizer retrieves full information about the recipients, it uses that information to apply policies, route the messages, and perform content conversion.
If the email is sent to internal user, those emails are then delivered locally by the store driver to a recipient’s mailbox, if the emails is intended for external recipient they’re delivered remotely by using SMTP to send messages to another transport server.

Exchange 2010 DAG local and Site DR/Failover and Fail back

2012-08-31T15:58:00.002-07:00

Microsoft Exchange DR and High Availability features have evolved a long way to reach DAG in Exchange 2010. DAG provides the features to recover Exchange 2010 Database from Database, Server or Network Failures. It is uses asynchronous replication and log reply technology concept from Exchange 2007 CCR and SCR. Exchange 2010 DAG provides more robust, easy and quicker HA and DR Failover faculty. Let’s understand the how to create DAG and how to failover and fail back on a DR scenario within the Site and cross Sites.
Current Infrastructure:
In our lab I have Created Two sites and it has the following Infrastructure in each of the sites Ref. Table 1. Mailbox Role servers has two NICs. Nic with IP address 172.x.x.x is for MAPI connection and Nic with 10.x.x.x is for replication traffic. Router has to be configured between Asite and Bsite for the communication. To be more specific we should be able to reach both the IP address 172.x.x.x and 10.x.x.x.x from other mailbox servers from the same site and from the other site. This link has information on how to configure Windows 2008 machine as router using RRAS
ASite – Primary Site

Server name	IP Address	Role
ADC	172.168.1.1	Domain Controller
AHC1	172.168.1.2	Hub and CAS
AMBX1	172.168.1.3(MAPI)	Mailbox Server
	10.0.1.1(Replication)
AMBX1	172.168.1.4(MAPI)	Mailbox Server
	10.0.1.1(Replication)

10.0.2.10 -NIC2 NIC1 – 172.168.1.10
Router
10.0.2.10 -NIC2 NIC1 – 172.168.2.10
BSite – Secondary Site

Server name	IP Address	Role
BDC	172.168.2.1	Domain Controller
BHC1	172.168.2.2	Hub and CAS
BMBX1	172.168.2.3(MAPI)	Mailbox Server
	10.0.2.1(Replication)

Table 1: LAB Infrastructure
Great, now we have the complete LAB Infrastructure created for testing our DAG across the Site. I will just run throw the steps on creating and configuring DAG on the above Infrastructure as we will be more focusing on Failover and fail back settings. If you wanted more In-depth details on DAG configuration then you can always refer TechNet and some nice articles from Neil Hobson, Link 1 and Link 2.
We will begin by creating a DAG to spread across two sites, Site Asite and Bsite. So we need some details from both the Sites and below Table 2 has the all the required details. Lets Create DAG using below details
Create A DAG

We will create a DAG which will spread across both the sites, we need some information from both the sites and below are the details

DAG Name	DAG01
Witness Server	AHC1
Witness Directory	C:\DAG01Witness
Alternate Witness Server	BHC1
Alternate Directory	C:\DAG01Witness
IPAddress from both the sites	172.168.1.9,172.168.2.9

Table 2: Details for DAG Creation
Login to the Mailbox Role Server AMBX1 on a Primary Site. Execute the below commands on the PowerShell Console to create a new DAG with name DAG01. File Share Witness will be created on the Hub Transport Server (AHC1) and DAG IP from both the AD sites Figure 1. File share witness is a server outside DAG and it can be any server with the Same AD Site and recommended to be on Hub transport Server it’s one of the important component of the DAG

`1`	`New-DatabaseAvailabilityGroup` `-Name` `DAG01` `-WitnessServer` `AHC1` `-WitnessDirectory` `C:\DAG01Witness` `-DatabaseAvailabilityGroupIPAddresses` `172.168.1.9, 172.168.2.9`

Figure 1. New DAG Creation
Once we have DAG created we also need to configure Alternate file share witness on the DAG. Alternative File Share witness is configured to point to secondary site. If there is DR and if Secondary sites needs to bring up then this file share witness directory will be used
Let’s understand an Example: If there is a DR scenario and we failover to the secondary Site and secondary site is up and running with its exchange servers and File share witness. In the mean while if servers from the Primary Site up then primary Site has the majority of the nodes and it also has File share witness accessible from primary site. This can cause database on the primary Site to mount. This scenario is known as split brain syndrome. To avoid this situation we configure DAG in Database Activation Coordination (DAC) mode.
Database Activation co-ordination
Database Activation co-ordination mode uses the protocol DACP. One of the DAG member will always have the special memory bit set to 1. If any time any server wants to mount the Database it is to find the DAG node which has memory bit set to 1 and then it will mount the Database. If the above split brain syndrome scenario when primary site come up Active manager will try to find if the DAG is the DAC mode or not. If the DAG is running in DAC mode then server will have DACP flag set to 0 and try to query all the DAG members for DACP flag 1. If it finds all the members and member with DACP flag set to 1, then Active manager running on the DAG member will set DACP to 1 and mount the database. If the Active manager could not find the DAC member with DACP with 1 then database will remain unmounted state. This will avoid split brain Syndrome.
Let’s understand DAP with above example :If the network is restored between primary Datacenter and Secondary Datacenter and primary server is also up then these database which are is in unmounted state will remain unmounted. This is because during the process of activation of secondary site exchange servers will evict all the primary DAG servers from the DAG configuration. So, the members on primary Site contain old information which is no longer valid and this will not allow primary site Exchange severs to participate in the DAG.
This is exactly what we are trying to configure and achieve in the article.
Let’s now configure the alternative file share witness using the Powershell cmdlets shown below

`1`	`Set-DatabaseAvailabilityGroup` `-Identity` `DAG01` `-AlternateWitnessDirectory` `C:\DAG01Witness` `-AlternateWitnessServer` `BHC1`

Figure 2. Configuring Alternative File share Witness
Once we have the DAG created we can able to see the properties of the DAG with the PowerShell cmdlets. It has detail information on DAG like IP address, File share witness Ref. Figure 3.

`1`	`get-DatabaseAvailabilityGroup` `DAG01 \|` `fl`

Figure 3. Properties of new DAG Created
Once we have created DAG we need to ADD members to the DAG. Let’s add all the mailbox servers from Asite and Bsite into the DAG. Each mailbox server can participate is only one DAG. All DAG members must be running the same OS (windows 2008 R2 or Windows 2008 Sp2). Below Powershell cmdlets lets us to add the entire mailbox server AMBX1, AMBX2 and BMBX1 into the DAG01. Figure 4 is the execution snap of adding AMBX1 mailbox servers to DAG

1Add-DatabaseAvailabilityGroupServer -Identity DAG01 -MailboxServer AMBX1 

2Add-DatabaseAvailabilityGroupServer -Identity DAG01 -MailboxServer AMBX2 

3Add-DatabaseAvailabilityGroupServer -Identity DAG01 -MailboxServer BMBX1 

4

Figure 4. Adding AMBX1 to the DAG01
When any mailbox Server is added to the DAG, it installs Windows failover clustering component on to the server and creates a failover cluster and joins the mailbox server to the newly created cluster.
Now let’s configure the DAG to DAC (Database Activation co-ordination) mode and we have already discussed the importance of DAC with the example

`1`	`Set-DatabaseAvailabilityGroup` `-Identity` `DAG01` `-DatacenterActivationMode` `DagOnly`

Figure 5. Enable DAG into DAG mode
Once we have DAG created with member servers in it then we need configure database copies for the Databases in the DAG. I have created two Database in each of the mailbox server in Asite (Primary) and below is Powershell to get the list of Data from the both the mailbox servers Ambx1 and Ambx2 under Primary Site.

`1`	`Get-MailboxDatabase` `\|?{$_.Server` `-like` `"AMBX*"}`

Figure 6. Databases list from Primary Site (Asite) mailbox Servers
Let’s configure each of the Databases from AMBX1 and AMBX2 with one non lagged passive copy on the other server on the same site and one lagged passive copy on the other BSite server BMBX1. Below Table 3 Has defined the list of Database configuration to be configured.

Source Database	Destination Server	Preference	Lagged/Non Lagged passive copy
MDB01	AMBX2	2	Non Lagged
MDB01	BMBX1	3	Lagged
MDB02	AMBX2	2	Non Lagged
MDB02	BMBX1	3	Lagged
MDB03	AMBX1	2	Non Lagged
MDB03	BMBX1	3	Lagged
MDB04	AMBX1	2	Non Lagged
MDB04	BMBX1	3	Lagged

Table 3. Database copy configuration table
Let’s configure the each of the Database define in the above Table 3.
Below are the PowerShell cmdlet to add Database MDB01 to Mailboxdatabasecopy. First cmdlet adds MDB01 Mailbox Database Non lagged copy into the mailbox Server AMBX2 with the Activation Preference set to 2. Activation Preference is used by the Active manager for best Database selection process. Lower the preference number higher the priority. Similarly the next command adds MDB01 to the BMBX1 with Lag reply time of 3 days and truncation lag time is set to 0 and activation preference is set to 3. ReplayLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service should wait before replaying log files that are copied to the database copy and TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service should wait before truncating log files that have replayed into a copy of the database.
Once we have Database are configured with mailbox database copy then automation seeding starts. Seeding is the process of copying of Database from Active to Passive. For non-lagged copy we allow seeding to happen immediately but for lagged copy we configure with seeding postponed. This stops from seeding immediately. This is because we have to configure the mailbox database copy with Activationlyonly. To Configure lagged mailbox database copy as activation only we need to suspend and updated and configure -activationonly. Below PowerShell cmdlets does it for us.
We need to make sure that we configure -Activationonly on the Lagged mailbox database copy. Activation occurs automatically as process of database or server failure. If there is any datacenter failover then his activation has to be manually performed. -Activationonly disables the database to automatically mount in case of Datacenter failures. Figure 7 shows the execution of the below cmdlets

1Add-MailboxDatabaseCopy -Identity MDB01 -MailboxServer AMBX2 -ActivationPreference 2 

2   

3Add-MailboxDatabaseCopy -Identity MDB01 -MailboxServer BMBX1 -ReplayLagTime 3.00:00:00 -SeedingPostponed -ActivationPreference 3 

4   

5Suspend-MailboxDatabaseCopy -Identity MDB01\BMBX1 -SuspendComment "Seed from AMBX1" -Confirm: $False

6   

7Update-MailboxDatabaseCopy -Identity MDB01\BMBX1 -SourceServer AMBX1

Figure 7. Execution of Powershell cmdlets to configured lagged and non-lagged
Mailbox Database copy
We have configured MDB01 with one lagged copy on BMBX1 and one non lagged copy on AMBX2. Now let’s configure Database MDB02 in the same fashion. Below PowerShell cmdlets configures non-lagged copy on AMBX2 and lagged copy on BMBX1. Lagged database is also configured with -Activationonly settings

1Add-MailboxDatabaseCopy -Identity MDB02 -MailboxServer AMBX2 -ActivationPreference 2Add-MailboxDatabaseCopy -Identity MDB02 -MailboxServer BMBX1 -ReplayLagTime 3.00:00:00 -SeedingPostponed -ActivationPreference 3 

2Suspend-MailboxDatabaseCopy -Identity MDB02\BMBX1 -SuspendComment "Seed from AMBX1" -Confirm: $False

3  

4Update-MailboxDatabaseCopy -Identity MDB02\BMBX1 -SourceServer AMBX1 -Deleteexistingfiles

5  

6Suspend-MailboxDatabaseCopy -Identity MDB02\BMBX1 -ActivationOnly

7

With the above cmdlets we have configured both the database of AMBX1, now let’s configure databases of AMBX2. Below PowerShell adds non-lagged mailbox Database copy to AMBX1 and lagged mailbox Database copy on BMBX1. Lagged database is also configured with -Activationonly configuration

1Add-MailboxDatabaseCopy -Identity MDB03 -MailboxServer AMBX1 -ActivationPreference 2 

2Add-MailboxDatabaseCopy -Identity MDB03 -MailboxServer BMBX1 -ReplayLagTime 3.00:00:00 -SeedingPostponed -ActivationPreference 3 

3Suspend-MailboxDatabaseCopy -Identity MDB03\BMBX1 -SuspendComment "Seed from AMBX3" -Confirm: $False

4Update-MailboxDatabaseCopy -Identity MDB03\BMBX1 -SourceServer AMBX1 -Deleteexistingfiles

5Suspend-MailboxDatabaseCopy -Identity MDB03\BMBX1 -ActivationOnly

Below PowerShell cmdlets configures MDB04 with Non-lagged mailbox database copy on AMBX1 and lagged mailbox database copy on BMBX1. Lagged Database is configured with -Activationonly

1Add-MailboxDatabaseCopy -Identity MDB04 -MailboxServer AMBX1 -ActivationPreference 2Add-MailboxDatabaseCopy -Identity MDB04 -MailboxServer BMBX1 -ReplayLagTime 3.00:00:00 -SeedingPostponed -ActivationPreference 3 

2Suspend-MailboxDatabaseCopy -Identity MDB04\BMBX1 -SuspendComment "Seed from AMBX3" -Confirm: $False

3Update-MailboxDatabaseCopy -Identity MDB04\BMBX1 -SourceServer AMBX1 -Deleteexistingfiles

4Suspend-MailboxDatabaseCopy -Identity MDB04\BMBX1 -ActivationOnly

5Suspend-MailboxDatabaseCopy -Identity MDB02\BMBX1 -ActivationOnly

With this we have configured the entire database on Asite with lagged copy and non-lagged copy. Let’s check if they are configured properly and there status with the below PowerShell cmdlets. It looks like all the Database copy is in healthy status which is very god for us. Figure 8 shows the complete mailbox Database copy status

`1`	`Get-MailboxDatabaseCopyStatus` `-Identity` `MDB0* \|` `select` `name, status, SelectcontentIndexState \|` `sort` `Status \|` `ft` `-auto`

Figure 8. Mailbox Database copy Status
Let’s Discuss couple of failures and try to simulate the same and discuss how to fix the same
Type of Failure
1. Database Failure
2. Server Failure
3. Site/Datacenter Failure
Database Failure
If there is a situation where one of the database is failed and it is in Dismounted state and it’s not able to mount the same then we bring other passive database up, this process is knows a Database switchover. In this example we have one of our Database MBX01 is dismounted. Below Powershell gets us the status of the MDB01 which is in Dismounted and Figure 9. Shows the execution result.

`1`	`Get-MailboxDatabaseCopyStatus` `-Identity` `MDB01 \|` `select` `name, status, SelectcontentIndexState \|` `sort` `Status \|` `ft` `-auto`

Figure 9. Cmdlet to get Mailbox Database copy Status.
Let’s try to enable to the passive copy of MDB01 on AMBX2. Execute the below PowerShell cmdlet to do the same. Once the PowerShell cmdlet is executed it show the complete result of the status on Figure 10. PowerShell cmdlet parameter MountDailoverride is set not to override the default settings. Below are the MountDailoverride's options with their details
BestAvailability (default)
Mount the database if the copy queue length ≤12. Those logs are replicated and the database is mounted
GoodAvailability
Mount the database if the copy queue length ≤6. Those logs are replicated and the database is mounted;
Lossless
Only mount the database if the copy queue length is 0, meaning all logs on the original active copy have been replicated. In that case the database is mounted.

`1`	`Move-ActiveMailboxDatabase` `MDB01` `-ActivateOnServer` `AMBX2` `-MountDialOverride: None`

Figure 10. Enabling the passive copy of the MDB01 on AMBX02
Now the active database copy on the AMBX2 may be still Dismounted state. This is because the previous statue of the Database is dismounted. To mount the database uses the PowerShell cmdlet with mount-Database. Once the database is mounted that old database which was failed will reseed with the latest copy and bring the status into healthy state. This may take some time and it depends on the size of the database. Figure11. With red mark show the mounted state of MDB01 on AMBX2

`1`	`Get-MailboxDatabaseCopyStatus` `-Identity` `MDB01 \|` `select` `name, status, SelectcontentIndexState \|` `sort` `Status \|` `ft` `-auto`

Figure 11. MDB01 Mailbox Database copy is mounted on AMBX2 server
We have successfully moved the database to new node and you may need to move back the database to the original server then execute the below PowerShell cmdlet. This time database automatically mounts it because we have the Active copy in mounted state and replicated copy is also healthy. Figure 12 also show the mounted status on the result of Move Active Mailbox Database cmdlet execution

`1`	`Move-ActiveMailboxDatabase` `MDB01` `-ActivateOnServer` `AMBX1` `-MountDialOverride: None`

Figure 12. Moving MDB01 back to AMBX1
With this we have successfully tested and completed Database failure and Fail back
Server Failure /Fail back

Let’s assume scenario where we have the server AMBX1 down due to hardware failure or server is reboot accidentally
Let’s check what the Mailbox database copy status is after the server failure with the help of below PowerShell cmdlet. We see from the Figure 13. That all the database of AMBX1 has been mounted on AMBX2 and Database copy of AMBX1 has the status service down.
Primary Active manager running of the DAG use the preference settings and Best copy Selection process by listing the available copies and mounts the Best possible copy. During this process PAM has determine AMBX2 is the Best server to mount the database MDB01 and MDB02.

`1`	`Get-MailboxDatabaseCopyStatus` `-Identity` `MDB0* \|` `select` `name, status \|` `sort` `Status \|` `ft` `-auto`

Figure 13. Mailbox Database copy Status after AMBX1 Failure
Let’s bring AMBX1 up and check the Database copy status using the below PowerShell Cmdlet. It shows that database copy on AMBX1 is in healthy state Figure 14.

`1`	`Get-MailboxDatabaseCopyStatus` `-Identity` `MDB0* \|` `select` `name, status \|` `sort` `Status \|` `ft` `-auto`

Figure 14. Mailbox Database copy status after AMBX1 server is up.
Now if you think it’s time to move back the database from MDB01 and MBX02 to AMBX1 then let’s do it..

Move-ActiveMailboxDatabase MDB01 -ActivateOnServer AMBX1 -MountDialOverride: NoneMove-ActiveMailboxDatabase MDB02 -ActivateOnServer AMBX1 -MountDialOverride: None

This is great right, now finally let’s take a scenario that you wanted to patch AMBX2 and you wanted to move the entire database for now to AMBX1. You run a single line below PowerShell cmdlet to mount all the passive Database of AMBX2 on AMBX1. Then if the AMBX2 server is up then you can move/mount back the database using the above cmdlet Move-ActiveMailboxDatabase and using the right parameters.

Move-ActiveMailboxDatabase -Server AMBX2 -ActivateOnServer AMBX1

With this we have successfully tested and completed Server failure and Fail back
Site/Datacenter Failure and Fail back

Now this is most Interesting part of the above all. This is because in the above scenario PAM (Primary Active Manager) helps to bring the database up in case of the failure. But here we have defined not to bring the database up in case of failure by setting Activation bit. So, we have to manually execute some PowerShell cmdlets to bring the services up and running...
Before we understand and simulate Datacenter failure and fail back let’s do some post configuration on the DAG network. We know that all the servers which are in the DAG have two NIC, Public and Private. We also know that Private is for replication traffic and public IP is for MAPI traffic but it not defined in the DAG. We need to disable replication traffic happening thought MAPI network and dedicate only replication IP for replication. Let’s see what the current status of DAG network is? Below cmdlet pulls the details. Figure 15. Shows the details of the current DAG network. It has 4 subnets from both the sites and they are 172.168.1.0/24, 172.168.2.0/24, 10.0.1.0/24 and 10.0.2.0.0/24 and Replication is enabled on the entire Network

Get-DatabaseAvailabilityGroupNework

Figure 15. DAG network Status
The current DAG network looks very odd and replication is enabled on the entire DAG Networks. Let’s rework to create two new DAG Network using below PowerShell, one for MAPI with replication disabled and other for replication. Then add only the required subnets into it.

New-DatabaseAvailabilityGroupNetwork -DatabaseAvailabilityGroup DAG01 -Name MAPI -Subnets 172.168.1.0/24,172.168.2.0/24 -ReplicationEnabled: $falseNew-DatabaseAvailabilityGroupNetwork -DatabaseAvailabilityGroup DAG01 -Name Replication -Subnets 10.0.1.0/24,10.0.2.0/24

Figure 16. Execution result after creating two new DAG network with required subnets
Now we create two new DAG network and added the subnets into it. It’s time to remove the old subnets. Before that let’s see what the status of the DAG network is? Figure 17 show the details. It has two new DAG network, MAPI with replication set to False and MAPI subnets from both the Sites and Replication network with replication enabled

Figure 17. DAG network status after new DAG Network creation
Let’s remove the old DAG network01 - 04 which does not have any subnets in it. lets use below PowerShell cmdlet to do the same. Figure 18. Shows the result of the Powershell execution

Get-DatabaseAvailabilityGroupNetwork DAG01\DAGNetwork* | Remove-DatabaseAvailabilityGroupNetwork

Figure 18. Removing old DAG network
Let’s talk and understand how we can simulate the Datacenter failures and how we can fail back once the Primary datacenter come up. Now I have disconnected the Network between the AD sites and brought down all the Servers in ASites to have complete Datacenter failure. Lets see the status of the DAG01 from the BMBX1 using the below Powershell cmdlet. Figure 19. Show that the entire Database from Primary site is service down and Passive copy is in Disconnected state and healthy. We have also defined not to bring Secondary server Database up in case of Primary Datacenter Failures. This is done using DAC configuration

Get-MailboxDatabaseCopyStatus -Identity MDB0* | select name, status | sort Status | ft -auto

Figure 19. DAG status after the Primary DC Failure
Let’s understand some more important concept here.
In a our 3 server DAG, cluster quorum is maintained by a node majority - so at this point with two nodes offline the remaining server cannot hold quorum and this is also a reason our secondary server database is dismounted and cannot be re-mounted as well.
In Figure 20. Marked in red has the details about started mailbox servers and Stopped Mailbox Servers. Started mailbox servers are the servers which are available for DAG for bringing the Database online. Stopped mailbox Servers are no longer participating in the DAG. They me be servers which are offline or down because of Datacenter failures. When we are restoring the service on secondary site, ideally all the servers which are in primary should be marked as stopped and they should not use when the services are brought online.

Figure 20. DAG details
To move the Primary Site Servers into stopped state we need use the below PowerShell cmdlet. We also have to use the parameter -Configurationonly. This is because we cannot connect directly to the server as the server is offline. Use these below two PowerShell cmdlet to remove both the servers out to Stopped server state and Figure 21. Show the result of the same. You may see some warning and error message because these servers are not reachable.

Stop-DatabaseAvailabilityGroup -Identity DAG1 -Mailboxserver AMBX1 -ConfigurationonlyStop-DatabaseAvailabilityGroup -Identity DAG1 -Mailboxserver AMBX2 -Configurationonly

Figure 21. Stopping the DAG server to stopped Server State
Let’s verify again to see if the server has moved to stopped state. Figure 22. Show AMBX1 and AMBX2 has been moved to stopped state. Now these servers are not available for the DAG recovery.

Figure 22. DAG status after moving Asite servers into stopped mailbox Servers
Let’s now work on Recovering the DAG. Next we need to verify and make sure if cluster services are stopped on all the mailbox servers on Secondary Site. In our Secondary site we have only one mailbox servers BMBX1. So, let’s stop the cluster service using the command "Net stop Clussvc” or manually stop the cluster service from services console.
Now we need to restore DAG at the BSite. To restore use the below PowerShell cmdlet. Restore-databaseavailablilitygroup cmdlet does the following
1. Custer Quorum will be formed at the new server BMBX1 as old Quorum is no
Longer reachable
2. AMBX1 and AMBX2 nodes will be marked as stopped state and it will evict servers
One by one leaving only one node BMBX1 into the DAG
3. Switch to use Alternative file share Witness which was defined while creating the DAG

Restore-DatabaseAvailabilityGroup -Identity DAG01 -ActiveDirectorySite BSite

Figure 23. Execution result of Restore Database availability group
Let’s look at the DAG -status before we continue. Figure 23 should has the new details like Operational Servers is BMBX1 as we have evicted other servers out and also PAM(Primary Active Manager) is operational from BMBX1

Figure 23. Dag PAM and Operation Server Status
Let’s check out how the Failover cluster manager looks. We should see that there is only one Node BMBX1 and current node hosting cluster is BMBX1 and it’s using the alternative file share witness BHC1 which is good from Figure 24

Figure 24. Failover Cluster manager Status
Let’s verify again the Mailbox Database copy status using the powershell cmdlet and Figure 25 shows that we have still Databasecopies on BMBX1 is in Disconnected and Healthy state

Figure 25. Mailbox Database copy Status
During the DAG configuration we had set activation block on database copies on BMBX1. To remove the activation block on all the copies, we need to execute the blow Powershell cmdlets. Figure 26 has the execution result

Resume-MailboxDatabaseCopy 'MDB01\BMBX1'Resume-MailboxDatabaseCopy 'MDB02\BMBX1'Resume-MailboxDatabaseCopy 'MDB03\BMBX1'
Resume-MailboxDatabaseCopy 'MDB04\BMBX1'

Figure 26. Execution result of Resume mailbox Database copy
With this we have resumed all the Mailbox Database copies on BMBX1. Now let’s check the status. Figure 27 show that DAG status with the entire database mounted on BMBX1 and serving the email for the users

Figure 27. DAG Status with all the Database copies mounted on BMBX1
This cool right... Just to make you remember every day is not Sunday and some times it can also be a Friday evening and things don't come up. Friday even at office its worst than Monday morning . If databases are not mounted automatically using above technique then you can use below Powershell command to manually mount. You bunch of options to troubleshoot and mount the database. TechNet has more details description on parameters of Move-Activemailboxdatabase

Move-ActiveMailboxDatabase –Server FQDNofaServerinPrimarySite –ActivateOnServer FQDNofaServerinDRSite

Thank God lets go home and come back on Monday... Haa haa
Fail back to Primary Site
Lets bring all the servers at primary site up and as these servers are out of DAG configuration, it will have no impact on the DAG. Now the DAG has only one server BMBX1. To fail back to the primary site we need add the Primary Site mailbox servers AMBX1 and AMBX2 into DAG back. To add the server back, below Powershell cmdlet would help us to do the same. You also need to make sure cluster service has been started on the mailbox servers before running this command.

Start-DatabaseAvailabilitygroup -Identity DAG01 -mailboxServer AMBX1Start-DatabaseAvailabilitygroup -Identity DAG01 -mailboxServer AMBX2

Figure 28. Execution result of adding AMBX1 and AMBX2 into the DAG
If we see the Database available group status you would find that all the mailbox servers are in started and operation state. Figure 29 has the details of the same.

Figure 30. DAG status after adding mailbox servers back
Execute the below PowerShell cmdlet to set the changes. This would seed all the changes from the Active copies and bring the passive copies into the healthy state

Set-DatabaseAvailabilitygroup -Identity DAG01

Let’s now verify the Mailbox Database copy to make sure that we have all active copies mounted on BMBX1 and passive copies replicated and also it’s in healthy state both on AMBX1 and AMBX2. Figure 31

Get-MailboxDatabaseCopyStatus -Identity MDB0* | select name, status | sort Status | ft -auto

Figure 31. Mailbox Database copy Status
To bring the respective copies of AMBX1 and AMBX2 up, we need to run
Move-Activemailboxdatabase PowerShell cmdlet and other complete set of cmdlets are below. Figure 32 show the result of the same

Move-ActiveMailboxDatabase MDB01 -ActivateOnServer AMBX1 -MountDialOverride: GoodAvailabilityMove-ActiveMailboxDatabase MDB02 -ActivateOnServer AMBX1 -MountDialOverride: GoodAvailabilityMove-ActiveMailboxDatabase MDB03 -ActivateOnServer AMBX2 -MountDialOverride: GoodAvailability
Move-ActiveMailboxDatabase MDB04 -ActivateOnServer AMBX2 -MountDialOverride: GoodAvailability

Figure 32. Move Active mailbox Database execution result.
Verify and confirm again, to see if we have the entire database moved and mounted on the primary node and other copies are replicated in Healthy state. Figure 33. Show the details of the same

Figure 33. Mailbox Database copy Status after the recovery of Database at Primary Site
Finally last but not least we wanted to disable automatic activation of database in secondary (DR) Site. This configuration is very important and it can be again disabled using the same old below PowerShell cmdlet and Figure 34 show the result of the same

Suspend-MailboxDatabaseCopy -Identity MDB01\BMBX1 -ActivationOnlySuspend-MailboxDatabaseCopy -Identity MDB02\BMBX1 -ActivationOnlySuspend-MailboxDatabaseCopy -Identity MDB03\BMBX1 -ActivationOnly
Suspend-MailboxDatabaseCopy -Identity MDB04\BMBX1 -ActivationOnly

Figure 34. Disabling Activation bit on Passive copy of the Database on secondary site
With this we have tried to simulate all different type of failure - Database Failure, Server failure and Datacenter failure and how to recover back from the failure. DAG has made HA very easy and quicker to recover. Here we just talked about the DAG and the mailbox servers and Mailbox Database and the recovery it. Exchange is not just DAG. We have to plan and design for the failover and fail back of other servers like Hub, Client etc. This TechNet article has good details on other servers. I hope this article is information and you can use this in your real life scenario.

Configuring Database Availability Group

2012-08-31T15:56:00.002-07:00

1) Directory services – Win2k3ad.happy.com

2) Domain Name System (DNS) name resolution – Win2k3.happy.com

3) File Share Witness (FSW) – Non –Exchange Server (Member Server)

4) 2 DAG Servers – DAG1 & DAG2

Current Configuration:

I have the following server setup:

1) Win2k3AD – This is my AD & DNS for happy.com

2) A Member Server – This is just a placeholder for my File Witness Share

3) DAG-1 – My DAG Member Server

a. Public Ip Address : 192.168.1.11

b. HeartBeat – 10.10.10.10

4) DAG-2 – My DAG Member Server

a. Public Ip Address : 192.168.1.12

b. HeartBeat – 10.10.10.20

In Summary for the above:

Network Configuration

Host Name	FQDN	IP Address	Default Gateway	DNS	OS Version	Service
Win2k3ad	Win2k3ad.happy.com	192.168.1.1	192.168.1.1	192.168.1.1	Win2k3 Sp2	AD & DNS
E2K10	E2k10.happy.com	192.168.1.x	192.168.1.1	192.168.1.1	Win2k8R2	FSW
DAG-1	DAG-1.happy.com	192.168.1.5	192.168.1.1	192.168.1.1	Win2k8R2	E2K10SP1
DAG-2	DAG-2.happy.com	192.168.1.4	192.168.1.1	192.168.1.1	Win2k8R2	E2K10SP1
DAG-1 (RN)		10.10.10.10
DAG-2 (RN)		10.10.10.20

Note : It is recommended to have static routes between the replication network and for this we can use netsh

To know more about netsh http://support.microsoft.com/kb/242468 or http://www.microsoft.com/downloads/en/details.aspx?FamilyID=f41878de-2ee7-4718-8499-2ef336db3df5&displaylang=en

Inorder to configure routing between replication network copy paste this command on the replication network server

netsh interface ipv4 add route 10.10.10.0/24 Replication 10.10.10.254

Ensure that Register this connection's addresses in DNS is cleared for Replication Network

Network Adapter Configuration

Features	Mapi Network	Replication Network
Client for Microsoft Networks	Enable	Disbale
QoS Packet Scheduler	Not Necessary	Not Necessary
File and Printer Sharing for Microsoft Networks	Enable	Disable
Internet Protocol Version 4 (TCP/IP v4)	Enable	Enable
Internet Protocol Version 6 (TCP/IP v6)	Not Necessary	Not Necessary
Link-Layer Topology Discovery Mapper I/O Driver	Enable	Enable
Link-Layer Topology Discovery Responder	Enable	Enable

FSW Consideration:

There is no hard or any major requirement for File Share Witness server. It can run on any sort of configuration and can be any server. Recommend to have member server instead of DC. And also it is very important for you to understand when you should go FSW model, for more details see my last article which talks about How the Failover occurs for DAG.

Deployment of DAG:

So far I hope you are aware about the setup model which I planned for DAG. Now let’s get into the creation of DAG.

Just to summarize in short…

Already I have exchange 2010 in place for DAG. For Each Server I have two independent disk database storage. Now we are in the process of creating the DAG.

Key Notes:

1) DAG can be supported upto 16 copies

2) Unique Name for the DAG should not be more than 15 characters.

3) Without using DatabaseAvailabilityGroupIpAddresses parameter it will assign an IP address from DHCP server

4) Always keep static routes between the replication network

Step1 : Creation of DAG

Inorder to create DAG you can use either EMC or EMS. Both of them will work, however my personal recommendation is to use EMS. The reason behind this is, you can do modulation as per your requirement in one single line. Like let say we need a DAG to use static ip address then EMS will be the possible way, another reason adding the DAG for different Subnet Exchange Server.

Based on my above recommendation I am going to create folder called as DAG which is going to have static ip address 192.168.1.7 and witness directory path location for this DAG will be one of my member server “SCCM.happy.com”

Note: If I am using simple command just like providing the cmdlet to create new-databaseavailablitygroup with a name called as DAG. It will try to find my hub server which doesn’t have any mailbox server role installed automatically. In my case I don’t have any single stand-alone server which is having only hub server so that’s why I am going to specify my DAG hosting servername.

The command which I am going to use it here as follows:

New-DatabaseAvailabilityGroup -Name DAG -WitnessServer SCCM -WitnessDirectory C:\DAG -DatabaseAvailabilityGroupIPAddresses 192.168.1.7

Let’s understand more on the above command,

New-DatabaseAvailabilityGroup: It is the parameter which will create Database Availability Group

-Name: Specify the name for the DAG which you need to create, example I called it as DAG.

-WitnessServer: Witness Server is nothing but a File Witness Shareholding server. In Exchange 2007 we had a concept of CCR where both the servers are having disk independent with each other and there are lot of chance both the server can own the ownership of the exchange database, so inorder to avoid this Microsoft introduced a concept called a File Share Witness share where we will have witness directory. This FSW Server will decide who is going to own the ownership based on the voting poll. In our example I chosen a non-exchange server – SCCM

WitnessDirectory : Witness Directory is a folder which will be created under FSW Server. This Witness Directory folder will the witness log files which will keep a track of DAG responses.

The above screen shows the folder location where the witness Directory is created under FSW Server.

Once we run the new-databaseavailabilty command, it will configure the DAG Configuration Folder in the FSW Server and in the organization it will create a New DAG

Note:

Ø Witness Directory folder will be seen after you add the Exchange Server in DAG.

Ø Before you execute the above command and if your server is a non-exchange Server then you need to add this server to “Exchange Trusted Subsystem” Universal Security Group.

Ø If the server is a non-exchange ensure that your DAG Server is part of the Local Administrator Group of the non-exchange server.

Step2: Add Mailbox Server to the DAG

Now Add the Exchange Server into the newly created DAG Container. For me the Exchange Server is DAG-1 & DAG-2, and inorder to add this you can use EMC or EMS.

If you are using EMC, Expand the Organization, click on Mailbox, click on “Database Availability Group” Tab, right click DAG Container and select “Manage Database Availability Group Membership” then click on ADD and add those two Servers and finally click on Manage:

Instead of EMC if you would like to add the servers through EMS then type the following command

Add-DatabaseAvailabilityGroupServer -MailboxServer 'DAG-1' -Identity 'DAG'

Add-DatabaseAvailabilityGroupServer -MailboxServer 'DAG-2' -Identity 'DAG'

Once you add the Servers in the DAG, you will the servers in the Member Servers

Step 3: Configuration of DAG (Optional):

Most of the DAG configuration we had covered while creating the DAG, but still I would like to share you some of the other few optional which can be utilized as per the need.

Ø Alternate Witness Server & Alternate Witness Directory : Now let say due to some or the other reason if your FSW crashed or network outage, it will be kind of bit risk to run the show just because incase of any sort of network failure between the exchange servers then any server can take the ownership. So Ms came with a new option called as Alternate Witness Server

Ø If you forget to configure the static ip address, bydefault DAG will take an ip address from DHCP server, later if you want to configure static ip address you can use the following command

Set-DatabaseAvailabilityGroup -Identity DAG -DatabaseAvailabilityGroupIPAddresses 192.168.1.7

Ø If you are having DAG across different site then you need to configure static ip address for each site location

Set-DatabaseAvailabilityGroup –Identity DAG1 –DatabaseAvailabilityGroupIPAddresses 192.168.1.7,192.168.0.7

Ø Enabling DAC : Set-DatabaseAvailabilityGroup -Identity DAG -DatacenterActivationMode DagOnly

Note: Bydefault DAC will be disabled and it should be enabled if you are having more than 3 exchange servers across multiple AD Sites. This command will avoid split brain syndrome.

Ø Replication Port Configuration: Bydefault DAG will use 64327 port for log shipping and seeding. Sometime it might be concern because this port is a dynamic range defined by IANA & according to IANA dynamic ports cannot be registered, so if you want you can change the port by executing the following command:

Set-DatabaseAvailabilityGroup -Identity DAGID –ReplicationPort portnumber

And also ensure that new port which has been updated needs to allowed in the firewalls.

Ø If you want to see the current configuration details in much more details then execute the following command:

Get-DatabaseAvailabilityGroup | Fl

Step4: Add Mailbox Database Copies:

So far we configured the DAG, now it is a time to add the mailbox database into the DAG. Inorder to do this:

Ø Open the EMS and execute the following command

Add-MailboxDatabaseCopy -Identity Database1 -MailboxServer Dag-2

Add-MailboxDatabaseCopy -Identity Database2 -MailboxServer Dag-1

Note: If you want to set activation preference you can set that one also by adding –activationpreference.

Note: When you execute add-mailboxdatabase copy, it will seed the database and log file shipping to the exact drive name what we have it for the master database copy. Let say if my master Database is in the E Drive of DAG-2, it will place the database copy in the E Drive of DAG-1

Master Copy Location:

MailboxDatabase Copy Location:

Step5: Validate the DAG Configuration:

Now we are in a good stage where we have database high availability, however before we put this server under production it is very important for us to validate

Ø Run Test-replicationhealth command from the EMS:

Test-ReplicationHealth -Identity Dag1

Ø Check the MailboxDatabaseCopyStatus

Get-MailboxDatabaseCopyStatus -Identity Database2 | FL

Ø Check the database copies on a particular server :

Get-MailboxDatabaseCopyStatus -Server DAG-1 | FL

Ø Check the application and system log for any errors

Ø To make our life much more easy in Exchange 2010, we have scripts to find the performance and counters metrics, replication metrics etc..

o CollectOverMetrics.ps1

o CollectReplicationMetrics.ps1

o CheckDatabaseRedundancy.ps1

Ø Apart from the above, administrator can try the following:

o Shutdown the primary server

o Remove the Disk and see the status

o Unplug network cable

o Shutdown the FSW server to check activity of Alternate FSW

I just did a small test: Shutting down the DAG-1 Server .

Datacenter Activation Coordination (DAC)

2012-08-31T15:49:00.005-07:00

Datacenter Activation Coordination (DAC)

Datacenter Activation Coordination (DAC) mode is a property setting for a database availability group (DAG). DAC mode is disabled by default and should be enabled for all DAGs with two or more members that use continuous replication. DAC mode shouldn't be enabled for DAGs in third-party replication mode unless specified by the third-party vendor.
If a catastrophic failure occurs that affects the DAG (for example, a complete failure of one of the datacenters), DAC mode is used to control the startup database mount behavior of a DAG. When DAC mode isn't enabled, and a failure occurs that affects multiple servers in the DAG, when a majority of the DAG members are restored after the failure, the DAG will restart and attempt to mount databases. In a multi-datacenter configuration, this behavior could cause split brain syndrome, a condition that occurs when all networks fail, and DAG members can't receive heartbeat signals from each other. Split brain syndrome can also occur when network connectivity is severed between the datacenters. Split brain syndrome is prevented by always requiring a majority of the DAG members (and in the case of DAGs with an even number of members, the DAG's witness server) to be available and interacting for the DAG to be operational. When a majority of the members are communicating, the DAG is said to have quorum.
For example, consider a scenario where the first datacenter contains two DAG members and the witness server, and the second datacenter contains two other DAG members. If the first datacenter loses power and you activate the DAG in the second datacenter (for example, by activating the alternate witness server in the second datacenter), if the first datacenter is restored without network connectivity to the second datacenter, the active databases within the DAG may enter a split brain condition.

How DAC Mode Works

DAC mode is designed to prevent split brain from occurring by including a protocol called Datacenter Activation Coordination Protocol (DACP). After a catastrophic failure, when the DAG recovers, it won't automatically mount databases even though the DAG has a quorum. Instead DACP is used to determine the current state of the DAG and whether Active Manager should attempt to mount the databases.
You might think of DAC mode as an application level of quorum for mounting databases. To understand the purpose of DACP and how it works, it's important to understand the primary scenario it's intended to deal with. Consider the two-datacenter scenario. Suppose there is a complete power failure in the primary datacenter. In this event, all of the servers and the WAN are down, so the organization makes the decision to activate the standby datacenter. In almost all such recovery scenarios, when power is restored to the primary datacenter, WAN connectivity is typically not immediately restored. This means that the DAG members in the primary datacenter will power up, but they won’t be able to communicate with the DAG members in the activated standby datacenter. The primary datacenter should always contain the majority of the DAG quorum voters, which means that when power is restored, even in the absence of WAN connectivity to the DAG members in the standby datacenter, the DAG members in the primary datacenter have a majority and therefore have quorum. This is a problem because with quorum, these servers may be able to mount their databases, which in turn would cause divergence from the actual active databases that are now mounted in the activated standby datacenter.
DACP was created to address this issue. Active Manager stores a bit in memory (either a 0 or a 1) that tells the DAG whether it's allowed to mount local databases that are assigned as active on the server. When a DAG is running in DAC mode (which would be any DAG with three or more members), each time Active Manager starts up the bit is set to 0, meaning it isn't allowed to mount databases. Because it's in DAC mode, the server must try to communicate with all other members of the DAG that it knows to get another DAG member to give it an answer as to whether it can mount local databases that are assigned as active to it. The answer comes in the form of the bit setting for other Active Managers in the DAG. If another server responds that its bit is set to 1, it means servers are allowed to mount databases, so the server starting up sets its bit to 1 and mounts its databases.
But when you recover from a primary datacenter power outage where the servers are recovered but WAN connectivity has not been restored, all of the DAG members in the primary datacenter will have a DACP bit value of 0; and therefore none of the servers starting back up in the recovered primary datacenter will mount databases, because none of them can communicate with a DAG member that has a DACP bit value of 1.

DAC Mode for DAGs with Two Members

DAGs with two members have inherent limitations that prevent the DACP bit alone from fully protecting against application-level split brain syndrome. For DAGs with only two members, DAC mode also uses the boot time of the DAG's alternate witness server to determine whether it can mount databases on startup. The boot time of the alternate witness server is compared to the time when the DACP bit was set to 1.

If the time the DACP bit was set is earlier than the boot time of the alternate witness server, the system assumes that the DAG member and witness server were rebooted at the same time (perhaps because of power loss in the primary datacenter), and the DAG member isn't permitted to mount databases.
If the time that the DACP bit was set is more recent than the boot time of the alternate witness server, the system assumes that the DAG member was rebooted for some other reason (perhaps a scheduled outage in which maintenance was performed or perhaps a system crash or power loss isolated to the DAG member), and the DAG member is permitted to mount databases.

Important:

Because the alternate witness server's boot time is used to determine whether a DAG member can mount its active databases on startup, you should never restart the alternate witness server and the sole DAG member at the same time. Doing so may leave the DAG member in a state where it cannot mount databases on startup. If this happens, you must run the Restore-DatabaseAvailabilityGroup cmdlet on the DAG. This resets the DACP bit and permits the DAG member to mount databases.

Other Benefits of DAC Mode

In addition to preventing split brain syndrome at the application level, DAC mode also enables the use of the built-in site resilience cmdlets used to perform datacenter switchovers. These include the following:

Performing a datacenter switchover for DAGs that are not in DAC mode involves using a combination of Exchange tools and cluster management tools.
For more information about datacenter switchovers, see Datacenter Switchovers.

Enabling DAC Mode

DAC mode can be enabled only by using the Exchange Management Shell. Specifically, you can use the Set-DatabaseAvailabilityGroup cmdlet to enable and disable DAC mode, as illustrated in the following example.

Set-DatabaseAvailabilityGroup -Identity DAG2 -DatacenterActivationMode DagOnly

Transport Dumpster

2012-08-01T16:59:00.001-07:00

Introduction

The transport dumpster feature of Exchange 2007 is specific to the Hub Transport server role. The idea behind the transport dumpster is simple: each Hub Transport server in an Active Directory site that contains a CCR environment maintains a rolling queue of email messages that have recently been delivered to users whose mailboxes are hosted on that CCR environment. Then, during the recovery process that results after a lossy failover of the CCR environment, all Hub Transport servers in the Active Directory site containing the CCR environment automatically redeliver those messages in the transport dumpster queue.
It is important to understand that the transport dumpster protects against the loss of some data, not all data. For example, a transient email that is being sent from the Mailbox server to the Hub Transport server at the time of the lossy failover may not be included in the transport dumpster, resulting in data loss. Other examples include calendar appointments and any email messages stored as draft items when Outlook is running in online (non-cached) mode.
The transport dumpster feature is optional and therefore can be turned off. However, it is enabled by default and is likely that most organizations will want to make use of this feature. That being said, it is important to note the requirements, such as increased disk I/O, when running the transport dumpster feature. We will be looking at this in part two of this article.
Throughout this two-part article I am going to be assuming that Exchange 2007 Service Pack 1 has been deployed as this service pack brought many enhancements to the transport dumpster feature. For example, with Exchange 2007 Service Pack 1, the transport dumpster supports the Local Continuous Replication (LCR) feature. Despite the fact that LCR is supported, I’m going to be focusing this article on the transport dumpster’s involvement within a Cluster Continuous Replication (CCR) environment.

Transport Dumpster Configuration

The transport dumpster is configured on a per-storage group basis. The two configurable parameters that control the length of time that messages remain in the transport dumpster are:

MaxDumpsterSizePerStorageGroup - As you can probably tell from the name, this is the amount of storage space allocated per storage group for messages within the dumpster. Microsoft makes clear recommendations on the value that you should give MaxDumpsterSizePerStorageGroup. If your organization has a maximum permissible message size configured, simply make the MaxDumpsterSizePerStorageGroup parameter 1.5 x the maximum message size. For example, if your maximum message size is 30MB, the MaxDumpsterSizePerStorageGroup parameter should be set to 45MB. If your organization does not have a maximum permissible message size, you should set the MaxDumpsterSizePerStorageGroup parameter to be 1.5 x the average message size within your organization. If you don’t know what your average message size is, you can use the Exchange Profile Analyzer tool which is available for free download from the Microsoft downloads site. Alternatively, other 3rd party tools will be able to provide this information. The default value of MaxDumpsterSizePerStorageGroup is 18MB, so unless your maximum or average message size within your organization is 12MB, you will need to alter this value.
MaxDumpsterTime - This parameter states for how many days, hours, minutes and seconds a message can remain in the transport dumpster. By default, this parameter has a value of 7.0:0:0 which translates to 7 days, 0 hours, 0 minutes and 0 seconds. Microsoft recommends that the MaxDumpsterTime is set to 7 days so, generally speaking; you should not have to alter the configuration of this parameter.

To alter these values you can either use the Exchange Management Console or the Exchange Management Shell. Let us take a look at the Exchange Management Shell first. These values are organization-wide transport values and therefore are not tied to a specific Exchange server. Therefore, you would not expect to use the Get-TransportServer or Set-TransportServer cmdlets to view and alter these values. Rather, you need to use the Get-TransportConfig and Set-TransportConfig cmdlets. Figure 1 shows you a sample output from the Get-TransportConfig cmdlet where you can clearly see that the MaxDumpsterSizePerStorageGroup and MaxDumpsterTime parameters are both set to their default values, namely 18MB and 7 days respectively.

Figure 1: Results of the Get-TransportConfig Cmdlet
If you were required to change the MaxDumpsterSizePerStorageGroup parameter to a value of 45MB, you would simply run the following cmdlet:
Set-TransportConfig –MaxDumpsterSizePerStorageGroup 45MB
Similarly, the following cmdlet can be used to change the MaxDumpsterTime to a sample value of 5 days and 5 hours, although I do not recommend changing this parameter as I have stated earlier in this article. This is based on the fact that Microsoft itself recommends leaving the default value of 7 days in place.
Set-TransportConfig –MaxDumpsterTime 5.5:0:0
To use the Exchange Management Console to alter these settings, navigate to the Organization Configuration node of the console tree and highlight the Hub Transport object beneath it. In the result pane, select the Global Settings tab and you will see the Transport Settings object. Right-click the Transport Settings object and choose Properties from the context menu. You will be presented with the screen shown in Figure 2 where you can see where to change the two transport dumpster values.

Figure 2: Transport Dumpster Settings in Exchange Management Console
Note:
If you wish to disable the transport dumpster for all storage groups across your Exchange 2007 organization, you can set either the MaxDumpsterSizePerStorageGroup or MaxDumpsterTime values to 0. There is therefore no use in setting one parameter, leaving the other set to 0 and expecting the transport dumpster to be operational.

shared mailbox

2012-07-27T08:40:00.003-07:00

Create and configure a shared mailbox with PowerShell

After you create a shared mailbox, you have to assign permissions to all users who require access to the shared mailbox. Users can't sign in to the shared mailbox. They have to sign in to their own mailbox and then open the shared mailbox to which they've been assigned permissions.

Here's how to use PowerShell to create and configure a shared mailbox for the Corporate Printing Services department at Contoso Corporation.

Create a shared mailbox To create the shared mailbox for Corporate Printing Services, run one of the following commands:

New-Mailbox -Name "Corporate Printing Services" -Alias corpprint -Shared

Set-Mailbox corpprint -ProhibitSendReceiveQuota 5GB -ProhibitSendQuota 4.75GB -IssueWarningQuota 4.5GB

New-Mailbox -Name "Corporate Printing Services" -Alias corpprint -Shared

The new shared mailbox is displayed in the Mailboxes list in the Exchange Control Panel.

    2.   Create a security group for the users who need access to the shared mailbox   In the Exchange Control Panel, create a security group for the staff who need access to the shared mailbox for Corporate Printing Services.

a. Select My Organization > Users & Groups > Distribution Groups > New.
b. Specify a display name, alias, and e-mail address. In this example, we'll use Printing Services Staff, corpprintDG, and corpprintDG@contoso.com.

c. Select the Make this group a security group check box.

d. In the Ownership section, click Add to add an owner, if necessary.
e. In the Membership section, click Add.

f. In the Select Members page, select the users you want to add. When you are finished, click OK.
g. On the New Group page, click Save.

Note   After you create a security group, the membership is closed. When membership is closed, only group owners can add members to the security group, or owners have to approve requests to join the group. Additionally, only group owners can remove members from the security group.

   3.    Assign the security group the FullAccess permission to access the shared mailbox   To enable members of the Printing Services Staff security group to open the shared mailbox, read e-mail, and use the calendar, run the following command:

Add-MailboxPermission "Corporate Printing Services" -User corpprintDG -AccessRights FullAccess
     4.    Assign the security group the SendAs permission to the shared mailbox   To enable members of the Printing Services Staff security group to send e-mail from the shared mailbox, run the following command:

Add-RecipientPermission "Corporate Printing Services" -Trustee corpprintDG -AccessRights SendAs

Outlook Anywhere

2012-07-25T14:25:00.002-07:00

What is Outlook Anywhere?

This is a system that lets you connect Microsoft Outlook to to your Exchange server over the web, this means you can connect to to your email, calendaring and tasks etc, without the need for a VPN connection.

Outlook Anywhere wizard on the Exchange Server 2010 Client Access server to allow users to connect to their Exchange mailbox from the Internet. Outlook Anywhere eliminates the need for users in remote offices or mobile users to use a virtual private network (VPN) to connect to their Exchange servers.
Outlook Anywhere will be enabled on your Client Access server after a configuration period of approximately 15 minutes. To verify that Outlook Anywhere has been enabled, check the application event log on the Client Access server

The Windows RPC over HTTP Proxy component, which Outlook Anywhere clients use to connect, wraps remote procedure calls (RPCs) with an HTTP layer. This allows traffic to traverse network firewalls without requiring RPC ports to be opened. In Exchange 2010, as in Exchange 2007, it's easy to deploy and manage this feature. To deploy Outlook Anywhere in your Exchange 2010 messaging environment, you need to enable Outlook Anywhere on at least one Client Access server using the Enable Outlook Anywhere wizard in the Exchange Management Console

Install a valid Secure Sockets Layer (SSL) certificate from a certification authority (CA) that the client trusts.
Install the Microsoft Windows RPC over HTTP Proxy component if it wasn't already installed by default in Windows Server 2008. For detailed steps, see Install the Windows RPC Over HTTP Proxy Component.
Enable Outlook Anywhere on the Client Access server.

Step 1 Configure Exchange

In the console tree, navigate to Server Configuration > Client Access.
In the action pane, click Enable Outlook Anywhere.
In the Enable Outlook Anywhere wizard, type the external host name or URL for your organization in the box under External host name.
This is the URL, for example site.contoso.com, that users will use to connect to the Exchange server by using Outlook Anywhere.

Enable-OutlookAnywhere -Server 'Exch1' -ExternalHostname 'site.contoso.org' -DefaultAuthenticationMethod 'Basic' -SSLOffloading $false

Enable-OutlookAnywhere -Server:Server01 -ExternalHostname:mail.contoso.com -ClientAuthenticationMethod:Ntlm -SSLOffloading:$true

Availability service

2012-07-25T14:12:00.003-07:00

The Availability service retrieves free/busy information directly from the target mailbox for users on Exchange 2010 and Exchange 2007 and can be configured to retrieve free/busy information for users on earlier versions of Exchange. For topologies that have Exchange 2007 or Exchange 2010 mailboxes in which all clients are running Outlook 2007, the Availability service is used to retrieve free/busy information.

Note:
If you have Outlook 2007 clients running on Exchange Server 2003 mailboxes, Outlook 2007 will use public folders to retrieve free/busy information.

Outlook 2007 uses the Exchange Server 2010 Autodiscover service to obtain the URL of the Availability service. For more information about the Autodiscover service, see Managing the Autodiscover Service.
The Availability service is part of the Exchange 2010 programming interface. It is available as a public Web service to allow developers to write third-party tools for integration purposes.
You can use the Exchange Management Shell to configure the Availability service. You can't use the Exchange Management Console to configure the Availability service.
-------------------------------------------------------------------------------------------------------
You must create a test account before you can diagnose Availability service issues using the Test-OutlookWebServices cmdlet. To create the test mailbox, log on to the Exchange Server 2007 or Exchange 2010 Mailbox server

This example tests access to the Availability service for user User1@Contoso.com.

Test-OutlookWebServices -Identity: User1@Contoso.com
This example tests user access to the Availability service on the Client Access server ClientAccessServer01.

Test-OutlookWebServices -ClientAccessServer ClientAccessServer01

This example tests Availability service connectivity between users in two different Active Directory sites.






 

Test-OutlookWebServices -Identity User1@Site1.Contoso.com -TargetAddress User2@Site2.Fabrikam.com

--------------------------------------------------------------------------------------------------------
This example configures the Availability service for load balancing for a domain named Contoso.com.

Set-WebServicesVirtualDirectory -Identity "EWS*" -ExternalUrl "Https:// mail.contoso.com/EWS/Exchange.asmx" -InternalUrl "Https:// mail.contoso.com/EWS/Exchange.asmx"

Note:
If you have a set of load balanced Client Access servers, you don't have to specify the name of each server when you run this command. You only need to use the name of one of the servers in the set of load balanced servers.

------------------------------------------------------------------------------------------------------------
This example configures the Availability service to retrieve per-user free/busy information on a Client Access server in the target forest.

Get-ClientAccessServer | Add-ADPermission -Accessrights Extendedright -Extendedrights "ms-Exch-
EPI-Token-Serialization" -User "<Remote Forest Domain>\Client Access servers"

This example defines the free/busy access method that the Availability service uses on the local Client Access server in the source forest. The local Client Access server is configured to access free/busy information from the forest ContosoForest.com on a per-user basis. This example uses the service account to retrieve free/busy information.

Add-AvailabilityAddressSpace -Forestname ContosoForest.com -AccessMethod PerUserFB -UseServiceAccount:$true


To configure bidirectional cross-forest availability, repeat these steps in the target forest.

---------------------------------------------------------------------------------------------------------

This example configures trusted cross-forest availability with a service account.

Get-ClientAccessServer | Add-ADPermission -Accessrights Extendedright -Extendedright "ms-Exch-EPI-Token-Serialization"  -User "<Remote Forest Domain>\Exchange servers"

Autodiscover

2012-07-24T11:47:00.002-07:00

Autodiscover information is stored in a so called SCP or Service Connection Point. You can view this SCP using Active Directory Sites and Services after you have enabled the “View Services Node”
When installing the Client Access Server (Autodiscover is part of this Server Role) the SCP is automatically created in Active Directory and configured with the default values. If you have multiple CAS Servers there will be multiple SCP’s as well.

Get-AutodiscoverVirtualDirectory |FL
Get-AutodiscoverVirtualDirectory | Select name, internalURL, externalURL
Get-ClientAccessServer | fl name, autodiscoversitescope # to find out the present scopes
Set-ClientAccessServer –identity “Paris CAS Servername”–AutodiscoverSiteScope “Site1, Site2, Site3”

Exchange Server 2010 the properties related to these settings are configured during setup of the Client Access Server when entering the “this is an external facing Client Access Server” option. When you do not select this option, or in Exchange Server 2007 you have to configure these properties manually using the Exchange Management Shell:

Changing these properties doesn’t have the desired effect. For changing the internalURL settings you have to modify the Client Access Server properties. Enter the following command in an Exchange Management Shell:

Get-ClientAccessServer –Identity X2007SRV | Set-ClientAccessServer –AutodiscoverServiceInternalUrihttps://autodiscover.inframan.nl/autodiscover/autodiscover.xml

Set-OWAVirtualDirectory –Identity 2010CASHUB02\OWA (default web site) -ExternalURL https://webmail.exchange14.nl/OWA

Set-OABVirtualDirectory –Identity 2010CASHUB02\OAB (default web site) -ExternalURL https://webmail.exchange14.nl/OAB

Set-WebServicesVirtualDirectory –Identity 2010CASUB02\EWS (default web site) -ExternalURL https://webmail.exchange14.nl/ews/exchange.asmx

Set-ActiveSyncVirtualDirectory –Identity 2010CASHUB02\Microsoft-Server-ActiveSync (default web site) -ExternalURL https://webmail.exchange14.nl/Microsoft-Server-ActiveSync

This setting is only valid for Exchange Server 2010:

Set-ECPVirtualDirectory –Identity 2010CASHUB02\ECP (default web site) -ExternalURL https://webmail.exchange14.nl/ECP

The last step is to configure the external DNS. Both the webmail hostname as well as the Autodiscover hostname need to point to the external facing Client Access Server.
When you start up Outlook 2007 or Outlook 2010 you can automatically configure your profile, just by entering your e-mail address and password. When Outlook is configured it can take some time before Outlook is synchronized, but after some time you should be all set. If all goes well you should be able to set your out-of-office settings and check other mailboxes free/busy information.

Commands:

Set-ClientAccessServer -Identity CASServer -AutoDiscoverServiceInternalUri https://webmail.shudnow.localS/Autodiscover/Autodiscover.xml
Set-WebServicesVirtualDirectory -Identity “CASServer\EWS (Default Web Site)” -InternalURL https://webmail.shudnow.local/EWS/Exchange.asmx -ExternalURL https://webmail.shudnow.net/EWS/Exchange.asmx -BasicAuthentication:$true
Set-OABVirtualDirectory -Identity “CASServer\OAB (Default Web Site)” -InternalURL https://webmail.shudnow.local/OAB -ExternalURL webmail.shudnow.net/OAB -RequireSSL:$true
Enable-OutlookAnywhere -Server CASServer -ExternalHostname “webmail.shudnow.net” -ClientAuthenticationMethod “Basic” -SSLOffloading:$False
Set-ActiveSyncVirtualDirectory -Identity “CASServer\Microsoft-Server-ActiveSync (Default Web Site)” -ExternalURL https://webmail.shudnow.net/Microsoft-Server-Activesync
Set-UMVirtualDirectory -Identity “CASServer\UnifiedMessaging (Default Web Site)” -InternalURL https://webmail.shudnow.local/UnifiedMessaging/Service.asmx -ExternalURL https://webmail.shudnow.net/UnifiedMessaging/Service.asmx -BasicAuthentication:$true

CAS Array

And what role does the CAS Array play in the Autodiscover story? The CAS Array is implemented when you have multiple Client Access Servers in a load balanced scenario. Outlook clients connect to a Client Access Server instead of a Mailbox Server for retrieving Mailbox information. This is achieved using the RPC protocol and not using the HTTPS protocol. Think about Outlook 2003 which doesn’t use HTTPS at all. The CAS Array is also used as a ‘backlink’ from the Mailbox Databases to the Client Access Servers. Mailbox Databases have a RPCClientAccessServer property which links a Mailbox Database to a CAS Server. This is also based on the RPC protocol.
The first step is to create a NLB cluster on your Client Access Server and give the cluster a name, for example nlb.labs.local. If you are using Client Access Servers running on Hyper-V (or VMWare) you have to be aware of the MAC address issue. Hyper-V has a range of MAC addresses being used by Virtual Machine. When you create an NLB cluster a random MAC address for the NLB address is generated, and this MAC address is not recognized by the Hyper-V Servers. More information on how to configure this can be found in Microsoft knowledge base article 953828.
Now you can add the CAS Array to the Exchange configuration, and the only option is to use the Exchange Management Shell. Enter the following command:

New-ClientAccessArray -FQDN webmail.inframan.nl -Name CAS_Arrary

The CAS Array will be added to the Exchange configuration, and it Fully Qualified Domain Name is “webmail.inframan.nl”.
Your Outlook clients can now use “webmail.inframan.nl” as the Exchange Server using RPC.
Newly created Mailbox Databases will use the CAS Array as the RPC Proxy, but existing Mailbox Database will use the individual Client Access Servers as the RPC Proxy. To change the –RPCClientAccessServer property on all Mailbox Database in one time, open the Exchange Management

Shell and enter the following command:
Get-MailboxDatabase | Set-MailboxDatabase –RPCClientAccessServer “webmail.inframan.nl”

PowerSell Command(Exchange2010)

2012-07-16T04:48:00.001-07:00

Get-Mailbox -ResultSize Unlimited | select DisplayName, Alias, Database, PrimarySmtpAddress,@{name=’IssuewarningQuota’;expression={if ($_.IssueWarningQuota -match “UNLIMITED”) {“-1″} else {$_.IssueWarningQuota.value.tomb() }}},@{name=’ProhibitSendQuota’;expression={if ($_.ProhibitSendQuota -match “UNLIMITED”) {“-1″} else {$_.ProhibitSendQuota.value.tomb() }}},@{name=’ProhibitSendReceiveQuota’;expression={if ($_.ProhibitSendReceiveQuota -match “UNLIMITED”) {“-1″} else {$_.ProhibitSendReceiveQuota.value.tomb() }}},WhenCreated |export-csv C:\stats.csv
“DisplayName,Alias,MailboxSizeMB,ItemCount,PrimarysmtpAddress,IssueWarningQuotaMB,ProhibitSendQuotaMB,ProhibitSendReceiveQuotaMB,DatabaseName,CreationDate,LastLogonTime,LastLogoffTime,isActive” | out-file C:\MailstatsResult.csv

Get-MailboxStatistics -server "server" | Sort -Property TotalItemsize | Format-Table DisplayName, LastLoggedOnUserAccount, ItemCount, @{expression={$_.totalitemsize.value.ToMB()};label=”Size(MB)”}, LastLogonTime, LastLogoffTime | Export-CSV c:\test13.csv

Get-Mailbox -ResultSize Unlimited | select DisplayName, Alias, Database, PrimarySmtpAddress

Get-MailboxStatistics -server "server" | select DisplayName, Alias, Database, PrimarySmtpAddress

Get-Mailbox -ResultSize Unlimited | select DisplayName,Alias,MailboxSizeMB,ItemCount,PrimarysmtpAddress,IssueWarningQuotaMB

Get-Mailbox | Get-MailboxFolderStatistics | Select Identity,FolderPath,FolderSize,ItemsInFolder | Sort-Object ItemsInFolder | fl

Add-MailboxPermission testmbx -AccessRights FullAccess -user jaredz
Set-Mailbox testmbx -GrantSendOnBehalfTo jaredz
Add-ADPermission testmbx -ExtendedRights Send-As -user jaredz
Add-ADPermission user -User “DomainB\User” -Extendedrights “Send As”
“Set-Mailbox “USER” -GrantSendOnBehalfTo “DomainB\User”
Get-Globaladdresslist | update-Globaladdresslist
Get-Addresslist | Update-Addresslist
Add-MailboxFolderPermission -Identity marry:\Calendar -User harry -AccessRights Reviewer
Get-MailboxFolderStatistics -Identity marry
Get-MailboxFolderPermission -Identity marry:\Calendar
Get-MailboxFolderStatistics -Identity marry -FolderScope Calendar | Select-Object -First 1).Name
Get-MailboxFolderPermission -Identity marry:\Calendar
Set-MailboxFolderPermission -Identity marry:\Calendar -User harry -AccessRights Owner
Get-MailboxFolderPermission -Identity marry:\Calendar
Set-MailboxFolderPermission -Identity marry:\inbox -User harry -AccessRights Owner
Set-MailboxFolderPermission -Identity marry:\task -User harry -AccessRights Owner
Set-MailboxFolderPermission -Identity marry -User harry -AccessRights Owner
Update-Calendarpermission -identity marry -User harry -Permission ReadItems
Set-MailboxFolderPermission -Identity LasseP:\Calendar -User Eva -AccessRights Owner
Add-MailboxFolderPermission -Identity LasseP:\Calendar -User Eva -AccessRights Reviewer
Get-MailboxFolderPermission -Identity LasseP:\Calendar
Get-MailboxStatistics -server serverhere | Where-Object {$_.DisplayName -like "*MailboxUserName*"} | Format-Table DisplayName,ItemCount,TotalItemSize
Get-Mailbox -Database "Db3" -ResultSize Unlimited |Set-Mailbox -RecipientLimits 5
new-mailboxdatabase -Server 'ggncloud' -Name 'db3' -EdbFilePath 'E:\Exch2010-DBs\<DATABASE NAME>\db3.edb' -LogFolderPath 'E:\Exch2010-Logs\db3'
Mount-Database -Identity "db3"
Set-MailboxDatabase -ProhibitSendReceiveQuota '45Mb' -ProhibitSendQuota '40Mb' -IssueWarningQuota '35Mb' -RetainDeletedItemsUntilBackup $true -Identity "db3"
Set-MailboxDatabase -OfflineAddressBook '\Default Offline Address Book' -Identity "db3"
New-GlobalAddressList -Name "gal" -RecipientFilter {(MemberOfGroup -eq 'cn=<GROUP NAME>,OU=Exchange Groups,DC=ggncloud,DC=internal')}
Update-GlobalAddressList -Identity "gal"
Add-ADPermission -Identity $dngal -User "gal" -AccessRights extendedright -ExtendedRights "open address list" -Deny:$True
get-mailbox -ResultSize Unlimited
get-powersellvirtualdirectory
get-ActiveSyncMailboxPolicy

Get-MailboxDatabase -Status | Sort-Object name | Format-Table Name, DatabaseSize, AvailableNewMailboxSpace
Get-MailboxDatabase -Identity databasename -Status | Format-Table Name, DatabaseSize, AvailableNewMailboxSpace
New-ManagementRoleAssignment -Role "Mailbox Import Export" -User administrator
Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book"
Get-ExchangeServer | FT Name,ServerRole -auto
Get-Mailbox | Get-MailboxStatistics -Server ggncloud | Sort-Object TotalItemSize -Descending | Format-Table DisplayName,ItemCountTotalItemsize
Get-MailboxStatistics "Clayton Kamiya" | FT DisplayName, ItemCount,TotalItemSize
Get-Mailbox | Select Name, ProhibitSendQuota, ProhibitSendReceiveQuota | Export-Csv c:\report.csv
Get-MailboxDatabase -IncludePreExchange2010
ServerManagerCMD -i RPC-over-HTTP-Proxy
Set-OwaVirtualDirectory "ggncloud\owa (Default Web Site)" -ExternalURL $Null
Get-MailboxDatabaseCopyStatus | Format-List Name,Status,LastInspectedLogTime,ContentIndexState
Get-MessageTrackingLog | Format-table EventID,Source,Sender, MessageSubject
Test-WebServicesConnectivity
get-transportserver | fl *Log*
ServerManagerCmd -i Backup-Features
Import-Module Servermanager
Add-WindowsFeature Backup-Features
Servermanagercmd -query
Get-ExCommand *mailbox*
Get-LogonStatistics -Server ggncloud
test-replicationhelth

Managing distribution list in Exchange server 2010

2012-07-12T04:44:00.001-07:00

Mail enabled Universal Distribution Group
Mail enabled universal Security Group
Dynamic Distribution Group

Now we will have a look at some of the topics related to managing distribution list in exchange server 2010.

How to create a Distribution Group in Exchange Server 2010

How to add owner to a distribution group

Set-Group -Identity “DL Group Name” -ManagedBy “Domain Name\UserName”

How to add Permission to distribution group for Owner

After adding Managedby user on a distribution group, better to give read and write access permission for Owner

Add-ADPermission -Identity “DL Group Name” -User “DomainName\user” -AccessRights ReadProperty, WriteProperty -Properties ‘Member’

How to change the owner of a distribution group

Set-DistributionGroup -Identity “DL Group Name” -ManagedBy “DomainName\NewOwnerUser”

Add-ADPermission -Identity “DL Group Name” -User “DomainName\NewOwnerUser” -AccessRights ReadProperty, WriteProperty -Properties ‘Member’

How to add a second or additional owner for a distribution group

Giving read and write access permission at active directory level will allow the other user to function as a co owner for a Distribution Group

Set-DistributionGroup -ManagedBy ‘New Onwer Name’,'Old Owner Name’ -Identity ‘Distribution Group Name’

Add-ADPermission -Identity “DL Group Name” -User “DomainName\SecondOwner” -AccessRights ReadProperty, WriteProperty -Properties ‘Member’

How to remove additional owner from a distribution group

Remove-ADPermission -Identity “DL Group Name” -User ” DomainName\SecondOwner ” -AccessRights ReadProperty, WriteProperty -Properties ‘Member’

How to rename a Display name and Alias Name for a Distribution Group

Set-DistributionGroup -Identity ‘Distribution Group Name’ -DisplayName ‘Enter New Name’ -Alias “New_Alias”

How to export the members list from a Distribution Group

Get-DistributionGroupMember -Identity ‘Distribution Group Name” | FL Name

How to add a New Member to the distribution Group

Add-DistributionGroupMember -Identity “Distribution Group Name” -Member “UserName’

How to disable or remove a Distribution Group

Disable-DistributionGroup -Identity “Distribution Group Name”

Remove-DistributionGroup -Identity “Distribution Group Name”

How to mail enable or mail disable a security group

If we have an active directory security group available and if we want to mail enable that security group, we can use the below shell command and email address will be created for that security group

Enable-DistributionGroup –Identity “DL Display Name”

Disable-DistributionGroup –Identity “DL Display Name”

How to allow external users to send email to the distribution list

Set-DistributionGroup -Identity ‘Distribution Group Name’ -RequireSenderAuthenticationEnabled $True

How to allow owners to approve or restrict member to join or to leave a Distribution Group

Set-DistributionGroup -MemberJoinRestriction ‘ApprovalRequired’ -MemberDepartRestriction ‘Closed’ -Identity ‘Distribution Group Name’

How to allow only few users to send email to distribution list

Set-DistributionGroup -AcceptMessagesOnlyFromSendersOrMembers ‘User Name 1’,’User Name 2′ -RequireSenderAuthenticationEnabled $True -Identity ‘Distribution Group Name’

How to restrict few users to send email to distribution list

Set-DistributionGroup -AcceptMessagesOnlyFromSendersOrMembers “All Users” -RequireSenderAuthenticationEnabled $True -Identity ‘Distribution Group Name’ -RejectMessagesFromSendersOrMembers ‘User Name 1’,’User Name 2′

How to set a Message Moderator to allow emails and to bypass approval from few users

Set-DistributionGroup -ModerationEnabled $true -ModeratedBy ‘Moderator User Name’ -BypassModerationFromSendersOrMembers ‘User don’t require approval’ -Identity ‘Distribution Group Name’

How to hide a distribution group from Gloabll Address List

Set-DistributionGroup -Identity ‘Distribution Group Name’ -HiddenFromAddressListsEnabled $true

How to add additional email address to a distribution list

Set-DistributionGroup -Identity ‘Distribution Group Name’ -EmailAddresses ‘SMTP:existingemailaddress’,'smtp:Newemailaddress’

How to create a dynamic distribution list

New-DynamicDistributionGroup -Name “Name of DDG” -Alias “Alias_Name” -IncludedRecipients “MailboxUsers,MailContacts” -OrganizationalUnit “DomainName.com/Users” -ConditionalDepartment “DepartmentName1″,”DepartmentName2″ -RecipientContainer “DomainName.com”

Mailbox Report in Exchange Server 2010

2012-07-12T04:37:00.003-07:00

This information to get a mailbox report for an Exchange Organization. You can change some parameters to get a desired output, if you are facing any issue.

Normal Mailbox Report

To find a mailbox, we will use the below shell command

Get-Mailbox -Identity MailboxName

To get the result of all the mailbox in a Mailbox Database we can use the below shell command

Get-Mailbox -Database “Mailbox Database Name”

To get the result of Mailboxes in a Exchange Server, we can use the below shell command

Get-Mailbox -Server “Exchange Server Name”

To get the above result of all the Mailboxes, we can use Get-Mailbox on a Mailbox Database or a Exchange Server, but if we have more than 1000 mailbox, only the first 1000 mailbox will be displayed. To get all the mailbox, we have to use the below shell command

Get-Mailbox -ResultSize Unlimited

Get-Mailbox -Database “Mailbox Database Name” -ResultSize Unlimited

Get-Mailbox -Server “Exchange Server Name” -ResultSize Unlimited

How to find the entire mailbox and export them to csv file

Get-Mailbox -ResultSize Unlimited | Export-CSV C:\MailboxReport.csv

Above shell command will search for all the mailbox enable accounts in Exchange organization and the output will be passed to a csv file.

How to get the result of only the user mailbox in the exchange Server organization

Get-Mailbox -ResultSize Unlimited -RecipientTypeDetails UserMailbox | Export-CSV C:\MailboxReport.csv

Above shell command will export only the user mailbox in the exchange organization to a csv file. We can change the Recipient Type Details parameter to Room or Shared Mailbox to get the result of only the shared mailbox.

How to find the Mailbox Size Report for a Mailbox

Get-MailboxStatistics will allow an option to get the details on the mailbox size, so we can use the below shell command to find a report for single mailbox

Get-MailboxStatistics -Identity UserName | Ft DisplayName, ServerName, Database, TotalItemSize, ItemCount, StorageLimitStatus -Auto

If you want to get the above status report for all the users in a Mailbox Database or Exchange Server

Get-Mailbox -Database “Database Name” -ResultSize Unlimited | Get-MailboxStatistics | Select-Object DisplayName, ServerName, Database, TotalItemSize, ItemCount, StorageLimitStatus | Export-CSV C:\MailboxStatisticsReport.csv

Or to get the result for all the mailboxes in a Server

Get-Mailbox -Server “Server Name” -ResultSize Unlimited | Get-MailboxStatistics | Select-Object DisplayName, ServerName, Database, TotalItemSize, ItemCount, StorageLimitStatus | Sort TotalItemSize -Descending | Export-CSV C:\MailboxStatisticsReport.csv

How can I get the above mailbox size report for only the User mailbox in the Exchange Server Organization and to sort the output via Total Item Size?

Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize Unlimited |Get-MailboxStatistics | Select-Object DisplayName, ServerName, Database, TotalItemSize, ItemCount, StorageLimitStatus | Sort TotalItemSize -Descending | Export-CSV C:\MailboxStatisticsReport.csv

To find the number of mailboxes on a database or a server or in a exchange server organization

To get the total number of mailboxes in your exchange server organization

(Get-Mailbox -ResultSize Unlimited).Count

If you want to get the mailbox count based on the server

Get-Mailbox -ResultSize Unlimited | Group-Object -Property:Server | Select-Object Count

Or to find the mailboxes on a database per server

Get-Mailbox -ResultSize Unlimited -Server “Server Name” | Group-Object -Property:Database | Select-Object Name, Count

Or you can find mailbox count for all the mailbox database in exchange organization, without specifying the server name

Get-Mailbox -ResultSize Unlimited | Group-Object -Property:Database | Select-Object Name, Count

HTML Report on the Mailbox Report

Below shell command will help you to get the HTML Report for User Mailbox in a Exchange Organization

Or you can get the HTML Report for all the mailbox using the below shell command

Get-Mailbox -ResultSize Unlimited | Get-MailboxStatistics | Select-Object DisplayName, ServerName, Database, TotalItemSize, ItemCount, StorageLimitStatus | Sort TotalItemSize -Descending | Convertto-HTML -Body “”| Set-Content C:\MailboxReport.htm
--------------------------------------------------------------------------------------------------------------------------

1.To check whether all exchange server related services are running normal?
Test-ServiceHealth or Test-ServiceHealth -Server ServerName
1.To check the Database Mount Status, backup status
Get-MailboxDatabase -Server ServerName -Status | FT Name, Mounted, backupinprogress, lastfullbackup, lastincrementalbackup
1.If High availability configured for Mailbox Server, to check the storage group and mailbox database opy status
Exchange Server 2007 CCR -> Get-StorageGroupCopyStatus -Server ServerName
Exchange Server 2007 SCR -> Get-StorageGroupCopyStatus -Identity MBSRV\SG1 -StandbyMachine Server2
Exchange Server 2010 DAG -> Get-MailboxDatabaseCopyStatus -Server ServerName
1.To check the Mail queue status
Get-Queue -Server ServerName | FL
1.Testing Mailflow whether mail can be successfully sent from and delivered to the system mailbox on a computer that has the Mailbox server role installed
Test-Mailflow Server1 -TargetMailboxServer Server2
Test-Mailflow Server1 -TargetEmailAddress externalemailaddress
Inform if any details are needed.

Database availability group (DAG) Setup

2012-07-10T04:08:00.002-07:00

A database availability group (DAG) is the base component of the high availability and site resilience framework built into Microsoft Exchange Server 2010. A DAG is a group of up to 16 Mailbox servers that hosts a set of databases and provides automatic database-level recovery from failures that affect individual servers or databases.

A DAG is a boundary for mailbox database replication, database and server switchovers, failovers, and an internal Exchange 2010 component called Active Manager. Active Manager, which runs on every server in a DAG, manages switchovers and failovers. For more information about Active Manager, see Understanding Active Manager.

Any server in a DAG can host a copy of a mailbox database from any other server in the DAG. When a server is added to a DAG, it works with the other servers in the DAG to provide automatic recovery from failures that affect mailbox databases, such as a disk failure or server failure.

You can also create DAG group using the GUI option. But, if you use the Exchange Management Console (EMC) to create the DAG the task will configure the DAG to use Dynamic Host Configuration Protocol (DHCP) to obtain the necessary IP addresses. If you don't want the DAG to use DHCP, you can use the Set-DatabaseAvailabilityGroup cmdlet to configure one or more IP addresses for the DAG & also set the primary OR secondary file share witness.

Setup Steps

· To create a Database Availability Group (DAG)- Login with appropriate login permissions - Start Exchange Management Shell.

· Run the shell command

"Get-DatabaseAvailabilityGroup"

“New-DatabaseAvailabilityGroup –Name “DAGName” –WitnessServer “Server Name” –WitnessDirectory “Path” –DatabaseAvailabilityGroupIPAddresses Primary, DR”

o -Name (DAG Name)

o -WitnessServer (Prefrebally HubTransport Server – Recommended for even number cluster)

o -WitnessDirectory (Directory Path on the HubTransport Server)

o -DAG IP Addresses (IP addresses from the Primary & DR sites)

Type a name for the DAG. Remember that the DAG must be unique within the Exchange organization and it can consist of up to 15 characters. I will select the server that hosts the Hub Transport and as a witness server, and define C:\DAG1-WS as the witness directory. Click Next to create the DAG.

After DAG is created, run the command "Get-DatabaseAvailabilityGroup DAG1 | FL" to check the default properties of the DAG:

Note that the DAG has no IP addresses configured. It is recommended to assign static address to the DAG. We can run the below command to set IP address to the DAG. Set-DatabaseAvailabilityGroup DAG1 -DatabaseAvailabilityGroupIpAddresses 20.20.0.6

To add members to the DAG group. Open Exchange 2010 Management Console-> Organization Configuration-> Mailbox-> Database Availability Group-> Right Click on the DAG Name and Select Manage Database Availability Group Membership to add additional DAG members.

Click the Add button in the next screen to add the required DAG members. Select all the required servers to be part of this DAG group, and then click Manage.
(Note: The DHCP Client service must be enabled & running on all the DAG members before this step)

Click Finish, Once completed

Click Finish, once completed. Continue same steps until all the remaining members are added.
To check the DAG members. Run this “Get-DatabaseAvailabilityGroup” command

-----------------------------------------------------------------------------------------------------------

DAC mode can be turned on by running the shell command below.

Set-DatabaseAvailabilityGroup –identity “dagname” –DatacenterActivationMode DagOnly

http://www.servermigrationlabin.com/2011/07/how-to-work-on-cross-site-failure-in.html

ECP (Exchange Control Panel)

2012-07-09T04:25:00.003-07:00

ECP (Exchange Control Panel) can manage mailboxes, Distribution Groups, Contacts at mailbox level and several other objects at Organization level, such as Journaling, Transport Rules, Delivery Reports and so forth.

The ECP authentication by default follows the Outlook Web App settings but we can manage that separately on the Client Access Server, Exchange Control Panel tab as shown in

Figure 01

Figure 01

So, if you have already configured your Outlook Web App and it is working like a charm, let’s try the https://yourdomain.com/ECP and here you will get access to the management stuff using the same authentication process that we would use to access Outlook Web App. The main page is similar to the one shown in Figure 02, where we have four categories: Users & Groups, Roles & Auditing, Mail Control, Phone & Voice and each one of them has sub categories.

Figure 02

If you are already logged on in Outlook Web App, you can click Options and then See all Options, and then click on the option Manage Myself and change to My Organization. All areas that the current user has access will be available to be managed through the web interface.

Managing Mailboxes

On the first page we can solve one of the most asked questions around Exchange Control Panel which is the ability to create new Mailboxes, the answer is simple: No. The feature was removed in the RTM release of the product.

A list of all mailboxes will be listed on the initial page, and we can use the Select View field which has All Mailboxes, user mailboxes, Room mailboxes or Mailboxes on litigation hold to sort the mailboxes that are being listed based on those attributes. We can also search a specific mailbox typing in the field right below Details and Refresh buttons. In the same field we can use a wildcard, for example, if you want to list all users that end with 01, just type in *01 and here you have the results (figure 03).

CAS Proxy

2012-07-09T03:44:00.002-07:00

PowerShell(Exchange 2010)

2012-07-09T01:48:00.005-07:00

CommandLine
-- -----------
Restore-DatabaseAvailabilityGroup –Identity DAG1 –ActiveDirectorySite ggncloud
Remove-DatabaseAvailabilityGroupServer -MailboxServer 'RAKESH' -Identity 'DAG2
new-DynamicDistributionGroup -Name 'DDG-ITS' -RecipientContainer 'corp.mld/ITS' -IncludedRecipients 'AllRecipients' -OrganizationalUnit 'corp.mld/ITS' -Alias 'DDGits'
Import-PSSession $Session
$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://%3cfqdn/ of Exchange 2010 server>/PowerShell/ -Authentication Kerberos -Credential $UserCredential
Set-User rakesh -RemotePowerShellEnabled $True
Set-AdServerSettings -RecipientViewRoot "corp.mld/its"
Set-AdServerSettings -ViewEntireForest $true -PreferredGlobalCatalogggncloud.corp.mld
update-AddressList -Identity '\All Contacts
New-TransportRule -Name 'TS Rule1' -Comments 'transportrule' -Priority '0' -Enabled $true -From 'shailendra@corp.mld' -DeleteMessage $true -ExceptIfFrom 'john@corp.mld'
Suspend-MailboxDatabaseCopy -Identity DB1\MBX2 -ActivationOnly
Resume-MailboxDatabaseCopy -Identity DB1\MBX2
Set-MailboxServer -Identity MailboxServer–DatabaseCopyAutoActivationPolicy
Set-MailboxServer -Identity MailboxServer–DatabaseCopyAutoActivationPolicy
Get-DatabaseAvailabilityGroupNetwork -Identity DAG2 | fl name, MapiAccessEnabled
Set-Mailbox "John Doe" -RetentionPolicy "Finance"

Get-TransportServer
Get-RpcClientAccess
Get-CASMailbox
Get-ClientAccessArray
Get-ClientAccessServer
Get-MailboxServer
Get-ReceiveConnector
Get-MailboxDatabase
Get-MailboxDatabaseCopyStatus
Get-ExchangeServer
Get-AdServerSettings
Get-GlobalAddressList
Get-Group
Get-Mailbox
Get-MailContact
Get-Recipient
Get-RetentionPolicy
Get-RetentionPolicyTag
Get-RoleGroup
Get-User

Exchange CASArray

2012-07-06T01:53:00.003-07:00