70-410: Installing and Configuring Windows Server 2012: August 2013

Wednesday, August 28, 2013

Customizing the Interface with Features on Demand with windows server 2012

Features on Demand can be used to remove specific roles and features. By cherry-picking which components reside on your server, you can save disk space. In Hyper-V virtual machines, Features on Demand reduces the footprint of a virtual machine—insome instances, removing particular roles and features can reduce the size of a virtual machine by more than one gigabyte.

Figure 1. Minimal Server Interface

This is one of my favorite features in Server 2012. I’m not quite sure why Microsoft isn’t singing the praises of Features on Demand and hitting administrators over the head repeatedly about how great it is, instead of going on about Server Core install recommendations. Minimal Server Interface is a far better and more flexible option than simply going with a Server Core install if you don’t want the full GUI; it’s a customized GUI
that you pretty much design based on your management needs.

Another big advantage in Server 2012 over previous server versions is that in prior versions of Windows servers, you could disable server roles and features, but the binary files for them remained on the server. With Server 2012, however, these files are fully removable. Uninstalling files associated with server roles and features is a state called “disabled with payload removed.”

To remove these roles and features, you can use a PowerShell cmdlet. For instance, to remove Windows Explorer, Internet Explorer, and all dependent components, you can run the command:

Uninstall –WindowsFeatures Server-Gui-Shell –remove

Once you remove a role or disabled a feature with payload removed, you can reinstall it. Reinstalling requires access to an installation source (typically on the installation media). Use the PowerShell command Install-Windows Feature with the –Source parameter. If you don’t specify a source, Windows will attempt to download the needed files using Windows Update.

Deploying Minimal Server Interface for windows server 2012

Windows Server 2012 also offers an interface that is between Server with a GUI and Server Core: the Minimal Server Interface. With an initial Server with a GUI install, you can convert to the Minimal Server Interface through Server Manager. Minimal Server Interface removes components of the Server Graphical Shell, including Internet Explorer 10, Windows Explorer, the desktop, and the Start screen. The Microsoft Management Console (MMC), Server Manager, and a subset of Control Panel are retained.

To convert Server with a GUI to a Minimal Server Interface, from Server Manager launch the Remove Roles and Features Wizard. Select from the features list Graphical Management Tools and Infrastructure (see Figure 1).

Figure 1. Converting Server with a GUI to Minimal Server Interface

Click Next. Check the box next to “Restart the destination server automatically if required.” Click Remove. When prompted, allow automatic restarts. (See Figure 2.)

Figure 2. Allowing automatic restarts

Converting windows Server 2012 with a GUI to Server Core

To convert from Server with a GUI to a Server Core installation with Windows Power‐Shell, run the following cmdlet:

Uninstall-WindowsFeature Server-Gui-Mgmt-Infra -restart

Successful execution of the preceding cmdlet starts the removal process of the server shell (see Figure 1).

Figure 1 Converting Server with a GUI to a Server Core install

The server reboots once the graphical interface is removed. When the server comes back up, after login, the core interface is loaded.

If you convert to a Server Core installation, Windows features, server roles, and GUI management tools that require a Server with a GUI installation will be uninstalled automatically. You can specify the -WhatIf option in PowerShell to see exactly which features will be affected by the conversion.

Converting Windows Server 2012 Core to Server with a GUI

To convert a Server Core install into a Server with a GUI install, you will need to create a folder to mount a Windows Imaging File (WIM). WIM files are images of the operating system and reside on the installation media, in the sources folder. The image file that gets mounted is the install.wim file, which is located inside the sources folder.

To get started, first run the command mkdir from the command prompt to create a directory named mountdir. The syntax is mkdir c:\mountdir. (See Figure 1.)

Figure 1. Creating a directory named mountdir for mounting the WIM file

After you run the mkdir command, the mountdir folder is listed under the root of the C:\ drive (see Figure 2).

Next, you need to find the index number associated with the Server with a GUI image you want to install. For example, I am converting from Server Core with the Datacenter edition of Windows Server 2012. I want to find the Server with a GUI image located on my installation media and the index number that references that image. To do so, use the Dism command at an elevated command prompt. The proper syntax is runas /user:administrator to elevate permissions within the command prompt. Click Enter, and you will be prompted to enter the administrator password.

Figure 2. Newly created mountdir directory

Then run the following to get the correct index number (also shown in Figure 3):

Dism /get-wiminfo /wimfile:drive where installation media is located:\sources\install.wim

Figure 3. Command to locate the index number of the appropriate Server with a GUI image

Upon successfully running the command, you’ll see the Deployment Image Servicing and Management tool load. Find the index number of the Server with a GUI image you want to install (see Figure 4).

Figure 4. List of image files and associated index numbers

Mount the appropriate image file with the following command (also shown in Figure 5):

Dism /mount-wim /WimFile:drive where installation media is located:\sources\install.wim /Index:#_from_step_2 /MountDir:c:\mountdir/readonly
This again launches the Deployment Image Servicing and Management tool. The Server with a GUI image is mounted. After the message “The operation completed successfully” appears on screen, the image mount is complete. The final step requires installing the GUI from the mounted image
with PowerShell. Launch PowerShell by simply typing powershell at the command line.Again, you must run PowerShell with the administrator account’s elevated permissions for the installation to work.

