Category: Microsoft Windows Server

In this blog, I will configure iSCSI SAN which is a feature in Windows 2012, after setting up iSCSI SAN I will create a 2 Node Failover clustering in Windows 2012 accessing the shared iSCSI SAN.

Server 2012 Failover Clustering iSCSI

Environment Details.

Server2012-DC

Ethernet0 10.0.0.20

iSCSI (Server2012)

Ethernet0 10.0.0.100

Server-1 (Node1)

Ethernet0 10.0.0.20

Ethernet1 192.168.0.10

Server-1 (Node2)

Ethernet0 10.0.0.20

Ethernet1 192.168.0.20

CLUSTER IP ADDRESS – 10.0.0.110

First, we’d like to put in and Configure target iSCSI server in Windows Server 2012 (iSCSI – Server2012)

How to install and Configure iSCSI SAN in Server 2012 Click Here

How to Add Failover Manager Feature and iSCSI virtual disk to first Node (Server-1).

1- Open Server Manage, left side select dashboard and click on ADD Roles and Features.

2- Click Next.

3- Click Role-based or feature-based installation and then click Next.

4- Select a server from the server pool and click on next.

5- Click the Application Serve role and click next.

6- Select the Failover clustering box.

7- Click Add features.

8- After enabling the failover clustering feature, click next.

9- Application Server feature, click next.

10- Click Next.

11- Click Install.

12- Successfully enable the failover cluster feature, click Close.

Adding the Virtual Disk.

13- Open Server Manager, click Tools and Click iSCSI initiator.

14- Type the IP address or Name of the Target iSCSI server (my iSCSI target server IP is 10.0.0.100) and click Quick Connect.

15- Click on all the inactive disks and click connect.

16- After all the disk is connected, click Done.

17- Click OK.

Adding Failover Manager Feature and iSCSI virtual disk to 2 Node (Server-2).

Follow all the steps (from 1 to 17) the same as 1 Node (Server-1).

18- After successfully added the disk and connected.

Initializing the Disk and Formatting

Note: If you are working on a Failover cluster the following steps need to be performed only on a Single Node of the cluster.

The following steps are performed on the 1 Node (Server-1).

19- In Server Manager click Tools and click Computer Management.

20- Click on Disk Management.

In Computer Management You will see 2 disk’s which we added using iSCSI initiator as Unknown and offline status.

21- Right-click on each disk and select Online.

22- Right-click on disk and click Initialize Disk.

23- Select both the disks and click ok.

24- Now both the Disk are online and Unallocated.

25- Right-click on the unallocated disk and select New Simple Volume.

26- Click Next.

27- Click Next.

28- Assign a drive letter and click next.

29- Type a volume label and click next.

30- Click Finish.

Follow the same steps (from 25 to 30) for the 2nd disk (QUORUM).

31- Now both the disks are online and healthy.

The next step is to log in to 2 Node (Server-2).

Open Computer Management and click Disk Management.

Note:  Disks are offline and unallocated status.

32- Right-click and bring the disk online.

33- You will notice that disk are online with assigned drive letters and volume name.

34- Right-click on each disk and select offline on both the Nodes (Server-1 and Server-2)

35- Now both the disks are offline.

FAILOVER Cluster MANAGER CONFIGURATION.

I am logged in on 1 Node (Server-1) with domain Administrative rights.

36- Open Server Manager > select tools and then click Failover Cluster Manager.

37- Click Validate configuration.

38- Click Next.

39- Click the Browse button.

40- Type node names, click check names and then click ok.

41- After selecting both the servers, so click next.

42- Select Run all tests (Recommended) and then click next.

43- Click Next.

Make sure all the Failover Cluster Validation testing completes with no errors.

44- leave the Checkbox selected to create the cluster now using the validated nodes and then click Finish it will start the cluster creation wizard.

45- Click Next.

46- Click the Browse button.

47- Type server names, click check names and then click ok.

