Administering a Linux domain controller is our current phase. We have a Linux AD-DC on the network, installed on ESXi in a test environment where the infrastructure of a small business is growing ready for production. As well as the Untangle NG Firewall gateway, which sits behind everything we’ve already created. Administering a Linux domain controller to perform everyday tasks is exactly the same as a natural one. That’s what we’ll see in today’s record. We’ll put the Windows 10 Pro workstation into the domain. Let’s install RSAT on it, add a user to Active Directory, create APO and see the DNS rig. In real life, you should have a laptop or computer with a licensed Windows 10 Professional. In my case, the test version will be used in the newly installed trial version. The only change that was made to it after installation – open remote access. Let’s do it!
Briefly about the introductory:
|Linux Domain IP Controller||192.168.1.100|
|Linux domain controller name||ag-dc-1|
|Domain Administrator’s Name||Administrator|
|Domain Administrator Password||AdminGuide.Lan|
|The role of THE DHCP server||ag-dc-1|
|The role of DNS server||ag-dc-1|
|The name of the workstation plug-in||admin-win|
Check Windows network settings
We check that the customizable workstation receives DHCP settings from our domain controller’s DHCP server, as well as making sure that it is listed as dNS server.
ng sure that everything works as it should and the address is received by DHCP from the domain controller, and not from some inadvertently turned on gateway router we go further.
Introduce the computer into the domain
So far nothing remarkable, everything happens as if it is 100% masdai network (“Cool yes?!”). We go to the properties of the computer and there we carry out a standard
e Linux domain
After successfully logging into the domain, we are routinely rebooted and authorised as AdminGuide.Lan’Administrator
Administer the Linux domain controller. Install RSAT
We go to this page and swing and immediately install remote administration tools for Windows 10. At the time of writing it was WindowsTH-RSAT_WS_1803-x64.msu .
Another way to install RSAT in Windows 10 is to use “Additional Components.” I do not like that menu, and even more all tiled interface masdaya, so I will not focus on this way.
What do we actually have? The three basic snaps used in everyday life are quite workable. You can safely add to remove users, create GPO that will be on all vending machines domain, manage the local DNS zone. It’s like we’re ordinary Windies. You’re a mouse, you poke-poke and don’t even think that every single poke, saves you 2 years of life, and the company an extra 100 taps and CAL licenses.
The world is cruel. It should be understood that these rigs work only because the backend they serve, sharpened to work with them. If you try to connect to the ISC DHCP Server with the same tool, nothing will work. But what is enough for everyday tasks, if the network on Linux transferred only backend. Pray for the well-being of bind9 and samba