In this blog, I will solve active directory domain configuration error “Verification of prerequisites” for Domain Controller promotion failed…..
Verification of prerequisites
1- In the Server Manager dashboard and select the tools tab and then choose Computer Management.
2- Under the Computer management expands Local Users and Groups. So select Users and right click on the administrator account and then select Set Password.
3- So click on Proceed.
4- Then type the administrator account password and click ok and ok.
5- Now open the windows PowerShell
Type cd\ press enter
and then type net user administrator /passwordreq:yes and hit enter.
The command completed successfully.
6- Now click on Rerun perquisites check.
7- All prerequisite checks passed successfully and click Install.
Active Directory Migration – In this blog, we’ll move the roles on our Server2008 (Windows Server 2008 R2 SP1) AD server to Server2019 (new Windows Server 2019 Standard).
Before proceeding to migrate an Active Directory from Windows Server 2008 R2 to Windows Server 2019, you want to first install Windows Server 2019 on a replacement machine which can then be promoted to Active Directory Server 2019.
The next step is to configure the IP and the DNS Addresses on the new server.
Windows Server 2008
R2
Windows Server 2019
Computer Name: Server2008 Server2019
Domain Name:
xpertstec.local
IP Address (Static): 10.0.0.20
10.0.0.22
Subnet Mask:
255.255.255.0 255.255.255.0
Default Gateway: 10.0.0.1 10.0.0.1
Preferred DNS Server: 10.0.0.20 10.0.0.20
Active Directory Migration 2008
1- First, let’s have a glance at my environment. we have a domain controller xpertstec.local which is installed on Windows Server 2008 R2.
Raise the Forest Functional Levels and Domain Functional Levels in Windows Server 2008 R2.
2- Click Start and select Administrative Tools and then Active Directory Domains and Trusts.
3- Right click on Active Directory Domains and Trusts and choose Raise Forest Functional Level.
4- Select an available forest functional level “Windows Server 2008 R2 and click Raise.
5- Now click on OK.
6- The forest functional level was raised successfully so click on ok.
Now Raising the Function Level of the Domain
7- Right click on the Domain name (xpertstec.local) and click Raise Domain Functional Level.
8- It has already got raised the Domain Functional Level to Windows Server 2008 R2 so click on close.
9- Now type the Netdom query fsmo command to check which server has installed FSMO roles.
10- DNS Manager.
Active Directory Migration Steps
Join Windows Server 2019 to an Active Directory Domain.
How to Join Windows Server 2019 to an Active Directory Domain, Click here
Now sign in Windows Server 2019 with the domain administrator account.
Create Additional Domain Controller (ADC) In Windows Server 2019
How to Create Additional Domain Controller (ADC) In Windows Server 2019 so Click here
11- Now have a look at my active directory Domain Controllers Server2008. We can now see that our server Server2019 is in the domain role.
Transferring the Flexible Single
Master Operations (FSMO) Role
I have a Windows Server 2008 Domain Controller (server2008) and have a further Windows Server 2019 domain controller (Server2019). To finish the migration. We’d like to transfer 5 FSMO roles to the new domain controller.
Schema Master
Domain Naming Master
PDC
RID pool manager
Infrastructure Master
12- To find which server is currently holding FSMO then run the following command. netdom query fsmo
The FSMO roles are currently with the Windows Server 2008 R2 Active Directory domain controller (server2008)
Using Active Directory Schema snap-in to transfer the Schema Master role 13- Open Command Prompt in administrative mode and type regsvr32 schmmgmt.dll and then click on ok.
Operations Master Roles Tranfer
14- On the Server2019 server, open Active Directory Users and Computers, right click domain xpertstec.local and then click Operations Masters.
15- On the Operations Masters, Select the RID tab and select the Change button.
16- Now click Yes.
17- The operations master role was successfully transferred so click ok.
18- Now you can verify that Operation master now transferred to our new Server Server2019.xpertstec.local
19- On the Operations Masters, select the PDC tab and then click the change button.
20- Now click Yes.
21- The operations master role was successfully transferred, then click ok.
22- Now you can verify that Operation master now transferred to our new Server Server2019.xpertstec.local
23- On the Operations Masters, select the Infrastructure tab and click on change button.
24- Then click Yes.
25- The operations master role was successfully transferred, then click ok.
26- Now you can verify that Operation master now transferred to our new Server Server2019.xpertstec.local
27- Open Server Manager and select Tools and then click Active Directory Domains and Trusts.
28- Right click on Active Directory Domains and Trusts and then select change active directory domain controller.
29- Select this Domain Controller or AD LDS Instance and click on the domain controller that you want to be the schema master role and then click ok.
Transfer Domain Master Role
30- Right click Active Directory Domains and Trusts and then select Operations Master.
31- Now click on Change
32- then click Yes.
33- The operations master was successfully transferred then click ok.
34- Confirmed the domain naming operation master role and click on Close.
35- Now we need to move our Schema Master role, so we need to register the schmmgmt.dll open command prompt and run the command below.
Regsvr32.exe C: \ windows \ system32 \ schmmgmt.dll
The process was completed successfully so click on ok.
36- Open Microsoft Management Console mmc type mmc and then hit enter.
Console
37- Select the File tab and then select Add/Remove Snap-in.
38- From the left side, under Available Snap-ins, Select Active Directory Schema, click Add button and then click ok.
39- Right click Active Directory Schema, and then select Change Active Directory Domain Controller.
40- Select this Domain Controller or AD LDS Instance, click on the domain controller that you want to be the schema master role and then click on ok.
41- Now click OK.
42- In the console1, right click Active Directory Schema (Server2019.xpertstec.local) and then select Operations Master.
43- Select the Change button.
44- then click Yes.
45- The active directory schema Operations Master successfully transferred then click ok.
46- Now confirm your current schema master which is Server2019 and then click Close.
47- Now run the Netdom query fsmo command, so we can now see that our roles have been moved to our Windows Server 2019 Additional Domain Controller.
48- Now change the DNS address of our additional Domain Controller server to be the IP address of our Windows Server 2019 Domain Controller server.
After completing Active Directory Migration, Now the ultimate step is to get rid of (uninstalling) server2008 Active Directory domain controller.
Remove Active Directory Domain Controller 2008
49- Open command prompt Type dcpromo and then hit Enter.
50- Click Next.
51- The Active Directory domain controller has the global catalog service, make sure your primary DC also has the service enabled and click on ok.
52- Confirmed that the delete this domain, because this server is the last domain controller in the domain, is UNCHECKED and then click next.
53- Type a password for the new Administrator account on this server and click next.
54- Review the remove active directory domain services Summary and click Next.
55- Check the Reboot on completion box to restart the server after the service has been removed
56- After rebooting server2008 DC. Now log in with the local administrator account and then open Server Manager.
57- In Server Manager click Roles under Roles Summary and click Remove Roles.
This blog, we will configure a basic 2-node cluster (Share Quorum Failover Cluster Configuring), where we have two servers (SRV2019-1 and SRV2019-2) running Windows Server 2019 and a Windows Server 2019 Domain controller (SRV2019-DC). It also assumes that SRV2019-1 and SRV2019-2 will communicate with each other over two network connections; I have labeled Primary and Cluster.
Add the Failover Clustering feature on both of the servers you need to add to the cluster.
Open the Server Manager Dashboard and choose Add roles and features.
1- User the Following PowerShell command to enable failover clustering and management Toole Node1 (SRV2019-1)
11- Failover cluster installation completed and then click Close.
After enabling the Failover Cluster on both servers (SRV2019-1 and SRV2019-2), on your SRV2019-1
Share Quorum Failover Cluster Validate Configuring
12- Open server manager, select tools and then select Failover Cluster Manager.
13- After opening Failover Cluster Manager under the action menu click on Validate Configuration.
14- Validate a Configuration Wizard open and then click next.
15- Select Servers or Cluster options and click the Browse button.
16- Select the servers you want to cluster so, in my setup I selected (SRV2019-1 and SRV2019-2).
17- After selecting Servers, click on next.
18- Select Run all tests (recommended) and then click next.
19- Cluster validate confirmation so click next.
20- Now default Running Process.
21- Summary options, so click View Report.
22- Click close and then click Finish.
Failover Cluster Configuration
23- Once Validation completed, Select Create Cluster.
24- Click Next.
25- Click the Browse button.
26- Type both node names and click check names and then click ok.
27- After selecting nodes so click next.
28- Type your cluster name in the cluster name box (XTCLUSTER) and pick an IP address that will be associated with this name in DNS. This name is to manage your cluster Once you create this access point a new computer object will be created in AD with this name and a DNS A record will be created with this name and IP address and click next.
29- On the confirmation screen you’ll see the name of the cluster and two nodes and IP address you chose and uncheck Add all eligible storage to the cluster and then click on next.
30- You have successfully completed the create cluster wizard, now click View Report to check out any warnings.
31- There may be some warnings. In my case, the warnings are probably related to 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 (Share Quorum Failover Cluster Configuring) 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 SRV2019-DC and provides XTCLUSTER read/write access thereto.
Share Disk Configuration
32- Open server manager in SRV2019-DC, Left side select file and storage services and select shares under volume click tasks and then click New Share.
33- Select share profile (SMB share quick) and then click next.
34- Share Location, select by volume and then click Next.
35- Type a share name, share descriptions and then click next.
36- Under other settings, uncheck Allow caching of share and click Next.
37- In Permissions options select customize permissions.
38- Advanced Security Settings for FSW, click Add button.
39- Click on select a principal.
40- Select Object Types.
41- Check Computers under object types and click next.
42- Type your cluster name in my case (XTCLUSTER) click check names and click ok.
43- Under Basic permissions, check Modify box and click ok.
44- Select the Share tab and click the Add button.
45- Click Select a principal.
46- Select Object Types.
47- Check the computers box and click ok.
48- Type your Cluster name, click check names and click ok.
49- Under Permissions, check change and click ok
50- Click Apply and click ok.
51- Click Next.
52- Read the confirmation summary and click Create.
53- The share was successfully created, click Close.
54- Now the file share created on SRV2019-DC, Go back to your SRV2019-1 right-click XTCLUSTER.xpertstec.local and Select More Actions and select configure cluster quorum settings.
Configure Cluster Quorum Settings
55- Configure Cluster Quorum Wizard windows will pop up, click next.
56- Select the quorum witness option and click on next.
57- Select configure a file share witness options and click on next.
58- Click the Browse button.
59- Type FWS name and click the Browse button.
60- Type quorum shared server name, click check names, click ok and ok again.
61- Click Next.
62- Click Next.
63- Review the cluster summary and click Finish.
64- Now Current Host Server Node1 is SRV2019-1.
65- After testing Current Host Server Node2 is SRV2019-2.
High availability is one of the main key points to supply continued services. In lately, everyone wants the specified services on-demand. Organizations use different technologies and solutions to supply high availability and redundancy. Network Load Balancing (NLB) is one of the foremost popular high availability and redundancy features utilized in Windows Server 2019 based networks.
Setup Details.
SRV2019-DC
IP Address: 10.0.0.20
SRV2019-1
NLB
Node1
IP Address: 10.0.0.30
SRV2019-2
NLB
Node2
IP Address: 10.0.0.40
NLB IP Address 10.0.0.100
Installing the Network Load Balancing Feature on NLB nodes (SRV2019-1, SRV2019-2)
1- Install using power shell command or follow the below steps to enable NLB.
3- On SRV2019-1 Open server manager and then select Add roles and features.
4- Then click Next
5- Click Next.
6- Select SRV2019-1 from the server pool and then click Next.
7- Check the WEB Server (IIS) roles box.
8- Click Add feature.
9- After selecting the Web Server (IIS) server role so click next.
10- Check the Network Load Balancing box.
11- Click Add features.
12- After selecting the Network Load Balancing feature so click next.
13- Click Next.
14- Click Next.
15- Click Install.
Configuring Network Load Balancing in Windows Server 2019 After installing the Network Load Balancing feature on all the participating NLB nodes, the subsequent step is to configure Network Load Balancing. For this, you would like to perform the subsequent steps.
Create a New Cluster
16- On the Server Manager console of the SRV2019-1 NLB node, click Tools and then choose Network Load Balancing Manager.
17- Right-click Network Load Balancing Clustering and then choose New Cluster.
18- On the New Cluster: Connect panel, type SRV2019-1.xpertstec.local (or IP Address) in the Host field then click Connect. Verify that the Interface name is listed then click next.
19- On the New Cluster, set the priority (unique host identifier) value 1. This NLB node will reply to the clients’ queries, first, also ensure that the default status has set as Started and click next.
20- Click the Add button to add a new Cluster IP address.
Note: The Cluster IP address is that the new virtual IP address on which the host service, during this case, IIS will run.
21- Type Cluster IP Address such as 10.0.0.100 and click ok.
22- Then click Next.
23- Select a cluster operation mode, Unicast and then click next.
24- So click Finish.
25- Wait until the SRV2019-1 NLB node is added successfully. The Icon Color of the added NLB node should be green.
Network Load Balancing add the host to a cluster
26- Right-click on Cluster name and then select Add Host to Cluster.
27- Connect dialog box, type SRV2019-2, and then click Connect to add one more NLB node.
Important: If you get the Host unreachable error while connecting SRV2019-2 as the NLB node, move on to SRV2019-2 and open the Network Load Balancing Manager console. Repeat the same steps as you used to add the DC1 NLB node.
28- On the Add Host to Cluster: Host Parameters dialog box, set the priority value as 2 and proceed to next.
29- Click Finish.
30- Finally, verify that the second NLB node SRV2019-1 is added successfully.
Configuring Default Website to Test the
NLB Configuration
To test the NLB cluster, use an NLB-Aware application like the IIS service role with the Cluster IP address. Hence, we’ll use the Default Website on NLB node1 (SRV2019-1) and NLB node2 (SRV2019-2). the web site is going to be mapped with the cluster IP address “10.0.0.100”. To do so, first, you would like to perform the subsequent steps on SRV2019-1 (NLB node1).
31-Open
the Internet Information Services (IIS) Manager console.
Expand the Sites node, select and right-click the Default internet site.
Select Add the Virtual Directory
32- In the Alias box, type a name. In the Physical path box, type \\SRV2019-1\C$\Intetpub\wwwroot\ and click ok.
We need to add the same shared directory on both the NLB nodes so the same content can be displayed when an NLB node from the configured NLB cluster is failed.
33- Double-click Directory Browsing.
34- Click Enable.
35- Right-click Default Web Site, select Manage Website and then select Restart.
36- Close the web Information Services (IIS) Manager window.
Repeat the same steps to activate the Default Website on SRV2019-2 NLB node.
Optionally, if you would like to access the web site through the hostname like www.xpertstec.local, add the www DNS host record with the ten .0.0.100 IP address.
Verifying Network Load Balancing Configuration
To verify that your NLB Cluster is configured successfully and functioning properly, perform the subsequent steps.
37- Type 10.0.0.100 within the Internet Explorer and verify that you simply are ready to access the Default Webs
Close Internet Explorer. On the SRV2019-1 node.
38- open the Network Load Balancing Manager window, select and right-click SRV2019-1(Ethernet), select Control Host and then select Stop to stop this node temporarily.
39- Switch back to SRV2019-DC and try again to open the Default Website. the Default Website should still be displayed. However, this time, the SRV2019-2 NLB node will serve the Website.
In this blog, we’ll learn the skill to make a Microsoft Windows Failover Cluster with Windows Server 2019. The environment may be a two-node cluster with one shared disk.
Environment details:
SRV2019-DC
10.0.0.20
SRV2019-1
Primary – 10.0.0.30
Cluster – 192.168.0.10
SRV2019-2
Primary : 10.0.0.40
Cluster: 192.168.0.20
iSCSI Storage : 10.0.0.100
Cluster Name – XTCLUSTER
Cluster IP Address – 10.0.0.110
1- Before we start, make sure you meet the following prerequisites: I have 2 Windows Server 2019 machines with the latest updates installed. The machines have at least two network interfaces, I rename them Primary and Cluster.
Join both servers to your Microsoft Active Directory domain and confirm that both servers see the shared memory device available in disk management. So, don’t bring the disk online yet.
2- User the Following PowerShell command to enable failover clustering and management Toole 1 Node (SRV2019-1)
Before we create the cluster, we’d like to form sure that everything is about up properly.
26- In Server Manager click Tools and Click Failover Cluster Manager.
27- Under Action menu click Validate Configuration.
28- Click Next.
29- Select the browse button.
30- Type both the Nodes name, click check name and click ok.
31- After Selecting the two-node servers for validation, click next.
32- Select Run all tests (recommended) and click next.
33- Review the validate configuration confirmation and click next.
34- Cluster validation testing is in progress.
35- After you make sure that every applicable test passed with the status successful. If you have any errors or warnings, you can use the detailed report by clicking on View Report and click Finish.
Create a Failover Cluster Server 2019
36- Under Action Menu so, select Create Cluster.
37- Click Next.
38- Click the browse button.
39- Type both the node names, click check names and click ok.
40- Both the servers nodes selected, click next.
41- Type a Cluster name, select the IP address and click next.
42- As a last step, confirm everything, click next and wait for the cluster to be created.
43- Cluster setup successfully completed and click Finish.
44- The wizard will add the shared disk automatically to the cluster per default. If you did not configure it yet, then it is also possible afterward. As a result, you can see a new Active Directory computer object named XTCLUSTER.
45- You can ping the new computer to check whether it is online (if you allow ping on the Windows firewall).
As an alternative, you’ll create the cluster also with PowerShell. the subsequent command also will add all eligible storage automatically:
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 ClickHere
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).
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.
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-Ashare 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.
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.
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
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.
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.
