Windows Server Editions
Windows Server 2012 is available in different editions to support various requirements and workload needs. Each edition of Windows Server has different functionality and feature sets. Each edition also has different hardware capabilities.
Before watching the video take a moment to download and review the Windows Server 2012 R2 Products and Editions Comparison Chart. Pay particular attention to number of users, maximum number of sockets, maximum RAM, and the overlap of roles and features.
Install Fresh or Upgrade
When installing Windows Server you are given two choices: Upgrade: Install Windows and keep files, settings, and applications or Custom: Install Windows only (advanced).
To learn more mouse over each type of installation.
Upgrade or Migrate
Migration lets you to move the configuration of an existing server to a new server computer. Migrations are often selected over upgrades because the process is less destructive and more recoverable. Depending on the services and functionality that you need to migrate to a new server instance, there will be different requirements and actions you need to take. Fundamentally though, migration can be broken down into three phases.
- Installing, running migration tools and identifying any prerequisites. For example, drivers and ports.
- Preparing source server. For example, backing up your data.
- Preparing destination server. For example, ensuring drivers and ports are available.
- Exporting or migrating data from source server.
- Importing or migrating data to destination server.
- Verify destination server is running successfully.
- Decommission source server.
When you install Windows Server 2012 you are presented with two installation options: Server Core and Server with a GUI.
Server Core is the default option. Server Core installs fewer components and administrative management tools than the Server with GUI option.
Advantages of Server Core
- There are fewer features so fewer software updates are required. This means less downtime, less administrative overhead, and reduced restart requirements.
- By removing files that are not needed disk space and memory requirements are reduced. This means when virtualized you can deploy more servers on the same host.
- Since fewer files are installed there is less opportunity for security threats. Also, without a GUI, it limits a local user’s ability to interact with it.
Installing Windows Server
|Visit the TechNet Evaluation Center to download an evaluation copy of Windows Server 2012.|
In this Try It you will install Windows Server 2012 R2.
Note: The next Try It (Post-Installation Configuration) continues from the installation, so do not close your lab session.
- In the lab environment switch to the LON-SVR3.
- In the command window it will show Press any key to boot from CD or DVD.
- Click in the command window and click any key to proceed.
- In the Windows Setup Wizard verify the following settings, and then click Next
- Language to install: English (United States)
- Time and currency format: English (United States)
- Keyboard or input method: US
- On the next page, notice the Repair your computer option.
- Click Install now.
- On the Select the operating system you want to install page, select Windows Server 2012 R2 Datacenter Evaluation (Server with a GUI), and then click Next. Notice the other choices for Standard edition and for Server Core.
- On the License terms page, review the operating system license terms, select the I accept the license terms check box, and then click Next.
- On the Which type of installation do you want? page, click on Help me decide to read more about theoptions. Click Custom: Install Windows only (advanced).
- On the Where do you want to install Windows? page, select Drive 0 Unallocated Space and then clickNext.
- Note: Depending on the speed of the equipment, the installation takes approximately 5 minutes. Thevirtual machine will restart several times during this process.
- On the Settings page, in both the Password and Reenter password boxes, enter the passwordPa$$w0rd, and then click Finish.
- Login to the machine and notice Server Manager is automatically started.
- Switch to Windows Explorer and notice the DVD drive contains the Windows installation files. The server booted to this drive to start the installation.
Post Installation Configuration
The post-installation process involves configuring all of the other settings that the server requires before it can be deployed to a production environment.
- Configure the IP address
- Set the computer name
- Join the domain
- Configure the time zone
- Enable automatic updates
- Add roles and features
- Enable remote desktop
- Configure Windows Firewall settings
Can you think of anything else your organization needs to do?
In this Try It you will use Server Manager and sconfig.cmd to configure a server.
Note: This Try It continues from the previous installation.
- Login to LON-SVR3 as Adatum/Administrator with the password Pa$$w0rd.
- This computer has Server with GUI configuration.
- In Server Manager click Local Server.
- Take a moment to review the different computer settings that can be configured from this page.
- Click IPv4 address assigned by DHCP, IPv6 enabled.
- Right-click Ethernet, select Properties, and edit the Internet Protocol Version 4 (TCP/IP) properties.
- Static IP Address: 172.16.0.50
- Subnet Mask: 255.255.0.0
- Default gateway: 172.16.0.1
- Preferred DNS server: 172.16.0.10
- Alternate DNS Server: None
- Click Workgroup and Change:
- Computer name: LON-SVR3
- Domain: Adatum.com
- User name: administrator
- Password: Pa$$w0rd.
- Click OK to restart the computer.
- Login to LON-CORE as Administrator with password Pa$$w0rd.
- This computer has a Server Core installation.
- At the command prompt, run sconfig.cmd.
- Take a moment to look through the various settings that can be configured. These are same settings you just used in Server Manager.
- Switch to 8) Network Settings. Use the same settings as before with a static address of 172.16.0.49
- Switch to 1) Domain/Workgroup. Join the server to the domain, you can use the same credentials you used to login when prompted.
- When prompted change the Computer Name to LON-CORE.
- In the Restart dialog box, click Yes.
- Verify connectivity from both LON-SVR3 and LON-CORE to LON-DC1
Note: If you are having problems getting connected, you can verify your connectivity as follows:
From the command prompt use: ping LON-DC1
From a Windows PowerShell prompt use: Test-NetConnection -ComputerName LON-DC1.
This will verify connectivity to the domain controller. If the command is not successful double check your network settings.