Adding a new Svr2008 R2 DC to 2003 domain func level env
SETUP:
1 forest
2 DC/GC (I believe all are 2003 Std R2 SP2+
2003 func level
Both with DNS svrs AD integrated and set to the other as primary then themselves
1 first instance of exchange 2003 Std R2 SP2+ behind the firewall.
2 webservers; one in the dmz one unavoidably behind the firewall.
(1 behind the fw is a CRM mission critical svr w/Svr2003 Std SP updated)
a few other member servers that are 2003 housing db sw, etc..
Questions:
I am looking to implement a new 2008 R2 STd server and replace one demote one of the 2003 svrs DC. I have several new win7 I had to deploy to users for various reason, new hire/replacements, etc...
We are looking to eventually move all our stuff to hosted solution by end of next year, but I want and need to incorporate the 2008 DC now. What are some things I need to be aware of based on the env I have and doing this? We had no plans to do any further updates exchange at this time. The new DC 08 will be a GC too was the plan, while I realize I will not be able to update the domain func level to 2008, but will I be able to take advantage of some of the new AD features and administer to win7 machines? If anyone is going to say I really need to move to 2010 exchange, the best I'd possibly be able to do would be a "IN PLACE" if that is even possible 2007 upgrade, so please advise on that only if it's an absolute to my being able to do the new 08 DC svr R2 implement I'm asking about and need to do! I’m looking for insights to what to look out for, consider, etc… from people that have been dealing with integrating 2008 dc in their env already.
Thanks!
1 forest
2 DC/GC (I believe all are 2003 Std R2 SP2+
2003 func level
Both with DNS svrs AD integrated and set to the other as primary then themselves
1 first instance of exchange 2003 Std R2 SP2+ behind the firewall.
2 webservers; one in the dmz one unavoidably behind the firewall.
(1 behind the fw is a CRM mission critical svr w/Svr2003 Std SP updated)
a few other member servers that are 2003 housing db sw, etc..
Questions:
I am looking to implement a new 2008 R2 STd server and replace one demote one of the 2003 svrs DC. I have several new win7 I had to deploy to users for various reason, new hire/replacements, etc...
We are looking to eventually move all our stuff to hosted solution by end of next year, but I want and need to incorporate the 2008 DC now. What are some things I need to be aware of based on the env I have and doing this? We had no plans to do any further updates exchange at this time. The new DC 08 will be a GC too was the plan, while I realize I will not be able to update the domain func level to 2008, but will I be able to take advantage of some of the new AD features and administer to win7 machines? If anyone is going to say I really need to move to 2010 exchange, the best I'd possibly be able to do would be a "IN PLACE" if that is even possible 2007 upgrade, so please advise on that only if it's an absolute to my being able to do the new 08 DC svr R2 implement I'm asking about and need to do! I’m looking for insights to what to look out for, consider, etc… from people that have been dealing with integrating 2008 dc in their env already.
Thanks!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hopefully the links provided help to confirm my original points.
ASKER
Tony1044, 0441,
Thanks for the replies... yes these insights are helping with clarity. 0441, I would never just have one DC, always at least two. I had three, got rid of one and have two 2003, plan is to setup the new 2008 with new corp.domain.com domain and migrate all users over to the new domain. Wow just remembered I was creating a brand new domian and doing away with the old.. ROFL. So, based on that originally ommitted info, any additional recommendations on that deployment/plannning? I will have to give thought and plan for switching exchange to the new domain and how that will work, getting my users over to the new domain and figuring out what will happen to thier profiles/desktop. We have local profiles not roaming or nw stored profiles now, etc...
Also on a different note, is it recommended that your 08 dc not be your remote desktop admin role machine. I want to set that up and deploy some apps and look into the TS gateway feature, too.
Thanks!
Thanks for the replies... yes these insights are helping with clarity. 0441, I would never just have one DC, always at least two. I had three, got rid of one and have two 2003, plan is to setup the new 2008 with new corp.domain.com domain and migrate all users over to the new domain. Wow just remembered I was creating a brand new domian and doing away with the old.. ROFL. So, based on that originally ommitted info, any additional recommendations on that deployment/plannning? I will have to give thought and plan for switching exchange to the new domain and how that will work, getting my users over to the new domain and figuring out what will happen to thier profiles/desktop. We have local profiles not roaming or nw stored profiles now, etc...
Also on a different note, is it recommended that your 08 dc not be your remote desktop admin role machine. I want to set that up and deploy some apps and look into the TS gateway feature, too.
Thanks!
Remote Desktop Admin Mode is fine for a Windows 2008 Server running as a Domain Controller. RemoteApps is not recommended on a Domain Controller though
The link provides detailed steps to add a 2008 Server as a Domain Controller doesn't help confirm but shows the steps
The link provides detailed steps to add a 2008 Server as a Domain Controller doesn't help confirm but shows the steps
You used to get into permission issues with running Terminal Server on a DC as users wouldn't have remote desktop access amongst other things, but I believe this is no longer an issues with RDS.
Generally not recommended to have anything other than domain services on a DC though.
Have you considered running a free hypervisor and running your machines in that environment?
Generally not recommended to have anything other than domain services on a DC though.
Have you considered running a free hypervisor and running your machines in that environment?
ASKER
K, so with some clearer thought today after reading all comments based on my original setup
1 forest
2 DC/GC (I believe all are 2003 Std R2 SP2+
DC1 holding all FSMO roles
2003 func level
Both with DNS svrs AD integrated
I now remember I am
domain name: domain.com (presently a registered public domain name, but not associated with our company and not my setup).
IP scheme 192.168.122.0/24
03 exchange
PLAN and new ? :
new svr 08 R2 x64
new sub domain name to our real public reg domain... e.g. corp.realpubdomainname.com
WIth the entire new domain, single forest and dc, I had wanted to keep both nw up and running and not change IP/nw scheme, but dont' think "ll be able to do this without introducing a new IP e.g. 192.168.123.0/24 for config of DNS and DHCP on this new server. It's been a while since I greated a new Domain and this is my first day trying to start my planning, so any heads up will be appreciated. THx
1 forest
2 DC/GC (I believe all are 2003 Std R2 SP2+
DC1 holding all FSMO roles
2003 func level
Both with DNS svrs AD integrated
I now remember I am
domain name: domain.com (presently a registered public domain name, but not associated with our company and not my setup).
IP scheme 192.168.122.0/24
03 exchange
PLAN and new ? :
new svr 08 R2 x64
new sub domain name to our real public reg domain... e.g. corp.realpubdomainname.com
WIth the entire new domain, single forest and dc, I had wanted to keep both nw up and running and not change IP/nw scheme, but dont' think "ll be able to do this without introducing a new IP e.g. 192.168.123.0/24 for config of DNS and DHCP on this new server. It's been a while since I greated a new Domain and this is my first day trying to start my planning, so any heads up will be appreciated. THx
Why do all of that you don't have too?
ASKER
Darius, that question doesn't help me give you more info. My goal is to get a new 08svr with a new correctly named domain, going from fish.com to corp.meat.com, while my posting is to help me figure out the best plan to accomplish that. At this step of the thought process for me I'm just wondering how to do this while maintainng the same nw ip scheme, which I'd not planned on changing, but wth the need for DNS and DHCP config on the new 08, not sure how best to approach!? Looking for 'hey consider this', 'hey possibly do this first and then do this...', etc... from experts. Thank YOu!
ASKER
Thank you I'll post again for more insights to my thought on restructuring the domain.
Here are the steps on moving to adding a Windows 2008 Server as a DC to an existing Windows 2003 domain.
https://www.experts-exchange.com/questions/23665224/Windows-2008-Server-Migration-From-Server-2003.html
Below is an article that describe the changes with adprep in Windows 2008 Server R2
https://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/A_3644-Windows-2008-Server-R2-adprep-adprep32.html