Run the cmdlet:

Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart –Source c:\mountdir\windows\winsxs

Figure 5. Mounting the image file

If the cmdlet is successfully executed, you will see the GUI installation start within PowerShell (see Figure 6).

Figure 6. The GUI installation process within PowerShell

After install, the server reboots. When the server comes back up, the Ctrl-Alt-Delete screen is displayed. Login and the Server Core interface are now replaced with the full Windows 2012 Server shell.

You can also use Windows Update as the source, instead of a WIM file, by using this Windows PowerShell cmdlet (make sure you have an Internet connection):

Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart

Windows Server 2012 with a GUI installation procedures

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation version here.

Download a Windows Server 2012 evaluation here.

After you’ve inserted the installation media into the CD-ROM, DVD, or USB flash drive, or executed an install from the network, the install wizard begins. The first screen prompts you to click “Install now” to get the install process up and running (see Figure 1).

Figure 1. First screen of a Server 2012 installation

The install wizard then prompts you to select installation preferences such as language, time and currency format, and keyboard or other input device settings, as shown in Figure 2.

Figure 2. Installation preferences

Next, select the installation mode. For a Server with a GUI install, the selection option is Windows Server 2012 Enterprise (Server with a GUI Installation), as shown in Figure 3. Click Next to continue.

Figure 3. Server installation mode options

You are then asked to check a box to agree to the license terms. You cannot continue with installation if you don’t check the box (see Figure 4). Once you do, click Next.You’ll then select the option to perform a fresh install of Server 2012 or an upgrade from Server 2008 R2 (see Figure 5). Select “Custom: Install Windows only (advanced)” for a new install, or “Upgrade: Install Windows and keep files, settings, and apps” for an upgrade.
Now, select how you want to partition drives and the location to install Server 2012, as shown in Figure 6. Typically, most server administrators will create a system partition for loading the server operating system. You can create another partition for the rest of the space on the hard drive(s) and then allocate it into volumes after install, depending on your storage needs.

Figure 4. License terms agreement

Figure 5. Select the installation type: Custom for a new install, or Upgrade for upgrading from Server 2008 R2

Figure 6. Setting up drive partitions

I do recommend installing the operating system—in this case, Server 2012—on its own system partition and then creating separate partitions to store data. The partition and volumes containing the server data are what is usually included in regularly scheduled backup jobs. This way, if the server gets damaged or corrupted, you can reinstall the OS if you have to and then can restore data from backup. This is good practice on small desktop servers with one or two drives, or larger rack-mounts with up to eight drives. Configurations will vary depending on any RAID (Redundant Array of Inexpensive Disks) configurations deployed, but it’s best to keep the server install on a separate partition from data.

In this screen, you can also load third-party drivers that may be needed for Windows 2012 to recognize connected devices.

Windows then copies the server files to the hard disk, and after they’re installed, Server Core installation is complete. The next screen you will see is the Administrator login window (see Figure 7). Windows will prompt you to create a local Administrator’s password.

Figure 7. Initial local Administrator login

If you’ve worked with Windows Servers before, you’ll notice that the interface changes in Server 2012’s login screen from previous versions of Windows Server. One of the newinterface features is an eyeball icon in the password field (see Figure 8). Clicking it and holding down the left mouse button after entering a password will change the password characters from asterisks to the actual values.

After you log into a Server Core install of Server 2012, all you will see is a command prompt screen—no desktop icons, no Start button, and no Windows Explorer (see Figure 9). Any tasks you perform after install must be done through the command line.

Figure 8. The eyeball icon changes asterisks to text

After the GUI mode install finishes, you’ll see the Ctrl-Alt-Delete page, which pulls up the login screen (see Figure 9). This page is the first introduction to the new Windows 8–style look in Server 2012.

Press Ctrl-Alt-Delete to bring up the local Administrator login screen, as shown in Figure 10.

Figure 9. Windows 8–style login

Figure 10. Administrator login screen

After login, Windows Services loads, personalized settings are established, and you are brought to the Server 2012 desktop. The Server Manager dashboard opens by default (see Figure 2-13). Server Manager has a tile-based interface refreshed from Server 2008 R2. Server Manager and other components of the full desktop interface are explored in
more depth in further posts .

Figure 11. The new Server Manager dashboard

Windows Server Core 2012: installation procedures

Download a Windows Server 2012 evaluation here.

Download a Windows Server 2012 evaluation version here.

Download a Windows Server 2012 evaluation here.

Figure 2. Installation preferences

Next, select the installation mode. For a Server Core install, the selection option is Windows Server 2012 Enterprise (Server Core Installation), as shown in Figure 3. Click Next to continue.

Figure 4. License terms agreement

Figure 5. Select the installation type: Custom for a new install, or Upgrade for upgrading from Server 2008 R2

Figure 8. The eyeball icon changes asterisks to text

Figure 9. The Server Core install interface

Although the interface of Server Core is sparse, you can still perform almost any tasks from the command prompt. For example, install PowerShell by running the command sconfig at the command prompt (see Figure 10). You can also perform administrative duties from the command line—such as joining the server to a domain or workgroup,renaming the server, or configuring networking settings—and other tasks with the Sconfig utility.

