I had a lab and I was running into a problem building a Database Availability Group (DAG). I had installed Exchange 2013 Mailbox Role on 3 Windows Server 2008 R2 Standard machines. I was receiving the following error: A database availability group administrative operation failed. Error: Failed to add or remove the Failover-Clustering feature. Error:…
RBAC: Associating a Command With a Specific Groups
In some scenarios, it becomes prudent to know what Role is able to run which command. We can found out which groups are able to run which commands via the following syntax: Get-ManagementRoleEntry *\<command> For example, if you wanted to know who could run ‘Get-CalendarDiagnosticLog’, you would run the following command: Get-ManagementRoleEntry *\Get-CalendarDiagnosticLog If you…
O365: Exchange and AD – How msExchRecipientDisplayType and msExchangeRecipientTypeDetails Relate to Your On-Premises
Now maintained here: http://www.iseelondoniseefrance.se/2018/08/01/how-msexchrecipientdisplaytype-and-msexchangerecipienttypedetails-relate-to-your-on-premises/
Exchange 2013: High Availability – When Maintenance Might Be Necessary
During the course of your on-premises environment, it may become necessary to take a production Exchange server out of rotation and perform maintenance on it (i.e.: replace memory, patching, reconfiguration, etc.). During this time, it will become necessary to prevent RemoteMonitoring from testing against the server you need to repair. To understand this, we need to cover High…
Exchange 2013: High Availability, FAST Search, and the Windows Registry
One of the things not mentioned about High Availability (HA) and Database Availability Groups (DAGs) is that the automatic reseed feature is also used to maintain Exchange FAST Search indexes, independently, by HA. HA utilizes a registry key to keep the Content Index (CI) states in a central locale for referencing. It queries this key because determining…