In the previous article, we described how to create a child domain using the Server Manager console. In this article, we will show you how to do the same thing using Windows PowerShell. PowerShell is a powerful tool that can be used to automate many tasks in Windows Server. It is also a great way to create child domains, as it can save you time and effort.

To install AD DS and create a forest, you can follow the instructions in the article “Install Active Directory On Windows Server 2022 Using PowerShell“.

Steps to Create a Child Domain Using PowerShell

The creation and configuration of a child domain is part of the post-installation process of Active Directory Domain Services (AD DS). This process also includes promoting the server to a domain controller. First, the AD DS role must be added to the server. Once the role is added, you can create and add a child domain to the parent domain.

Add AD DS Role Using Windows PowerShell

Follow the steps below to add the Active Directory Domain Services (AD DS).

1. Open Windows PowerShell as administrator.
   • If you are working with Windows Server Desktop Experience, right-click on Windows PowerShell in the Start Menu and select Run as Administrator.
   • If you are working with Windows Server core, run powershell the command in the command prompt. It opens PowerShell. Once the PowerShell is opened, use Start-Process PowerShell -Verb runAs to open it as administrator.

2. Before installing the AD DS role, let’s first see if it is available. To do so, run Get-WindowsFeature AD-Domain-Services. As shown in the below command, it is not already installed and it is available.

3. To install the AD DS role, run the Install-WindowsFeature AD-Domain-Services -IncludeManagementTools command. Wait for a moment until it finishes the installation, and it will show the result as shown in the picture below.

The Active Directory Domain Service role is by now added to our Server. You can verify it using the Get-Windows-Feature AD-Domain-Services command. If it is properly installed, It will not be available for installation anymore. Now, in the second section, let’s go through the steps to creating and configuring a Child Domain using Windows Powershell in Server 2022.

Create a Child Domain Using Windows PowerShell

Now that we have the AD DS role added, we can create and configure a Child Domain using PowerShell in the AD DS post-installation process. Below are the steps.

1. Import AD DS module. To do so, run the Import-Module ADDSDeployment command.

2. Provide the credential to specify the user name and password of an admin used to accomplish this configuration. Use it only if you are not logged in with administrative privilege. To do so, use the Get-credential cmdlet and fill the pop-up window with an administrator’s username and password.

3. To create a Child Domain, use the Install-ADDSDomain cmdlet followed by the following mandatory arguments and their values.
   • -DomainType followed by the “ChildDomain” value.
   • -NewDomainName followed by the single-labeled (left-most part of a domain) child domain name which is “ca” in our example.
   • –ParentDomainName followed by the Fully Qualified Domain Name (FQDN) of the parent which is “technig.lab” in our example.

Note: the above arguments are the mandatory arguments that we must specify when we create a Child Domain. For more optional parameters click HERE.

So, considering the cmdlet and the required arguments, our whole line of code becomes: Install-ADDSDomain -DomainType ChildDomain -NewDomainName ca -ParentDomainName technig.lab

4. Now, it prompts us to specify the safe mode administrator password. Enter the password and confirm it. Then, type down Y and press enter. Wait for a while until it finishes the Child Domain installation and configuration process. Once the process completes, it will restart the machine.

Once the machine restarts, the Child Domain is created on it. To this end, we are all done with the child domain configuration.

Steps on how to create a child domain in Server 2022 using PowerShell:

1. Open PowerShell as an administrator.
2. Run the following command to install the ADDSDeployment module:

Install-Module ADDSDeployment

3. Create a variable to store the parent domain name and the child domain name. For example:

$parentDomainName = "technig.com"
$childDomainName = "lab.technig.com"

4. Run the following command to create the child domain:

Install-ADDSDomain -NewDomainName $childDomainName -ParentDomainName $parentDomainName

5. Enter the SafeModeAdministratorPassword when prompted.
6. The child domain will be created.

Here is an explanation of the command:

• Install-ADDSDomain is the PowerShell cmdlet that creates an Active Directory domain.
• -NewDomainName specifies the name of the child domain.
• -ParentDomainName specifies the name of the parent domain.
• -SafeModeAdministratorPassword specifies the password for the Directory Services Restore Mode (DSRM).

Here are some additional details that might be helpful for a beginner:

• The child domain name must be a single-label domain name.
• The child domain name must not already exist.
• The parent domain name must be a valid domain name.
• The SafeModeAdministratorPassword must be a strong password.

Summary

In this article, we installed the Active Directory Domain Services (AD DS) role on a Windows Server 2022 server using PowerShell. We then created a child domain using PowerShell cmdlets. The steps involved in creating a child domain using PowerShell are as follows:

• Install the ADDSDeployment module.
• Create variables to store the parent domain name and the child domain name.
• Run the Install-ADDSDomain cmdlet to create the child domain.
• Enter the SafeModeAdministratorPassword when prompted.

I hope you found this article helpful. Please share your thoughts and queries in the comment section below.

The post Create a Child Domain in Server 2022 Using PowerShell appeared first on TECHNIG.

As part of our DNS server guides, this article covers how to change the DNS zone settings in Windows Server 2022 after creating and configuring DNS zones. It is a vitally important and often required skill to know how to modify DNS zone configuration. Among other configurations, the three most often required settings that we need to change are the DNS zone type, ADI zone replication scope, and DNS zone dynamic updates. Hence, with a step-by-step approach, we will cover these three topics throughout this article, each in a separate section.

Related articles:

1. How to Install DNS In Server 2022 Using Server Manager And Powershell?
2. Configure DNS Forwarder And DNS Conditional Forwarder In Server 2022.
3. Detailed step-by-step DNS zone configuration.

How to Change a DNS Zone Type?

The DNS zone type definition is the very key setting when we create and configure a DNS zone. It specifies the zone’s function and further configurations options accordingly. It is also possible to change the zone type of a specific zone after it is created and configured. As part of changing DNS zone settings, we can change it anytime we need to in Windows Server 2022 using the below simple steps.

1. Press the Windows Key + R Keys on your keyboard to open the Run dialogue box.

2. Type indnsmgmt.mscand press Enter, consequently.

3. On the DNS Manager console, right-click on the zone you want to change the setting and click on the Properties option from the list.

