Posted by Alan McBurney on April 8, 2013
Ran into an error this morning trying to add members to a DAG running on Server 2012
When I try to add the nodes to the DAG I got the error
“You must provide an value for this property”
Decided I better do some reading on TechNet regarding 2010 DAGs and Server 2012 and it turns out that you must pre-stage the CNO (Cluster Named Object)
The documentation states
Pre-staging the CNO is required for Windows Server 2012 DAG members due to permissions changes in Windows Server 2012 for computer objects.
There are 2 methods to achieve the pre-staging.
- Add the “Exchange Trusted Subsystem” group with Full Control to the CNO
- Add the first DAG member with Full Control to the CNO
For me I choose to add the “Exchange Trusted Subsystem”
Adding the Nodes to the DAG after making the necessary changes worked without issue
Posted in Database Availability Group, Exchange 2010, Windows Server 2012 | Tagged: Cluster, CNO, DAG, Exchange 2010, Exchange Trusted Subsystem, Windows Server 2012, You must provide an value for this property | Leave a Comment »
Posted by Alan McBurney on April 10, 2012
Recently I’ve been working with a customer where their DAG has been misbehaving.
The DAG was stretched between 2 AD sites. There were multiple issues with cluster resources in addition to the PAM (Primary Active Manager) not failing over properly
After looking at it for a few hours I decided that the best course of action would be to rebuild the DAG
The following are the steps required in order to remove the DAG and rebuild it
- Remove All Database Copies from the DAG
Remove-MailboxDatabaseCopy “DBName\ServerToRemove” –Confirm:$False
- Turn off DataCenter Activation Mode
Set-DatabaseAvailabilityGroup -Identity DAG1 -DatacenterActivationMode Off
- Remove the MailboxServers from the DAG
Remove-MailboxDatabaseAvailabilityServer DAG1 –MailboxServer ServerToRemove
Be sure to allow time for replication to occur between executing commands
New-DatabaseAvailabilityGroup -Name DAG1 –WitnessServer “WitnessServer” -WitnessDirectory D:\DAG1 -DatabaseAvailabilityGroupIpAddresses 192.168.100.100,192.168.101.100
- Add the servers back into the DAG
Add-DatabaseAvailabilityGroupServer -Identity DAG1 –MailboxServer “SourceMBXServer”
repeat this command for all servers that you wish to add
- Enable Database Activation Mode
Set-DatabaseAvailabilityGroup -Identity DAG1 -DatacenterActivationMode DAGOnly
- Finally Add the mailboxdatabase copy server
Add-MailboxDatabaseCopy –Identity DBName -MailboxServer MBXServerToAdd -ActivationPreference 2
- Finally we can test the Primary Active Manager Failover
Cluster.exe DAG1.DOMAIN.LOCAL Group “Cluster Group” /MoveTo:PassiveServerNode
Posted in Exchange 2010, PowerShell | Tagged: Cluster, DAC, DAG, DatacenterActivationMode, Exchange 2010, Failover, PAM, SAM | Leave a Comment »
Posted by Alan McBurney on March 14, 2012
As part of a large scale migration from Exchange 2007 to Exchange 2010 I’ve been installing a number of Client Access Server using the SP2 binaries of Exchange 2010
The servers displayed the error below when installing the Client Access Server role complaining about End Point mappings
After digging around the ExchangeSetup.log file located in the C:\ExchangeSetupLogs folder I noticed that setup was trying to configure some firewall rules
I checked the status of the Firewall and sure enough it was disabled.
All servers were deployed from a template which has the firewall disabled.
I uninstalled Exchange from the server, set the firewall to Automatic and rebooted.
After the reboot the Exchange Client Access role installed on all servers without issue.
Posted in Exchange 2010, Windows 2008 R2 | Tagged: CAS, Client Access Server, Error 0x800706D9, Exchange 2010 | Leave a Comment »
Posted by Alan McBurney on December 20, 2010
I have just migrated a company from a mixed 2003 & 2007 environment to 2010.
2003 server removed successfully without issue, however when trying to add the 2010 server as a public folder replica the issues began.
Lots of 1020 MSExchangeStoreDriver and 3091 Replication Errors in the event logs
Finally tracked the issue down to the server object in First Administrative Group in ADSIEDIT.
Open adsiedit and check if there any objects in
CN=Servers,CN=Fist administrative group,CN=Administrative Groups,CN=Erste Organisation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local. Is the container “CN=Servers”
If servers is empty, then delete it.
Full blog post available at
Posted in Exchange 2010 | Tagged: Exchange 2010, Public Folders, Replication | 2 Comments »
Posted by Alan McBurney on November 16, 2010
Recently while patching Exchange 2010 servers one Mailbox server failed to patch throwing the error
Some controls aren’t valid. Setup previously failed while performing the action “Install”. You can’t resume setup by performaing the action “BuildToBuildUpgrade”.
The solution was a painless affair
Open up registry editor…
- Export Key hive for backup.
- Look in each “role” folder (MailboxRole, HubTransportRole, etc) and delete any key labelled “Watermark” and “Action”
Setup completed after performing the steps above.
Posted in Exchange 2010 | Tagged: Exchange 2010 | 1 Comment »
Posted by Alan McBurney on August 30, 2010
There is a great tutorial over on ExchangeServerPro by Paul Cunningham on how to setup a SAN cert for Exchange 2010 using an internal PKI
See here for full tutorial post.
Posted in Exchange 2010 | Tagged: Certificates, Exchange 2010 | Leave a Comment »