48- Type a Cluster Name and IP address and then click next.

49- Leave the Checkbox to add all storage to Cluster and then click next.

50- Default Running Process.

51- Failover cluster Successfully completed, so click Close.

Quorum Settings.

52- When creating a cluster, depending on the number of Nodes it automatically picks the correct quorum settings and then disk.

53- If you need to change settings, right-click cluster, more action select configure cluster quorum settings.

We have successfully created the Failover Cluster, let’s test the Failover.

54- Active Node (Server-1) before Failover.

55- Active Node (Server-2) after Failover.

We have successfully tested the Failover Cluster in Windows Server 2012.

For more details click here

Installing and Configuring target iSCSI server in Windows Server 2012

Installing and Configuring Target iSCSI Server 2012

1- Open Server Manager, click Dashboard and then select Add Roles and features.

2- Click Next.

3- Select the Role-based or feature-based installation and then click on the Next button.

4- Select a server from the server pool and then click on next.

5- Select the iSCSI Target Server box.

6- Click Add Features.

7- After Selecting the iSCSI target server feature and then click next.

8- Click Next.

9- Click Install.

10- iSCSI services successfully installed, so click Close.

11- Open Server Manager and then click File and Storage Services.

12- Click iSCSI and under iSCSI Virtual Disks click Tasks and then click New iSCSI Virtual Disk.

13- Select a volume and click next.

14- Type an iSCSI virtual disk name and click next.

15- Select a Size for the disk in GB and click next.

16- Select New iSCSI target and click next.

17- Target servers will identify the disk with this Name, so Type a Name, description and click next.

18- Click Add we need to Add all the Servers which will be accessing this disk.

Note: Make sure on the target server you have enabled the iSCSI initiator service.

19- Click the Browse button.

20- Type a node server name, select check names and click ok.

21- Add all the server you want the disk to have access, I have added both the servers (Server-1 and Server-2) and click next.

22- Enable any authentication if you need and click next.

23- Confirm the iSCSI virtual disk settings and click Create.

24- Virtual Disk created successfully, click Close.

25- Please follow the above steps from (1 to 24) to add one more disk name Quorum.

For more details click here

In this blog, we’ll configure a basic 2-node Failover Cluster Server 2012, where we’ve two servers (Server2012-1 and Server2012-2) running Windows Server 2012 and Windows Server 2012 Active Directory Domain controller (Server2012-DC). It also assumes that Server2012-1 and Server2012-2 will communicate with one another over two network connections, I even have labeled Ethernet and Private

Failover Cluster Server 2012

Add the Failover Clustering feature on both of the servers you would like to feature to the cluster.

1- Open the Server Manager Dashboard and choose Add roles and features. (You got to add failover cluster feature to completed on both Server2012-1 and Server2012-2).

2- Click Next.

3- Select the role-based or feature-based installation and click on next.

4- Select a server from the server pool on which you would like to enable the failover cluster feature and click on next.

5- Server roles page, click next.

6- On the features, page select the Failover Clustering box.

7- Select the Add feature button the feature required for the Cluster.

8- After adding Failover Cluster Server 2012 features, click next.

9- Click the Install button to start out the failover cluster installation.

10- Windows server 2012 cluster role successfully Installed, click Close.

11- After enabling Failover Cluster on both servers (Server2012-1 and Server2012-2), on your Server2012-1 open server manager, select tools and choose Failover Cluster Manager.

Failover Cluster Validation Configuration

12- After opening the Failover Cluster Manager under management-click on Validate Configuration option.

13- Cluster validate a configuration wizard windows will pop up, click next.

14- Select servers or cluster options and click on the Browse button.

15- Select the servers you would like to cluster, in my setup I selected (Server2012-1 and Server2012-2) and click on ok.

16- After selecting servers, click next.

17- Select run all tests (recommended) and click on next.

18- Failover cluster validate confirmation, click next.

