Module 1: Module 2: Module 3: Module 4: Module 5: Module 6:

Transcription

1

2 Module 1: Module 2: Module 3: Module 4: Module 5: Module 6:

3

4

5

6

7

8

9

10

11

12 362 Days Remaining Optimistic Estimates Server migration: 200 days Application migration: 300+ days 7/24/

13 No No No Now updates compliance safe haven is the time to act Start Impact Windows 37 critical planning on 2003/R2 updates both your servers released migration Impact will not on and transforming Increased your datacenter today Discontinued physical pass in 2013 a compliance for and Windows audit Server Microsoft Small operations costs support for many virtualized 2003/R2 Business Server applications servers 2003

14 1 Discover 2 Assess 3 Target 4 Migrate

15

16

17

18

19

20

21

22 Migration Between Two Multi-Node Clusters In-Place Migration

23 Source Cluster Node OS Windows Server 2008 SP2 Windows Server 2008 R2 SP1 Windows Server 2012 Windows Server 2012 R2 Target Cluster Node OS Windows Server 2012 R2 Windows Server 2012 R2 Windows Server 2012 R2 Windows Server 2012 R2 Note: The Windows Server 2012 Cluster Migration Wizard requires that the latest service packs be installed on the source clusters. Windows Server 2008 clusters are required to be upgraded to Service Pack 2 prior to migration. Windows Server 2008 R2 clusters are required to be upgraded to Service Pack 1 prior to migration.

24

25

26 not will be re-used

27 Hyper-V VMs / VM Configuration Scale-out File Server CSV Disk Storage Pools, Storage Spaces File Server Physical Disk Cluster Registry Settings DFS-Namespace DHCP DTC Gen App / Script / Service Hyper-V Replication Broker iscsi Target / iscsi Target Disk Proxy isns MSMQ / MSMQ Triggers Network Name Distributed Network Name NFS

28 not SQL Server Exchange Server Print Spooler Remote Desktop Connection Broker DFS-R Volume Shadow Copy Service Tasks Task Scheduler Tasks Cluster Aware Updating (CAU)

29 Please Read Them! Record of Role and Resource copies Highlights any additional steps necessary Shows changes in disk mapping / resource names All Copy Roles Reports are saved in the Reports folder

30

31

32

33 The following WSUS migration scenarios are supported: Windows Server 2012 Standard and Datacenter editions can be used as source or destination servers. Windows Server 2012 Enterprise edition can be used as a source server. Migration between physical operating systems and virtual operating systems. Migration from a source server that is running SQL Server 2005 to a destination server that is running SQL Server 2008 R2 SP1. Migration from a source server that is running Windows Internal Database to a destination server that is running SQL Server 2008 R2 SP1. Migration from a domain to a workgroup or from a workgroup to a domain. However, if the source server is running SQL Server from a remote location, migration from the domain to a workgroup is not supported. The destination server must meet the Windows Server 2012 WSUS role minimum system requirements for hardware and software.

34 Copy WSUS Binaries to Destination Server Migrate Local Users and Groups to Destination Server if applicable Backup WSUS Database on Source Server Restore WSUS Database to Destination Server Change WSUS Server Identity

35

36

37 Uptime Users still connecting Reliability Resources still available Ease of process No onerous administration

38 Windows 2012 R2 Media Domain Controller - Windows Server 2003 or above ( Knowledge of current environment (documentation!)

39

40

41

42

43

44

45

46

47

48

49 Build Virtual Machine in the Cloud Migrating an Existing Virtual Machine

50 Windows Azure Supports VHD File Format Upload Existing VHDs using PS (Add-AzureVHD) Things to Do Before Uploading OS Disk

51 1. Create a place to store your hard disk in Microsoft Azure 2. Prepare your virtual hard disk

52 3. Upload your virtual hard disk PowerShell

53 4. Create the Virtual Machine PowerShell Microsoft Azure Portal

54 On-Premises Virtual Machine Machine Name: SRV1 Memory: 8 GB Cores: 4 Ports: 80/443 for http/https Guest: C:\ Host: C:\VMs\APP-OS.vhd Guest: D:\ Host: D:\VMs\APP-Data.vhd Guest: E:\ Host: E:\VMs\APP-Logs.vhd Migration Steps 1) Upload VHDs Azure PS or other Tools Add-AzureVHD 2) Create VM Configuration with data disks attached Data Disk 1 = APP-Data.vhd Data Disk 2 = App-Logs.vhd New-AzureVMConfig 3) Create VM New-AzureVM 4) Adjust App for Drive Letters 5) Add Endpoint(s) 80, TCP, http 443, TCP, https Cloud Service Name: myapp1.cloudapp.net Deployment Slot Production Virtual Machine Role Name: SRV1 4 Cores 7 GB Ram TCP Endpoints 80 and 443 Guest: C:\ WAStorage\VMs\APP-OS.vhd Guest: E:\ WAStorage\VMs\APP-Data.vhd Guest: F:\ WAStorageVMs\APP-Logs.vhd

55

56

57 TechNet Virtual Labs Deep technical content and free product evaluations Hands-on deep technical labs Free, online, technical courses Download Microsoft software trials today. Find Hand On Labs. Take a free online course. Technet.microsoft.com/evalcenter Technet.microsoft.com/virtuallabs microsoftvirtualacademy.com

58