After the Add Roles and Features wizard was completed, the server had installed Active Directory and rebooted, I clicked on the yellow triangle by the flag icon at the top of the Server Manager window, and under that, selected Promote this server to a Domain Controller. This opened another wizard giving the option to add a new Forest.
A Forest is the entire AD structure which is a database, which is the top of the hierarchy. One or more Domains are units inside the Forest. After selecting to add a new Forest, I gave the domain a DSRM password which you would only use rarely but if AD breaks you'd need to use. I gave it WinServ2025 to keep things simple since this is only for learning and will not be doing anything sensitive. Although instructions told me I should use 12 characters, upper and lowercase letters and numbers and symbols. I only had letters and numbers, 11 of them, and upper and lowercase letters. I don't know why it worked but it did. In my experience with Windows Server's Server Manager so far, if the field doesn't meet the criteria set, then it doesn't let you proceed, and neither does Proxmox for that matter. So these instructions must be wrong in that regard.
I got a message saying "A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found. But I am skipping past this, there's no parent DNS zone like .local on the internet to delegate from and my Proxmox setup isn't running a higher-level DNS server that could delegate to testlab.local, which is what I named it. It asked me to create a DNS delegation, which I called testlab.local since I'm bad at naming things. The wizard had me confirm the the NETBIOS name, which had TESTLAB in capital letters, which will always use the first part of your domain name. I simply confirmed it. On the Paths page, I left everything default since I had no reason to change it. I then got two warnings, a Static IP Warning saying my network adapter needs static IPv4 and IPv6 addresses. I already had a static v4 address, and fixed the v6 address problem by disabling IPv6. The other problem was a DNS delegation warning. External DNS servers won’t know how to find my testlab.local domain, but I will ignore this for the purposes of my AD project. I pressed Install at the bottom of this page.
In trying to understand the DNS delegation problem, I did come up on something I could install that would stop the warning from appearing every time:
Install-ADDSDomainController -NoGlobalCatalog:$false -CreateDnsDelegation:$false -InstallDns:$true -DomainName "testlab.local" -DomainNetbiosName "TESTLAB" -SafeModeAdministratorPassword (ConvertTo-SecureString -AsPlainText "YourPassword" -Force) -Force:$true
But I'm not doing this because I want everything to happen the same way it would unfiltered in the workplace. I am aware that installing this may very well just stop this one warning and in reality in the workplace if I just got the system running properly and needed to make this domain searchable by external DNS servers, then this warning would not pop up, but I don't know enough about this to say that it's a good idea to stop this warning from appearing.
My friend Matt Petersen is helping me with this, and suggested that I learn about the error. And Doug, my former instructor showed me a webpage for learning Active Directory so I have navigated to it to look at it:
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/understanding-the-active-directory-logical-model#main
Instructions I am following said to open the CMD in Windows Server and enter:
echo %USERDOMAIN%
This returned "TESTLAB", which indicates the server successfully recognized the domain I just created. It's an active directory domain and the machine is properly joined to the domain, the promotion worked! I have an Active Directory!
Initially, I wrote that the promotion to DC (domain controller) worked, I didn't know that officially meant I had an active directory. 404 plan not found!
This isn't exactly promoting the server, but since I imagine my evaluation period for windows server is going to be up in the next month or two, i looked up how to back up my progress so i can simply transfer it to another VM or whatever. So in the Proxmox interface, I clicked Datacenter in the side-pane > Backup > Add, which produced a window to back it up. Unfortunately the picture I provided was grayed out because I had already done something in the backup window I didn't want to lose and decided to capture this image so I moved it to the side while I grabbed it.
In the backup window under Node, selected Poxmox, Storage set as Local, and in schedule, it didn't offer the exact time I would have preferred, instructions online suggested the same scheme used in Cron on Linux, so I typed "0 2 * * *". "where the first star represents the minute (0-59), the second star represents the hour (0-23), the third star represents the day of the month (1-31), the fourth star represents the month (1-12), and the last star represents the day of the week (0-7, Sunday-Saturday)." I was led to understand that everything in Proxmox uses military time, Cron syntax, and the three asterisks means daily. 0 = minute 0, 2 = hour 2 (2 AM), * * * = every day, month, and weekday in another thing. It kept giving me n error 400 no matter what I did. Another thing said you can't just enter 02:00 because it wont work every day. But I found a page online where this guy explained what I was doing and just entered 21:00 for his backup. Then I went back to the field in Proxmox and looked at the dropdown menu options I was dissatisfied with. I selected everyday 21:00, and it simply displayed a straight 21:00, which I changed to 02:00. Since I selected every day, I would assume that this would carry with it some sort of indicator, a series of symbols the asterisks or whatever if it didn't automatically do this every day. No symbols, no syntax of any kind. So I entered 02:00.
Now in reality I couldn't get it to work and was trying everything and entered just straight 02:00 and pressed okay and it took it, and then tried a few more things to discover that you can't change it once it's done, which lines up with my experience with hypervisors so far. And since I then learned later that 02:00 apparently stands for 2am every day, I stuck with it thankful I didn't have to go back. I will see later if this is automatically backing up each day.
In the next field I went INCLUDE SELECTED VMs and check marked the VM below in the window below. I had several VMs that I developed in order to troubleshoot the BIOS problem that kept me from installing Windows Server, and when I found out about workarounds and SeaBIOS, I created several VMs to test all these, I don't want them backed up though. I just know now to use SeaBIOS because of the TPM 2.0 problem. ZSTD for compression which Proxmox says is fast and good, the other options are good or fast. Without doing research, draw you're own conclusions.
The last field is more interesting, Mode, which has the option to do Snapshot, Stop or Suspend.
Stop: the VM is shut down completely during the backup, then restarted afterward. This is Safer for good, consistent backups but causes downtime. I like this best for lacking issues and am used to logging in every time anyway. Suspend: The VM is paused (frozen), backup runs, then resumed.
Less downtime than Stop, but can cause issues with some apps. Snapshot: Uses Proxmox snapshots to back up while VM runs. Fast and no downtime if guest agent is installed and supported. Might cause data inconsistency if apps aren’t snapshot-aware. Since I don’t have the guest agent set up, Stop is the safest.
This has been Truncat3d 00000000111100010100110______________end of line
No comments:
Post a Comment