4. Select the General tab in the zone Properties and click on the Change button associated with the Zone Type, as shown in the below picture.

5. On the Change Zone Type window, choose the new zone type from the available zone types. When it is all set, click on the OK button. Then, click on the Yes button on the warning window.

That is all about how to change a DNS zone type. Straightforward! Now, let’s go with how we can change the replication scope for an Active Directory Integrated (ADI) DNS zone.

How to Change an ADI Zone Replication Scope?

If you already know the difference between the DNS zone types, you know that the replication scope setting is associated only with an Active Directory DNS zone. Similar to the above section, we can change the replication scope of an ADI zone from the Properties window of the zone. Let’s go with the steps.

1. Open DNS Manager console (steps 1 and 2 of the above section)

2. Right-click on the zone you want to change its replication scope and click on the Properties option. (step 3 of the above section)

3. Select the General tab and click on the Change button next to the Replication, as shown in the below picture. This option is available only in the ADI zone and not in other zone types.

4. Now, on the Change Zone Replication Scope window, choose the replication scope for your ADI zone. Once set, click on OK.

With four simple steps, we changed the ADI DNS zone’s replication scope in Windows Server 2022.

How to Change a DNS Zone Dynamic Update?

Before straightly going to the steps to change the dynamic update of the DNS zone, it is necessary to know that this setting is available only with the primary and ADI zones and not with the Secondary and Stub zones. Similar to the above two sections, we can modify this setting in the Properties window of the zone. Let’s walk through all the steps.

1. Open up the DNS Manager console as described in the above sections.

2. On the DNS Manager console, right-click on the zone you want to change its dynamic updates settings and click on the Properties option. ( step 3 of the first section)

3. On the General tab of the zone properties, expand the options associated with the Dynamic updates and select the appropriate option (see the picture below). Once selected, click on OK to save the setting and exit the window.

That is all we need to do to change the Dynamic Update settings of a DNS zone.

Conclusion

So far, in this step-by-step article, we have covered the three most required settings of a DNS zone in Windows Server 2022. We discussed the steps to change a DNS zone type first. Then, we went through the guide to change the replication scope setting of an ADI zone. Finally, we covered the instructions to modify the dynamic update for the Primary and ADI DNS zones.

In the end, I hope this article could provide you with helpful instructions and insights. Please feel free to share your thoughts and further questions in the comment section below.

The post How to change DNS zone settings in Windows Server 2022? appeared first on TECHNIG.

In a domain-joined networked environment, we always need to restrict users’ access to most PC settings and resources. It is necessary to do so for security and safety reasons. One crucial restriction that we always need to apply is to deny users access to PC Settings and Control Panel. And that is what this article is about. More specifically, this article covers the detailed steps to preventing users’ access to the Control Panel and PC Settings using Group Policy on Windows Server 2022.

In our example, our domain controller machine runs Windows Server 2022, on which we create the group policy. We create an Organization Unit (OU) level group policy directly on the (OU) that contains the users to which we apply the policy.

You may also like to read Install Active Directory On Windows Server 2022 Using PowerShell.

Steps to Deny Access to PC Settings and Control Panel

As we described in the scenario earlier, we create the policy that is linked to an OU, which contains the users to which we apply the restriction. We can create the group policy first and link that to the OU, or we can create the group policy directly on the OU. Either way ends up with the same result. However, we go with the second approach in our example. That being said, let’s go with the steps.

1. Press down the Windows key + R keys on your keyboard to open the Run dialogue box.
2. Type in gpmc.msc and press Enter to open the Group Policy Management console.

3. Right-click on the OU to which you want to associate the group policy. Then, select Create a GPO in this domain,… option.

4. Put a name for the Group Policy Object (GPO) in the relevant box, and click OK.

5. Once the GPO is created, right-click on it, and select Edit from the context menu.

6. On the Group Policy Management Editor window, expand Policies under User Configuration. Then, expand the Administrative Template and click on Control Panel. Finally, double-click on Prohibit access to Control Panel and PC settings.

7. On the configuration window, check the Enabled option. Then, click OK, and close the Group Policy Management Editor window.

To this end, we have created the group policy to prevent users’ access to the Control Panel and PC settings. We created it directly linked to the OU that contains user accounts that we want to restrict. So, it is all done. To verify it, go with the next section.

Verifying the Above Group Policy Configuration

To check the above restriction, we need to log in with a user account that is a member of the OU to which we linked the group policy. Then, we update the group policy and try to open the Control Panel and PC Settings. See the below steps.

1. Login to the client’s computer with a user account that is a member of the OU to which you linked the restriction.
2. Run gpupdate /force in the Run dialog box to perform group policy updates. Wait for a while until the group policy completes.

3. Once the group policy gets updated, try to open the Control Panel or PC Settings. It doesn’t open, and you will face the pop-up window shown in the below pic.

That is all we need to do to check how the restriction we configured works and if it is applied correctly.

Conclusion

It is a common setting in a domain environment to deny users access to the Control Panel and PC settings. It is essential for security and safety reasons. As the steps discussed above, we can apply this restriction simply by defining and configuring a group policy object to an OU that contains the target users.

In the end, I hope you found this article helpful. Do not hesitate to share your thoughts and queries in the comment section.

The post Deny Users Access to PC Settings and Control Panel using Group Policy appeared first on TECHNIG.

System admins have the ability to prevent/block users’ access to all removable storage media drives. Such restrictions play an important role in the security and safety of a networked environment. And they are very common and most often used inside almost all organizations. Additionally, the tool that helps us create such restrictions is the Group Policy Management Console (GPMC). It is a feature that we add along with the AD DS role installation. That all being said, this article covers a step-by-step guide to preventing domain-joined users’ access to removable storage media drives using group policy in Windows Server 2022.

In our example, the domain controller machine runs Windows Server 2022 Standard. Additionally, we define the group policy directly on an Organizational Unit (OU) that contains the target users. So, we have already created an OU and moved the target user(s) into it.

You may also like to read DNS Server Guides and DHCP Server Articles.

Steps to Prevent Access to Removable Media

With the above scenario in mind, it is a straightforward process to prevent users’ access to removable media.

1. Press down the Windows Key + R on your keyboard. It opens the Run dialogue box.
2. Type in gpmc.msc and press the enter. It opens the Group Policy Management (GPM) console.

