Windows 10: Migrating services from old 2012 R2 Domain Controller to new 2022 servers...

Currently our old DC also incorrectly has DHCP, CA, and Print Services /management.So not only do most static machines already have a dns entry that points to the old DC server, but i have this mess of services that need to go elsewhere.Its my understanding from going from 08 to 12 way back when, i just need to move the 5? ad roles to the new member server? I thought i read something about FSR sysvol issues as well?Beyond this, once they are on the new 2019 server, i guess i just run the domain and forest upgrades to 2022 level after the fact?Is there some way to avoid changing the dns ip

:)

 

Raising the windows domain and forest issues?


hi,

I run a domain that was all 2003 r2 servers. I recently upgraded all my domain controllers to windows 2012 r2.
That went off without any problems.. Our trust relationships had no issues also.

My first step was to raise the Domain and Forest levels past 2003 to 2008. This went off without a hitch.
These are the features for raising the levels to 2008:

• Features and benefits include all default Active Directory features, all features from the Windows Server 2003 domain functional level, plus:
• Read-Only Domain Controllers – Allows implementation of domain controllers that only host read-only copy of NTDS database.
• Advanced Encryption Services – (AES 128 and 256) support for the Kerberos protocol.
• Distributed File System Replication (DFSR) – Allows SYSVOL to replicate using DFSR instead of older File Replication Service (FRS). It provides more robust and detailed replication of SYSVOL contents.

Forest Level Windows Server 2008

• Features and benefits include all of the features that are available at the Windows Server 2003 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2008 domain functional level by default.

My next step is to raise the domain and forest to 2008 r2, then 2012, and finally 2012 r2. I have been trying to find out exactly what I could expect from raising the Domain and Forest for each step.

The step involving 2008 r2 seems relatively a non issue. But getting the couple of new features seem very nice

Domain Level Windows Server 2008 R2

• All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus 2 new features

Forest Level Windows Server 2008 R2

• All of the features that are available at the Windows Server 2003 forest functional level, plus the following features:

• Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. <== New Feature very cool
• All domains subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default.

Here is my big concerns for the next raising of domain and forest to 2012.

Forest Level Windows Server 2012:

• All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features.
• All domains subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.

Domain Level Windows Server 2012 R2: <=====Need to investigate more and why this post

• DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer:

• Authenticate with NTLM authentication <==============(what issues may arise)
• Use DES or RC4 cipher suites in Kerberos pre-authentication
• Be delegated with unconstrained or constrained delegation
• Renew user tickets (TGTs) beyond the initial 4-hour lifetime

Will this affect my exchange anywhere users with remote access authenticating either clear of NTLM???
and what would/may not to work properly day 1 when I raise the domain and forest to 2012. I cant really find anyone that can answer a straight question.

Has anyone gone through this? what problems did you have, if any , if a lot???

Any thoughts and suggestions will be much appreciated??

thanks


- - - Updated - - -

One more point... I am not sure if I posted this to the correct forum.. So if I was wrong and it should be in a different one..
PLEASE LET ME KNOW

 

How to add Windows 2012 R2 as new domain controller in the existing Windows 2008 R2 domain.

In our environment we had three domain controller as single forest and all the servers on windows 2008 R2, one is located at branch office in different region, two at Head Office among which one is PDC. Additional DC has crashed today ( Hardware failure),
now i am planning to have Windows 2012 R2 DC on new Hardware. kindly suggest the best practice to achieve this. kindly note i had Wins and Certification authority also on the crashed server.

 

migrating Print Server From Server 2012 R2 Standard to Server 2012 R2 Standard

Hi dears ,

I want to use Printer migration tool to transfer my printers from my print-server 2012 R2 To another one Server 2012 R2 Which already Contain some printers in same network and shutdown old one so I exported all my printers data to a file and came to a new
print server to import them but Unfortunately while I want to import the printers I get error saying :

Windows could not read printer data from the import file , issue attached

thanks for any help .