19- Failover cluster validation summary, click View Report.

20- you’ll see all of your warnings are associated with storage, because I even have not configured any shared storage.

Failover Cluster Configuration

21- Once the Validation checking completed, create cluster wizard will automatically open, click next.

22- Type your cluster name in the cluster name option (XTCLUSTER) and pick an IP address that will be related to this name in DNS. This name is to manage your cluster Once you create this access point a replacement computer object is going to be created in AD with this name and a DNS A record are going to be created with this name and IP address and click on next.

23- On the confirmation screen you’ll see the name of the cluster and two nodes and IP address you chose. Uncheck Add all eligible storage to the cluster and click on next.

24- you’ve got successfully completed the create cluster wizard, click View report back to inspect any warnings.

25- There could also be some warnings. In my case, the warnings are probably associated with the quorum configuration.

We have no shared storage; we’ll not be employing a Node and Disk Majority quorum as suggested. Instead, we’ll use and Node and File Share Majority quorum.

A File Share Witness must be configured on a server that’s not a part of the cluster. A file share witness may be a basic file share that the cluster computer name (XTCLUSTER in my step) has read/write access. I’m getting to create a file share on my Server2012-DC and provides XTCLUSTER read/write access thereto.

Configure File Share Witness

26- Open server manager in Server2012-DC, Left side select file and storage services and choose shares under volume click tasks and click on New Share.

27- Select share profile SMB share quick and click on next.

28- Select the server and path for SMB share and click on next.

29- Type-A share name and share descriptions and click on next.

30- Under other settings, uncheck Allow caching of share and click on next.

31- Specify permissions to regulate access, click on customize permissions.

File Share Permission

32- Advanced security settings for share (FSW), click Add button.

33- Click on Select a principal.

34- Select Object Types.

35- Check the computers box under object types and click on next.

36- Type your cluster name in my case (XTCLUSTER), click check names and click on ok.

37- Under basic permissions check to Modify box and then click on ok.

39- In advanced security settings, select the share tab and then click on the Add button.

40- Select object types.

41- Check the computer box and then click on ok.

42- Type your Cluster name, click Check Names and then click on ok.

43- Click Apply and then ok button.

44- Read the share SMB confirmation summary and then click on Create.

45- The SMB share was successfully created, so click Close.

46- To configure Cluster Quorum share created on Server2012-DC, return to your Server2012-1 right-click XTCLUSTER.xpertstec.local and choose more actions and choose to configure cluster quorum settings.

47- In configure cluster quorum wizard, so click next.

48- Select add or change the quorum witness option and then click on next.

49- Select configure a file share witness (recommended for special configurations) and then click on next.

50- Click the Browse button and choose the trail of the file share witness that we created on the Server2012-DC and then click on next.

51- In configure cluster quorum wizard, so click next.

52- Review the configure cluster quorum settings summary and then click on Finish.

For more information click here

In this blog, we’ll configure Network Load Balancing (NLB), where we’ve two servers (Server-1 and Server-2) running Windows Server 2012 and a Windows Server 2012 Domain controller (Server2012-DC). It also assumes that Server-1 and Server-2 will communicate with one another over two network connections I even have labeled Ethernet and NLB.

Servers IP Address.

Server2012-DC –            10.0.0.20

Server-1

                        Ethernet0 – 10.0.0.30

                        NLB –           192.168.0.10

Server-2

                       Ethernet0 – 10.0.0.40

                       NLB –            192.168.0.20

Cluster IP – 192.168.0.30                      

192.168.0.40

Network Load Balancing Process

1- On Server-1 open server manager and choose Add roles and features.

2- Click Next.

3- Select the role-based or feature-based installation and click on next.

4- Select a server from the server pool and click on next.

5- Server Roles, click next.

6- Select the Features Network Load Balancing.

7- Select Add feature.

8- After selecting Network Load Balancing, click next.

9- Confirm installation selections and click on Install.