3. On the group policy management console, right-click on the OU that contains the target users. Then, select Create a GPO… from the context menu.

4. Type a name for the new GPO. Then, click OK to continue.

5. Right-click on the GPO that you created. Then, select Edit from the context menu.

6. On the GPM Editor window, expand User Configuration -> Administrative Templates -> System. Then, select the Removable Storage Access folder as shown in the below picture. Finally, double-click on All Removable Storage classes: Deny all access.

7. On the GPO configuration window, check the Enabled option. Then, click OK and close the GPM Editor window.

8. The GPO configuration is all set throughout the previous steps. However, it will affect only after we perform a group policy update on the client machine or restart it. So, to perform a group policy update, use gpupdate /force the Command Prompt or Run dialogue box.

9. Now, if you insert a removable media like a USB drive and try to open it, you will face an error saying the media is not accessible.

That is all with the steps to deny users access to removable storage media using group policy.

Conclusion

To conclude this article, first, we talked about the importance of restricting users’ access and discussed the Group Policy Management tool. Then, we briefly introduced our scenario. Lastly, we covered detailed steps to prevent users’ access to removable storage media.

In the end, as always, I hope you find this article helpful. And feel free to share your thoughts and queries in the comment section.

The post How to Prevent Access to Removable Storage Media Using Group Policy? appeared first on TECHNIG.

A child domain is a subdomain of another domain in a tree which we call the parent domain. In the active directory hierarchical structure, the subdomain segmentation helps partition the active directory into smaller segments. It is useful when we have a sub-business design and geographical differences. Put it another way, if, for example, company.com is a domain, we can create a subdomain CA.company.com for that larger domain. This subdomain has its own domain controller and administrative boundary for its users and computers. With this brief illustration in mind, this article aims to cover how to create a child domain in Windows Server 2022 with a step-by-step approach and visual illustration.

Steps to Create a Child Domain in Windows Server 2022

To create a child domain, we need to install the Active Directory Domain Services (AD DS) role on our Windows Server 2022 Machine. Then, following its post-installation task, we create a child domain in an existing domain. Thus, to keep the article simple and easy to understand, we will accomplish the abovementioned two processes in two separate sections. First, we will install the AD DS role in our Windows Server 2022. Then, we will go through the post-installation process and create our new child domain.

To install AD DS and create a forest using Windows PowerShell, read Install Active Directory On Windows Server 2022 Using PowerShell article.

Install AD DS role in Windows Server 2022

To install the AD DS role using Server Manager, follow the steps below.

1. Open the Server Manager from the Start Menu.
2. On the Server Manager console, click on Manage and select Add roles and features.

3. Click Next on the first window.
4. Choose the first option on the Installation Type window. Click Next afterward.

5. Select the server on which you install the AD DS and click Next.

6. Check out the Active Directory Domain Services checkbox on the Server Roles window. Then, click on Add Features button on the pop-up window. Finally, click on Next.

7. Let the Features window as its default, and click Next.
8. Likewise, click Next on the AD DS window.
9. On the Confirmation window, check out the Restart Server option, so it restarts the machine automatically if it needs to. Then click on the Install button. Wait for a few moments until it finishes the installation process.

10. In the last step, once the AD DS installation completes, click on the Close button to close the window.

To this point, we have installed the AD DS in our Windows Server 2022 Machine. Now, let’s move forward and go with the post-installation tasks and create our child domain.

Create a Child Domain in Windows Server 2022

Now that we have installed the AD DS role in our Windows Server 2022 machine, we can create a child domain in its post-installation task. Follow the steps below to do so.

1. On the Server Manager console, click on the flag notification. Then, click on Promote this server to a domain controller option.

2. On the Deployment Configuration window, check out the Add a new domain to an existing forest option. Select the Child Domain as illustrated in the below picture. Then, enter the parent domain name in the relevant box, or use the Select button to select from the existing domains. Finally, enter the Child Domain Name in its relevant textbox. The child domain name must be single-labeled. Use the Change button to change the credential if needed. Once everything is set, click on Next.

3. Set the Domain functional level and Global Catalog settings. Then, provide the DSRM password and click on Next.

4. Click Next on the DNS Options window.

5. Verify the NetBIOS name and click Next to continue.

6. Set the AD DS database and other files’ paths or leave it as its default. Click on Next afterward.

7. Read the details of your setting on the Review Options window. If everything is set correctly, click on Next to continue.

8. Click on Install on the Prerequisite Check window once it has passed the requirements. Wait for a moment until it finishes the installation task. It automatically restarts during the installation operation.

That is it! We have created our child domain throughout the above steps.

Conclusion

To sum up this article, we first explained briefly what a child domain is and where we use it. Then, we discussed the steps to install Active Directory Domain Services in Windows Server 2022. Finally, in a separate section, we promoted the server to a domain controller and created the child domain.

We are happy to be effective throughout our articles. Please do not hesitate to share your thoughts and questions in the comment section.

The post How to Create a Child Domain in Windows Server 2022 appeared first on TECHNIG.

As part of a DNS server configuration, it is also possible to create and configure an internal root DNS zone for an environment. When we create it manually, the DNS forwarders and DNS Root Hints that resolve external DNS queries automatically get disabled. That is how we can stop external name resolutions by using an internal root zone. Once we have created a root zone, it acts as a parent zone for all the root zones. Having said this overview, this article covers how to create and configure a Root DNS Zone in a step-by-step approach. We use Windows Server 2022 for this configuration. However, the instruction also applies to other versions of Windows Server OSes.

Other DNS articles:

1. How to Install DNS Service Using PowerShell and Server Manager?
2. Configure DNS Forwarder and DNS Conditional Forwarder.
3. Detailed Instruction to Create and Configure DNS Zones.

Steps to Create and Configure a Root DNS Zone

With the above brief overview in mind, let’s get our hands dirty and go through the steps to create and configure a root DNS zone in Windows Server 2022.

1. Press down the Windows key + R keys on your keyboard to open the Run dialogue box.

2. Type indnsmgmt.msc command and press enter.

3. Expand the server name on the DNS Manager console. Then, right-click on the Forward Lookup Zone and select the New Zone option. Click Next on the Welcome Wizard afterward.

