Link to home
Start Free TrialLog in
Avatar of Albert Widjaja
Albert WidjajaFlag for Australia

asked on

Excluding one particular Exchange CAS server to not participating in Autodiscover ?

Hi,

I have built and deploy Exchange 2013 CAS role only for basic authentication purpose back to the existing primary Mailbox/CAS role in the same AD site.

How can I exclude certain Exchange 2013 – CAS server so that it is not participating in the Autodiscover process?

AD Domain: MyCompany.com

AD Site: Site1DC1
PRDMAIL01-VM1 [MBX DAG1 member & CAS role]
PRDMAIL01-VM2 [MBX DAG1 member & CAS role]

AD Site: Site2DC2
PRDMAIL02-VM1 [MBX DAG1 member & CAS role]
PRDMAIL02-VM2 [MBX DAG1 member & CAS role]
PRDMAIL02-VM3 [CAS role only] --> the CNAME I created for this server is Auth.MyCompany.com

The objective of PRDMAIL02-VM3 server is just running for 3rd party application and NOT to actively participating in Autodiscover, Free Busy, EWS methods, etc… so all of my workstations picked it up as being active in the CAS array.

Thanks in advance.
Avatar of Justin Evans
Justin Evans

first of all open a EMS and type the following:

Get-ClientAccessServer |ft identity, AutodiscoverServiceInternalUri,AutodiscoverSiteScope

This will show you who is in the CAS Array.

Then to remove type the following:

Set-ClientAccessServer –identity PRDMAIL02-VM3 –AutodiscoverServiceInternalUri: https://PRDMAIL02-VM3.Auth.MyCompany.com/autodiscover/autodiscover.xml

Kind Regards

Justin
Avatar of Albert Widjaja

ASKER

Hi Justin,

Does it mean it is just setting the AutodiscoverServiceInternalUri into another Exchange server or some random strings ?
SOLUTION
Avatar of timgreen7077
timgreen7077

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi Tim,

When I do NSlookup, the autodicover.domain.com resolves to all CAS server except PRDMAIL02-VM3.
Good so that server will not be found by auotdiscover. I would just verify that th wre is no autodiscover DNS A record for that server, but most likely there isn't since nslookup didn't find it. you should be good to go.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks all !