10- Select the close button after completing the network load balancing installation.

Repeat an equivalent steps 1 to 10 for server-2 to enable feature network load balancing

11- After this, I check out my NIC’s most vital that we use two NIC’s in Servers.

I gave Nic’s an IP that’s not within the same subnet because of the production LAN, and also you’ll use a special VLAN for the NLB tropic.

NLB Server-1

12- I rename them one is Ethernet and therefore the other is NLB.

13- In server-1 open server manager, click tools and choose the Network Load Balancing Manager.

New Cluster Setup

14- After opening the Network Load Balancing Manager, right-click on network load balancing cluster and choose the new cluster

15- In host Type, the IP address of the primary NLB Server-1 (192.168.0.10) click connect.

There are two IP Addresses, one is for Ethernet0 IP and One is for NLB IP Address, click next.

16- Click Next.

17- Now we will create the cluster IP select Add button.

18- Type the IP address which will be used for the Cluster NLB and click on ok.

19- Click Next.

20- you’ll use multiple IP Addresses the add the NLB, that way you’ll run multi-sites on one NLB management but all on different IP Addresses / FQDN names / DNS. And on different ports. Or settings.

Now I select an FQDN for the NLB cluster name (xpertstec.local) and under cluster operation mode select Unicast and click on next.

21- Click Finish.

22- Uncheck All box.

23- After selecting cluster IP Address under port range select from 80 to 80 just the ports that we’d like and click on ok.

24- Now the cluster is prepared (one node).

25- Right-click your cluster (xpertstec.local) and choose Cluster Properties.

26- Select the cluster IP Address option and click on Add.

27- I added a second IP to the cluster and click on ok.

29- Select Port Rules and click on the Add button.

30- Uncheck All and sort the second IP Address of the cluster Select Port range and click on ok.

31- After adding second IP Address, click ok.

Now we’ve two IP addresses and different ports.

Add Host To Cluster

32- Right-click your cluster and choose Add Host To Cluster.

33- Type second node IP address (Server2012-2 – 192.168.0.20) and click on connect.

34- Select the Interface name NLB and click on next.

35- Priority (Unique host identifier) select 2 and click on next.

36- Click Finish.

37- Both nodes are now joined to the NLB cluster and that we can build an NLB website.

For more details click Here

Create a Failover Cluster in Windows Server 2012

In this blog, I will explain how to install an Additional Domain Controller (ADC) in Windows server 2019. An additional domain controller is a backup domain

1- Click the Windows start button and choose the server manager.

Install Additional Domain Controller

2- Windows Server Manager, Dashboard, Under configure this local server and select Add roles and features.

3- Add roles and features wizard so, click on next.

4- Installation Type so, select Role based or feature-based installation and then click on next.

5- Select a server from the server pole and then click on ext.

6- Select the Active Directory Domain Services box.

7- Select Add Features that are required for the Active Directory Domain Services.

8- After selecting the active directory features so, click next.

9- Active directory add roles and features wizard and click on next button.

10- Now click Next.

11- So, click the Install button to start out the active directory installation.

12- After active directory installation and click on Close.

Promote Domain Controller

13- In Server Manager click warning message and then click on Promote this server to a website controller.

14- Select the deployment operation (Add a DC to an existing domain). then click the select button and browse to xpertstec.local, verify that credentials are Administrator and then click on next.

15- If you get this message Verification of replica failed so, please cancel the setup and then follow the below steps.

Update you’ll verify if the system uses the FRS using follow below steps

SYSVOL migration from FRS to DFSR Click Here

16- Return again open Server Manager click warning message and then click on Promote this server to a DC.

17- Deployment Configuration option So, Select Add a domain controller to an existing DC, and then click the select button and browse to xpertstec.local, verify that credentials are Administrator and then click on next.

18- Verify that the name System (DNS) server and Global Catalog (GC) are selected and sort the directory services restore mode DSRM Password and then click on next.