4. On the Zone Type section, select the zone type for your new zone and click Next. In our example, we chose the Primary zone for which we check the first option and uncheck the last option.

5. Put only a dot (.) in the Zone name box and click Next to continue.

6. On the Zone File section, specify a name for the zone file or leave it as its default. Then, click on the Next button.

7. Select the appropriate Dynamic Update option for your root DNS zone and click on Next. On the next page, click on the Finish button.

That is it! Following the above seven steps, we can create a root DNS zone in Windows Server 2022. Now, you can see the new zone with “.(root)” name is added to the zone list.

As we have added the root zone, the root hints and forwarders are all gone if you check them. So, this way, the root DNS zone stops all external name resolutions.

Summary

To summarize what we discussed in this article, we first covered a brief overview of the Root DNS zone. We discussed its function and use. Then, we went through step-by-step instructions and practically created and configured a Root DNS zone in Windows Server 2022.

In the end, I hope this article can provide you with the exact answer to your question. Make sure to share your thoughts and further queries in the comment section.

The post Create and Configure a Root DNS Zone and Stop External Name Resolution appeared first on TECHNIG.

As a core component of a DNS Server, a DNS Zone creates and stores DNS resource records. That means the DNS zones store all the resource records of a DNS namespace in themselves, and according to those records, the DNS Server resolves names to IP addresses upon the DNS queries by clients. The DNS Servers manage the DNS zones. It is the very fundamental configuration we must accomplish right after installing the DNS Service. Hence, this article covers how to create and configure a DNS Zone in Windows Server 2022 step-by-step. Before that, we need a comprehensive understanding of the DNS Zone types and their functions. That’s why we will first cover a brief overview of the DNS zone types and their functions. Then, we will create and configure DNS zones of all types in a separate section.

You may also like to read: Install DNS In Server 2022 Using Server Manager And Powershell.

Forward Lookup Zone and Reverse Lookup Zone

Broadly classifying, there are two types of zones available in a DNS Server. The first one is the Forward Lookup Zone which resolves names and, sometimes, services to IP addresses. The second one is the Reverse Lookup Zone which resolves IP addresses to names. While we always use the first type in every networking environment, we rarely use the second type for some security reasons. Furthermore, we have four types of zones that we can create and configure in each one of these two zone classes. In fact, when we talk about zone configuration, we configure one of these four types, whether in the Forward Lookup Zone or the Reverse Lookup Zone. Wherever we create them, they function accordingly. Now, let’s see each of these four zone types we can create and configure.

1. Primary DNS Zone

As the name refers, the Primary DNS Zone is the main DNS zone that a primary DNS server hosts. It stores the read/write copy of the zone data (resource records). Let’s say we have a DNS Server for our main office with a thousand clients. Now, that DNS Server hosts a primary zone and stores the DNS records of all those thousand clients with both read and write privileges.

2. Secondary DNS Zone

The Secondary DNS Zone stores a read-only copy of the Primary DNS zone. It goes hand-in-hand with the primary zone. If a change occurs in the primary zone, that change replicates in the secondary zone. We can not delete or add a new resource record in a secondary DNS zone. We use it mainly to reduce the workload on the primary DNS server, prevent a single point of failure, and reduce other resource usages like network bandwidth in a scenario where the company’s branches are connected over a WAN link.

3. Stub DNS Zone

A Stub DNS Zone is very similar to a secondary DNS zone. But, it stores a copy of resource records of only the name servers (NS) of a primary zone and not all resource records of a primary zone. Like the primary-secondary zones, we use it to reduce loads on the primary DNS Server, prevent a single point of failure, and reduce other resource usage.

4. Active Directory Integrated (ADI) DNS Zone

An active directory Integrated zone, or ADI zone for short, can be hosted only on a DNS server which is also the Domain Controller. Using the ADI zone, all the resource records automatically replicate between the two DNS servers. It is entirely bidirectional and multi-master. That means any changes on one side replicate to the other side. This type is the most secure as the replications are encrypted.

Now that we have a conceptual understanding of each DNS zone type, we will go forward and practically configure each one in a separate section.

Create and Configure a Primary DNS Zone

From the above descriptions, we understand what a Primary DNS Zone is and where we use it. We will walk through the below steps to create and configure a primary DNS zone in Windows Server 2022.

1. Open the DNS Manager console. To do so, open the Run dialogue box by pressing the Windows Key + R keys combination on your keyboard. Typednsmgmt.msccommand and press enter to open it. You can also open it by navigating through Server Manager >> Tools >> DNS.

2. Under the Server name on the DNS Manager console, you can create a new zone of both Forward Lookup Zones and Reverse Lookup Zones. Whichever you intend to create, right-click on it and choose the New Zone option. Consequently, click on the Next button on the first screen.

3. To create a Primary Zone, check out the first option and uncheck the last checkbox. Then, click on Next.

4. On the Zone Name console, type your zone name and click on Next to continue.

5. Now, configure the zone file. Choose the first option to create a new zone file, and click on the Next. The DNS zone creates a file to save the associated resource records. This file will be saved in the C:\Windows\System32\dns directory.

6. In this step, configure the Dynamic Updates. For the Primary DNS Zone, we have two options, and almost always, we choose the first active option, as shown in the picture. If we select the Do not allow dynamic updates option, we must manually update the resource records each time there is a new record, which is impossible in most cases. When it is set, click on the Next button. Finally, click on Finish on the last page.

That is all with the Primary DNS zone configuration. However, we still need to configure zone transfer.

Configure Primary DNS Zone Transfer

We learned how to create and configure a new Primary DNS zone in Server 2022. But, we still need to configure the zone transfer for our newly created primary DNS zone. The zone transfer configuration specifies the server(s) with which our primary zone must replicate its information. Follow the steps below to configure Zone Transfer.

1. Right-click on your DNS Zone and select the Properties option from the list.

2. On the zone properties page, select the Name Servers tab and click on Add button.

3. On the New Name Server Record screen, type the name or IP address of the secondary server with which you want to replicate this zone’s resource records. Use the Resolve button to resolve it. Once you have added the secondary server(s), click on the OK button. Do not care about the warning sign with the resolved server(s). Finally, close the zone’s Properties window.

