Quickly Create 100 Test Users and Mailbox

This Awesome Command will quickly create 100 Test Users and Mailbox`s in your test lab.

 

Just copy and paste the command below exactly straight into the Exchange Powershell

 

1..100 | ForEach { Net User "User$_" MyPassword=01 /ADD /Domain; Enable-Mailbox "User$_" }

Quick Powershell Script to Verify the health and status of the DAG

 Save the following commands as a PowerShell script (.PS1) file:

(Get-DatabaseAvailabilityGroup -Identity (Get-MailboxServer -Identity $env:computername).DatabaseAvailabilityGroup).Servers | Test-MapiConnectivity | Sort Database | Format-Table -AutoSize
Get-MailboxDatabase | Sort Name | Get-MailboxDatabaseCopyStatus | Format-Table -AutoSize
function CopyCount
{
$DatabaseList = Get-MailboxDatabase | Sort Name
$DatabaseList | % {
$Results = $_ | Get-MailboxDatabaseCopyStatus
$Good = $Results | where { ($_.Status -eq "Mounted") -or ($_.Status -eq "Healthy") }
$_ | add-member NoteProperty "CopiesTotal" $Results.Count
$_ | add-member NoteProperty "CopiesFailed" ($Results.Count-$Good.Count)
}
$DatabaseList | sort copiesfailed -Descending | ft name,copiesTotal,copiesFailed -AutoSize
}
CopyCount

Run the PS1 Script to see a overview on the complete status of the DAG

Want to Prioritise Windows NLB Traffic on Exchange 2010 or 2007 CAS Servers ?

Scenario
========
Multiple Exchange 2010 CAS Servers, Possible Mixture of Virtual and Physical configurations, or Lower and Higher Spec Servers.

Requirement
===========
You would like to ensure that most of the traffic is handled by the Higher spec or physical servers to utilise as much resource as possible.

Solution
========
Use Windows NLB LOAD WEIGHT Parameter
To prioritise traffic to the server with the Higher Load weight,

When using Multiple hosts filtering mode, this parameter specifies the relative amount of load-balanced network traffic that this host should handle for the associated port rule. Allowed values range from 0 (zero) to 100. To prevent a host from handling any network traffic, set the load weight to 0 (zero).

The actual fraction of traffic handled by each host is computed as the local load weight divided by the sum of all load weights across the cluster.

You can specify different load weights for each host in the cluster by using the Load weight parameter. You can specify that all hosts distribute the network load equally by using the Equal load distribution parameter instead of the Load weight parameter.

OK, But How do I know its doing whats its suppose to do ?
===============================================
Easy, and Very Accurate, Using good old Perfmon you can add the following counters to see how many
RPC Access Clients are connected (Outlook) and how many OWA Users are connected,
and you should see the load is spread as you want.
Counters:
"MSExchange RPCClient Access\Active User Count"
"MS Exchange OWA\Current Users"

Unable to Activate Exchange 2010 Mailbox Database "Error: content index catalog files in the following state: 'Failed'.

Issue:
you attempt to move the active copy from a mailbox DAG Member server to another server you get error:

--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Cannot activate database copy 'Activate Database Copy...'.

Activate Database Copy...
Failed
Error:
An Active Manager operation failed. Error: The database action failed. Error: An error occurred while trying to validate the specified database copy for possible activation. Error: Database copy 'DB1' on server 'dag01' has content index catalog files in the following state: 'Failed'.

To Resolve this issue re-seed the Content Index:
1. Restart the MSExchange Search service on the node which has the active database.
2. Run update-mailboxdatabasecopy -catalogonly on each passive DAG Member
3. Activate Required Database

e.g. Command
update-MailboxDatabaseCopy -Identity "DAG01-DB10\DAGMB02" -CatalogOnly

This will seed from Datatabase DAG-01\DB10 to Passive Server DAGMB02