19- Ignore the DNS options warning and then click on next.

20- Specify Additional replication Options interface, besides the Replicate from Select Server2008.xpertstec.local and then click on next.

21- Specify the situation of the AD DS database, log files, and SYSVOL folders and then click on next.

22- Active directory 2019 preparation options and then click Next.

23- Review the choices interface so, verify all the knowledge and then click on next.

24- On the prerequisites check to verify that each one prerequisites checks passed successfully and then click on Install.

25- Now please awaits jiffy for the method to finish and then click on Close.

26- After restarting windows Server 2019 operating system and then log in as Domain Administrator.

27- Then log in to your DC, open active directory users and computers, expand your domain.local (xpertstec.local) and then choose DC and here you’ll find the extra DC.

Watch this video on our YouTube Channel

For more details click here

In this article, I am going to share how to setup and Configure an active directory in Windows Server domain controller using windows server 2019 standard.

Requirements for Configuration of Active Directory.

The administrator account features a strong password

Static IP is configured

Latest windows updates

A firewall turned off

Rename Computer (optional)

1- Click the Search button and type Server Manager and then click on the Server Manager.

2- From the Server Manager windows so, select Dashboard and under configure this local server select Add Roles and Features.

3- So, click Next.

4- Under Installation Type, Select Role-based or feature-based installation and then click on next.

5- Select a server from the server pool on which you would like to configure AD and then click on next.

6- Now chose the Active Directory Domain Services box from the server roles page.

7- A Windows will popup be showing additional required features so, click on Add Features.

8- After adding active directory features so, click next.

9- Default settings and then click on next.

10- Review Active Directory Domain Services and then click on next.

11- Review the confirmation of active directory configuration and then click on Install.

12- Active directory 2019 setup completed and then click on close.

Configuring Active Directory.

13- From Server Manager in Active Directory Configuration click on the notifications icon and then click on Promote this server to a website controller.

14- Now under the deployment in Setting up Active Directory, operation select add a replacement forest under the basis name and then click on next.

15- Keep as forest and domain functional level Windows Server 2016 because of the default level.

Keep the name System (DNS) server and Global Catalog (GC) checked and sort the active directory services restore mode (DSRM) password and then click on next.

16- Ignore warnings within the DNS options window during Configuration of Active Directory and click on next.

17- within the additional options During the Setup Active Directory window, verify the NetBIOS name and click on next.

18- Specify the situation of the AD DS database, log files, and SYSVOL folders and click on next.

19- Within the review options window > review name, NetBIOS name, and Global catalog, etc. and click on next.

20- When all prerequisite has been successfully passed on Active Directory then click on Install.

21- When the installation completes, you’ll be prompted that your machine is successfully configured in Active Directory as a domain controller and can be rebooted automatically.

Watch our YouTube Video about how to setup Active Directory on Windows server 2019.

For more details click here

Install Additional Domain Controller Server 2019

In this guide, I will explain how to change the computer name in Windows Server 2019 by GUI. You can rename your windows computer from the instruction using WMIC Powershell. if you want to know how to install windows server 2019 click here

To change the pc name using Server Manager

1- Select the beginning button then click on the Server Manager

2- After opening Server Manager > on your left side select Local Server > under Properties and click on computer name.

3- System Properties will open and click on change.

4- Type-A name under the pc name and click on ok.

5- Click OK.

6- Click Close.

7- Click Restart Now.

8- To rename the pc using Computer Properties, right-click on this PC and choose properties.

9- Under Computer name, domain and workgroup settings and click on Change Settings.

10- PC System Properties window will open, click on the change button to rename Server name.

11- Under Computer Name, type the server name and click on ok.

12- Click ok to restart PC.

13- Click Close.

14- Click Restart Now.

Change computer name from the command prompt

15- Select Windows button, select Windows system, right click on command – prompt and then click Run as administrator.

16- Type hostname command to know the current computer name