We are all done with the primary zone. We have created and configured it, and then we configured the zone transfer. It is all set and ready to resolve names and replicate its records with the secondary DNS zone on the Server(s) we have just added.

Create and Configure a Secondary DNS Zone

A secondary DNS zone, as we described earlier, is a read-only copy of the primary DNS zone that updates itself with a replication of the Primary DNS zone records associated with it. It is also very similar in terms of configuration steps. Anyway, let’s move on and go with those steps to create and configure a Secondary DNS zone in Server 2022.

1. Open the DNS Manager console on the secondary server (Same as the Primary DNS zone described above)

2. Create a new DNS zone (Same as the step 2 of the primary DNS zone described above)

3. Choose the Secondary Zone option as shown in the below picture to create a secondary DNS zone. Then, click on the Next button.

4. Name the Secondary DNS zone. Remember that it is mandatory that the Secondary DNS zone name must be the same as the Primary DNS zone with which you want to associate. That is what makes them correlate with each other. So our secondary DNS name becomes Zone1 as of the primary DNS zone. Click on Next when it is set.

5. Specify the Master DNS Server(s) using their IP addresses or names. Once specified correctly, click on the Next button. Finally, click on the Finish button on the next page.

At this point, we have successfully created and configured the secondary DNS zone. Now, let’s verify if they work correctly.

Verify Primary-Secondary DNS Zones

We already know the purpose of the primary and secondary DNS zones. So, it is clear that all the resource records from the primary DNS zone should automatically get stored in the secondary DNS zone. Besides learning how to create and configure a DNS Zone in Server 2022, we verify this replication of resources and check if it works.

To verify this configuration, first, we manually create a new record in the primary DNS zone on the DNS server that hosts it (DC1 in our scenario). Then, we check if it is replicated in the secondary DNS zone on the DNS server that hosts our secondary zone (SRV1 in our scenario). Let’s move on step by step.

1. On the primary DNS server (DC1 in our example), right-click on the primary zone you have created and choose New Host (A or AAAA) option from the list.

2. Put the name of the new record in the Name box, and put the IP address associated with that name in the IP address box. Then, click on the Add Host button. Next, click on the OK button on the message window. Finally, click on the Done button.

3. On the secondary DNS server (SRV1 in our example), click on the secondary zone and see if the record you have created in the primary zone is added there. Remember that it might take a few seconds to replicate. So, refresh the DNS manager window on the secondary server.

This way, we can manually add a DNS record in our primary zone and check if it replicates to the secondary zone.

Create and Configure a Stub DNS Zone

Earlier in this article, we discussed the Stub DNS zone. We know where we use it and what resource records it stores. Now in this section, we dive into the steps on how we can create and configure a Stub zone in Windows Server 2022. Most of the steps are similar to the secondary zone configuration we covered above. So, to keep it short, we will refer to the secondary zone configuration steps for similar ones.

1. Open DNS Manager console (same as the Step 1 of secondary zone configuration)

2. Create a new DNS zone (Same as the step 2 of the secondary zone configuration)

3. Choose the Stub zone option on the Zone Type window.

4. Enter the name of the Stub zone. (Same as step 4 of the secondary zone configuration)

5. Configure zone file. (Same as the step 5 of the Primary zone configuration discussed above)

6. Add the master server (primary server which hosts the primary zone) as we did for the secondary DNS zone.

We configured a Stub Zone following these six steps. It is straightforward and requires almost the same steps as the secondary zone configuration except for steps three and five, where we specify the zone type and configure the zone file.

Create and Configure an Active Directory Integrated (ADI) DNS Zone

We are familiar with the concept of Active Directory Integrated (ADI) DNS Zones, as we discussed earlier in this article. To remind you, the ADI zones can be hosted only on the DNS servers, which are also the domain controller. With that in mind, this section covers the steps on how to create and configure an ADI DNS zone in Windows Server 2022. Let’s walk through the steps. To keep it short, we will refer to some of the above section’s steps if there are similar steps to the above sections.

1. Pull up the DNS Manager console as we did in previous sections.

2. Create a new DNS zone. (step 2 of the above sections)

3. Select the Primary zone option and check out the last checkbox option for the ADI DNS zone. Click on Next afterward.

4. Select the replication scope for the ADI zone in which it must replicate its resource records. We always use one of the two first options. The first one is to replicate the zone to all servers in the forest, and the second option is to replicate it to all servers in the domain. It depends on your environment and the plan accordingly. When done, click on Next.

5. Type a name for your ADI DNS zone and click on Next to continue.

6. Configure the Secure Dynamic Update in this step. For the ADI DNS zone, the first option is also available. Almost always, we use the first option for an ADI zone. It also depends on your plan. Click on the Next button when it is set. Then, click on Finish in the next window.

That is all the steps we walk through to create and configure an ADI DNS zone in Windows Server 2022.

Summary

To revise what we covered in this article, we started with an overview of the DNZ zones. First of all, we discussed the Forward Lookup Zone and Reverse Lookup Zone. We covered a brief overview of the four zones we can create and configure in each Forward and Reverse Lookup Zones. Next, in a step-by-step approach, we covered the primary zone creation and configuration. Likewise, we stepped into secondary zone configuration steps. Another small topic we covered was verifying primary-secondary zones. A stub zone configuration was the next section we covered. Finally, we explained the ADI DNS Zone configuration in six steps.

In the end, I would like to share my happiness in having you read our articles. Please feel free and let us know your thoughts and queries regarding our content.

The post Create and Configure a DNS Zone in Windows Server 2022 appeared first on TECHNIG.

As essential parts of a DNS Server, the DNS Forwarders and the DNS Conditional Forwarders are the two topics that we will configure after installing the DNS role and configuring the DNS zones. A DNS Forwarder is responsible for serving external DNS requests. We manually configure the DNS Forwarder on our DNS Server and specify the DNS server(s) it should refer to for any external DNS requests. A DNS Conditional Forwarder resolves the external DNS requests only for a specific domain that we specify. Mainly, we configure it between partners and trusted organisations. With this brief introduction in mind, we will cover how to configure a DNS Forwarder and a DNS Conditional Forwarder in Windows Server 2022. We will cover each one in a separate section following a straightforward step-by-step approach.

