SIDE BY SIDE MIGRATION STEPS. John Johnston, Senior Solutions Architect SA IT Services

Transcription

1 SIDE BY SIDE MIGRATION STEPS John Johnston, Senior Solutions Architect SA IT Services

2 TABLE OF CONTENTS CONTENTS Document Properties 1 Author 1 Revision 1 Background 1 Summary 2 Prerequisites 3 SCCM 2012 R2 3 Windows 7 or Windows 8 Hosts 3 Process 4 Host Preparation 4 Destination Preparation 5 Bare Metal Machine 5 Task Sequence Perparation 15 Migration 27 Coclusion 55 Contact Information 56 Company Information 56

3 1 DOCUMENT PROPERTIES AUTHOR John Johnston, Senior Solutions Architect - SA IT Services REVISION 1.0 December 2013 BACKGROUND I work as a Senior Architect that specializes in System Center deployment/integration and optimization as well as various other Microsoft Technologies. Page 1

4 2 SUMMARY This document is intended to show how to prepare, implement, and deploy side by side migration strategies in System Center Configuration Manager 2012 R2 (SCCM 2012 R2) using computer associations in the Admin Control panel and two Windows 8.1 hosts. This strategy can further be used for migration from Windows 7 to Windows 8 (and 8.1). Page 2

5 3 PREREQUISITES SCCM 2012 R2 Functioning Primary Site - Functioning Distribution Point Functioning State Migration Point WINDOWS 7 OR WINDOWS 8 HOSTS Source Host (migrating from) Destination Host (migrating to) Page 3

6 4 PROCESS HOST PREPARATION First step to confirm successful migration of content between source and destination hosts is to ensure that the SCCM 2012 R2 agent is installed on the host machine and the agent is healthy. As seen by the below screenshots, my source machine, identifiable by the broken screen desktop background, has the SCCM 2012 R2 agent installed and is reporting back to a fuctioning Primary Site. Additionally, we can see that that client is healthy in the SCCM 2012 R2 Admin Console. Page 4

7 5 DESTINATION PREPARATION There are two situations we will provide examples for in terms of possible destination machines Bare metal machine not already on the domain Pre-Imaged Domain joined machine BARE METAL MACHINE To bring a bare metal machine into SCCM 2012 R2 and prep it for OS deployment and content migration from the source machine, we need to identify the MAC address that the machine will boot from. After we have documented the MAC address, we create a record in SCCM 2012 R2 Admin Console. Browse to Devices in the Admin Control Panel under the Assets and Compliance section. In the ribbon, select Import Page 5

8 6 Computer Information to create a record to associate against the new hardware. Select Import Single Computer in the Import Computer Information Wizard. Page 6

9 7 Provide a computer name and the MAC address from the destination hardware. We are also going to create a computer association between the source and the newly created destination record. Select Search to locate the source record in SCCM 2012 R2. Page 7

10 Page 8 8

11 Page 9 9

12 10 After locating the source computer, we must identify the parameters that the USMT tool will leverage to capture data on the source machine. There are three options available to use: Capture and restore specified user accounts Capture all user accounts and restore specified accounts Capture and restore specified user accounts Page 10

13 11 For purposes of this demonstration, we will use the Capture and restore specified user accounts option. Page 11

14 12 After completing the USMT selection, the wizard will show the association between the source and destination computer. Finally, add the newly created system to a device collection that we can advertise an OSD task sequence to. Page 12

15 13 After completing the wizard, let s validate that all of the settings we selected have been properly associated in SCCM 2012 R2 Admin Console. Navigate to Assets and Compliance and select Devices Page 13

16 14 In the search field, type the name of the computer we just imported. Notice the record has been created and SCCM is showing that an agent has not been installed on the client. Now browse to User State Migration under Assets and Compliance. Notice the computer association between the source and the destination machine has been created. This association is what provides the restore segment of the task sequence the required information (such as USMT storage location and recovery Page 14

17 15 key) to perform the restore to the new destination machine. TASK SEQUENCE PERPARATION Now that the source and destination machines have been prepared for migration, we can now begin creating our task sequences for migration. I have created two collections; one called Capture USMT data - my source machine will reside here, the other called Install Win 8 (With USMT Restore) my destination Page 15

18 16 machine will reside here. After the collections are populated with the source and destination machines, navigated to Software Library -> Operating Systems -> Task Sequences, right click task sequences and select Create Task Sequence. Page 16

19 17 We are now going to create a new custom task sequence: Page 17

