Mastering Windows Server 2022 with Azure Cloud Services: IaaS, PaaS, and SaaS (Series Monographs in Applied Toxicology)

Product Information

There it is! Okay, so now that I know the correct name of the feature, let’s run the command to install it, as shown in the following example: Add-WindowsFeature Telnet-Client

If I now choose to add a new role from inside Server Manager that is aware of multiple servers in the network, when I get to the screen asking me where I want to install that role, I see that I can choose to install a new role or feature onto one of my other servers, even though I am not working from the console of those servers, as shown in Figure 2.23: Updated with Server 2022 content, this book covers a wide variety of information pertaining to your role as a server administrator. We will expand upon versions and licensing models for this OS, and explore the 'single pane of glass' administration methodology by utilizing tools like Server Manager, PowerShell, and even Windows Admin Center. This book is primarily focused on Windows Server 2022 LTSC version, but follow along as we discuss the latest news for SAC server releases as this impacts Containers, Nano Server, and general OS release cadence. Using Server Manager on a single server to manage and monitor all of your servers is pretty handy, but what if we could take one more step out of that process? What if I told you that you didn’t have to log in to any of your servers, but could perform all of these tasks from the computer sitting on your desk? unattend: There is a special answerfile that you can create that, when specified, will be used in conjunction with the Sysprep process to further configure your new servers as they come online. For example, you can specify in this answerfile that a particular installer or batch file is to be launched upon the first Windows boot following Sysprep. This can be useful for any kind of cleanup task that you might want to perform, for example, if you had a batch file on your system that you used to flush out the log files following the first boot of new servers. Disk: Server 2022 requires a PCI Express ( PCIe) storage adapter. ATA/PATA/IDE are not allowed for boot drives. The minimum storage space requirement is 32 GB, but Desktop Experience consumes about 4 GB more space than Server Core, so take that into consideration.Keep in mind, these are the bare minimum specs that your server is going to require. Any real server in a production environment will need far more memory and disk space, and there is no magic number for what you will need. It depends on what workload you are going to expect out of your server. New servers created from a sysprepped image file always receive a new hostname when they boot. This often confuses admins who might have named their master server something such as MASTER. After booting your new servers, you can expect to see randomized names on your new servers, and you will have to rename them according to their new duties in life.

If I wanted to install the web server role onto WEB1, a new server that I am prepping to be a web server, I would not have to log into the WEB1 server. Right here, from Server Manager running on CA1, I could run through the Add Roles wizard, define WEB1 as the server that I want to manipulate, and install the role directly from here. Remote Server Administration Tools (RSAT) shutdown: This shuts down the system (not a restart) when Sysprep is finished. This is an important one and is one that I typically use. Foundational explanations of core Azure capabilities, including Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), and Software-as-a-Service (SaaS)Without a doubt, the most common place that roles and features get installed is right inside the graphical wizards available as soon as your operating system has been installed. By default, a tool called Server Manager launches automatically every time you log in to Windows Server 2022. We will take a closer look at Server Manager itself later in this chapter, but for our purposes here, we will simply use it as a launching platform to get to our wizard, which will guide us through the installation of our first role on this new server we are putting together. In Mastering Windows Server 2022 with Azure Cloud Services: IaaS, PaaS, and SaaS, 5-time Microsoft MVP Winner William Panek delivers a comprehensive and practical blueprint for planning, implementing, and managing environments that include Azure IaaS-hosted Windows Server-based workloads. You’ll learn to use the expansive, hybrid capabilities of Azure, how to migrate virtual and physical server workloads to Azure IaaS, PaaS, and SaaS, and how to manage and secure Azure virtual machines running Windows Server 2022. Stop doing that! It’s here to help, I promise. Figure 2.18 shows the default view of Server Manager on my new domain controller:

Continue to save yourself time and effort by creating new copies of your master images every few months. This way, the newest patches are always included in your master image, and it continues to save you more and more time throughout the life of Windows Server 2022. Running Sysprep to prepare and shut down your master server Explorations of the tools you’ll need to implement Azure solutions, including Windows Admin Center and PowerShell First, just like you have already done, we need to prepare our first server by getting the Windows Server 2022 operating system installed. Refrain from installing any full roles onto the server because, depending on the role and its unique configuration, the Sysprep process that we run shortly could cause problems for individual role configurations. Install the operating system and make sure device drivers are all squared away and you’re ready for the next step. Configuring customizations and updates onto your new server Examples of implementing identity in Hybrid scenarios, including Azure AD DS on Azure IaaS and managed AD DS So, anyway, we will not focus on an automated approach to server rollouts, but rather we will do a few minutes of extra work on our very first server, which then results in saving numerous minutes of setup work on every server that we build afterward. The core of this process is the Sysprep tool, which is baked into all versions of Windows, so you can take this same process on any current Windows machine, whether it be a client or a server.generalize: This specifies that Sysprep is to remove all of the unique system information (SID) from the Windows installation, making the final image usable on multiple machines in your network because each new one spun up from the image will get a new, unique SID. As with many executables that you run from Command Prompt, there are a variety of optional switches that you can tag onto the end of your command to make it do specific tasks. From your Command Prompt window, if you simply run the sysprep.exe command, you will see a graphical interface for Sysprep, where you can choose between the available options, as shown in Figure 2.37: This book covers a range of remote access technologies, and even teaches management of PKI and certificates. You will be empowered to virtualize your datacenter with Hyper-V, and deploy your own Remote Desktop Services "farm". Learn about Server Core, built-in redundancy, and explore troubleshooting skills. All this on top of chapters about core infrastructure technologies such as Active Directory, DNS, DHCP, and Group Policy. What you will learn