17- You can rename your windows computer from WIN-MJFV43IQRP4 to SRV2019 we will use the below command.

netdom renamecomputer WIN-MJFV43IQRP4 /newname:SRV2019 /reboot 0

Press Y to reboot computer

18- After renaming successful you the computer is restarting.

For more information click here

In this blog, I will go through the steps installation Windows Server 2019 on a physical PC, Windows Server 2019 was released date October 2, 2018.

You can download Windows Server 2019 in ISO format from Microsoft Website, from Here

System requirements

Processor – 1.4 GHz 64-bit processor

RAM – 512 MB

Disk Space – 32 GB

Network – Gigabit (10/100/1000baseT) Ethernet adapter

Optical Storage – DVD drive (if you want to install the OS from DVD media)

Video – Super VGA (1024 x 768) or higher (optional)

Input Devices, Keyboard & mouse (optional) Internet – Broadband access (optional)

How to Install Windows Server 2019.

1- Insert the DVD or USB installation media, restart your PC and set boot option from computer bios to a DVD drive or USB.

Press any key else from CD or DVD……..

2- Windows Server 2019 setup > select language to put in > Time and currency format > keyboard or input method and click on next.

3- Click Install Now to start out the windows server 2019 installation.

4- Only two versions of the windows server 2019 are available, Standard and Datacenter

Select the server version you would like to put in and click on next.

5- Select I accept the license terms and click on next.

6- Upgrade option: > the previous version of windows server 2012 or 2016 to 2019. Select Custom option: Install Windows only (advanced)

7- Select partition where you would like to put in Windows or Create partition click new select size click apply and click on next.

8- Click OK.

9- Select the partition where you would like to put in Windows server 2019 and click on next.

10- The windows setup takes some minutes to repeat all the specified files then installs the Windows Server 2019.

11- After restarting several times create a password for the administrator and click on Finish.

12- Finally server is prepared to type your administrator password and press enter to login.

13- Windows Server 2019 Server Manager.

For more information click Here

In this blog, I will be able to migrate our existing Active Directory Domain Controller which is Windows Server 2012 (Server2012) to Windows Server 2016 (Server2016).

My active directory domain controller Server (xpertstec.local).

Additional Domain Controller Windows Server 2016.

How to Create an Additional Domain Controller (ADC) In Windows Server 2016 so, click here

1- After Restarting the Server2016. So, login as Domain Administrator.

2- Type the Netdom query fsmo command, to see which server has installed FSMO roles.

Now we’d like to Migrating FSMO (Flexible Single Master Operation) roles to Windows Server 2016 (Server2016).

Migrate Active Directory Server 2012 to Server 2016

3- On the Server2016, open Active Directory Users and Computers and right click domain xpertstec.local and then click on Operations Masters.

4- On the Operations Masters and select the RID tab and then choose the Change button.

5- Now click Yes.

6- The operations master role was successfully transferred so, click on ok.

7- Now you can verify that Operation master role now transferred to our new Server SRV2016.xpertstec.local

8- On the Operations Masters and select the PDC tab and then choose the change button.

9- Then click Yes.

10- The operations master role was successfully transferred and then click on ok.

11- Now you verify that the Operation master role now transferred to our new Server SRV2016.xpertstec.local

12- On the Operations Masters and select the Infrastructure tab and then choose the change button.

13- Then click Yes.

14- The operations master role was successfully transferred so, click on ok.

15- Verify that Operation master role now transferred to our new Server SRV2016.xpertstec.local

16- Open Server Manager and select the Tools tab and then click on Active Directory Domains and Trusts.

Change Active Directory Domain Controller

17- Right click Active Directory Domains and Trusts and then choose to change the active directory domain controller.

18- Select this Domain Controller or AD LDS Instance and click on the domain controller that you simply want to be the schema master role and then click on ok.

19- Right click Active Directory Domains and Trusts and then choose Operations Master.

20- Now select Change.