20 18 Give the task sequence a name, for demonstration purposes we will use the name Capture USMT Data. We will also select a boot image. Page 18

21 19 After the task sequence has been created, right click the task sequence and select Edit We will now populate our empty task sequence with the appropriate steps to capture USMT data from any source computer. Each step can be populated by selecting Add at the top of the task sequence editor window; all steps for this procedure will be under Settings and User State sections below Add. Below are the appropriate screenshots for each step: Page 19

22 Page 20 20

23 Page 21 21

24 Page 22 22

25 Page 23 23

26 Page 24 24

27 25 Now that the task sequence has been created, we can now deploy to our Capture USMT Data collection that we created earlier. We are advertising this task sequence as Available for demonstration purposes, however for a production deployment we would traditionally make this Required with an available and expiration date to ensure that it is run on all source machines. Furthermore we will make the following available only to configuration manager clients. All defaults are selected after that. Page 25

28 Page 26 26

29 27 MIGRATION After downloading the latest policy from the SCCM Server, the source machine now shows the Capture USMT Data task sequence under Available Software in the software center. Select Install to initiate the USMT capture. A warning asking you to confirm that you want to install a new operating system on your computer will show up, however this task sequence is nothing more than a capture so select Install Operating System to proceed. Page 27

30 28 Below are some screenshots so you know what to expect when the task sequence is running. Page 28

31 Page 29 29

32 Page 30 30

33 31 To validate that the USMT capture was successful, you can review the scanstate.log in C:\Windows\CCM\Logs\ or you can navigate to your server that holds the state migration point role and Page 31

34 32 browse to the location specified in the state migration point properties. Page 32

35 33 Next, we will create another task sequence that installs an OS on the bare metal destination PC called Install Windows 8 (With USMT Restore). This time we will select Install and existing image package Page 33

36 Page 34 34

37 Page 35 35

38 Page 36 36

39 37 Under the state migration settings, ensure that Capture user settings and files as well as Capture network settings and Capture Microsoft Windows Settings is checked Page 37

40 38. Page 38

41 Page 39 39

42 40 After the task sequence has been created, right click it and select Edit we are going to delete the section labeled Capture File and Settings first. Page 40

43 41 Next we will navigate to the section Restore User Files and Settings, below is what it looks like by default. We have to modify this section with one change to make this task sequence work. Page 41

44 42 **********************Very Important********************* We are capturing and restoring all user profiles including local profiles. When the destination machine creates the new local profiles, a password must be specified in order to successfully create those new local profiles. We do this by checking the Restore local computer profiles and setting a default password for all the newly created profiles. If you fail to do this the restore of the USMT data will fail. Page 42

45 43 Next deploy the task sequence to the collection we created earlier called Install Windows 8 (With USMT Restore) as Available and to make the task sequence available to Configuration Manager Clients, media and PXE so we can PXE boot the destination hardware and install the operating system. Select all Defaults. Page 43

46 44 Now that the task sequence is deployed to the collection containing the destination machine, we can PXE boot the destination and kick off the OSD and USMT restore sequence. Page 44

47 Page 45 45

48 Page 46 46

49 47 After task sequence has completed running, log into destination machine and notice all desktop content and settings have been migrated to new host. Page 47

50 Page 48 48

51 49 In some cases, one team will image systems in bulk and not perform any user data migration until the system is ready to be placed desk side. In this case the task sequence for data capture would be the same. The data restore task sequence will look like the below screenshot. Page 49

52 Page 50 50

53 51 The computer association must be manually created between the host and destination machines. In this situation, the destination has already been joined to the domain and already has the SCCM agent installed on it. The steps to manually create the source and destination association are as follows: Right click User State Migration in Assets and Compliance and select Create Computer Association Page 51

54 52 Search for the source and destination in the wizard. Page 52

55 Page 53 53

56 Page 54 54

57 55 On the User Accounts tab, select Capture and Restore all user account under migration behavior. Only after this association has been completed can you advertise the restore only task sequence to the destination computer. COCLUSION This OSD process can be performed in bulk by using the multicasting technology in the SCCM 2012 R2 distribution point. As long as the task sequence, distribution point, and network infrastructure are configured for multicasting, mass deployment and migration time is decreased dramatically. Page 55

58 56 CONTACT INFORMATION JOHN JOHNSTON SENIOR SOLUTIONS ARCHITECT Tel COMPANY INFORMATION SA IT Services 1125 Northmeadow Parkway, Suite 120 Tel Page 56