Figure 10. Running the Sconfig utility from the command prompt

Important information for x64-based operating systems for windows server 2012

Ensure that you have updated and digitally signed kernel-mode drivers for Windows Server 2012
If you install a Plug and Play device, you may receive a warning if the driver is not digitally signed. If you install an application that contains a driver that is not digitally signed, you will not receive an error during Setup. In both cases, Windows Server 2012 will not load the unsigned driver.
If you are not sure whether the driver is digitally signed, or if you are unable to boot into your computer after the installation, use the following procedure to disable the driver signature requirement. This procedure enables your computer to start correctly, and the unsigned driver will load successfully.
To disable the signature requirement for the current boot process:

Restart the computer and during startup, press F8.
Select Advanced Boot Options.
Select Disable Driver Signature Enforcement.
Boot into Windows® and uninstall the unsigned driver.

For more information, see http://go.microsoft.com/fwlink/?LinkId=66577.

Pre - defined steps before we upgrade to windows Server 2012

Before you install Windows Server 2012, follow the steps in this section to prepare for the installation.

Disconnect UPS devices. If you have an uninterruptible power supply (UPS) connected to your destination computer, disconnect the serial cable before running Setup. Setup automatically attempts to detect devices that are connected to serial ports, and UPS equipment can cause issues with the detection process.
Back up your servers. Your backup should include all data and configuration information that is necessary for the computer to function. It is important to perform a backup of configuration information for servers, especially those that provide network infrastructure, such as Dynamic Host Configuration Protocol (DHCP) servers. When you perform the backup, be sure to include the boot and system partitions and the system state data. Another way to back up configuration information is to create a backup set for Automated System Recovery.
Disable your virus protection software. Virus protection software can interfere with installation. For example, it can make installation much slower by scanning every file that is copied locally to your computer.
Run the Windows Memory Diagnostic tool. You should run this tool to test the RAM on your computer. To use the Windows Memory Diagnostic tool, follow the instructions in the Windows Memory Diagnostic Users Guide (http://go.microsoft.com/fwlink/?LinkId=50362).
Provide mass storage drivers. If your manufacturer has supplied a separate driver file, save the file to a floppy disk, CD, DVD, or Universal Serial Bus (USB) flash drive in either the root directory of the media or the amd64 folder. To provide the driver during Setup, on the disk selection page, click Load Driver (or press F6). You can browse to locate the driver or have Setup search the media.
Be aware that Windows Firewall is on by default. Server applications that must receive unsolicited inbound connections will fail until you create inbound firewall rules to allow them. Check with your application vendor to determine which ports and protocols are necessary for the application to run correctly.

For more information about Windows Firewall, see http://go.microsoft.com/fwlink/?LinkID=84639.

Supported upgrade paths for windows Server 2012

The table below briefly summarizes supported upgrade paths to Windows Server 2012. For more details on upgrade paths, important caveats to upgrade, and additional information about evaluation versions, see http://go.microsoft.com/fwlink/?LinkId=260917.

If you do not see your current version in the left column, upgrading to this release of Windows Server 2012 is not supported.
If you see more than one edition in the right column, upgrade to either edition from the same starting version is supported.

If you are running:	You can upgrade to these editions:
Windows Server 2008 Standard with SP2 or Windows Server 2008 Enterprise with SP2	Windows Server 2012 Standard, Windows Server 2012 Datacenter
Windows Server 2008 Datacenter with SP2	Windows Server 2012 Datacenter
Windows Web Server 2008	Windows Server 2012 Standard
Windows Server 2008 R2 Standard with SP1 or Windows Server 2008 R2 Enterprise with SP1	Windows Server 2012 Standard, Windows Server 2012 Datacenter
Windows Server 2008 R2 Datacenter with SP1	Windows Server 2012 Datacenter
Windows Web Server 2008 R2	Windows Server 2012 Standard

Windows Server 2012 Management Packs

I wanted to put together a list of all recently released MP’s which surround the Windows Server 2012 Operating System release, and the roles and feature MP’s that support it.

I’ll update this as new MP’s release. Last updated 5/30/2013

Management Pack	Download Link
Active Directory	http://www.microsoft.com/en-us/download/details.aspx?id=21357
AD Certificate Services (ADCS)	http://www.microsoft.com/en-us/download/details.aspx?id=34765
AD Federation Services (ADFS)	http://www.microsoft.com/en-us/download/details.aspx?id=19265
AD Rights Management Services (ADRMS)	http://www.microsoft.com/en-us/download/details.aspx?id=34766
DHCP	http://www.microsoft.com/en-us/download/details.aspx?id=39062
File Services	http://www.microsoft.com/en-us/download/details.aspx?id=34970
Hyper-V	http://www.microsoft.com/en-us/download/details.aspx?id=36438
IIS	http://www.microsoft.com/en-us/download/details.aspx?id=34767
MSMQ	http://www.microsoft.com/en-us/download/details.aspx?id=36775
Network Access Protection	http://www.microsoft.com/en-us/download/details.aspx?id=35365
Network Load Balancing	http://www.microsoft.com/en-us/download/details.aspx?id=13302
Power Management	http://www.microsoft.com/en-us/download/details.aspx?id=34806
Print Services	http://www.microsoft.com/en-us/download/details.aspx?id=3290
Remote Access Role	http://www.microsoft.com/en-us/download/details.aspx?id=36496
Remote Desktop Services (RDS)	http://www.microsoft.com/en-us/download/details.aspx?id=35812
Windows Deployment Services	http://www.microsoft.com/en-us/download/details.aspx?id=36817
Windows Operating System	http://www.microsoft.com/en-us/download/details.aspx?id=9296
Windows Server Backup	http://www.microsoft.com/en-us/download/details.aspx?id=36390
Windows Server Clustering	http://www.microsoft.com/en-us/download/details.aspx?id=2268
Windows Server Updates Services (WSUS)	http://www.microsoft.com/en-us/download/details.aspx?id=36784

Management and Tools for Windows Server 2012 R2 and Windows Server 2012

This section contains tool and reference information for IT pros using Windows Server 2012.

Windows PowerShell Module Reference for Windows Server and Client
This topic lists the Windows PowerShell modules included with Windows Server 2012 R2 Preview, Windows 8.1 Preview, Windows Server 2012, and Windows 8. The Windows PowerShell modules in the list support automating the features of those operating systems and provide links to the cmdlet references for each module. These modules enable you to use Windows PowerShell to administer, maintain, configure, and develop new features for Windows Server 2012 R2 Preview, Windows 8.1 Preview, Windows Server 2012, and Windows 8.
Manage Multiple, Remote Servers with Server Manager
The content in this section describes how to use Server Manager in Windows Server 2012 R2 Preview and Windows Server 2012 to manage both local and remote Windows-based servers from desktop computers.
Deploy Remote Server Administration Tools
To ease remote server management, you can download and install Remote Server Administration Tools for Windows 8.1 Preview. Remote Server Administration Tools for Windows 8.1 Preview includes Server Manager, Microsoft Management Console (MMC) snap-ins, consoles, Windows PowerShell cmdlets and providers, and some command-line tools for managing roles and features that run on Windows Server 2012 R2 Preview and Windows Server 2012.
Install and Use Windows PowerShell Web Access
The content in this section describes how to configure and use Windows PowerShell Web Access, a feature that allows a server that is running Web Server (IIS) to act as a Windows PowerShell gateway and provide a web-based Windows PowerShell console to users in your organization.
Getting Started with Windows PowerShell Workflow
The content in this section describes Windows PowerShell Workflow, a feature that lets IT pros and developers leverage the benefits of workflows with the automation capabilities and ease of Windows PowerShell.
Command-Line Reference for Windows Server 2012 R2 Preview and Windows Server 2012
The content in this section describes the command-line tools that enable IT pros to create batch files or scripting tools that automate common management tasks.

Microsoft four Windows Server 2012 editions and features: What you need to know

Editions

Windows Server 2012 has four editions: Foundation, Essentials, Standard and Datacenter.

Specifications	Foundation	Essentials	Standard	Datacenter
Distribution	OEM only	Retail, volume licensing, OEM	Retail, volume licensing, OEM	Volume licensing and OEM
Licensing model	Per server	Per server	Per CPU pair[c] + CAL [d]	Per CPU pair[c] + CAL[d]
Processor chip limit[43]	1	2	64[e]	64[e]
Memory limit	32 GB	64 GB	4 TB	4 TB
User limit	15	25	Unlimited	Unlimited
File Services limits	1 standalone DFS root	1 standalone DFS root	Unlimited	Unlimited
Network Policy and Access Services limits	50 RRAS connections and 10 IAS connections	250 RRAS connections, 50 IAS connections, and 2 IAS Server Groups	Unlimited	Unlimited
Remote Desktop Services limits	20 Remote Desktop Services connections	250 Remote Desktop Services connections	Unlimited	Unlimited
Virtualization rights	N/A	Either in 1 VM or 1 physical server, but not both at once	2 VMs[c]	Unlimited
DHCP role	Yes	Yes	Yes	Yes
DNS server role	Yes	Yes	Yes	Yes
Fax server role	Yes	Yes	Yes	Yes
UDDI Services	Yes	Yes	Yes	Yes
Print and Document Services	Yes	Yes	Yes	Yes
Web Services (Internet Information Services)	Yes	Yes	Yes	Yes
Windows Deployment Services	Yes	Yes	Yes	Yes
Windows Server Update Services	Yes	Yes	Yes	Yes
Active Directory Lightweight Directory Services	Yes	Yes	Yes	Yes
Active Directory Rights Management Services	Yes	Yes	Yes	Yes
Application server role	Yes	Yes	Yes	Yes
Server Manager	Yes	Yes	Yes	Yes
Windows Powershell	Yes	Yes	Yes	Yes
Active Directory Domain Services	Must be root of forest and domain	Must be root of forest and domain	Yes	Yes
Active Directory Certificate Services	Certificate Authorities only	Certificate Authorities only	Yes	Yes
Active Directory Federation Services	Yes	No	Yes	Yes
Server Core mode	No	No	Yes	Yes
Hyper-V	No	No	Yes	Yes

Microsoft four Windows Server 2012 editions and Pricing: What you need to know

Windows Server 2012 delivers a dramatically simplified licensing experience. Shaped by feedback from customers and partners, the new Windows Server licensing approach will help make choosing the right Windows Server easier while delivering the following benefits.

Simple

It’s easier than ever to determine the right Windows Server edition for you. Choose from just four editions of Windows Server 2012, based on the size of your organization and your requirements for virtualization and cloud computing.

Economical

All editions of Windows Server 2012 deliver excellent economics and ROI for your business. For example, Datacenter edition with unlimited virtualization rights provides the benefits of cloud-level scale with predictable, lower costs. Standard edition now offers all of the same enterprise-class features as Datacenter and is differentiated only by virtualization rights.

Cloud-optimized

Businesses today are rapidly adopting a hybrid approach across private and public cloud computing. Windows Server 2012 offers the right edition for you, no matter where you are on your path to the cloud; Datacenter edition for highly virtualized cloud environments, Standard edition for lightly virtualized environments progressing toward cloud, or Essentials edition for an ideal cloud-connected first server.

Edition & Pricing Overview

Edition	Ideal for...	High Level Feature Comparison	Licensing Model	Pricing Open NL(US$)
Datacenter	Highly virtualized private & hybrid cloud environments	Full Windows Server functionality with unlimited virtual instances	Processor + CAL*	$4,809**
Standard	Low density or non-virtualized environments	Full Windows Server functionality with two virtual instances	Processor + CAL*	$882**
Standard	Low density or non-virtualized environments	Full Windows Server functionality with two virtual instances	Processor + CAL*	$882**
Standard	Low density or non-virtualized environments	Full Windows Server functionality with two virtual instances	Processor + CAL*	$882**

*CALs are required for every user or device accessing a server. See the Product Use Rights for details.

**Pricing represents Open No Level (NL) ERP. For your specific pricing, contact your Microsoft reseller.

You can purchase Windows Server 2012 licenses through multiple channels, providing you with optimum flexibility and choice to acquire the software. Learn more about the channels below and determine the option that best meets your needs.

Hyper-V 3.0 Requirements with Windows server 2012

Adding the Hyper-V role to Server 2012 requires some particular server specifications.If you plan to add the Hyper-V role to Server 2012, you need to increase the minimum hardware requirements for Hyper-V.
Deploying Hyper-V in Server 2012 requires:

• A 64-bit AMD-V or Intel-VT virtualization-capable processor.
• At minimum, 4 GB of RAM to run up to four virtual machines. Take note, this memory requirement differs from the minimum memory requirement needed to install only Server 2012. If you plan to run five or more virtual machines, plan on more memory.

Server 2012 Requirements

Server 2012 has specific hardware requirements for installation, despite the edition you are installing. Minimum requirements are:

• 1.4 GHz x64 processor (only 64-bit server architecture is supported)
• 512 MB of RAM
• 32 GB of free disk space
• DVD-ROM
• Super VGA (800 × 600) or higher resolution monitor
• Keyboard
• Mouse or compatible pointing device

Keep in mind, if you are installing Server 2012 on a system with more than 12 GB of RAM, you will need more than 32 GB of disk space for paging, hibernation, and dump files. You also will need more memory if you’re installing over a network. Also, remember these are minimum requirements with no roles added to the installation. For the optimal installation experience, use the best hardware possible, and if you have to bump up any specification and are working within a limited hardware budget, splurge on the most memory you can. Currently, most servers—especially ones targeted to small to midsize businesses—ship by default with at least 2 GB of RAM.

Windows Server 2012 Editions

Windows Server 2012 is currently available in four editions, also known as SKUs (an acronym for “stock keeping units”). As with the last server release—Server 2008 R2 all SKUs are available only in 64-bit; no 32-bit SKUs are available. Microsoft has done away with the Enterprise SKU of Server 2008 R2 in an attempt to streamline versioning and licensing. The four currently available editions are Windows Server 2012 Datacenter, Windows Server 2012 Standard, Windows Server 2012 Essentials, and Windows Server 2012 Foundation.Pricing for each edition can vary, of course, based on the number of servers as well as every user or device accessing the server directly or indirectly. Each user and device requires its own CAL (client access license).

Server 2012 Datacenter

The Datacenter edition is the beefiest offering of Server 2012 and is designed for enterprises. If your organization is heavily dependent on virtualization and cloud deployments, then the Datacenter edition is the best option.High availability is a key advantage with Datacenter because you can hot-add and hot-replace processors as well as hot-replace memory. “Hot” in this context refers to the ability to replace and add these components without needing to shut down the server.Datacenter supports an unlimited number of virtual machines (VMs) running on up to two processors. In addition, Datacenter supports unlimited network and remote access connections; the number of connections is limited only by available network bandwidth and any hardware constraints. This is the edition to go with if your network needs enterprise-class virtualization and high scalability, because you can quickly expand the server to meet the demands of an organization that adds lots of users and resources such as data and devices.Datacenter customers will typically purchase volume licenses. Volume licenses can also be purchased through Microsoft’s Software Assurance program. Licensing costs are based on the size of the business and number of PCs and devices that need to connect to the server. If your organization will use many virtual machines, needs a cloud-ready platform, and has hundreds of clients, your best option is the Datacenter edition.

Server 2012 Standard

The Standard edition of Server 2012 is suited for midsize organizations without heavy virtualization demands and those that run most business applications and systems on-site. Enterprise offers the same features as Datacenter, except you can run only up to two VMs on two processors.

Server 2012 Essentials

Server 2012 Essentials is the server edition suited for smaller organizations (fewer than 25 PCs, devices, and/or end users). This edition does not offer Hyper-V, provides a limited-application server role, and offers no Windows Server Update Services (WSUS).
Essentials can run on a server with up to two processors.

Server 2012 Foundation

Foundation is a small-business edition that comes preinstalled only on servers targeted for the SMB (small to midsize business) market. It’s ideal for small businesses with no more than 15 users. Foundation does not include Hyper-V or Windows Server Update Services. It has partial or limited file services, network policy and access services, and limited remote desktop services. If your organization has existing server licenses and CALs in place for legacy Windows Server, some of that licensing may be honored and applied to a Windows Server 2012 upgrade. Consult Microsoft’s Windows Server 2012 licensing FAQ to determine which licensing model your organization should go with.

What's New in Windows Server 2012

The content in this section describes what's new and changed in Windows Server 2012. This content focuses on changes that will potentially have the greatest impact on your use of this release.

What's New in AD CS and PKI?
Active Directory Certificate Services (AD CS) in Windows Server 2012 provides multiple new features and capabilities over previous versions. This document describes new deployment, manageability, and capabilities added to AD CS in Windows Server 2012.
What's New in Active Directory Domain Services (AD DS)
Active Directory Domain Services (AD DS) in Windows Server 2012 includes new features that make it simpler and faster to deploy domain controllers (both on-premises and in the cloud), more flexible and easier to both audit and authorize access to files with Dynamic Access Control, and easier to perform administrative tasks at scale, either locally or remotely, through consistent graphical and scripted management experiences.
What's New in Active Directory Rights Management Services (AD RMS)?
Active Directory Rights Management Services (AD RMS) is the server role that provides you with management and development tools that work with industry security technologies—including encryption, certificates, and authentication—to help organizations create reliable information protection solutions.
What's New in BitLocker for Windows 8 and Windows Server 2012
BitLocker encrypts the hard drives on your computer to provide enhanced protection against data theft or exposure on computers and removable drives that are lost or stolen.
What's New in BranchCache
BranchCache in Windows Server 2012 and Windows 8 provides substantial performance, manageability, scalability, and availability improvements.
What's New in DFS Namespaces and DFS Replication in Windows Server 2012
DFS Namespaces and DFS Replication in Windows Server 2012 provide new management functionality as well as interoperability with DirectAccess and Data Deduplication.
What's New in DHCP in Windows Server 2012
Dynamic Host Configuration Protocol (DHCP) is an Internet Engineering Task Force (IETF) standard designed to reduce the administration burden and complexity of configuring hosts on a TCP/IP-based network, such as a private intranet.
What's New in DNS
Domain Name System (DNS) services in Windows Server 2012 and Windows 8 are used in TCP/IP networks for naming computers and network services. DNS naming locates computers and services through user-friendly names.
New and changed functionality in File and Storage Services
File and Storage Services provides a number of new management, scalability, and functionality improvements in Windows Server 2012.
What's New in Failover Clustering
Failover clusters provide high availability and scalability to many server workloads. These include file share storage for server applications such as Hyper-V and Microsoft SQL Server, and server applications that run on physical servers or virtual machines.
What's New in File Server Resource Manager
File Server Resource Manager provides a set of features that allow you to manage and classify data that is stored on file servers.
What's New in Group Policy in Windows Server 2012
Group Policy is an infrastructure that enables you to specify managed configurations for users and computers through Group Policy settings and Group Policy Preferences
What's New in Hyper-V
The Hyper-V role enables you to create and manage a virtualized computing environment by using virtualization technology that is built in to Windows Server 2012. Hyper-V virtualizes hardware to provide an environment in which you can run multiple operating systems at the same time on one physical computer, by running each operating system in its own virtual machine.
What's New in IPAM in Windows Server 2012
IP Address Management (IPAM) is an entirely new feature in Windows Server 2012 that provides highly customizable administrative and monitoring capabilities for the IP address infrastructure on a corporate network.
What's New in Kerberos Authentication
The Microsoft Windows Server operating systems implement the Kerberos version 5 authentication protocol and extensions for public key and password-based authentication. The Kerberos authentication client is implemented as a security support provider (SSP) and can be accessed through the Security Support Provider Interface (SSPI).
What's New for Managed Service Accounts
Standalone Managed Service Accounts, which were introduced in Windows Server 2008 R2 and Windows 7, are managed domain accounts that provide automatic password management and simplified SPN management, including delegation of management to other administrators.
What's New in Networking in Windows Server 2012
Discover new networking technologies and new features for existing technologies in Windows Server 2012. Technologies covered include BranchCache, Data Center Bridging, NIC Teaming, and more.
What's New in Remote Desktop Services in Windows Server 2012
The Remote Desktop Services server role in Windows Server 2012 provides technologies that enable users to connect to virtual desktops, RemoteApp programs, and session-based desktops. With Remote Desktop Services, users can access remote connections from within a corporate network or from the Internet.
What's new in Security Auditing
Security auditing is one of the most powerful tools to help maintain the security of an enterprise. One of the key goals of security audits is to verify regulatory compliance.
What’s new in Server Manager
In this blog post, senior Server Manager program manager Wale Martins describes the innovations and value of the new Server Manager. Server Manager in Windows Server 2012 lets administrators manage multiple, remote servers that are running Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003.
What's New in Smart Cards
Smart cards and their associated personal identification numbers (PINs) are an increasingly popular, reliable, and cost-effective form of two-factor authentication. With the right controls in place, a user must have the smart card and know the PIN to gain access to network resources.
What's New in TLS/SSL (Schannel SSP)
Schannel is a Security Support Provider (SSP) that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) Internet standard authentication protocols. The Security Support Provider Interface (SSPI) is an API used by Windows systems to perform security-related functions including authentication.
What's New for Windows Deployment Services for Windows Server 2012
Windows Deployment Services is a server role that enables you to remotely deploy Windows operating systems. You can use it to set up new computers by using a network-based installation.
What’s new in Windows PowerShell 3.0
Windows PowerShell 3.0 includes many new features and improvements in the scripting and automation experience, such as Windows PowerShell Workflow, multiple new features in Windows PowerShell ISE to help make scripting and debugging faster and easier, updatable Help, Windows PowerShell Web Access, and over 2,200 new cmdlets and functions.

