If we want to promote a Windows Server 2012 R2 or Windows Server 2016 to a DC, the Domain Functional Level (DFL) must be at least Windows Server 2003.Īs Dave mentioned, the minimum requirement to add a Windows Server 2019 Domain Controller is a Windows Server 2008 functional level. Īs for the domain controller upgrade, we should pay attention to the domain and forest functional level. Meanwhile, for SQL, we could turn to the dedicated SQL forum. We may need to know the compatibility of SQL version and server version. That method is preferable to upgrading the operating system of an existing domain controller.įor more information, we could refer to: Īccording to my knowledge, SQL has different versions, Windows server also has different versions and there are new features in every new server version.
#Office 365 windows server 2008 r2 upgrade
As mentioned, for Exchange, we have a dedicated Exchange forum, So I suggest we submit a service request to that forum so that a dedicated support professional can further assist you with this request.Īs for the domain controller upgrade, as mentioned before, the recommended way to upgrade a domain is to promote domain controllers that run newer versions of Windows Server and demote the older domain controllers as needed. We could have a check of the information provided by Dave.
Later on we demote the old DC and later we go with forest and domain functional level upgrades (once all legacy domain controllers are demoted).
Then promote it as DC and move roles to the new system. Typically when we upgrade from old DC to new version, we add a new server or servers to the same network and then add it to the existing forest, domain. It allow organizations to use new features, enhancements available on new directory services. It is important to keep the domain environments running with its latest versions.
We could choose 2012 R2 or 2016 or 2019 according to our requirement. Do we begin with our Domain Controllers? And if we choose 2012 R2, how long can we expect to have no compatibility issues? Is 2016, or 2019 preferred?įor what is new in Windows server 2012 R2, we could refer to:.Many thanks for your assistance everyone.
#Office 365 windows server 2008 r2 software
What server version, and what Exchange version, do we require in order to have complete compatibility with our migration to 365?ģ) Regarding both upgrades above, should we look at software upgrades on the existing servers, or completely new installs on new hardware?Ĥ) Once our Domain Controllers and Exchange have been upgraded, will our existing 20 Servers (some are SQL servers) still function normally?ĥ) Are there any hidden dangers that we may be unaware of? What I am hoping someone here can help with, are the following questions.ġ) Do we begin with our Domain Controllers? And if we choose 2012 R2, how long can we expect to have no compatibility issues? Is 2016, or 2019 preferred?Ģ) Regarding Exchange, my question is the same. It's not just about buying licences for 365 for our users, we need to upgrade our Domain Controllers and our Exchange first. My team has been tasked with drawing up a project road map. Our company wants to transition to Microsoft Office 365. Our corporate domain is set up as followsġ) Our Active Directory controllers (we have 2) are both Windows Server 2008 R2 Enterprise.Ģ) Our Exchange Server is also Server 2008 R2 Enterprise, and Exchange itself is 2007 v 08.03ģ) Our users all use Microsoft Office 2007 Service Pack 3.
0 kommentar(er)
