After executing this command i found: :
\netdom query fsmo
Schema Owner DC1.domain2.net
Domain Role Owner DC1.domain2.net
PDC Role DC1.domain2.net
RID Pool Manager DC1.domain2.net
Infrastructure Owner Dc1.domain2.net
:\\repadmin \options
Current DC options: (none)
Hi,
How did you raise the domain function level, via ADUC, ADDT or commands? Did you recieve any error message?
In general, it is needed to configure tge domain mode to native mode before you raise the domain level.You can follow the article below to check the msDS-Behavior-Version and ntMixedDomain attribute:
How to raise Active Directory domain and forest functional levels
After you raise the domain function level, you can also raise your forest function level if needed.
Best regards,
Susie
Hello,
"But before executing adprep\ the 2003 server's Raise forest functional level has to be raised from 2000 to 2003 but it was disabled by default"
What do you mean with "but it was disabled by default"?
netdom query fsmo will show you the current FSMO roles holder. So is that machine the Windows Server 2003 DC?
Check below link...
https://social.technet.microsoft.com/Forums/windowsserver/en-US/641198b6-64a2-4af2-bd17-6c4265be0396/planning-migration-windows-2003-r2-32-bit-to-windows-2008-r2-standard-64-bit?forum=winserverMigration#1c0ada63-b426-493f-8d1b-8c81c1d9f9db
The Fsmo roles holds by a 2008 R2 DC if that was the case how the raise level can be done in the 2003 server for the migration to take effect into another new 2008 R2 server
Hello,
I still don't understand your question. The new server should be added to the existing domain and then should be promoted to DC.
If you have installed a fresh Windows Server 2008 R2 using the same domain name as on the Windows Server 2003 machine then you can NOT migrate them.
PLEASE elaborate in detail what steps you have done on which server.
Have two domain controllers: Dcntrl1.Domain1 & Dcntrl2.Domain2
While executing fsmo roles in Dcntrl2 (2003 server) it shows
Domain role Owner Dcntrl1.Domain2
PDC Dcntrl1.Domain2
RID Dcntrl1.Domain2
Infrastrure Dcntrl1.Domain2
The Dcntrl2 is replicated through RPC from Dcntrl1 which i found under sites and services although its broken or corrupted in the 2003 server however Dcntrl1 is not, the replication is never enabled to this domain(2003).
- Edited by isbest Tuesday, April 14, 2015 3:19 PM
Have two domain controllers: Dcntrl1.Domain1 & Dcntrl2.Domain2
While executing fsmo roles in Dcntrl2 (2003 server) it shows
Domain role Owner Dcntrl1.Domain2
PDC Dcntrl1.Domain2
RID Dcntrl1.Domain2
Infrastrure Dcntrl1.Domain2
The Dcntrl2 is replicated through RPC from Dcntrl1 which i found under sites and services although its broken or corrupted in the 2003 server however Dcntrl1 is not, the replication is never enabled to this domain(2003).
- Edited by isbest Tuesday, April 14, 2015 3:19 PM
Hello,
to understand you correct:
- currently you have 2 DCs listed in AD sites and services where both machines are Windows server 2003
- one of this DCs is NOT existing anymore but still existing in some settings
- the new Windows server 2008 R2 is NOT added to the domain yet
To remove the not longer existing DC from the domain complete please follow http://support.microsoft.com/kb/230306 Also assure after all that steps that neither in the DNS zones and zone properties nor AD sites and services the not longer existing DC is listed.
If all that steps are done you should be able to raise the functional levels.
The 1st DC is 2008 R2, the 2nd DC is 2003 server and the 2nd DC has to be replaced with new 2008 R2 in same ip and domain name and i found the 2003 ADDS was replicated from 2008 r2 (1st DC) earlier
But under Sites and Service in the 1st DC there is no such replications or may be the admin might have removed 2003 server DC
- Edited by isbest Wednesday, April 15, 2015 6:35 PM
The 1st DC is 2008 R2, the 2nd DC is 2003 server and the 2nd DC has to be replaced with new 2008 R2 in same ip and domain name and i found the 2003 ADDS was replicated from 2008 r2 (1st DC) earlier
But under Sites and Service in the 1st DC there is no such replications or may be the admin might have removed 2003 server DC
- Edited by isbest Wednesday, April 15, 2015 6:35 PM
Hi,
If you want to keep the same name for the new DC, then you need to demote the existing Windows Server 2003 DC and make sure everything is replicated to the other DC, then either rename it so you still have it in the domain for copying needed data or copy needed data before and remove it complete to free the name. After that, you can add the new Windows Server 2008 R2 to the domain and promote it to a DC using the same name, the the new DC will replicate from the first Windows Server 2008 R2 DC.
Best regards,
Susie
Hello,
if the errors are resolved and the domain is free from old entries you can follow the next articles.
For migration to a new OS version please see http://blogs.msmvps.com/mweber/2010/02/10/upgrading-an-active-directory-domain-from-windows-server-2003-to-windows-server-2008-or-windows-server-2008-r2/ and for keeping a DCName please see http://blogs.msmvps.com/mweber/2010/02/13/upgrade-a-domain-controller-to-a-new-operating-system-version-and-keep-the-name/
- Edited by isbest Monday, April 20, 2015 8:33 PM
How about offline, by disconnecting from Active connection of the existing 2003 server and replacing it with 2008 r2 with same ip and domain name by connecting back Active LAN, entering the users manually, would that make any difference??
Hello,
using the same domain name in a new installed server will NOT work. The SID(Security Identifier) will be different and the domains will NOT connect for replication etc.
This DC doesnt need replications any more and so will the domain name works if it assigned the same and as a subdomain or can go for new domain & forest because this DC is in different location.
Hello,
if you use the same domain name on a new installed DC all clients must be added to the NEW domain and also all user accounts policies etc. must be created NEW.
Profiles on domain machines are not usable within the new domain by default. Additional steps are needed if the profiles must be usable on the new domain.
Its ok for creating new user accounts and policies but is it possible in by creating a subdomain or go for new domain in new Forest and implementing all those specified above.
Hello,
sorry but i don't understand this question
Hello,
if you use the same domain name on a new installed DC all clients must be added to the NEW domain and also all user accounts policies etc. must be created NEW.
Profiles on domain machines are not usable within the new domain by default. Additional steps are needed if the profiles must be usable on the new d