Windows Server 2019 Essential Training by Scott M Burrell (Part 1)

Windows Server 2019 Essential Training by Scott M Burrell (Part 1) - Getting Started

The course is in 6 sections, so I'll separate them by parts. I do have Windows Server experience, and 2019 is new to me, though the general idea is the same.

The first relevant video opens with

"I was speaking recently with a network administrator for a global company. He told me that his IT infrastructure was out of date because his Windows Servers were a version or two behind the newest thing from Microsoft."

Just because you can upgrade doesn't mean you should! If your stuff works (well), it works. If new features help your business, or have the possibility for your business to 'grow' into them then sure, upgrade. But there's no need to keep up with the Jones or Gates.

💭 Consider the role of Active Directory and how it will work with your new servers.

💭 In-place upgrades keep the settings and configurations while pushing it to a new version of Server. Roles may or may not transfer, or need to be configured differently. Use SMIG tools to port old settings to a new server.

💭 Some roles require more resources than others. Some done. Consider coexisting of less powerful roles on the same server.

💭 Windows Defender on Server 2019 has Ransomware protection. It was a challenge to keep machines current, so ATP was invented to centralizing the task of interpreting data, that you access via a web based portal (via Azure, so subscription needed), with scanners on each machine.

💭 DNS also keeps track of things in Active Directory, and DHCP helps it keep track of devices that have received IP addresses with IP Address Management Server.

Comments

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

What Do You Need? [List of Offered Services]

2023 Version is here, at this handy Notion Page.

Building, Breaking, and Building A CRM with Retool

I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself. I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is: To have a GUI to add people to a NRM (Network Relationship Management). Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others). Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see. When you get set up, there's a plethora of resources you can use -- Incl

RUN TCP/IP | Morgan Lucas' Tech Portfolio

Search This Blog