SIDE BY SIDE MIGRATION STEPS · PDF fileSIDE BY SIDE MIGRATION STEPS . ... Page 2 2 SUMMARY...

John Johnston, Senior Solutions Architect – SA IT Services

SIDE BY SIDE MIGRATION STEPS

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

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.

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).

3

PREREQUISITES

SCCM 2012 R2

• Functioning Primary Site - http://technet.microsoft.com/en-us/library/gg682077.aspx

• Functioning Distribution Point

• Functioning State Migration Point

WINDOWS 7 OR WINDOWS 8 HOSTS

• Source Host (migrating from)

• Destination Host (migrating to)

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.

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

6

Computer Information” to create a record to associate against the new hardware.

Select “Import Single Computer” in the Import Computer Information Wizard.

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.

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

11

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

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.

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”

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

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

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.”

17

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

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.

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:

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.

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.

28

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

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

32

browse to the location specified in the state migration point properties.

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”

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

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.

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.

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.

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.

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.

47

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

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.

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”

52

Search for the source and destination in the wizard.

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.

56

CONTACT INFORMATION

JOHN JOHNSTON SENIOR SOLUTIONS ARCHITECT

Tel 770-569-2828 [email protected]

COMPANY INFORMATION

SA IT Services

1125 Northmeadow Parkway, Suite 120

Tel 770-569-2828

http://www.saitservices.com

SIDE BY SIDE MIGRATION STEPS · PDF fileSIDE BY SIDE MIGRATION STEPS . ... Page 2 2 SUMMARY...

Documents

Transcript of SIDE BY SIDE MIGRATION STEPS · PDF fileSIDE BY SIDE MIGRATION STEPS . ... Page 2 2 SUMMARY...