Professional Documents
Culture Documents
All information is from Microsoft site purpose is to compile document for better understanding. If its useful please leave a comment. Awais Mirza
Install and Deploy Windows Server 2012 Installing Windows Server 2012
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.] This document provides information about installing the Windows Server 2012 operating system, including any known issues that you may need to work around before starting an installation. It also provides information that you can use to troubleshoot problems that may occur during the installation. For information about serious known issues that you may need to work around after installation is complete, see the release notes, available at the same location as this document. Setup works in several stages. You will be prompted for some basic information, and then Setup will copy files and restart the computer. Setup concludes by presenting a menu for Initial Configuration Tasks, which you can use to configure your server for your specific needs.
Processor
Processor performance depends not only on the clock frequency of the processor, but also on the number of processor cores and the size of the processor cache. The following are the processor requirements for this product:
RAM
The following are the estimated RAM requirements for this product:
Minimum: 512 MB
Minimum: 32 GB
Note
Be aware that 32 GB should be considered an absolute minimum value for successful installation. The system partition will need extra space for any of the following circumstances:
If you install the system over a network. Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files.
Other requirements
You also need to have the following:
DVD drive Super VGA (800 x 600) or higher-resolution monitor Keyboard and Microsoft mouse (or other compatible pointing device) Internet access (fees may apply)
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: 1. 2. 3. 4. 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.
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.
Hyper-V
You should be aware of the following issues affecting Single-Root I/O Virtualization (SR-IOV):
SR-IOV supports only 64-bit guest operating systems, either Windows Server 2012 or 64-bit versions of Windows 8 Release Preview. In addition, SR-IOV requires both hardware and firmware support. If you configure a guest operating system to use SR-IOV and either the hardware or firmware is not supported, the Network tab in Hyper-V Manager will show Degraded (SR-IOV not operational). Contact your system manufacturer to determine if your system supports SR-IOV, as well as the required BIOS version and settings to enable memory and interrupt remapping. Even with the supported hardware and all appropriate firmware, BIOS settings, and network drivers configured, the Network tab in Hyper-V Manager for a selected virtual machine might show Degraded (SR-IOV not operational). In this circumstance, check the event log for event 12607 in Application and Services\Microsoft\Windows\Hyper-V-SynthNic\Admin with this text: VMName Network Adapter ({GUID}) is configured to use SR-IOV but that capability is disabled by policy on this machine. (Virtual Machine ID {GUID}). If this occurs, first check with the system manufacturer to determine if a BIOS update is available. If no update is available, run the following command from an elevated command prompt, and then restart the physical computer: reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Virtualization" /v IOVEnableOverride /t REG_DWORD /d 1
Important
After the computer restarts, you will find event 24012 in the event log, warning you that the system is vulnerable and could experience reduced performance or system instability. Although SR-IOV might function, this warning is valid and you should assign SR-IOV devices only to virtual machines that run trusted workloads (or do not use SR-IOV).
If the Network tab in Hyper-V Manager still shows Degraded (SR-IOV not operational) and you do not find event 12607 in the event log, run the Windows PowerShell commands below from an elevated Windows PowerShell prompt to get further information on the cause:
get-vmhost
If the cause is related to the platform, the properties IovSupport and IovSupportReasons will contain further information.
get-vmswitch * | fl *
If the cause is related to the physical network adapter or driver, the properties IovSupport and IovSupportReasons will contain further information.
get-vmnetworkadapter * | fl *status*
If the cause is related to the virtual network adapter, the properties Status and StatusDescription will contain further information.
Server Manager
If you install a role service or feature using a method other than Server Manager (such as DISM.exe or an Unattend.xml file) and did not install all of its dependencies and then later install a different role service or feature using Server Manager or a Server Manager Windows PowerShell cmdlet, in some cases the original role service or feature will be unintentionally uninstalled. To avoid this, use only Server Manager or Server Manager PowerShell cmdlets to install server roles, role services, and server features. If this has already occurred, use Server Manager (or Server Manager PowerShell cmdlets) to reinstall the item that was uninstalled. After a server has been added to the Server Manager server pool, if a Best Practices Analyzer scan has never been run on the server, Server Manager displays a red Manageability status indicator in the servers thumbnail on the dashboard page. To resolve this issue, run a Best Practices Analyzer scan on servers after adding them to the Server Manager server pool.
Storage
If you use storage spaces that use the parity resiliency type and then install this release of Windows Server 2012, the data in those storage spaces will not be accessible. To avoid this, back up data stored in those storage spaces and delete the storage spaces before installing this release. After installation is complete, re-create the storage spaces and restore the data.
Storage spaces that are not in the healthy state prior to installing this release may never complete repair operations after installation. To avoid this, ensure that repair operations have completed on all storage spaces and they are in the healthy state prior to installation. You can check the health of a storage space with the HealthStatus property reported by the Get-VirtualDisk Windows PowerShell cmdlet. command. If you delete a clustered storage pool, cluster resources which depend on the storage pool will go offline and may become permanently unavailable. To avoid this, only delete a clustered storage pool when it is on a node with the cluster resource for the pool in the online state.
With this option, the standard user interface (the Server Graphical Shell) is not installed; you manage the server using the command line, Windows PowerShell, or by remote methods.
User interface: command prompt (Server Graphical Shell is not installed) Install, configure, uninstall server roles locally: at a command prompt with Windows PowerShell. Install, configure, uninstall server roles remotely: with Server Manager, Remote Server Administration Tools (RSAT), or Windows PowerShell. Microsoft Management Console: not available locally. Desktop Experience: not available. Server roles available:
Active Directory Certificate Services Active Directory Domain Services DHCP Server DNS Server File Services (including File Server Resource Manager) Active Directory Lightweight Directory Services (AD LDS) Hyper-V Print and Document Services Streaming Media Services Web Server (including a subset of ASP.NET) Windows Server Update Server Active Directory Rights Management Server Routing and Remote Access Server
To convert to a Server with GUI installation with Windows PowerShell: follow the steps in the procedure below:
To use Windows PowerShell to convert from a Server Core installation to a Server with a GUI installation
1. 2.
3.
4.
Create a folder to mount a Windows Imaging File (WIM) in with the command mkdir c:\mountdir Determine the index number for a Server with a GUI image (for example, SERVERDATACENTER, not SERVERDATACENTERCORE) using this command at an elevated command prompt: Dism /getwiminfo /wimfile:<drive>:sources\install.wim Mount the WIM file using this command at an elevated command prompt: Dism /mount-wim /WimFile:<drive>:\sources\install.wim /Index:<#_from_step_2> /MountDir:c:\mountdir /readonly Start Windows PowerShell and run this cmdlet:
User interface: standard graphical user interface (Server Graphical Shell). The Server Graphical Shell includes the Metro-style Start screen, but does not include support for Metro-style apps. To enable support for Metro-style apps, install the Desktop Experience feature. Install, configure, uninstall server roles locally: with Server Manager or with Windows PowerShell Install, configure, uninstall server roles remotely: with Server Manager, Remote Server, RSAT, or Windows PowerShell
Microsoft Management Console: installed Desktop Experience: installable with Server Manager or Windows PowerShell To convert to a Server Core installation with Windows PowerShell: run the following cmdlet:
Note
When you change any of these options, you will have to restart the server for the change to take effect.
See the table below for a summary of which selections to make in Server Manager (or cmdlets to use in Windows PowerShell) in order to get a given installation state:
To reach the installation Server Core state in each column installation option
Select these features in Server Manager: none
Run the Windows PowerShell install/uninstall commands with these values for the Name parameter:
none
Server-GuiMgmt-Infra
Server-Gui-MgmtInfra, Server-GuiShell
Features on Demand
In previous versions of Windows, even if a server role or feature was disabled, the binary files for it were still present on the disk, consuming space. In Windows Server 2012, not only can you disable a role or feature, but you can also completely remove its files, a state called disabled with payload removed. To reinstall a role or feature that is disabled with payload removed, you must have access to an installation source.
To completely remove a role or feature, use Remove with the Uninstall-WindowsFeature cmdlet of Windows PowerShell. For example, to completely remove Windows Explorer, Internet Explorer, and dependent components, run the following Windows PowerShell command:
Practical applications
These examples give you an idea of how you can choose the installation option that might be most appropriate for your deployment needs:
Server Core installations require approximately 4 GB less space than a Server with a GUI installation. By using Server Core installations on virtual machines, you can achieve a significant space savings by not having to store the GUI files on the virtual machines disk. Servers often have comparatively large amounts of memory and complex disk arrays, both of which can take a significant amount of time to initialize at startup. Because Server Core installations minimize the number of restarts required for updates, the frequency at which disk arrays and memory must be reinitialized is reduced. Certain server applications have dependencies on certain Windows services, libraries, applications, and files that are not available in Server Core installations, but the administrator wants to take advantage of the reduced need for updating typical of Server Core installations. The Minimal Server Interface offers additional compatibility while still maintaining a reduced system footprint (though to a lesser extent than a Server Core installation). Features on Demand can be used to reduce the footprint for your virtual machine deployments by removing roles and features that will never be deployed in your virtual machines. Depending on the roles and features used in your virtual machines, it is possible to reduce the size by over 1 GB.
Reference table
This table summarizes which features are available locally depending on which installation option you choose.
Windows PowerShell / available Windows .NET Server Manager Microsoft Management Console Control Panel Control Panel applets Windows Explorer Taskbar Notification area Internet Explorer Built-in help system Themes Metro-style Start screen Metro-style apps Windows Media Player not available not available not available not available not available not available not available not available not available not available not available not available not available
available available
available available
available available
not available some available not available not available not available not available not available not available not available
available available available available available available available not available not available
available available
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.] In Windows Server 2012, the Server Core installation option is no longer an irrevocable selection that is made during setup. In Windows Server 2008 R2 and Windows Server 2008, if your requirements changed, there was no way to convert to a full installation or a Server Core installation without completely reinstalling the operating system. An administrator now has the ability to convert between a Server Core installation and a full installation as needed. There are several scenarios in which this capability is especially useful:
An administrator installed and is running a full installation option of Windows Server 2012, but exclusively using the roles that run on a Server Core installation. The administrator can convert the servers to Server Core installations to reduce the image size and increase servicing advantages without having to reprovision all of their servers. An administrator installs a Server Core installation and now needs to make a change or troubleshoot something that is not possible with the remote GUI. The administrator may not know how to make the change from the command line or cannot find a command-line equivalent. The administrator can convert the server to a full installation, perform the changes, and then convert it back to a Server Core installation to reduce the image size and maintain servicing advantages. An administrator wants to use the GUI for all of the initial configuration steps to make the initial configuration experience as easy as possible, yet wants to reduce the image size and maintain the servicing advantages that a Server Core installation provides. The administrator can install a full installation, configure the server as needed, and then convert it to a Server Core installation. An enterprise mandates a single server operating system image, so it cannot use a Server Core installation because it requires two images. Windows Server 2012 integrates the Server Core installation and the full server installation options. Now the enterprise can use a single server operating system image to deploy full installations of Windows Server 2012 and then convert them to Server Core installations to reduce the image size and provide the servicing advantages that it offers.
Requirements
You need a Server Core installation or a full installation of Windows Server 2012. No special hardware is required.
Technical overview
In Windows Server 2008 R2 and Windows Server 2008, the Server Core installation and the full installation options were selections that an administrator made at the time of installation.
Figure 1 Earlier Windows Server installations In Windows Server 8, the installation options are integrated, and three large optional features are provided. An administrator can install or uninstall these options to move between Server Core and full server installations.
intended for IT professionals who are updating operating systems in a commercial environment. This list is subject to change in subsequent releases and may not include every deprecated feature or functionality.
Support for applications that use the NT Token mode configuration of the web agent is removed. Applications are expected to move to Windows Identity Foundation and use the Claims to Windows Token Service to convert a UPN from a SAML token to a Windows token for consumption in the application. Support for Resource Group is removed. (Resource groups are explained at http://technet.microsoft.com/library/cc753670(WS.10).aspx) Support for using Active Directory Lightweight Directory Services (AD LDS) as an authentication store is removed You are required to migrate to the AD FS version in Windows Server 2012. In-place upgrade from AD FS 1.0 or out of box AD FS 2.0 is not supported.
Clustering
The Cluster Automation Server (MSClus) COM application programming interface (API) has been made an optional component called FailoverCluster-AutomationServer which is not installed by default. Cluster programmatic functionality is now provided by the Failover Cluster API and the Failover Cluster WMI provider. The Cluster.exe command-line interface has been made an optional component called FailoverClusterCmdInterface which is not installed by default. Cluster command-line functionality is provided by the Failover Cluster PowerShell cmdlets. Support for 32-bit cluster resource DLLs has been deprecated. Use 64-bit versions instead.
Graphics
Support for hardwire drivers for XDDM has been removed. As a result, XDDM graphics drivers will not load in Windows Server 2012. Instead, you can do any of the following:
Use the WDDM basic display-only driver included in the operating system. Use a WDDM display-only driver provided by a hardware vendor. Use a full WDDM driver provided by a hardware vendor.
Support for native VGA via the PC/AT BIOS is removed. The WDDM basic display-only driver included in the operating system will replace this functionality. In UEFI systems, you may see fewer highresolution (VESA) modes, but there is no other impact.
Hyper-V
VM Chimney (also called TCP Offload) has been removed. The TCP chimney will not be available to guest operating systems. Support for Static VMQ has been removed. Drivers using NDIS 6.3 will automatically access Dynamic VMQ capabilities that are new in Windows Server 2012.
Networking
NetDMA has been removed. Support for Token Rings has been removed.
Server roles
The Role Collector (Ceiprole.exe) and the associated API (Ceiprole.dll) have been removed. To collect telemetry data on server roles, use Server Manager.
SQL Server
Versions of Microsoft SQL Server prior to 7.0 are no longer supported. Computers running Windows Server 2012 that connect to computers running SQL Server 6.5 (or earlier) will receive an error message.
Storage
The Storage Manager for SANs snap-in for MMC has been removed. Instead, manage storage with PowerShell cmdlets and Server Manager. The Storage Explorer snap-in for MMC has been removed. The SCSIport host-bus adapter driver has been removed. Instead, either use a Storport driver or a different host-bus adapter.
Visual Studio
Support for Visual Studio Analyzer 2003 over ODBC, OLEDB, and ADO has been removed.
Windows Help
The Windows Help program (specifically, WinHlp32.exe, the executable file that opens *.hlp help files) has been removed from Windows since Windows Server 2008. Previously, downloadable packages that provide this functionality were made available (see http://support.microsoft.com/kb/917607). Starting with this release, no download will be provided to enable you to view *.hlp files on Windows Server 2012. For this milestone release, Windows Help is also currently unsupported in Windows 8 Release Preview.
Networking
The Network Driver Interface Specification (NDIS) version 5.0, 5.1, and 5.2 APIs are deprecated. New drivers for NDIS 6.0 must be written.
Hyper-V
The WMI root\virtualization namespace is deprecated. The new namespace is root\virtualization\v2. Windows Authorization Manager (AzMan) is deprecated. You may need to use new management tools for virtual machines or redesign the authorization model.
Printing
The line printer daemon protocol (LPR/LPD) is deprecated. Clients that print to a server using this protocol, such as UNIX clients, will not be able to connect or print. Instead, UNIX clients should use IPP. Windows clients can connect to UNIX shared printers using the Windows Standard Port Monitor (see http://support.microsoft.com/kb/246868 for more information).
SMTP
SMTP and the associated management tools are deprecated. Though the functionality is still available in Windows Server 2012, you should begin using System.Net.Smtp. With this API, you will not be able to insert a message into a file for pickup; instead configure Web applications to connect on port 25 to another server using SMTP.
Transport protocols
The Transport Driver Interface (TDI) is deprecated. Use Windows Filtering Platform instead. Layered Service Providers (LSP) are deprecated. Use Windows Filtering Platform instead.
SQL Server
ODBC/OLEDB support for SQL is deprecated for versions beyond SQL Server 7and SQL 2000. Migrate to SQL Native Client (SNAC) to use features provided by SQL Server 2005, SQL Server 2008, and later versions. SQLXMLX is deprecated. Migrate code to use SQLXML.
WMI providers
The WMI provider for Simple Network Management Protocol (SNMP) is deprecated because the SNMP service is being deprecated. The WMI provider for the Win32_ServerFeature API is deprecated. The WMI provider for Active Directory is deprecated. Manage Active Directory with PowerShell cmdlets. The WMI command-line tool (Wmic) is deprecated. Use PowerShell cmdlets instead. The namespace for version 1.0 of WMI is deprecated. Prepare to adapt scripts for a revised namespace.
XML
XML-Data Reduced (XDR) schema elements are deprecated. Migrate Web applications that use this schema to the W3C Standards-compliant XML schema. The XSL pattern feature of MSXML3 is deprecated. Migrate Web applications that use this feature to the W3C Standards-compliant XML Path Language (XPath) feature set.
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.] Windows 8 Release Preview and Windows Server 2012 feature the new Windows Metro style user interface. This topic will help you find and open common management tools, create shortcuts to frequently-used programs, run programs with elevated privileges, and perform common tasks like signing in and out, restarting, and shutting down computers running Windows Server 2012 and Windows 8 Release Preview. Options are available for installing Windows Server 2012 with a minimal user interface well-suited to remote management. For more information, see Windows Server Installation Options. In this topic:
Open the Start screen Shut down or restart the computer Lock the computer or sign out Close a Metro style app Access Settings for the current screen Access Control Panel Access Administrative Tools Create shortcuts Open the Run dialog box Run a program as administrator or as another user Use common IT Pro tools:
Open Server Manager Start Windows PowerShell Open Remote Desktop Connection Open Command Prompt Open Microsoft Management Console (MMC) and snap-ins
Keyboard shortcuts
Use keyboard shortcuts in a Remote Desktop session Use keyboard shortcuts in Hyper-V virtual machines
Press the Windows logo key. In a virtual machine, you can press Ctrl+Esc. Hover the mouse cursor in the upper right corner of the screen, and then click Start. On the desktop, hover the mouse cursor in the lower left corner of the screen, and click when the thumbnail of the Start screen appears.
1. 2.
Hover the mouse cursor in the upper right corner of the screen, and then click Settings. Click Power, and then click Shut down.
1. 2.
Hover the mouse cursor in the upper right corner of the screen, and then click Settings. Click Power, and then click Restart.
On the Start screen, click your user name in the upper right corner, and then click Lock. Alternatively, on the Start screen, press the Windows logo key+L.
On the Start screen, click your user name in the upper right corner, and then click Sign out.
When Windows Metro style apps like Internet Explorer are open but not in use, they are automatically minimized and become inactive, freeing resources for other apps. This functionality is similar to a cell phone, tablet PC, or other mobile computer. It is not necessary to close a Metro style app, but you can follow steps in this section if you want to do so.
With the Metro style app active, hover at the top edge of the screen until the mouse cursor becomes a hand, click and drag the app to the bottom of the screen, and then release.
Press the Windows logo key+i to open the Settings bar for the current screen (for example, Start, the desktop, or a Metro style app). Alternatively, hover the mouse cursor in the upper right corner of the screen, and then click Settings.
You can access Control Panel from the Start screen and from the desktop.
1. 2.
On the desktop, hover the mouse cursor in the upper right corner of the screen, and then click Settings. Click Control Panel.
1. 2. 3. 4.
Open Control Panel. In the Control Panel Search box, type desktop. In the Control Panel Search results, in Display, click Show or hide common icons on the desktop. In Desktop Icon Settings, select Control Panel, and then click OK.
The Administrative Tools folder contains links to many common Microsoft Management Console (MMC) snap-ins, including Computer Management, Event Viewer, and the management tools for installed roles or features.
Tip
The Start screen settings (accessed by pressing the Windows logo key+i on the Start screen) include an option to enable or disable Administrative Tools appearing in search results and on the Start screen. This setting is enabled by default.
In the Server Manager menu bar, click Tools to access the contents of the Administrative Tools folder.
1. 2.
On the Start screen, type Administrative Tools, and in the Search bar, click Settings. In the Settings results, click Administrative Tools.
Tip
If the Show Administrative tools setting is disabled, the Administrative Tools folder and its contents will not
appear in the Settings results. The Show Administrative tools setting is available when you hover the mouse cursor over the upper or lower right edge of the Start screen, and then click Settings.
Open Control Panel, click System and Security, and then click Administrative Tools.
Create shortcuts
1. 2.
In Windows Explorer, navigate to the location of the program for which you want to create a shortcut. Right-click the executable file in the program folder, and then click Create shortcut.
1. 2.
On the Start screen, search for or navigate to the app that you want to pin to the desktop taskbar. Right-click the app tile, and in the app bar, click Pin to taskbar.
1. 2. 3.
Open Windows Explorer. Navigate to the folder where the program that you want to pin to the desktop taskbar is located. Right-click the executable file in the program folder, and then click Pin to Taskbar.
1. 2. 3.
Open Windows Explorer. Navigate to the program or folder that you want to pin to the Start screen. Right-click the executable file or folder, and then click Pin to Start.
On the desktop, press the Windows logo key+R to open the Run dialog box. Alternatively, on the Start screen, type Run, and then press Enter.
1. 2.
On the Start screen, navigate to the app that you want to run as Administrator. Right-click the app tile, and in the app bar, click Run as administrator.
1. 2.
Right-click the executable file in Windows Explorer, or right-click the program shortcut on the desktop. Click Run as administrator.
Do one of the following. Add the Run as a different user command to the app bar by enabling the following Group Policy setting: User Configuration/Administrative Templates/Start Menu and Taskbar/Show "Run as different user" command on Start. To start Local Group Policy Editor, on the Start screen, type gpedit.msc, and then press Enter.
Use the runas command from a command prompt. For more information about how to use the runas command, at a command prompt, type runas /?, and then press Enter.
By default, Server Manager starts when a member of the Administrators group signs in to a computer that is running Windows Server 2012. If Server Manager is not already open, or if administrators have changed Server Manager default settings so that it does not open automatically at sign-in, open Server Manager by using procedures in this section.
Tip
If the Show Administrative tools setting is disabled, the Server Manager tile will not appear on the Start screen.
To run Windows PowerShell as an administrator from the Start screen, right-click the Windows PowerShell tile, and in the app bar, click Run as administrator. To run Windows PowerShell as an administrator from the desktop, right-click the Windows PowerShell shortcut in the taskbar, and then click Run as Administrator.
1. 2.
On the Start screen, type mstsc. In the Search Apps results, click mstsc.
1. 2.
On the desktop, press the Windows logo key+R to open the Run dialog box. In the Run dialog box, type mstsc, and then press Enter.
1. 2.
On the Start screen, type cmd. In the Apps results, click cmd.
1. 2.
On the desktop, press the Windows logo key+R to open the Run dialog box. In the Run dialog box, type cmd, and then press Enter.
1. 2.
On the Start screen, type mmc. In the Apps results, click mmc.
1. 2.
On the desktop, press the Windows logo key+R to open the Run dialog box. In the Run dialog box, type mmc, and then press Enter.
1.
On the Start screen, type the executable file name of a snap-in. Example: Type gpedit.msc.
2.
When the snap-in is displayed in the Apps results, click the tile.
1. 2.
On the desktop, press the Windows logo key+R to open the Run dialog box. Type the executable file name of a snap-in, and then press Enter. Example: Type gpedit.msc.
Tip
Alternatively, you can open a technology-specific snap-in from the Administrative Tools folder. For information about how to access the Administrative Tools folder, see Access Administrative Tools in this topic.
Keyboard shortcuts
This section provides keyboard shortcuts that are unchanged from Windows 7 and Windows Server 2008 R2, and a table of shortcuts that are new for the Windows Metro style user interface in Windows 8 Release Preview and Windows Server 2012.
Note
Keyboard shortcuts require certain settings and environments to work in a Remote Desktop or virtual machine session.
Keyboard shortcuts that are unchanged from Windows 7 or Windows Server 2008 R2
Key
Windows logo key
Dock active window of a desktop app to left half of screen (no effect on Metro style app windows)
Dock active window of a desktop app to right half of screen (no effect on Metro style app windows)
Maximize active desktop app window (no effect on Metro style app windows)
Restore or minimize active desktop app window (no effect on Metro style app windows)
Maximize active desktop app window vertically, maintaining width (no effect on Metro style app windows)
Restore or minimize active desktop app window vertically (no effect on Metro style app windows)
Move active desktop app window to monitor on the left (no effect on Metro style app windows)
Move active desktop app window to monitor on the right (no effect on
arrow
Minimize all non-active windows, restore on second keystroke (no effect on Metro style app windows)
Open or switch to the program located at the specified position on the taskbar (Example: Windows logo key+1 to open first program.)
Open a new or additional session in the program located at the specified position on the taskbar
Open a new or additional session of the program located at the specified position on the taskbar, running as Administrator
Show the desktop, restore on second keystroke (no effect on Metro style app windows)
Lock your computer (if you are connected to a network domain), or switch
Restore minimized windows to the desktop (no effect on Metro style app windows)
Zoom in (Magnifer)
Close Magnifier
Keyboard shortcuts that are new for Windows 8 Release Preview and Windows Server 2012
Key
Windows logo key+spacebar
Opens Narrator
Cycles through Windows Metro style apps and snaps them as they are cycled
Before you connect to a Remote Desktop (also known as RDP) session, you can configure the session to accept Windows key combinations, whether the session is contained within a window, or occupies the full screen.
1.
If the Remote Desktop Connection dialog box is not already open, open it by typing mstsc on the Start screen, and then pressing Enter.
2. 3.
On the Remote Desktop Connection dialog box, click Show Options to display connection setting tabs. In the Keyboard area of the Local Resources tab, select one of the following from the Apply Windows key combinations drop-down list. To apply keyboard shortcuts to a full-screen Remote Desktop session, select Only when using the full screen.
4.
To apply keyboard shortcuts to a Remote Desktop session that is contained within a window, select On the remote computer.
When you are finished configuring other settings for your Remote Desktop session, click Connect to connect to the session and start working, or click Save on the General tab to save your connection settings as an RDP file that you can use for future connections.
Before you start a virtual machine connection, you can apply Windows key combinations to virtual machine connections on a physical host computer by editing the Hyper-V settings for the physical computer in the Hyper-V Manager console.
Note
The setting in this procedure is selected by default if the Hyper-V host computer is running Windows Server 2012. If the host computer is running Windows 8 Release Preview, Windows Server 2008 R2, or Windows Server 2008, you must change the setting to apply Windows key combinations to virtual machine connections.
1.
Open the Hyper-V Manager snap-in if it is not already open. If you are running Remote Server Administration Tools for Windows 8 Release Preview, or you are running Windows Server 2012, open Server Manager, and then open Hyper-V Manager from the Tools menu in Server Manager.
On the Start screen, click Hyper-V Manager. If the Hyper-V Manager tile is not on the Start screen, type all or part of the name, Hyper-V Manager until the Hyper-V Manager tile appears on the Start screen.
2. 3. 4.
In the tree pane, right-click the physical host computer, and then click Hyper-V Settings. In the User area of the navigation pane, click Keyboard to display keyboard shortcut settings. Select Use on the virtual machine to allow new virtual machine connections to accept Windows key combinations from the physical computer. Click OK to save your changes and close the Hyper-V Settings dialog box.
Note
This setting does not apply to virtual machine connections that are already open.