Windows Server 2012

Successful execution of any task always begins with planning. If your job involves the migration of your organization’s IT infrastructure to Microsoft Windows Server 2012, you wanna prepare both your environment and yourself for this task.

Window Server

This article describes common infrastructure migration scenarios and outlines the steps involved in a typical server-migration process. The article also examines some approaches and tools you can use for assessing the readiness of your environment for migrating to Windows Server 2012. 

Lessons in this Article:

• Planning for Wsus 2012

• Assessing the readiness of your environment

Before you begin

To complete the practice exercises

• You should've some familiarity with the new features and capabilities found in Windows Server 2012. If not, then before continuing take time to browse some of the following sources of information:

• The demo videos available on the Microsoft Server And Cloud Platform page at

• The topic “What’s New in Wsus 2012” and the subtopics linked from that page in the TechNet Library at

• The free ebook “Introducing Windows Server 2012,” which can be downloaded from

• You should've downloaded an evaluation copy of Wsus 2012 from the TechNet Evaluation Center at

• You should've got a server system available for testing purposes that meet the minimum hardware requirements for installing Wsus 2012. This server should also meet the following additional requirements:

• The system hardware should meet the minimum requirements for installing version 7.0 of the Microsoft Assessment and Planning (MAP) Toolkit. For more information about these requirements, see

• The server should've Wsus 2008 R2 SP1 or Wsus 2008 SP2 installed. If needed, you can download an evaluation copy of Wsus 2008 R2 SP1 from the TechNet Evaluation Center at

• The server should be a standalone server belonging to a workgroup.

• The network where the server resides should've Internet connectivity, and the server should be configured with a static IP address, subnet mask, default gateway, and primary and secondary DNS servers that enable the server to access the Internet.

• It's recommended that the server be a physical server (not a virtual machine) for the purposes of performing the exercises in this Article. If you decide, however, to run the server as a virtual machine using Hyper-V on Wsus 2008 R2 SP1, be sure to install the update described in so that you will be able to upgrade the virtual machine’s guest operating system to Windows Server 2012 as required by one of the practice exercises.

• You will also need a client computer that has Microsoft Office 2010 or Office 365 installed for viewing the reports generated by the MAP Toolkit is one of the practice exercises in this Article. 

Lesson 1: Planning for Windows Server 2012 The success of an infrastructure-migration project depends on careful planning combined with meticulous execution. You wanna start by defining the scope of the project so that you know where you wanna end up. Then you wanna lay out a project plan that involves pilot testing to familiarize yourself with the new platform and to identify any potential issues that might arise throughout the migration process. 

A thorough assessment of your existing environment is also necessary to ensure there aren't surprises coming. A methodology needs to be developed to migrate existing servers and roles. Finally, once the migration is underway, continued testing must be performed to ensure everything is happening as planned. After this lesson, you'll be able to do.

• Describe six possible migration scenarios for organizations that wanna take advantage of the new features and capabilities found in Windows Server 2012.

• Understand some of the steps involved in an infrastructure-migration method, including pilot testing, assessment, server migration, and the role and feature migration.

Secure Cloud Computing
turning off android Screen