Chapter 13. Configuring a server

 

This chapter covers

  • Renaming a server and joining it to a domain
  • Configuring network adapter settings
  • Setting the license key and activating a server
  • Setting the power plan

I add servers to my test domain on a regular basis. An organization of any size could be adding many servers over the course of a year, especially if they’re undertaking a major piece of infrastructure work, such as server consolidation or the introduction of a thin client environment using Terminal Services or Citrix. The key premise of this chapter is that you’re adding a new server to a domain. Many of the techniques are still valid in a workgroup environment, but most organizations with more than a handful of computers will be using a domain.

Tip

I’ve assumed in this chapter that the new server has a usable IP address (possibly via DHCP) and that the Windows Firewall is either off or configured to allow remote WMI-based management.

There are a number of tasks you’ll need to perform after the operating system has been installed and prior to the installation of applications. These tasks are common across most servers, providing a good reason for automating them. As you’ll see, the automation of these tasks builds on some of the PowerShell and WMI functions you’ve seen in earlier chapters.

13.1. Initial tasks

13.2. Controlling server restarts

13.3. Configuring network adapter settings

13.4. Activating a server

13.5. Summary