Also, read Install DNS In Server 2022 Using Server Manager And Powershell.

Configure a DNS Forwarder in Server 2022

We discussed a brief overview of the DNS Forwarder. In this section, we will go step-by-step to see how we can configure it in a Windows Server 2022.

1. Pull up the DNS Manager console. To do so, press down the Windows Key + R keys on your keyboard. Then, typednsmgmt.mscin the Run dialogue box and hit enter. An alternative way is to navigate through Server Manager >>Tools >> DNS.

2. On the DNS Manager console, select the server name on the left pane and double-click on Forwarders at the right pane.

3. Select the Forwarders tab on the DNS server’s properties, and click on the Edit button, afterwards.

4. Now, add the IP address of the DNS server(s) to which you want to forward the DNS external requests. You can add many DNS servers. As of our example, we have added two Google public DNS servers (8.8.8.8 and 8.8.4.4). Click on a DNS server you have added, and you can set the order or delete it using the buttons on the right pane. Once everything is set, click on the OK button.

5. As you can see in the below picture, our two DNS servers are added to DNS Forwarders. Now our DNS server forwards any external DNS requests to one of these two DNS servers. Finally, Click on OK to close the window.

All right. In five simple steps with picture illustration, we have explained how to configure a DNS forwarder in Windows Server 2022.

Configure a DNS Conditional Forwarder in Server 2022

A Conditional Forwarder, as we discussed earlier, resolves the external DNS requests only for a specific domain. We define that external domain in our DNS server. Our DNS server then resolves the external DNS request only for that domain. It forwards any external DNS requests other than for that domain to the DNS server(s) defined in forwarders or to the DNS servers in the root hint. Having said this stuff, let’s move on and see the steps to configure a DNS Conditional Forwarder in Windows Server 2022.

1. Open up the DNS Manager console (step 1 of the previous section)

2. Expand the DNS server and right-click on Conditional Forwarders. Select the New Conditional Forwarder option from the list.

3. On the New Conditional Forwarder window, first, enter the domain’s name that your DNS server should resolve the request for it. Then, enter the IP address of that domain. Next, if you want to store this conditional forwarder in the active directory, check out the relevant checkbox (labelled 3 in the below picture) and choose the appropriate replication option. Otherwise, leave this option unchecked. Finally, click on the OK button.

These are all the steps required to configure a conditional forwarder on a DNS server with Windows Server 2022. Pretty easy!

Conclusion

Throughout this article, first, we discussed a brief overview of the DNS Forwarder and DNS Conditional Forwarder. Then, in two separate sections, we covered a step-by-step guide on how to configure a DNS Forwarder and DNS Conditional Forwarder in Windows Server 2022.

I hope you find this article helpful in any way. Make sure to share your thoughts and queries in the comment section below.

Read More:

• DHCP PowerShell Commands.
• How To See Wi-Fi Password On Windows 11?
• How To Bypass Windows 11 Requirements?

The post Configure DNS Forwarder and DNS Conditional Forwarder in Server 2022 appeared first on TECHNIG.

As a solution to DHCP failure, the DHCP Failover was first introduced in Windows Server 2012 for the high availability of DHCP service. The DHCP high availability is a super important topic in DHCP Server setup and configuration. If the DHCP server fails to lease IP addresses to the clients, the whole network fails. Among other solutions to this issue, DHCP Failover is preferred and the most used. The way it works is that we have two DHCP servers working together. If one fails, we have the second one that provides the service. This article covers a step-by-step guide on how to configure DHCP Failover in Windows Server 2022. Before that, it covers a brief overview of the DHCP Failover configuration modes. This overview is required to distinguish between DHCP Failover configuration modes and which one to choose.

Before this configuration, you need to have DHCP installed and configured. You also need to have a DHCP scope. For those two topics, read the below articles.

• Install And Configure DHCP In Windows Server 2022 Using Server Manager.
• Create And Configure A DHCP Scope In Windows Server 2022.
• Install And Configure DHCP In Windows Server 2022 Using PowerShell.

DHCP Failover Configuration Modes

As mentioned above, two DHCP servers are involved with the DHCP Failover configuration. They work together to make the DHCP service highly available. To define how they should work together, we have two options: the Load Balance mode and the Hot Standby mode. We must go for the one that best suits our needs in accordance with the environment.

1. Load Balance Mode

Using the Load Balance mode, both the DHCP servers concurrently lease IP addresses to the clients. Also referred to it as Active/Active. That means both DHCP servers are active at the same time. They share the DHCP scope with one another, and each one leases IP addresses to a specific number of clients in the network. The number of clients each should serve is defined manually in percentage while we configure DHCP Failover. What happens when one fails? The other one takes the responsibility and leases IP addresses to all the clients.

2. Hot Standby Mode

Using this mode, only one of the DHCP servers is leasing IP addresses to the clients at a time. The primary one leases IPs to the clients. The secondary one is in the Standby mode and updates itself with a replication of the records from the primary server. The secondary one steps in and serves the clients only when the primary server crashes for any reason. This mode is also referred to as Active/Passive. That means only one is active at a time.

Step by Step DHCP Failover Configuration in Server 2022

Now that we are familiar with the DHCP Failover configuration modes, it is time to dive into the steps and practically configure the DHCP Failover on our DHCP Server.

1. Open DHCP Manager console. To do so, open the Run dialogue box using Windows Key + R keys on your keyboard and run dhcpmgmt.msc. You may also access the DHCP console by navigating through Server Manager > Tools > DHCP.

2. On the DHCP console, right-click on IPv4 under your domain and choose Configure Failover option from the list.

3. Remove the check for the Select all check box, and select the DHCP scope(s) from the list. Then, click on Next to continue.

4. Now, choose the partner server using the Partner Server box and Add Server button. You can type the name or IP address of the partner server in the Partner Server box or browse for it using the Add Server button. Click on the Next button once set.

5. The last step is to specify the DHCP Failover mode. You can use one of the Load Balance, or Hot Standby modes discussed earlier. You can set the properties for each one here on this page. Remove the Check for Enable Message Authentication check box if you do not use this authentication. Or, set it if you use it. Then, click on Next. Click on Finish on the next window and close the window using the Close button.

