[UC2OFS051] – Windows Servers, Active Directories, Considerations

Setting up the server OS and interacting with the server manager was surprisingly incredibly straightforward and intuitive. A very effective and powerful tool by my first impressions at a glance. I even got a Windows client to join the domain as a member during first try, which was again... Surprising.

Though in reference to the activity sheet, if I were to set up an actual server for an actual company with ~2000 plus clients... I don't know. I assume you wouldn't want an admin user with '1234' as password. So I'd perhaps start off with ensuring that the domain controller machine is up to date with Windows updates, has a decent firewall and antivirus set up and have remote connection capabilities turned off. I'd also rename the Administrator user to something less predictable, and ensure it has a strong password as well.

I'm not sure if Windows has that capability, but preferably by my own personal preference, anyone with Admin permissions should have a Two-Step Verification process of logging in. Whether that's a possible thing or not though - No idea.

I'd probably want computers to have a logical name, by a structured naming convention. Say that the company has a location in Oslo, Kristiansand and Bergen. The different computers could be structured with their hostnames being something like <Region> - <OS> - <Floor><IncrementalNumber>. So, as an example, KRS-Win-a001. So that'd be a Windows computer located in the Kristiansand office, on floor ‘a’ (first floor, first letter in the alphabet).

Other than that, I can't really think of anything much else. I've done some googling, but most of the other tips and best practices are a bit beyond my scope of knowledge and insight into systems yet, so I can't really elaborate further on what, how or why in regards to that.

Leave a Comment