Course Outline 70-410: Installing and Configuring Windows Server 2012

Module 1: Deploying and Managing Windows Server 2012

This module introduces the new Windows Server 2012 administrative interface. This module covers the different roles and features that are available with the Windows Server 2012 operating system. It also discusses the various installation and configuration options you can use when deploying and configuring Windows Server 2012.

Lessons

Windows Server 2012 Overview
Overview of Windows Server 2012 Management
Installing Windows Server 2012
Post-Installation Configuration of Windows Server 2012
Introduction to Windows PowerShell

Lab : Deploying and Managing Windows Server 2012

Deploying Windows Server 2012
Configuring Windows Server 2012 Server Core
Managing Servers
Using Windows PowerShell to Manage Servers

After completing this module, students will be able to:

Describe Windows Server 2012.
Describe the management tools available in Windows Server 2012.
Install Windows Server 2012.
Perform post-installation configuration of Windows Server 2012.
Perform basic administrative tasks using Windows PowerShell.

Module 2: Introduction to Active Directory Domain ServicesThis module introduces Active Directory Domain Services (AD DS) in Windows Server 2012. It covers general AD DS infrastructure including forests, trees, schema, Global Catalog, and Operations Masters. It also covers installing and configuring domain controllers.Lessons

Overview of AD DS
Overview of Domain Controllers
Installing a Domain Controller

