none
Exchange 2010 Public Folder to Office 365 Hybrid RRS feed

  • Question

  • I am currently setting up an EX2010/365 hybrid config, and I'm working on Public Folders and had a few items I need some clarification on.
    Currently we have 1 CAS server and 2 MB servers in a DAG; 1 of the MB servers is hosting PFs.

    I've reviewed MS documentation about installing the CAS role on all Ex2010SP3 MB servers that are hosting Public Folders and this is where I need some clarification. (I plan to install the CAS role over a weekend during a maintenance window and want to avoid any Monday Morning gotchas)

    1) When installing CAS role it asks 'do you want this to be internet facing?'
    This is not enabled by default and I assume it doens't need to be since the connection to the PF should be proxied through the CAS server. (not the new CAS/MB server)

    2) I assume I still don't need a CA SSL on the MB server hosting PFs, the only server that should need a CA SSL is the CAS server (not the CAS/MB server)

    3) After I install the CAS role on the MB server how do I configure CAS on the MB server so it does not conflict/break internal autodiscover lookups?
    Ideally I would hope the new CAS/MB server would have it's "AutodiscoverServerInternalUrl" configured to $Null by default and it would not try to make any changes to the internal AD site used by the AutoDiscover Service Outlook client's internal on the network. Then I assume external URLs on the new CAS MB server would be empty since this server is not public facing.

    4) Is there anything else I need to be aware of after installing CAS on the MB server so it doesn't impact production?
    --

    I've read over this article https://social.technet.microsoft.com/Forums/en-US/560f27d6-ed1f-45aa-a53a-4fea0801fe15/office-365-configure-public-folder-for-a-hybrid-deployment?forum=exchangesvrgeneral
    And it mentions:
    You can set the autodiscover URI on the NEW cas to an existing CAS or Load Balanced Arry FQDN that already has a valid cert:

    For example: Set-ClientAccessServer -Identity <NEW CAS>  -AutoDiscoverServiceInternalUri  https://OriginalCAS.domain.com/autodiscover/autodiscover.xml

    or set it to $null

    Set-ClientAccessServer -id yournewCASname -AutodiscoverServiceInternalUrl $Null


    Friday, July 19, 2019 2:36 PM

Answers

  • Hi wicrosoft,

    1. Yes, it does't need to be internet facing.
    2. Yes, MB/CAS server does not need a CA.
    3. As you have referred, you can set the autodiscover URL on the MBX/CAS server to the existed CAS server or $null:

    Set-ClientAccessServer -Identity <The Name of the MBX/CAS server>  -AutoDiscoverServiceInternalUri  https://CASServerName.domain.com/autodiscover/autodiscover.xml
    4. Per my experience, in addition to the above points, nothing else will impact.


    Best Regards,
    Niko Cheng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com

    • Marked as answer by wicrosoft Tuesday, July 23, 2019 2:28 PM
    Monday, July 22, 2019 9:02 AM
    Moderator