Can DHCP and static be configured simultaneously on Windows Server 2019?

In the scenario where the device is only connected to the network, it receives a specific range of IP addresses (192.168.2.0/24), without access to domain resources.

However, if the device is joined to the domain controller, it will be assigned a static IP address from a different network (192.168.1.0/24).

To achieve this, one possible method is to utilize vlan definition combined with 802.11x authorization on the networking equipment.

However, implementing this approach requires a robust infrastructure, which includes network equipment that supports all the required features, as well as a radius server and possibly a pki (public key infrastructure).

By establishing such a setup, organizations can enhance network security and ensure secure access to their systems.

Theoretically, these issues should be addressed by the Network Policy Server on Microsoft, particularly if you are using Windows AD (Active Directory).

However, despite seeing this functionality mentioned in the manual, I have not witnessed its practical implementation.

In your situation, it would be advisable to assign a DHCP range of .2.0/24 and configure static IP addresses on the same DHCP server based on device MAC addresses.

Nevertheless, be cautious, as encountering a device with pre-configured static IP addresses on the .1.0/24 range may lead to complications.

Exploring alternate solutions or seeking expert advice would be prudent to ensure seamless network management and avoid potential complications.

Indeed, it is possible to achieve the desired configuration. This can be accomplished by utilizing switches that support 802.1x authorization, configuring it through a Network Policy Server (NPS), and assigning devices to different VLANs based on their authorization status.

Once a device successfully completes the authorization process, it can be granted access to the primary VLAN, which would typically have its own DHCP cluster to assign IP addresses. Conversely, if a device fails the authorization process, it can be redirected to a failover VLAN.

Yes, it's possible to set up a scenario where devices can receive an IP address via DHCP but also have the option of using a static configuration when connected to specific networks, like your example involving different subnets.

First, typically, a DHCP server is used to automatically allocate IP addresses to devices on the network. In your case, you would configure your Windows Server 2019 to run a DHCP service. You could set the DHCP scope to provide addresses from the range of 192.168.2.0/24. This is beneficial for devices that are not joined to the domain controller but still need connectivity on the local network.

When a device is connected to the domain, you would normally want it to receive a static IP address from a different network, like 192.168.1.0/24. To achieve this, you'd set the static IP configuration directly on the device or through Group Policy. If you're working with multiple devices or a larger environment, manually setting static IPs can get tricky. Therefore, using DHCP reservations can be a practical solution. With DHCP reservations, you can reserve a specific IP address within the DHCP scope for the device's MAC address, ensuring that it always gets the same IP address.

The important thing to remember is that when a device is assigned a static IP address, it won't be affected by the DHCP server settings. However, there can be conflicts if the static IP is not excluded from the DHCP scope. For instance, if the static IP for the domain-joined device happens to fall within the range of addresses assigned by the DHCP server, you could face issues like IP conflicts.
It's entirely feasible to use both DHCP and static IP configurations simultaneously on Windows Server 2019. Just ensure proper subnetting, avoiding overlapping IP ranges, and possibly utilizing DHCP reservations to manage device IP assignments efficiently. Also, keep an eye on proper routing and subnet masks to ensure connectivity across your different networks without issues.

This is known as "dual-stacked" or "hybrid" configuration. In your scenario, the device can be configured to obtain an IP address from the 192.168.2.0/24 range via DHCP when not connected to the domain, and then switch to a static IP address from the 192.168.1.0/24 range when joined to the domain.
This is achieved through the use of multiple network adapters or IP settings, and careful configuration of the IP address assignment policies.