Lab : Installing Domain Controllers

Installing a Domain Controller
Installing a Domain Controller by Using IFM

After completing this module, students will be able to:

Describe the structure of AD DS.
Describe the purpose of domain controllers.
Explain how to install a domain controller.

Module 3: Managing Active Directory Domain Services ObjectsThis module covers configuring Active Directory objects such as users, groups and computers. The functionality of AD DS administrative tools is addressed, in addition to the configuration of user profiles and the process of delegating permissions to perform AD DS administration.Lessons

Managing User Accounts
Managing Group Accounts
Managing Computer Accounts
Delegating Administration

Lab : Managing Active Directory Domain Services Objects

Delegating Administration for a Branch Office
Creating and Configuring User Accounts in AD DS
Managing Computer Objects in AD DS

After completing this module, students will be able to:

Manage user accounts with graphical tools.
Manage group accounts with graphical tools.
Manage computer accounts.
Delegate permissions to perform AD DS administration.

Module 4: Automating Active Directory Domain Services Administration
This module covers using command-line tools to configure and administer AD DS. It introduces using Windows PowerShell cmdlets for AD DS administration, and using Windows PowerShell to perform bulk AD DS administrative operations.Lessons

Using Command-line Tools for AD DS Administration
Using Windows PowerShell for AD DS Administration
Performing Bulk Operations with Windows PowerShell

