Download Windows Server 2012 Foundation Trial



July 8, 2012 by chrisadmin In this tutorial of the “How to setup a virtual lab environment” video series we will be setting up Windows Server 2012 in VirtualBox. One of the ways I teach myself server related topics is to install a virtual environment and configure it as closely as possible to a real life environment. You can download the 180-day Windows Server 2012 trial here, you find out more about it at Microsoft's Windows Server 2012 site. The trial is available for download as an ISO file for installation directly onto hardware, or as a VHD file for use with Microsoft's Hyper-V virtualisation software.

-->

Applies To: Windows Server 2012 R2, Windows Server 2012

This topic includes information about Graphical Management Tools and Infrastructure, Server Graphical Shell, Desktop Experience, and Media Foundation.

Graphical Management Tools and Infrastructure is the set of features that comprises the difference between a Server Core installation and the Minimal Server Interface option of a Full server installation. Uninstalling this feature will convert a Full server installation to a Server Core installation.

Server Graphical Shell is the same user interface that is installed by default when you choose the “Server with GUI” installation option during Setup. To decrease the servicing requirements of your server while still being able to use Microsoft Management Console (MMC) locally, you can uninstall the Server Graphical Shell using Server Manager, which leaves you with the Minimal Server Interface. The Minimal Server Interface requires Graphical Management Tools and Infrastructure to be installed. For more information about the server installation options, what is included with each, and how to switch between them (as well as information about the Minimal Server Interface and Features on Demand), see Windows Server Installation Options.

The Desktop Experience feature allows you to install a variety of applications and features that are provided in the Windows client operating system on your server that is running a Windows Server operating system. If you are running Windows Server 2012, the following Windows 8 features are installed when you install Desktop Experience:

  • Windows Media Player

  • Video for Windows (AVI support)

  • Windows SideShow

  • Disk Cleanup

  • Sync Center

  • Sound Recorder

  • Character Map

  • Snipping Tool

  • Support for desktop apps

  • Windows Store

If you are running Windows Server 2012 R2, the following Windows 8.1 features are installed when you install Desktop Experience:

  • Windows Media Player

  • Video for Windows (AVI support)

  • Windows SideShow

  • Disk Cleanup

  • Sync Center

  • Sound Recorder

  • Character Map

  • Snipping Tool

  • Support for desktop apps

  • Windows Store

  • PC settings (adds Change PC settings to the Settings charm)

  • The ability to play a slide show on your lock screen

  • Integrated search (searches through the Search charm integrate results from the local computer and the Internet through Bing)

  • View Scanner and Cameras

Important

When you install Desktop Experience in Windows Server 2012 R2, the integrated search is on by default. This feature sends information to Microsoft. You can turn off the integrated search feature with the following steps:

To turn off integrated search

  1. Open the Windows charm bar (WINDOWS+C)

  2. Click Settings, click Change PC Settings, and then click Search & Apps.

  3. In the Use Bing to search online section, move the slider to Off. Alternately, in the Your Search Experience section, select Don’t get personalized results from Bing.

Note

Windows server 2012 r2 trial

The Desktop Experience feature requires that you also install the Graphical Management Tools and Infrastructure and Server Graphical Shell features.

Media Foundation, which includes Windows Media Foundation, the Windows Media Format SDK, and a server subset of DirectShow, provides the infrastructure required for applications and services to transcode, analyze, and generate thumbnails for media files. You can install Media Foundation separately with Server Manager—but if you install the Desktop Experience feature, you must install the Media Foundation feature as well.

Requirements for running Desktop Experience, Media Foundation, or Server Graphical Shell

There are no special hardware or software requirements for using these features.

Note

The following server features and roles require the Server Graphical Shell—they will automatically be disabled if you uninstall the Server Graphical Shell:Remote Desktop for Administration is supported with or without the Server Graphical Shell.There is only partial functionality if the Server Graphical Shell is not installed:

Running Desktop Experience, Media Foundation, or Server Graphical Shell

How do I deploy and configure these features by using Windows PowerShell?

To install Graphical Management Tools and Infrastructure with Windows PowerShell, use the following commands:

