W
whunt188852
Guest
Hi
Hopefully someone can offer some advice - Please forgive my ignorance I am quite new to Windows Server! Apologies if this is a bit long winded but I want to make sure I get all the info across.
So basically we have a customer that currently runs a Hyper-V host on which there are 2 virtual servers - One is a SBS 2011 VM that runs their single domain/email (Exchange 2010 SP3)/file shares etc and the 2nd is a server 2012r2 VM that is used purely to share Sage Data (because Sage Data Service does not like SBS 2011).
They will be hiring a load more people over the next 12 months and want to upgrade their server to meet demand and also to ensure they can use the latest version of Office for Mac and Office 2019 (when its released).
We will be quoting for a new much higher spec Hyper-V host on which we will restore their current virtual servers but to ensure that they can continue to have exchange email beyond MS Office 2016 they will also need to move away from Exchange 2010. Given that Exchange 2010 can only run on Server 2012 or above I thought about installing Exchange 2016 on their virtual Sage Server (Server 2012r2) - It is barely being used as its just effectively sharing a Sage data folder so seems like a good idea, We would assign this VM lots more RAM / CPU from the Hyper-V host.
As they don't want much downtime and have a lot of customisation on the SBS 2011 virtual machine they don't want to upgrade that they simply want to upgrade email to Exchange 2016.
So my questions are:
1. Can I install Exchange 2016 onto their current Sage Server (Server 2012 r2) and migrate their mailboxes etc onto it from their SBS 2011 (running Exchange 2010 SP3 with latest CU updates) ?
2. If the above is possible is it just a case of dismounting the databases on the SBS 2011 server and disabling the Exchange services (information store etc) after migration? Eventually I would delete the email databases on the SBS to recover HDD space.
3. Assuming I can do the above do I then just install their public SSL cert on the new Exchange 2016 server to ensure OWA works properly? Set port forwarding on the router to send port 25 to the new internal IP of the Exchange 2016 server (instead of the SBS server).
4. Assuming the above then do I just recreate new Outlook profiles on the Outlook clients to point to the new Exchange 2016.
5. Finally assuming the above I would expect the SBS 2011 server to run a lot smoother as a result because RAM is not being hogged by information store etc.
I know in an ideal world given the above they would move Active Directory onto a new 2016 DC server and then move email onto the Exchange 2016 server but they are unwilling to retire or alter the current SBS server (other than migrate the email to a new Exchange 2016 VM).
Note - I have tried to suggest O365 migration but the boss of this company totally refuses to have any form of subscription service also he is completely against having data hosted off premises so O365 is a non-starter (despite it being the best option given the small current number of users).
Thanks in advance.
Continue reading...
Hopefully someone can offer some advice - Please forgive my ignorance I am quite new to Windows Server! Apologies if this is a bit long winded but I want to make sure I get all the info across.
So basically we have a customer that currently runs a Hyper-V host on which there are 2 virtual servers - One is a SBS 2011 VM that runs their single domain/email (Exchange 2010 SP3)/file shares etc and the 2nd is a server 2012r2 VM that is used purely to share Sage Data (because Sage Data Service does not like SBS 2011).
They will be hiring a load more people over the next 12 months and want to upgrade their server to meet demand and also to ensure they can use the latest version of Office for Mac and Office 2019 (when its released).
We will be quoting for a new much higher spec Hyper-V host on which we will restore their current virtual servers but to ensure that they can continue to have exchange email beyond MS Office 2016 they will also need to move away from Exchange 2010. Given that Exchange 2010 can only run on Server 2012 or above I thought about installing Exchange 2016 on their virtual Sage Server (Server 2012r2) - It is barely being used as its just effectively sharing a Sage data folder so seems like a good idea, We would assign this VM lots more RAM / CPU from the Hyper-V host.
As they don't want much downtime and have a lot of customisation on the SBS 2011 virtual machine they don't want to upgrade that they simply want to upgrade email to Exchange 2016.
So my questions are:
1. Can I install Exchange 2016 onto their current Sage Server (Server 2012 r2) and migrate their mailboxes etc onto it from their SBS 2011 (running Exchange 2010 SP3 with latest CU updates) ?
2. If the above is possible is it just a case of dismounting the databases on the SBS 2011 server and disabling the Exchange services (information store etc) after migration? Eventually I would delete the email databases on the SBS to recover HDD space.
3. Assuming I can do the above do I then just install their public SSL cert on the new Exchange 2016 server to ensure OWA works properly? Set port forwarding on the router to send port 25 to the new internal IP of the Exchange 2016 server (instead of the SBS server).
4. Assuming the above then do I just recreate new Outlook profiles on the Outlook clients to point to the new Exchange 2016.
5. Finally assuming the above I would expect the SBS 2011 server to run a lot smoother as a result because RAM is not being hogged by information store etc.
I know in an ideal world given the above they would move Active Directory onto a new 2016 DC server and then move email onto the Exchange 2016 server but they are unwilling to retire or alter the current SBS server (other than migrate the email to a new Exchange 2016 VM).
Note - I have tried to suggest O365 migration but the boss of this company totally refuses to have any form of subscription service also he is completely against having data hosted off premises so O365 is a non-starter (despite it being the best option given the small current number of users).
Thanks in advance.
Continue reading...