One of the new features in Windows Server 2012 R2 to decrease complexity is the so called Active Directory detached cluster. This is a regular Failover Cluster, but without a computer account in Active Directory. So, when deploying the Failover Cluster there’s no need to pre-create the Computer Name Object (CNO) anymore, but please note that the individual Cluster nodes still need to be a member of the Active Directory domain though.
Since the CNO is no longer available in an Active Directory detached cluster, the Cluster Administrative Access Point (CAAP) is not available either and in turn this cluster AAP was used by the Failover Cluster Management to access and manage the cluster. Since the cluster AAP is no longer available this is also referred to as an AAP-less, cluster AAP-less or CAAP-less cluster.
Continue reading Cluster Administrative Access Point and Database Availability Group
While testing mail flow I noticed that when an NDR was sent out by my Exchange 2013 the default postmaster account was used, with the default domain, i.e. firstname.lastname@example.org (I use a .local TLD on my Active Directory domain) instead of a regular and routable SMTP domain.
To change this you can open the Exchange Admin Center, navigate to Mail Flow | Receive Connectors and click the more options (the three dots) and select Organization Transport Settings as shown in the following figure.
Continue reading How to change the Postmaster address in Exchange 2013
Just a quick heads-up on support for Exchange 2007. Mainstream support for Exchange 2007 ended on April 10, 2012 and Extended Support will end on April 11, 2017. Rollup updates might be made available for another 2 years but you at this moment you should be planning to upgrade your platform.
Continue reading Call to action: Exchange 2007 and Windows 2003 support
I am always amazed by the amount of customers running Exchange 2007 or Exchange 2010 and NOT using Autodiscover. Their response is always “we don’t need it” and “we configure the Outlook profile manually”. In Exchange 2007 and Exchange 2010 you can get away with this (you cannot with Exchange 2013 and Autodiscover is mandatory) but when you want to implement a hybrid scenario with Exchange online you really need Autodiscover since Exchange Online uses Autodiscover to find relevant information regarding your on-premises Exchange environment.
Recently a customer with Exchange 2010 wanted to build a hybrid environment with Exchange Online, and one of my first findings was the lack of Autodiscover. So, after configuring their Exchange environment and creating the necessary DNS records Autodiscover was working properly as shown in the following picture:
Continue reading Disabled Outlook Anywhere causing free/busy issues
I am working with a customer that’s running Exchange 2010 on-premises and want to move to Office 365 in a hybrid scenario. The hybrid servers are running Exchange 2010. After implementing a hybrid scenario everything was working fine, but after some time I received calls that free/busy wasn’t working correctly anymore.
When a user with a Mailbox in Exchange online and he wants to schedule a meeting with a Mailbox in Exchange 2010 on-premsises all goes well and the user can see all free/busy information from all users.
When a user with an on-premises Mailbox (on Exchange 2010) wants to schedule a meeting with a Mailbox in Office 365 free/busy information from a Mailbox that’s not Domain joined he cannot check the availability information from Mailbox in Exchange Online as shown in the following screenshot:
Continue reading Free/Busy cross-premises not working correctly