This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Mobile Control tasks for Exchange 2016 upgrade

Hi All,

We are about to start our Exchange 2010 to Exchange 2016 upgrade and need to know the tasks relating to Sophos Mobile Control.

Currently our Sophos Mobile Control server sits in our DMZ and uses a hosts file to point to our internal Exchange 2010 Client Access Server (CAS) for Exchange Active Sync connections.

I'm thinking that when we move to Exchange coexisting (Exchange 2010 and Exchange 2016) stage we would need to update the hosts file to point to a Exchange 2016 Server.

Is my thinking correct? and\or is there any other SMC tasks I would need to perform?

 

Thanks in advance,

Phil



This thread was automatically locked due to age.
Parents
  • Hi  

    Can you please help me with the following questions? 

    1. Which version of Sophos Mobile Control On-Premise are you using? 

    2. Is the database on the same server or on a different server? If it is on a different server, then you will need to move it to the same server. This article should help: https://community.sophos.com/kb/en-us/119727

    3. Have you set up clustering for the server?

    Thanks,
    Yashraj Singha
    Manager | Global Community Support
    Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
    If a post solves your question, please use the "Verify Answer" button.
    The New Home of Sophos Support Videos!  Visit Sophos Techvids
  • Hi ,

     

    Thanks for your reply but I'm confused on some of your questions.

     

    1. We are currently version 9.02.

    2. I'm not understanding why this question is relevant or why we would need to move the SMC database to the same server. Please explain why we would need to do this. We are doing an Exchange 2016 migration, from Exchange 2010, and will need to point our SMC server at the Exchange 2016 for the coexisting phase of the migration. Currently our SMC server has a hosts file enter that points EAS connections to one of our Exchange 2010 CAS.

    3. No we don't have a cluster and why would we need this for the Exchange 2016 migration?

     

    Thanks

Reply
  • Hi ,

     

    Thanks for your reply but I'm confused on some of your questions.

     

    1. We are currently version 9.02.

    2. I'm not understanding why this question is relevant or why we would need to move the SMC database to the same server. Please explain why we would need to do this. We are doing an Exchange 2016 migration, from Exchange 2010, and will need to point our SMC server at the Exchange 2016 for the coexisting phase of the migration. Currently our SMC server has a hosts file enter that points EAS connections to one of our Exchange 2010 CAS.

    3. No we don't have a cluster and why would we need this for the Exchange 2016 migration?

     

    Thanks

Children