That is all the steps we require to Configure DHCP Failover on Windows Server 2022. Just five easy steps to accomplish it. If you switch to the partner server and go to the DHCP console, you will notice the DHCP scope(s) from your primary DHCP Server are replicated into it. Let’s verify it in a separate section.

Verify DHCP Failover Configuration

To verify if the DHCP Failover configuration works correctly, we have to check the partner server and see if the DHCP scope(s) that we chose are replicated. We have two ways to access the partner server’s DHCP console. One is to go to that server and navigate all the way to the DHCP Manager console. The second way is to access it remotely from the DHCP console. Let’s access it remotely and verify our DHCP Failover configuration through the steps below.

1. On the DHCP console, right-click on DHCP at the top and select Add Server option.

2. On the Add Server screen, select the target DHCP Server to access it. If the target DHCP Server is not already in the list, use the first option and the Browse button to find it. When you added the target server, click on OK.

3. Now that the Partner DHCP Server is added to the console, expand it, and you can see that the scope(s) that you chose in the DHCP Failover configuration are replicated and are present in both the servers.

4. One more thing. If you right-click on the DHCP scope(s) configured in DHCP Failover, you will notice the options to Deconfigure Failover, Replicate Scope, and Replicate Relationship.

By observing the replicated scope(s) and deconfiguration options for Failover, we can verify that our DHCP Failover configuration is correctly configured.

Conclusion

In a step by step approach, we covered how to configure a DHCP Failover in Windows Server 2022. We started with an overview of DHCP Failover configuration modes’ concepts. Then, we walked through the steps to practically configure the DHCP Failover. Finally, we remotely accessed our partner DHCP Server and verified the DHCP Failover configuration on it.

As always, I hope this article could be helpful to you. And, if there is any further question and thoughts you might want to share, let us know in the comment section.

The post How to Configure DHCP Failover in Windows Server 2022? appeared first on TECHNIG.

Domain Name System or DNS for short is a fundamental service that resolves names/services to IP addresses and sometimes vice versa. It is a key service that must be running in every network. The very first configuration regarding this topic is installing its capability on the server. Then, there are bundles of configurations and settings to understand and care about. So, as a beginner article regarding DNS, this article covers how to install DNS in Windows Server 2022 using both Server Manager and PowerShell tools.

You may also like to read: Install And Configure DHCP In Windows Server 2022 Using PowerShell.

Install DNS Using Server Manager

Using Server Manager is a user-friendly and easy method to install roles, including DNS, in Windows Server Operating Systems. We just graphically navigate through the options and install it. The steps are listed below.

1. Open Server Manager console. It is present in the Start Menu by default. If it is not, search for it.

2. On the Server Manager console, click on Manage in the top-right corner. Then, select Add Roles and Features option.

3. On the Before You Being page, just click on Next to continue. Choose the Role-based or feature-based installation option on Installation Type. Then, click on the Next button.

4. On the Server Selection section, choose the server on which you want to install DNS and click on the Next button, afterwards.

5. In this step, check out the DNS Server checkbox option on the Server Roles section. Click on Add Features on the next window that pops up. Finally, click on Next.

6. Click on Next on both Features and DNS Server wizards. On the Confirmation window, check out the option for the Restart if it needs to during the DNS role installation. And, finally, click on the Install button. See the picture below.

7. Wait for a few moments until the DNS role installation completes. Once completed, click on the Close button in the Result section.

As simple as the above steps, we have installed the DNS Server in Windows Server 2022 using Server Manager. Now, if you open the Tools menu on the Server Manager console, you will observe the DNS is present there.

Install DNS using Windows PowerShell

Using Windows PowerShell is always a preferred and professional method of accomplishing such tasks. Besides other benefits, it takes us less time. Now, let’s dive into the brief steps to install DNS using the Windows PowerShell tool.

1. Open Windows PowerShell as administrator. To do so, go to the Start Menu, right-click on it and choose Run as Administrator. You can also open it using the Run dialogue box by using powershellas command.

2. Once you have opened the PowerShell tool, check the DNS if it is available to install. To check the DNS, use the Get-WindowsFeature DNS command. As you can see in the picture below, it is available to install.

3. To install DNS run Install-WindowsFeature DNS -IncludeManagementTools PowerShell command. Then, wait for a while until it finishes the installation process.

4. Now that we have installed DNS, once more, run Get-WindowsFeature DNS PowerShell command to verify the installation. You can see in the below picture that it is installed.

5. It is also the right point to mention how we can uninstall DNS using Windows PowerShell. To uninstall it, run Remove-WindowsFeature DNS PowerShell command. Wait for a moment until it completes the operation. You will receive a message to restart the server if it needs to. you can restart the server using Restart-Computer PowerShell command.

That is it. We learned how to install and uninstall the DNS in Windows Server 2022 using Windows PowerShell.

Summery

To summarize this article, we have walked through a step-by-step guide on how to install DNS service in Windows Server 2022 using Server Manager and Windows Powershell tools. We covered a detailed illustration to install DNS using Server Manager, first. Then, in a separate section, we discussed the PowerShell commands to install, verify and uninstall DNS in Server 2022.

In the end, I hope you find this article helpful. If you have any further questions, do not hesitate to share us in the comment section.

The post Install DNS in Server 2022 using Server Manager and Powershell appeared first on TECHNIG.

As an essential part of a DHCP Server, we create and configure a DHCP Scope to specify the range of IP addresses from which a DHCP server can assign one to a client in our subnet. That is the primary and well-known use of a DHCP Scope. There are multiple ways to create and configure a DHCP Scope in Windows Server OSs including Windows Server 2022. One interesting, easy, and yet professional method is using Windows PowerShell. Throughout this article, we will cover the steps to configure a DHCP Scope in Windows Server 2022 Using PowerShell.

To create and configure a DHCP Scope using the GUI method, read Create And Configure A DHCP Scope In Windows Server 2022 article.

You may also like to read: Install And Configure DHCP In Windows Server 2022 Using PowerShell.

DHCP Scope Configuration Steps Using PowerShell

Using Windows PowerShell, we just write the commands and run them directly. That means, we must know the related commands and have a good knowledge of working with PowerShell. This section will describe all the details to configure a DHCP Scope in Server 2022 using PowerShell in the below simple steps. Let’s dive into it.

