Kick starting your migration to Windows Server 2012Alex Pubanz, Jesse SunaSenior PFEs, Microsoft

WSV331

Overvieweverything that will be covered in this session

Migrating Active Directory to Windows Server 2012Deploying additional Windows Server 2012 DCs using the new cloning technologyMigrating SYSVOL to DFS-R Migrating File Cluster Resources to Windows Server 2012Getting started with Dynamic Access Control and File Classification

Migrating your Active Directory to Windows Server 2012

Migrating your AD to Windows Server 2012What’s New

Upgrading forests and domainsUsing the new Server Manager

Deploying new replica DCsUsing the new Server Manager

Managing AD DS using AD Administrative CenterPowerShell History ViewerAD Recycle bin GUIFine Grained Password Policy GUI

demo

Deploying the 1st Windows Server 2012 DC

Deploying additional Windows Server 2012 DCs

Deploying Domain ControllersCloning

demo

Deploying additional Windows Server 2012 DCs

Migrating your SYSVOL to DFS-R

Migrating your SYSVOLHow to benefit from DFS-R

Goals of migrationEfficient and scalable synchronizationFlexible scheduling and bandwidth throttlingRemote Differential Compression (RDC)

Global Migration StateUsage of DfsrMig.exe tool to set the Global migration state

Local Migration StateEach domain controller is also at a particular ‘Local migration state’ (local migration state could be either a stable state or a transition state)

Migrating your SYSVOLMigration State Transitions

demo

Migrating Sysvol to DFS-R

Migrating your File Cluster Resources to Windows Server 2012

Windows Server 2012 Cluster improvementsScalability

Windows Server 2008 and Windows Server 2008 R2

16 nodes1,000 virtual machines384 virtual workloads per node

Windows Server 201264 nodes8,000 virtual machines1,024 virtual workloads per node

Windows Server 2012 Cluster improvementsTotal Cost of Ownership

Scalability improvements allow customers to transition more of their physical environmentFailover Clustering feature included in Windows Server 2012 Standard Edition

No more Enterprise Editionoffers both high availability and virtualization capability in a less costly product

Windows Server 2012 Cluster improvementsSMB 3.0

SMB Transparent FailoverAllows file shares to failover to other nodes in the cluster without interruption to client connections (zero downtime)

SMB Multi-channelAllows for aggregation of network bandwidth and network fault tolerance if multiple paths are available between the SMB Client and SMB Server

SMB DirectHigh bandwidth, low latency, uses very little CPU

File Server Cluster MigrationScenarios and Paths

Scenario 1: Purchase new server and storage hardware, install and configure a Windows Server 2012 Failover Cluster and then migrate resourcesScenario 2: Reuse old hardware (Servers + Storage) or purchase new server hardware but use the same storage attached to the source cluster that is being migratedUse built-in migration wizardMigration Paths -

File Server Cluster MigrationBuilt-in Flexibility

Migration can occur between different SKUsMigration can occur between different processor architecturesStatic IP addresses can migrate to DHCP environmentIPv4 resources can migrate into an IPv6 environmentServer CORE (Hyper-V Server) can migrate to a Full version clusterPhysical cluster can migrate to a Guest cluster

Cannot include virtual machinesMigration can occur across routed subnets

File Server Cluster Migration Migration Reports

Pre-Migration ReportDetails resource groupings that can be migrated

Core Cluster Group and Available Storage Group are never eligible for migrationIndicates which groups can be partially migrated and may require additional steps be completed after migration completes

Post-Migration ReportDetails what actually happened during the migrationProvides details about additional steps that need to be completed

demo

Migrating of File Share Cluster Resources to Windows Server 2012

Start using Dynamic Access Control and File Classification

demo

File Classification

Central Access Policies

User claimsUser.Department = Finance

User.Clearance = High

ACCESS POLICY

Applies to: @File.Impact = HighAllow | Read, Write | if (@User.Department == @File.Department) AND

(@Device.Managed == True)

Device claimsDevice.Department = Finance

Device.Managed = True

Resource propertiesResource.Department =

FinanceResource.Impact = High

AD DS File Server

demo

Central Access Policies

Related ContentFind Us Later At the “Microsoft Services Premier Support” stand - Expo area

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the

part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.