Import-Module ServerManager

Install-WindowsFeature Server-Gui-Mgmt-Infra

To install the Server Graphical Shell with Windows PowerShell, use the following commands:

Import-Module ServerManager

Install-WindowsFeature Server-Gui-Shell

To install Desktop Experience with Windows PowerShell, use the following commands:

Import-Module ServerManager

Install-WindowsFeature Desktop-Experience

To install Media Foundation with Windows PowerShell, use the following commands:

Import-Module ServerManager

Install-WindowsFeature Server-Media-Foundation

To uninstall the Server Graphical Shell with Windows PowerShell, use the following commands:

Import-Module ServerManager

Uninstall-WindowsFeature Server-Gui-Shell

How do I deploy and configure these features in a multiserver environment?

All of these features are relevant to a single server at a time.

Can I run these features on virtual machines?

These features function normally on virtual machines with no changes required.

Can I run these features in a clustered environment?

It is possible to run any of these features in a clustered environment, but it is not recommended.

Security considerations for running these features

After installation, these features are designed to be secure by default.

Special considerations for managing these features on the Server Core installation option

These features are not supported on Server Core installations.

See also

-->

Applies To: Windows Server 2012, Windows Server 2012 R2

This document summarizes key information about evaluation versions of Windows Server® 2012, including where to obtain them, the limits on their use, and how to convert them to full retail versions. It also summarizes the supported upgrade paths from previously licensed retail versions of Windows Server to Windows Server 2012.

Evaluation versions of Windows Server 2012

Fully functional time-limited evaluation versions of Windows Server 2012 are available for the following editions:

  • Windows Server 2012 Standard

  • Windows Server 2012 Datacenter

  • Windows Server® 2012 Essentials

Download

These evaluation versions are 64-bit only and can be installed with the Server Core option or the Server with a GUI option. For more information about these installation options, how to convert between them, and how to use the new Minimal Server Interface and Features on Demand, see https://technet.microsoft.com//library/hh831786.

For all editions, you have 10 days to complete online activation, at which point the evaluation period begins and runs for 180 days. During the evaluation period, a notification on the Desktop displays the days remaining the evaluation period (except in Windows Server 2012 Essentials). You can also run slmgr.vbs /dlv from an elevated command prompt to see the time remaining.

Windows Server 2012 Foundation Download

Where to find evaluation versions