Step 1: Open Windows PowerShell

In the Start Menu right-click on Windows PowerShell and choose Run as Administrator. Search for it if it is not available in the Start Menu. We can also open it from the Run by typing powershell in the Run dialogue box.

Step 2: Create a New DHCP Scope Using PowerShell

To create a new scope, we use the Add-DhcpServerv4Scope PowerShell command. Using this command, we need to specify the following four parameters:

• The first one is the scope name. We use the -Name parameter name followed by the scope name enclosed in the double quotation.
• Secondly, we specify the start of the range IP address using the -StartRange parameter name followed by its value (IP address).
• The third one is to specify the end of the rage IP address using the -EndRange parameter name followed by its value (IP address).
• And, the last one is to specify the subnet mask IP address using -SubnetMask parameter name followed by its address.

As of my new scope, the whole command becomes Add-DhcpServerv4Scope -Name "Office B" -StartRange 192.168.1.100 -EndRange 192.168.1.2 -SubnetMask 255.255.255.0 See the picture illustration below.

Step 3: Verify DHCP Scope Using PowerShell

Now that we have created our new DHCP Scope in step 2, we can verify it using the Get-DhcpServerV4ScopePowerShell command. Using this command, we can see a list of DHCP Scopes available on our DHCP Server. We can see the details for each of the scopes such as Scop ID which is most often used for further configuration of a DHCP Scope. See the illustration in the below image.

Step 4: Add Exclusion Range in a DHCP Scope Using PowerShell

To add a new Exclusion Range in a DHCP Scope, we use the Add-DhcpServerv4ExclusionRange PowerShell command. We specify the scope using the -ScopeId property. Then we use the -StartRange and -EndRange parameters each followed by the IP address that makes up the exclusion range. The command we used to create an exclusion range isAdd-DhcpServerv4ExclusionRange -ScopeId 192.168.1.0 -StartRange 192.168.1.150 -EndRange 192.168.1.160. Looking into it, we see that we have created an exclusion range that starts at 192.168.1.150 and ends at 192.168.1.160 in our scope with scope ID 192.168.1.0.

We can also verify the Exclusion Range(s) in a specific DHCP Scope. To do so, use the command Get-DhcpServerv4ExclusionRange. We should use the Scope ID with this command to point to our specific Scope. So, our command is Get-DhcpServerv4ExclusionRange -ScopeId 192.168.1.0. As we see, the picture below shows the exclusion range we just created.

Step 5: Set the Lease Duration Using PowerShell

Use the Set-DhcpServerv4Scope PowerShell command to set the lease duration. We must point to the scope using the -ScopeId parameter name followed by its value. Then we just specify the Lease Duration using the –LeaseDuration parameter name followed by its value. The format to define the Lease Duration value is day.hours:minutes:seconds. Saying those explanations, the whole command to define the Lease Duration, in our example, is Set-DhcpServerv4Scope -ScopeId 192.168.1.0 -LeaseDuration 10.00:00:00. Also shown in the below image. A duration of 10 days is defined for the Lease Duration in our example.

Now, to verify the Lease Duration configuration, use Get-DhcpServerv4Scope the command. By default, it is set to 8 days. But as we defined 10 days for it, we can see the changes.

Step 6: Configure the Default Gateway Using PowerShell

We can specify the Default Gateway for a DHCP Scope using the Set-DhcpServerv4OptionValue command. Like other steps, we need to point to the Scope using the Scope ID. We use the parameter name -Router followed by its value (IP address) to define the Default Gateway for a DHCP Scope. In our example, the complete command is Set-DhcpServerv4OptionValue -ScopeId 192.168.1.0 -Router 192.168.1.1. We set 192.168.1.1 as the Default Gateway address for our DHCP Scope.

We will verify the Default Gateway configuration at the end of the next step, as we use the same command to verify these two steps.

Step 7: Configure DNS Domain and DNS Server Using PowerShell

As the Default Gateway configuration, we use the Set-DhcpServerv4OptionValue PowerShell command to configure the DNS Domain and DNS Server. We can configure the three of them in one command line using their parameter names and their values. Use -DnsServer parameter name followed by its value (IP Address) to configure the DNS Server. Use the -DnsDomain parameter name followed by its value enclosed in double quotation to configure the DNS Domain. Remember to address the scope using the Scope ID properties. In my example, the whole command becomes Set-DhcpServerv4OptionValue -ScopeId 192.168.1.0 -DnsServer 192.168.1.2 -DnsDomain "Technig.com".

To verify the Default Gateway configuration, DNS Server configuration, and DNS Domain configuration, use the Get-DhcpServerv4OptionValue PowerShell command followed by the Scope ID properties. In my case, Get-DhcpServerv4OptionValue -ScopeId 192.168.1.0 is the whole command line.

That is all with the DHCP Scope configuration using PowerShell commands. We can do all the settings and configuration, which we could do with the GUI method, using PowerShell. This method may not be user-friendly, but it is a time-saving, professional and maybe elegant method.

Delete A DHCP Scope Using PowerShell

In addition to the above DHCP configuration steps, this is the appropriate point to describe how we can delete a DHCP Scope using Windows PowerShell. To delete a DHCP Scope, use the -Remove-DhcpServerv4Scope command followed by the -ScopeId properties. Considering the DHCP scope I work with, the complete command is -Remove-DhcpServerv4Scope -ScopeId 192.168.1.10. See the picture below.

Now, to verify if it is deleted, run the Get-DhcpServerV4Scope command and there will no longer be that scope available.

As simple as that, we can delete a DHCP Scope and verify the deletion using Windows PowerShell.

Conclusion

In a step by step approach, we covered how to configure a DHCP Scope in Windows Server 2022 using Windows PowerShell. We discussed the PowerShell command for creating a new DHCP Scope in an initial step. Then we went through the steps to add an exclusion range, the default gateway, DNS Domain, and DNS Server to a DHCP Scope all using the PowerShell command. Of course, we also verified each step. Lastly, we covered how we can remove a DHCP scope using PowerShell.

I hope you found this article helpful to your questions. You can always share us your thoughts and queries in the comment section.

The post Configure a DHCP Scope in Server 2022 Using PowerShell appeared first on TECHNIG.