Pepuri Server world Eng Version

Windows Server 2025 has been released.

To take advantage of the new OS, I'll upgrade the AD Domain Controllers DC01 and DC02 to Windows Server 2025.

In a real-world environment, many factors would need to be considered, but since this is a test environment, I will only cover the basic upgrade process.

 

The Windows Server 2025 installation image created earlier using Sysprep was utilized.

Test Environment

 

https://youtu.be/YcF0ztnJJ8A

 

 

The process was carried out in the following steps:

1. DC02: Windows Server 2022 Demote

2. DC02: Windows Server 2025 Promote

3. Change the Master role to DC02.

4. DC01: Windows Server 2022 Demote

5. DC01: Windows Server 2025 Promote

6. Change the Master role back to DC01.

 

 

Step 1. Remove DC02

 

 

Add roles and features

 

 

Start the Remove Roles and Features Wizard

 

 

Next

 

 

Next

 

 

Active Directory Domain Services

 

 

Remove Features

 

 

Demote this domain controller

 

 

Next

 

 

Proceed with removal -> Next

 

 

Next

 

 

Next

 

 

Demote

 

 

Close

 

 

Close

 

 

Verify that the Domain Controller (DC) has been successfully removed.

 

 

After rebooting, proceed with removing the roles again.

 

 

Switch the machine to WORKGROUP mode.

 

 

Remove DC02 from Active Directory Users and Computers (ADUC).

 

 

Yes

 

 

Step 2. Install the Domain Controller (DC) role on Windows Server 2025.

 

 

Proceed with joining the server to the Active Directory (AD).

 

 

Server Manager -> Add roles and features

 

 

Next

 

 

Next

 

 

Next

 

 

Active Directory Domain Services

 

 

Add Features

 

 

Next

 

 

Next

 

 

Next

 

 

Install

 

 

Promote this server to a domain controller

 

 

Add a domain controller to an existing domain -> Next

 

 

Enter the Password and click Next.

 

 

Next

 

 

Next

 

 

Next

 

 

Next

 

 

Next

 

 

Install

 

 

Once completed, the system will reboot.

 

 

Enter the following command to change the DC Master role to DC02:

Move-ADDirectoryServerOperationMasterRole -Identity DC02 -OperationMasterRole SchemaMaster, DomainNamingMaster, PDCEmulator, RIDMaster, InfrastructureMaster

 

 

Netdom query fsmo

 

 

Step 3. Remove DC01

 

 

Update the DNS Address to point to DC02.

 

 

Server Manager -> Add roles and features

 

 

Start the Remove Roles and Features Wizard

 

 

Next

 

 

Active Directory Domain Services

 

 

Remove Features

 

 

Demote this domain controller

 

 

Next

 

 

Proceed with removal -> Next

 

 

Next

 

 

Enter the Password and click Next.

 

 

Demote

 

 

Close

 

 

After rebooting, navigate back to the Roles and Features removal menu and proceed with the Active Directory Domain Services (AD DS) removal process.

 

 

Click Close and proceed with the system reboot.

 

 

Switch the machine to Workgroup mode.

 

 

Remove DC01 from Active Directory Users and Computers (ADUC).

 

 

Step 4.. Install DC01

 

 

On the new VM for DC01, configure the IP address and set the DNS server to DC02.

 

 

Domain Join

 

 

Add Roles and features

 

 

Next

 

 

Next

 

 

Next

 

 

Active Directory Domain Services -> Next

 

 

Promote this server to a domain controller

 

 

Next

 

 

Enter the Password and click Next.

 

 

Next

 

 

Next

 

 

Next

 

 

Next

 

 

Install

 

 

Click Close, and the system will reboot.

 

 

Set DC01 as the Primary DNS and DC02 as the Alternate DNS.

S and DC02 as the Alternate DNS.

 

 

Run the following command to change the Master role back to DC01:

Move-ADDirectoryServerOperationMasterRole -Identity DC01 -OperationMasterRole SchemaMaster, DomainNamingMaster, PDCEmulator, RIDMaster, InfrastructureMaster

 

 

Netdom query fsmo

 

 

Step 5. Raise Forest Functional Level

Active Directory Domains and Trusts

 

 

In Active Directory Domains and Trusts, right-click and select Raise Forest Functional Level to upgrade the forest functional level.

 

 

Raise

 

 

OK

 

 

Use the following command to verify the current functional level:

Get-ADDomain |fl name, DomainMode
Get-ADForest |fl Name, ForestMode

Windows Server 2025 has been released.

Whenever a new OS is launched, I create a disk image of the installed system using Sysprep to facilitate testing in a Hyper-V environment.

This method is highly convenient because, when creating a new VM, I can simply copy the disk image file to immediately load the OS.

Although I’ve covered this topic before, I’m writing it again as part of a renewal for a YouTube video.

This is based on Windows Server 2025 and Hyper-V.

 

https://youtu.be/snj74akjzCA

 

 

Hyper-V -> New -> Virtual Machine

 

 

Name specification -> Set Default Location -> Next

 

 

Name specification -> Set Default Location -> Next

 

 

Confirm Generation 2 -> Next

(From 2025, Generation 2 is set as the default.)

 

 

Set RAM -> Next

 

 

Specify Network Adapter -> Next

 

 

Confirm Disk Location -> Next

 

 

Specify Installation Disk -> Finish

 

 

Double-click on the created VM

 

 

Start

 

 

Enter the key to proceed with the installation process.

 

 

Select Language -> Next

 

 

Next

 

 

Agree -> Next

 

 

Enter Product Key -> Next (I entered an AVMA key as I am using it in a Hyper-V environment.)

 

 

Accept

 

 

Next

 

 

Install

 

 

Proceed with Installation

 

 

The system will automatically reboot.

 

 

Once the installation is complete, the screen will appear as shown. At this point, press Shift + Ctrl + F3 simultaneously.

 

 

The system will reboot, and the screen will appear as shown. Select OOBE, Generalize, and Shutdown, then click OK.

 

 

Sysprep will run, and once completed, the system will shut down.

 

 

Back up the created VHDX disk image. This disk can be used to streamline the OS installation process.

 

 

You can select the disk image from the menu below to create a new VM.