Exchange 2016 CAS Server Isn't in the Active Directory

Hi All, hope someone out there can help me. I have an Exchange 2016 Server with 40 PCs connected, mix of Windows 7 and 10 all using Office 2016. We are experiencing some performance issues so I am checking the HP Proliant Server to see if there is anything I can do to speed things up. I've noticed I should disable Hyperthreading so that will be turned off soon but the other thing is after I have run BPA it states that The Exchange Client Access Server isn't in the Active Directory, Make sure your Client Access Server is in the Active Directory , even though It's running on the Domain Controller. Is the AD missing a record. Outlook takes over 3 mins to connect on a 1 year old PC the first time it's run.

Who is Participating?
Seth SimmonsConnect With a Mentor Sr. Systems AdministratorCommented:
...even though It's running on the Domain Controller.

please build another CAS server and get it off the domain controller...start there

Installing Exchange on a domain controller is not recommended

aside from that, check your autodiscover will definitely cause issues with clients trying to connect if something isn't configured properly

Autodiscover service
Hasin Ahmed ChoudharyConnect With a Mentor Exchange AdministratorCommented:
Is that warning from BPA. Ideally, exchange 2016 doesn't have separate CAS server role. I just have Client Access Service within mailbox server role.

Check this few links if those help:
Hasin Ahmed ChoudharyExchange AdministratorCommented:
NO further comments from Author
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.