70-410-Renaming a Windows 2012 Server

Renaming a Windows 2012 Server

70-410 Exam Series

Please click the +1 button if you find this post helpful.

This post is intended to demonstrate some common methods for changing a computer name. The Command Line options  (Option 3 & Option 4) provide a good introduction to administrators unfamiliar with working with Server Core installations.

Option 1: GUI - Server Manager
Option 2: GUI - System Properties
Option 3: CLI - NETDOM
Option 4: CLI - SConfig

Option 1: GUI - Server Manager

The Server Manager loads automatically upon login on any Windows Server 2012 full installation. On any new installation, your first stop will likely be a visit to the Local Server (Properties) with in Server Manager. This screen is similar to what you would see upon first logging in to a Windows 2008 Server. You can perform all of your basic set up tasks, such as Changing the computer name and domain membership, enabling Remote Desktop, setting Network properties and the Time and Time Zone, and installing updates.

1. From the Server Manager Dashboard, click Local Server in the left navigation pane.
2. In the Local Server Properties window, click on the hyperlinked Computer Name. This will launch the familiar System Properties dialog. From here, the process is the same as using System Properties specified in Option 2.

Server Manager: Local Server

1. On the Computer Name tab, click the Change button.
2. Replace the contents of the Computer Name text box, with the new computer name. 
3. Optionally, if you need to change your Domain or Workgroup membership, you can do so now, then click OK. 
4. Click Apply/OK on the System Properties dialog to exit. You'll be prompted to restart your computer for the change to take affect.

Option 2: GUI - System Properties

Using the Computer Properties is arguably this most common method for changing the Computer Name and Domain or Workgroup membership. While in previous versions of Windows, getting here was as simple as right clicking on My Computer and selecting Properties, now, with My Computer being absent from the desktop or Start screen getting here becomes more complex if you're avoiding the Server Manager for some reason.

1. From the Charms bar, click Settings.
2. Click on Server Info. This takes  you to Control Panel, System and Security, System. (Which is yet another way to get here).
3. Under Computer name, domain, and workgroup settings, click the Change Settings link.

Control Panel: System

1. On the Computer Name tab, click the Change button.
2. Replace the contents of the Computer Name text box, with the new computer name. 
3. Optionally, if you need to change your Domain or Workgroup membership, you can do so now, then click OK. 
4. Click Apply/OK on the System Properties dialog to exit. You'll be prompted to restart your computer for the change to take affect.

System Properties: Computer Name/Domain Changes

Option 3: CLI - NETDOM

Once you're familiar with the syntax for using NETDOM, you'll likely find it much easier and quicker, than using the GUI for common setup tasks such as changing the Computer Name. 

The command string below can be run on the local computer to change it's name.

> netdom renamecomputer %computername% /NewName: <NewComputerName> /REBoot

EXAMPLE: NETDOM -renamecomputer

For those of you unfamiliar with working on the command line or batch scripting, the percent sign encloses an environment variable. If you type "set" at a command prompt, you'll see the variables listed.

IMPORTANT: While you can execute netdom from within PowerShell, the Environment Variable %ComputerName% will not be recognized properly. 

EXAMPLE: SET (Environment Variables)

If you find the line starting with COMPUTERNAME= that will tell you the current name of your computer. While you could type in that name when using NETDOM, using the variable is often easier.

For example, let's assume this is a new installation. Microsoft has created a randomly generated name for your new PC or Server, such as the one in the Example above (WIN-APQHOUBNTL4). It would be easy to make a mistake typing this name and take additional time finding it. 

As with renaming a computer using the GUI, a reboot is required. This can be accomplished using the /REBoot switch at the end of the NETDOM command, or it can be issued separately using the "shutdown /r" command.

Option 4: CLI - SConfig

SCONFIG is a command line based application, reminiscent of those old DOS programs. Once launched the Server Configuration main screen will appear. You can then select the number for the action you want to perform, then simply follow the onscreen prompts. In my personal opinion, this is a bit cumbersome for many of the tasks, however it is a convenient and easy way to modify the network settings and install windows updates.

SCONFIG is available in both Core and Full installations and can be launched from either the command line or PowerShell. 

SCONFIG: Rename Computer

While an entire blog post could be devoted simply to SCONFIG, the purpose of this article is simply to demonstrate how to change the computer name. 

1. From the Command Line type SCONFIG and press Enter.
2. Once the Server Configuration menu appears, enter the number two (2), then press Enter.
3. You'll be prompted to enter the new computer name, then press Enter.
4. A popup dialog will prompt you to restart your computer. If you have completed your changes, click Yes, otherwise, if you need to make additional changes, you can click No, and restart by selecting option  13 from the SConfig menu, or existing and using the "shutdown - r" command. 

Topics: Windows Server 2012, Core Installation, Command Line, CLI, PowerShell, Po$h, NETDOM, SCONFIG, 70-410

Extending Operations Monitor Beyond the Trust: Part 1

Extending Operations Monitor Beyond the Trust

Part 1: System Center 2012 Operations Manager: An Overview

Please click the +1 button if you find this post helpful.

Operations Manager relies on Kerberos to perform authentication, but there are some instances when Operations Manager needs to monitor a host which resides outside of a Kerberos Realm.

• The host is a member of a Workgroup (not joined to a domain)
• The host reside in an untrusted Active Directory Domain

A comprehensive monitoring  system needs to be flexible and account a variety of environment configurations, since most networks are dynamic and include a variety of security related controls which can limit our designs. It's rare that what we work with in real life will ever look like a textbook example. Operations Manager is able to be adapted to many of these challenges furthering it's reach and usefulness.

Scenario 1: Using Certificate Based Authentication

When Operations Manager and the client it needs to monitor reside on opposite sides of a trust boundary, mutual authentication can not be performed using Kerberos. 

Scenario 2: Deploying a Gateway Server

While it is possible to use certificate based authentication on every client, management of the clients and certificates can become a time consuming task, as the number clients outside of the trust boundary grows. When numerous clients in a non-trusted domain, or domain separated by a firewall need to be monitored, deploying an Operations Manager Gateway Server will help to simplify management.

When a Gateway Server is deployed client agents use Kerberos to mutually authenticate with the Gateway Server, in the same way that clients would normally authenticate with the Operations Manager Management Server. Once authenticated, the Gateway Server uses Certificate Based Authentication to traverse the enclave and/or trust boundary and communicate with the Management server as depicted in the figure below.

The benefits of a deploying a Gateway Server are:

• Only one certificate needs to be obtained to allow mutual authentication between the Gateway Server and Management Server.
• Firewalls can be configured to permit traffic between a limited set of Gateway and Management servers, which are unlikely to change as often as individual clients.
• Agents can be automatically deployed. Manual or scripted installation and configuration of the Operations Manager Agent is not required.

 Each Gateway Server can support a maximum of 2000 Agent Managed hosts.

For more details, check out the up coming articles:

• Part 2: Extending Operations Monitor Beyond the Trust: Step By Step: Scenario 1: Using Certificate Based Authentication
• Part 3: Extending Operations Monitor Beyond the Trust: Step By Step: Scenario 2: Deploying a Gateway Server

Topics: Windows Server 2012, System Center 2012 Operations Manager, Managed Agent, Monitoring, Gateway Server, Active Directory, Kerberos, Trust Relationship, Authentication, Certificate,