Justin Hannah
asked on
Exchange Hybrid Migration - Autodiscover
Hi guys,
Was hoping to clarify few questions with your help.
For Exchange Hybrid Migration:
Q1: Do we need to publish Autodiscover externally and point to the on-prem Exchange infrastructure?
Q2: At what stage is this required?
Q3: On-prem Exchange 2013 only has internal Autodiscover service URL, do we need to configure external URL also?
Q4: Once all mailboxes in O365, do we point Autodiscover to O365 instead?
Q5: What changes are required in internal DNS
Q6: Do we disable SCP with powershell? Set-ClientAccessServer -Identity servername -AutoDiscoverServiceIntern alUri $NULL
Clients have combination of Outlook 2010, 2013, 2016
Outlook Anywhere is enabled
Thank you
Was hoping to clarify few questions with your help.
For Exchange Hybrid Migration:
Q1: Do we need to publish Autodiscover externally and point to the on-prem Exchange infrastructure?
Q2: At what stage is this required?
Q3: On-prem Exchange 2013 only has internal Autodiscover service URL, do we need to configure external URL also?
Q4: Once all mailboxes in O365, do we point Autodiscover to O365 instead?
Q5: What changes are required in internal DNS
Q6: Do we disable SCP with powershell? Set-ClientAccessServer -Identity servername -AutoDiscoverServiceIntern
Clients have combination of Outlook 2010, 2013, 2016
Outlook Anywhere is enabled
Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ok Sounds Good.
ASKER
Hi Saif,
Can you please collaborate on Q3 as to why is it necassary and what needs to be set?
Thank you
Can you please collaborate on Q3 as to why is it necassary and what needs to be set?
Thank you
Migration end point will look for external aurodiscover URL when you setup hybrid or run hybrid setup. So that is the purpose of requirement.
ASKER
Do I just put the same as for the InternalUri for each CAS? This won't affect anything else right?
Set-ClientAccessServer -Identity "Mailserver" -AutoDiscoverServiceExtern alUri https://autodiscover.contoso.com.au/Autodiscover/Autodiscover.xml
Thanks
Set-ClientAccessServer -Identity "Mailserver" -AutoDiscoverServiceExtern
Thanks
O sorry my bad you were asking about this.
Sorry for earlier comment no it is not required external URi for autodiscover. Olly internal uri is fine.
I thought you were asking about web services virtual directory.
Sorry for earlier comment no it is not required external URi for autodiscover. Olly internal uri is fine.
I thought you were asking about web services virtual directory.
ASKER
Yea I was wondering why? :) All good.
I'm assuming there's no change for end users after publishing the Autodiscover externally? Apart from potential DoS attact. Might keep it right before the HCW configuration.
I'm assuming there's no change for end users after publishing the Autodiscover externally? Apart from potential DoS attact. Might keep it right before the HCW configuration.
ASKER
With the last step we won't be uninstalling Exchange as will still have to manage certain Exchange attributes.