You can get evaluation versions by the following methods:

  • Windows Server 2012 Standard; Windows Server 2012 Datacenter: from the TechNet Evaluation Center (https://technet.microsoft.com/evalcenter/hh670538.aspx). These editions are also available as pre-created VHDs for use in virtualized environments.

  • Windows Server 2012 Essentials: from https://go.microsoft.com/fwlink/p/?LinkId=266340

Limits of evaluation versions

All evaluation versions are fully functional during the evaluation period, although booting to Safe mode is not available. The Windows Server 2012 Standard and Windows Server 2012 Datacenter editions come with the activation key pre-installed. After the 180-day evaluation period elapses, the server warns you in various ways depending on the edition:

Windows Server 2012 Standard; Windows Server 2012 Datacenter:

  • The following warning appears on the Desktop: Windows License is expired

  • When you log on to Windows, you are prompted with the following options:

    • Activate now

    • Ask me later

  • The system shuts down every hour.

  • The only updates that can be installed are security updates.

  • Event ID 100 from source WLMS “The license period for this installation of Windows has expired. The operating system will shut down every hour.” appears in the Application log.

Windows Server 2012 Essentials: you receive warnings on the Desktop and on the dashboard, but the server does not shut down.

Converting evaluation versions of Windows Server 2012 to full retail versions

Most evaluation versions can be converted to full retail versions, but the method varies slightly depending on the edition. Before you attempt to convert the version, verify that your server is actually running an evaluation version. To do this, do either of the following:

  1. From an elevated command prompt, run slmgr.vbs /dlv; evaluation versions will include “EVAL” in the output.

  2. From the Start screen, open Control Panel. Open System and Security, and then System. View Windows activation status in the Windows activation area of the System page. Click View details in Windows activation for more information about your Windows activation status.

If you have already activated Windows, the Desktop shows the time remaining in the evaluation period.

If the server is running a retail version instead of an evaluation version, see the “Upgrading previous licensed versions” section of this document for instructions to upgrade to Windows Server 2012.

For Windows Server 2012 Essentials: You can convert to the full retail version by entering a retail, volume license, or OEM key in the command slmgr.vbs.

If the server is running an evaluation version of Windows Server 2012 Standard or Windows Server 2012 Datacenter, you can convert it to a retail version as follows:

  1. If the server is a domain controller, you cannot convert it to a retail version. In this case, install an additional domain controller on a server that runs a retail version and remove AD DS from the domain controller that runs on the evaluation version. For more information, see https://technet.microsoft.com/library/hh994618.aspx.

  2. Read the license terms.

  3. From an elevated command prompt, determine the current edition name with the command DISM /online /Get-CurrentEdition. Make note of the edition ID, an abbreviated form of the edition name. Then run DISM /online /Set-Edition:<edition ID> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula, providing the edition ID and a retail product key. The server will restart twice.

For the evaluation version of Windows Server 2012 Standard, you can also convert to the retail version of Windows Server 2012 Datacenter in one step using this same command and the appropriate product key.

Tip

For more information about Dism.exe, see https://go.microsoft.com/fwlink/?LinkId=192466.

Upgrading previous retail versions of Windows Server to Windows Server 2012

The table below briefly summarizes which already licensed (that is, not evaluation) Windows operating systems can be upgraded to which editions of Windows Server 2012.

Download Windows Server

Note the following general guidelines for supported paths:

  • In-place upgrades from 32-bit to 64-bit architectures are not supported. All editions of Windows Server 2012 are 64-bit only.

  • In-place upgrades from one language to another are not supported.

  • In-place upgrades from one build type (fre to chk, for example) are not supported.

  • If the server is a domain controller, see https://technet.microsoft.com/library/hh994618.aspx for important information.

  • Upgrades from pre-release versions of Windows Server 2012 (such as the Release Candidate) are not supported. Perform a clean installation to Windows Server 2012.

  • Upgrades that switch from a Server Core installation to the Server with a GUI mode of Windows Server 2012 in one step (and vice versa) are not supported. However, after upgrade is complete, Windows Server 2012 allows you to switch freely between Server Core and Server with a GUI modes. For more information about these installation options, how to convert between them, and how to use the new Minimal Server Interface and Features on Demand, see https://technet.microsoft.com/library/hh831786.

  • 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

Per-server-role considerations for upgrading

Download Windows Server 2012 Foundation Trial Download

Even in supported upgrade paths from previous retail versions to Windows Server 2012, certain server roles that are already installed might require additional preparation or actions for the role to continue functioning after the upgrade. The following table summarizes these considerations.

Server role

Upgrade information

Active Directory

  • Active Directory Domain Services (AD DS): Active Directory domains can be upgraded by upgrading the operating system of existing domain controllers or by replacing existing domain controllers with domain controllers that run Windows Server 2012. For more information, see Deploy Active Directory Domain Services (AD DS) in Your Enterprise (https://go.microsoft.com/fwlink/?LinkId=262195).

  • Active Directory Lightweight Directory Services (AD LDS): For more information, see Upgrading from ADAM to AD LDS (https://go.microsoft.com/fwlink/?LinkId=186351).

Active Directory Federation Services (AD FS)

For more information about upgrading AD FS from Windows Server 2008 R2 to Windows Server 2012, see https://technet.microsoft.com/library/jj647765.aspx

Active Directory Rights Management Services (AD RMS)

You can perform an in-place upgrade from either Windows Server 2008 or Windows Server 2008 R2 to Windows Server 2012. After completing upgrade of your operating system for any servers running the AD RMS server role, you will need to run the AD RMS Upgrade wizard to upgrade your AD RMS cluster and ensure consistency. Otherwise, your AD RMS cluster might not be in a consistent state. The only other consideration when upgrading that you should be aware of when upgrading from these versions of the Windows Server operating system is that if the Windows Internal Database (WID) was previously selected for use to support your AD RMS database needs, that configuration will block your upgrade to Windows Server 2012 and require you to take additional steps. To unblock your upgrade to Windows Server 2012 you must first uninstall the AD RMS server role and migrate the existing WID instance to a SQL Server instance. For more information, see https://go.microsoft.com/fwlink/?LinkId=229299.

Fax Server

See https://technet.microsoft.com/library/jj134193.aspx.

File and Storage Services

After you upgrade a Windows Server 2008 R2-based server that has DFS Management installed, you must reinstall the DFS Management Tools on the server. To install the DFS Management Tools, run the following Windows PowerShell cmdlet as an administrator: Install-WindowsFeature RSAT-DFS-Mgmt-Con

You can also use the Add Roles and Features Wizard in Server Manager. On the Features page of the wizard, expand Remote Server Administration Tools, expand Role Administration Tools, expand File Services Tools, and then select the DFS Management Tools check box.

Hyper-V

Shut down and save all virtual machines prior to starting upgrade. For additional information, see https://technet.microsoft.com/library/hh831531

Print and Document Services

See https://technet.microsoft.com/library/jj134150.

Remote Access

Routing and Remote Access Service (RRAS) was a role service in Windows Server operating systems prior to Windows Server 2012 that enabled you to use a computer as an IPv4 or IPv6 router, as an IPv4 network address translation (NAT) router, or as a remote access server that hosted dial-up or virtual private network (VPN) connections from remote clients. Now, that feature has been combined with DirectAccess to make up the Remote Access server role in Windows Server 2012. For information about migration from Windows Server 2008 R2 and other versions prior to Windows Server 2012, see https://technet.microsoft.com/library/hh831423.aspx

Remote Desktop Services

Windows Server® 2008 R2 Remote Desktop Services role services cannot be migrated to Windows Server 2012, however an existing Windows Server 2008 R2 RD Session Host server deployment can be integrated into a Windows Server 2012 RDS deployment. The Windows Server 2012 RD Web Access can be configured to point to an existing Windows Server 2008 R2 RD Session Host server farm. Desktops and RemoteApp programs published on the Windows Server® 2008 R2 RD Session Host server farm can be accessed from a Windows Server 2012 RD Web Access server.The Following steps need to be completed in order to add an existing Windows Server® 2008 R2 RD Session Host server farm to a Windows Server 2012 Remote Desktop Services deployment:

  • Populate the TS Web Access Computers Security Group.

  • Configure Windows Server 2008 R2 Session Host servers with the right certificate to sign RDP files.

  • Pointing a Windows Server 2012 RD Web Access server to a Windows Server® 2008 R2 RD Session Host server farm.

Volume Activation Services

With Active Directory-based Activation, you do not need an additional host server; your existing domain controllers can support activation clients, with the following limitations:

  • Active Directory-based Activation cannot be configured on read-only domain controllers.

  • Active Directory-based Activation cannot be used with non-Microsoft directory services.

  • AD DS must be at the Windows Server 2012 schema level to store activation objects. Domain controllers running earlier versions of Windows Server can activate clients after their schemas have been updated using the Windows Server 2012 version of Adprep.exe. For more information, see What's New in Active Directory Domain Services Installation and Removal.

Web Server (IIS)

No functionality has been removed or changed. Web applications that work in IIS 7.0 run normally in IIS 8.0.

Converting existing Windows Server 2012 versions

At any time after installing Windows Server 2012, you can run Setup to repair the installation (sometimes called “repair in place”) or, in certain cases, to convert to a different edition.

You can run Setup to perform a “repair in place” on any edition of Windows Server 2012; the result will be the same edition you started with.

For Windows Server 2012 Standard, you can convert the system to Windows Server 2012 Datacenter as follows: From an elevated command prompt, determine the current edition name with the command DISM /online /Get-CurrentEdition. Make note of the edition ID, an abbreviated form of the edition name. Then run DISM /online /Set-Edition:<edition ID> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula, providing the edition ID and a retail product key. The server will restart twice.

For Windows Server 2012 Essentials, you can run Setup and convert it to Windows Server 2012 Standard by providing the appropriate retail license key.