Anybody know why installing Windows Server Essentials Role on server 2012R2, breaks Exchange 2013 if Client Access Role is installed on the same machine.
I have been trying to setup Exchange 2013 on a 2012R2 Domain Controller for a couple of weeks now and have found that if you install Windows Server Essentials role either before or after setting up Exchange with Client Access Role selected, you can not login to EAC and Exchange Management Shell reports access denied when trying to connect.
You can install it in Mailbox role only and have Client Access role on a second member server and it is not broken.
However if Windows Server Essentials role is not used and you configure AD manually, then you can install Exchange with Mailbox and Client Access Roles on the same domain controller.