Lab : Automating AD DS Administration by Using Windows PowerShell

Creating User Accounts and Groups by Using Windows PowerShell
Using Windows PowerShell to Create User Accounts in Bulk
Using Windows PowerShell to Modify User Accounts in Bulk

After completing this module, students will be able to:

Use command-line tools for AD DS administration.
Use Windows PowerShell cmdlets for AD DS administration.
Perform bulk operations by using Windows PowerShell.

Module 5: Implementing IPv4This module covers Internet Protocol Version 4 (IPv4) addressing.
It details the various IPv4 components, covers subnetting and supernetting, and discusses configuring and general troubleshooting of IPv4 addresses.Lessons

Overview of TCP/IP
Understanding IPv4 Addressing
Subnetting and Supernetting
Configuring and Troubleshooting IPv4

Lab : Implementing IPv4

Identifying Appropriate Subnets
Troubleshooting IPv4

After completing this module, students will be able to:

Describe the TCP/IP protocol suite.
Describe IPv4 addressing.
Determine a subnet mask necessary for subnetting or supernetting.
Configure IPv4 and troubleshoot IPv4 communication.

Module 6: Implementing Dynamic Host Configuration Protocol
This module covers the installation and configuration of DHCP in addition to managing a DHCP database. It also covers security and monitoring of DHCP, including auditing and logging.Lessons

