Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, July 9, 2019 10:56 PM
We have 2 sharepoint on-premises farms as follow:-
1. SharePoint 2013 on-premises farm with this high level architecture:-
- SharePoint application server under windows server 2008 R2
- SharePoint database server under windows server 2008 R2.
2. SharePoint 2010 on-premises farm with this high level architecture:-
- SharePoint application server under windows server 2008 R2
- SharePoint database server under windows server 2008 R2.
Now we want to upgrade the OS for the application servers and database servers from windows 2008 R2 to windows 2012/2016 R2. so can anyone advice if upgrading the Operating Systems for the SP application server and database server from windows 2008 R2 to windows 2012 R2 is a straight forward task? or we will need to re-deploy and/or re-configure sharepoint ? in our case the 2 farms contain site collections (mainly team sites and enterprise wikis) , sub-sites & farm solutions which implement event receivers.
All replies (6)
Wednesday, July 10, 2019 12:09 AM
SharePoint Server 2013 does not support Windows Server 2016. You can go to 2012 R2 max using the SharePoint Server 2013 w/ SP1 ISO. SQL Server 2014 (max supported by SharePoint 2013) supports up to Windows Server 2016. SharePoint Server 2010 also supports a max of Windows Server 2012 R2 w/ the SharePoint Server 2010 w/ SP2 ISO. SQL Server 2012 (max supported by SharePoint 2010) supports up to Windows Server 2012.
For the upgrades, never perform an in-place upgrade of Windows Server (Microsoft generally recommends against this). In your case, for the SharePoint servers, create new servers with the desired/supported OS, deploy SharePoint, configure it appropriately, rotate it into the farm, and then retire your older SharePoint servers.
For SQL Server, again build a new server, migrate the databases + SQL logins and retire the old SQL Server. You could even swap the computer names at that point so you don't have to use a SQL Alias, or if you are, just re-point your SQL alias.
The task itself is simple, but it takes some time to complete.
Trevor Seward
Office Apps and Services MVP
Author, Deploying SharePoint 2019
Author, Deploying SharePoint 2016
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
Wednesday, July 10, 2019 12:15 AM
Hi John,
In general scenarios, yes it's possible to upgrade the windows server from 2008 R2 to 2012 R2 in-place and SP 2013 does not support to Windows Server 2016.
Microsoft Knowledge Base article 2818510 describes the standard procedure to execute such an upgrade.
But it's heavily recommended to do not do that on the production servers. Recommended path for SharePoint Server would be to add servers with the desired/supported version of Windows Server to the existing farm. Minimal configuration should be required (IIS Bindings and SSL certs, any 3rd party apps you need to install locally). Other artifacts, such as WSPs are stored in the Config database and deployed as part of a Web App/farm deployment. DNS records may need to be adjusted. Search topology will need to be adjusted. As you add new SharePoint servers to the farm, eject the old ones they replace.
Web.config changes should never be made by hand, instead using the SPWebCofnigModification class.
This is the supported method to upgrading SharePoint servers to a newer version of Windows Server -- but you shouldn't remain in a mixed-OS state for SharePoint servers for very long.
For SQL - SQL can be upgraded via standing up a new SQL Server, restoring the databases and re-connecting the SP Farm.
Thanks & Regards,
sharath aluri
Wednesday, July 10, 2019 2:40 AM
Hi John,
As Trevor and Sharath said, we don't recommend upgrade for Windows Server with SharePoint installed. Basically, you will have to reinstall SharePoint on the new operating system. It is best practice to re-deploy and re-configure SharePoint on Windows Server 2012 R2.
Here are your references.
Prequisites for SharePoint Server 2013.
/en-us/sharepoint/install/prerequisites
Step by step Installation of SharePoint 2013 on Windows Server 2012 R2 part 1.
If you find any replies helpful to you, please remember to mark them as answers.
Thank you for your understanding.
Best regards,
Chelsea Wu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
SharePoint Server 2019 has been released, you can click here to download it.
Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.
Monday, July 15, 2019 1:35 AM
Hi John,
I'm checking how it is going on with this issue.
Please remember to update this thread if you have any progress.
Thank you for your understanding.
Best regards,
Chelsea Wu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
SharePoint Server 2019 has been released, you can click here to download it.
Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.
Tuesday, August 27, 2019 11:36 AM
Trevor -
What are your thoughts on this MS Support link. Obviously creating new servers with the desired/supported OS is the ideal route to take, but this appears to be a quicker method (and is likely a supported upgrade path by MS).
Tuesday, August 27, 2019 2:44 PM
The Windows PG never recommends upgrading Server OSes and going down the upgrade route doesn't give you a fallback path.
Trevor Seward
Office Apps and Services MVP
Author, Deploying SharePoint 2019
Author, Deploying SharePoint 2016
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.