21- Click on YES.

22- The operations master was successfully transferred so click on ok.

23- Confirmed the domain naming operation master role and then click on Close.

24- Now we’d like to move our Schema Master role, so we’d like to register the schmmgmt.dll open prompt and then run the command below.

regsvr32 C:\Windows\System32\schmmgmt.dll

25- the method was completed successfully and then click on ok.

26- Open Microsoft Management Console and open prompt and type mmc and then hit enter.

27- Now click on File tab and then choose Add/Remove Snap-in

28- From the left side and under Available Snap-ins and select Active Directory Schema and then click Add and click on ok.

29- Right click Active Directory Schema and then choose Change Active Directory Domain Controller to migrate active directory

30- Select this Domain Controller or AD LDS Instance and click on the domain controller that you simply want to be the schema master role and then click on ok.

31- Click OK.

Change Schema Master Role

32- Within the console1 and right click Active Directory Schema (SRV2016.xpertstec.local) and then choose Operations Master.

33- Click Change.

34- Click on Yes.

35- Operations Master successfully transferred and then click on ok.

36- Now you can confirm your current schema master which is Server2016.

37- Now run the Netdom query fsmo command so, we will now see that our roles are transferred to our Windows Server 2016 Additional Domain Controller.

Remove the Server2012 from Global Catalog.

On Server2016 open Active Directory Sites and Services.

38- Expand your Sites and expand the Default-first-site-name and expand the Servers and then expand local domain Server2012 and right click NTDS Settings and then choose Properties.

39- Under the general tab uncheck Global Catalog and then click on ok.

Demote Active Directory Domain Controller using the instruction or step by step demote active directory domain in window server 2012.

Follow the below steps (40 to 49).

Uninstalling Active Directory Domain Services from Server2012.

Log in to Server2012 machine with domain administrator credentials.

40- Open Windows PowerShell with elevated privileges and then type the command.

Uninstall-ADDSDomainController -DemoteOperationMasterRole –RemoveApplicationPartition

41- Type your local administrator password and then press enter.

42- Type Y and then hit Enter.

43- The operation is going to be completed during a jiffy and therefore the server is going to be rebooted automatically

Upgrading Forest Functional Levels and Domain Functional Levels to Windows Server 2016.

44- Login to Windows Server 2016 domain controller and Open PowerShell type below command to vary domain functional level.

Set-ADDomainMode –identity yourdomain.com –DomainMode Windows2016Domain

The domain name is xpertstec.local

Set-ADDomainMode –identity xpertstec.local –DomainMode Windows2016Domain 

Press Enter

46- Login to Windows Server 2016 domain controller and then Open PowerShell type below command to vary forest functional local.

Set-ADForestMode –identity yourdomain.com –ForestMode Windows2016Forest 

The domain name is xpertstec.local

Set-ADForestMode –identity xpertstec.local –ForestMode Windows2016Forest 

Press Enter.

48- Now the final step is to confirm if domain and forest functional levels have really been changed. Execute command,

Get-ADDomain | fl Name, DomainMode

Get-ADForest | fl Name, ForestMode

49- Step by step remove the active directory domain in window server 2012. Open Server Manager and select Dashboard and select Manage and then select to Remove Roles and features.

50- Click Next.

51- Select a Server from the server pole and then click on next.

52- Now Uncheck DNS Server role.

53- Remove features that need the DNS server, select Remove Features.

54- Uncheck Active Directory Domain Services box.

55- Remove features that need Active Directory Domain Services, select Remove Features.

56- Select Demote this domain controller.

57- Active Directory Domain Services Configuration Wizard, click Next.

58- Check Proceed with removal and click on next.

59- Type the Active Directory domain controller password and click on next.

60- Remove Active Directory Domain Services from this computer. Select the Demote button.

61- Demoting Active Directory Domain Controller server 2012 ongoing.

62- After restarting server2012 please join it to the workgroup.

For more information click here