Installing a DHCP Server Role
Configuring DHCP Scopes
Managing a DHCP Database
Securing and Monitoring DHCP

Lab : Implementing DHCP

Implementing DHCP
Implementing a DHCP Relay Agent (Optional Exercise)

After completing this module, students will be able to:

Install the DHCP server role.
Configure DHCP scopes.
Manage a DHCP database.
Secure and monitor the DHCP server role.

Module 7: Implementing Domain Name SystemThis module covers name resolution for Windows Server and clients. It details the installation of a Domain Name System (DNS) server and configuring Active Directory Integrated DNS zones.Lessons

Name Resolution for Windows Client and Servers
Installing and Managing a DNS Server
Managing DNS Zones

Lab : Implementing DNS

Installing and Configuring DNS
Creating Host Records in DNS
Managing the DNS Server Cache

After completing this module, students will be able to:

Describe name resolution for Windows operating system clients and Windows Server servers.
Install and manage DNS Server service.
Manage DNS zones.

Module 8: Implementing IPv6This module covers understanding and implementing IPv6 addressing.
It covers configuration and troubleshooting as well as co-existence with IPv4 using transition technologies.Lessons

Overview of IPv6
IPv6 Addressing
Coexistence with IPv6
IPv6 Transition Technologies

Lab : Implementing IPv6

