Link to home
Start Free TrialLog in
Avatar of ITm1010
ITm1010

asked on

Windows Server 2003 STD SP2 as a member server of 2016 domain

Dear All,

I have a trouble with one of my legacy systems, it can run on Windows 2003 only. My domain is 2003 as well. In the scope of my risk mitigation, I plan to upgrade my domain system. I have a hard time with my domain environment since my 2003 ERP server is a DC as well, as two additional DC. Fortunately, all servers are virtual (VMWare)

My plan:

1. Unpromote 2003 ERP server and make it a member server.
2. Upgrade domain from 2003 to 2016. Here is my major problem. I want to be 100% sure Windows 2003 Standard SP2 can run in a 2016 domain environment as a member server. I'd like to mention that the server runs SQL Server 2005 as well

Detailed answers will be highly appreciated
Avatar of John Tsioumpris
John Tsioumpris
Flag of Greece image

Since you have everything virtualized why don't you setup a lab and test if the scenario is viable or you need to take extra steps.....just copy your vms to a separate isolated host server and you are good to go...
Avatar of ITm1010
ITm1010

ASKER

Thank you, John, for your prompt response. Before I start doing lab environment I want to make sure that 2003 SP2 officially supported in 2016 environment as a member server. It a simple question to ask and it can save a lot of efforts.
Member server have no impact on a raised domain...so the 2003 server should function correctly on a 2016 environment...but is always to be safe than sorry...given the added bonus you have everything virtualized it would be a day's work to do all the steps without worrying if something goes wrong...and you will have all the steps to do it right and with minimum downtime.
2003 is not officially supported in a 2016 domain. 2003 is not officially supported in ANY domain. That's the definition of end-of-life. As for compatibility issues... There will be some. Mostly with negotiated encryption levels in kerb Eros and elsewhere. You can find this documented on the web and workarounds, but it is unsupported and your mileage may vary. T'is the nature of running an old OS.
Avatar of ITm1010

ASKER

Thank you, Cliff. As you mentioned my major concern is compatibility issues. Can I avoid issues if I upgrade my domain to 2012?
ASKER CERTIFIED SOLUTION
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ITm1010

ASKER

Dear Cliff and Lee, thank you for your time and patience. Before I mark your answers as "Best Solution" and "Assisted Solution" I would like to ask one last question: are there known issues with 2003 in 2012 domain level and in 2016 domain level environment?
You are stuck on "domain level." As I said above, the LEVEL doesn't matter. There are known issues with a 2003 server on a network with 2012 R2 domain controllers. Even if the functional levels are still 2003. The LEVEL doesn't prevent the issues. Old servers, new DCs are the problem. FULL STOP!!!
Avatar of ITm1010

ASKER

Thanks, Cliff. I'm not "stuck on domain level". Unfortunately real life and business are way more complicated than Microsoft white paper. I'm dealing with legacy ERP systems here... You can imagine what does it mean to upgrade out-of-date ERP from the process, regulatory and financial point of view. It is not an IT decision here. It is much more than IT.

Dear colleagues. thank you for your efforts and patience.
Avatar of ITm1010

ASKER

Thank you all for your time and patience