Configuring an IPv6 Network
Configuring an ISATAP Router

After completing this module, students will be able to:

Describe the features and benefits of IPv6.
Describe IPv6 addressing.
Describe IPv6 coexistence with IPv4.
Describe IPv6 transition technologies.

Module 9: Implementing Local Storage
This module covers the storage configuration options for Windows Server 2012, including managing disks and volumes and implementing file systems. It also covers creating and managing storage pools.Lessons

Overview of Storage
Managing Disks and Volumes
Implementing Storage Spaces

Lab : Implementing Local Storage

Installing and Configuring a New Disk
Resizing Volumes
Configuring a Redundant Storage Space

After completing this module, students will be able to:

Describe the various storage technologies.
Explain how to manage disks and volumes.
Explain how to implement Storage Spaces.

Module 10: Implementing File and Print Services
This module covers securing files, folders and network file shares, in addition to using shadow copies to protect network file shares. It also covers configuring network printing and creating a printer pool.Lessons

Securing Files and Folders
Protecting Shared Files and Folders by Using Shadow Copies
Configuring Network Printing

Lab : Implementing File and Print Services

Creating and Configuring a File Share
Configuring Shadow Copies
Creating and Configure a Printer Pool

After completing this module, students will be able to:

Secure shared files and folders.
Protect shared files and folders by using shadow copies.
Configure network printing.

Module 11: Implementing Group Policy
This module covers using Group Policy to centrally manage and apply configuration settings.Lessons

Overview of Group Policy
Group Policy Processing
Implementing a Central Store for Administrative Templates

Lab : Implementing Group Policy

Configuring a Central Store
Creating GPOs

After completing this module, students will be able to:

Create and manage Group Policy Objects.
Describe Group Policy processing.
Implement a central store for administrative templates.

Module 12: Securing Windows Servers Using Group Policy Objects
Increase security in a Windows Server 2012 infrastructure by using Group Policy Objects, AppLocker, and Windows Firewall.Lessons

Windows Operating Systems Security Overview
Configuring Security Settings
Restricting Software
Configuring Windows Firewall with Advanced Security

Lab : Lab A: Increasing Security for Server Resources

Using Group Policy to Secure Member Servers
Auditing File System Access
Auditing Domain Logons

Lab : Lab B: Configuring AppLocker and Windows Firewall

Configuring AppLocker Policies
Configuring Windows Firewall

After completing this module, students will be able to:

Describe Windows Server operating system Security.
Configure security settings by using Group Policy.
Restrict unauthorized software from running on servers and clients.
Configure Windows Firewall with Advanced Security.

Module 13: Implementing Server Virtualization with Hyper-V
This module describes Microsoft Virtualization technologies. It covers installing and configuring Hyper-V virtual machines, configuring virtual storage, and configuring virtual networks.Lessons

Overview of Virtualization Technologies
Implementing Hyper-V
Managing Virtual Machine Storage
Managing Virtual Networks

Lab : Implementing Server Virtualization with Hyper-V

Installing the Hyper V Role onto a Server
Configuring Virtual Networking
Creating and Configuring a Virtual Machine
Using Virtual Machine Snapshots

After completing this module, students will be able to:

Describe virtualization technologies.
Implement Hyper‑V.
Manage virtual machine storage.
Manage virtual networks.