PlateSpin Migrate 12 Administration-Workbook - New

Contents
Contents
Lab 1
Connect to the Lab Environment 1
Understanding the Lab Network 1
Exercise 1.1 Log into the Lab Environment 1
If Logging onto TS Cloud 1
If Logging onto VMware Workstation 2
Exercise 1.2 Launch the vSphere Client and Connect to the ESX Server 2
Lab 2
Install PlateSpin Migrate 4
Exercise 2.1 Prepare the Lab Environment 4
Exercise 2.2 Disable User Account Control (UAC) 5
Exercise 2.3 Install Prerequisite Software on the PlateSpin Server 5
Exercise 2.4 Install PlateSpin Migrate 8
Exercise 2.5 Launch the Clients 9
Lab 3
Discover Source Workloads and Migration Targets 11
Exercise 3.2 Discover Target Virtual Host with the Web Client 12
Exercise 3.3 Discover a Windows Source Server 13
Exercise 3.4 Discover a Linux Source Server 13
Lab 4
Configure and Run Migrations 15
Exercise 4.1 Perform an Initial Full Replication of a Windows Workload with the Web Interface 15
Exercise 4.2 Perform an Initial Full Replication of a Linux Workload with the Migrate Client 16
Exercise 4.3 Perform a Test Cutover of a Windows Workload with the Web Interface 18
Exercise 4.4 Perform a Cutover of a Windows Workload with the Web Interface 19
Exercise 4.5 Prepare a Linux Workload for an Incremental Replication with Cutover with the PlateSpin Migrate
Client 19
Exercise 4.6 Perform an Incremental Replication with Cutover of a Linux Workload with the PlateSpin Migrate
Client 20
Exercise 4.7 Clean up your working environment for the next exercise 21
i
PlateSpin Migrate Administration / Workbook
Lab 5
Automate Migrations with the Command Line Interface (CLI) 24
Exercise 5.2 Configure the PlateSpin.Migrate.Console.config File 24
Exercise 5.3 Discover the Target Virtual Host from the Command Line 25
Exercise 5.4 Discover the Source Windows Workload 26
Exercise 5.5 Run a Migration Job from an .INI File 26
Exercise 5.6 Schedule a Migration Job with Windows Scheduler 29
Lab 6
Migrate to Physical Systems and Manage Drivers 32
Exercise 6.1 Register a Physical Machine as a Target 32
Exercise 6.2 Upload Drivers into the PlateSpin Driver Database 33
Task 1 Upload a Windows Driver 33
Task 2 Upload a Linux Driver 34
Exercise 6.3 Inject a Driver into the RAMDisk 36
Lab 7
Generate and Download Diagnostics 38
Exercise 7.1 Generate Diagnostics with the Migrate Client 38
Exercise 7.2 Generate Diagnostics with the Migrate Web Client 38
ii
Connect to the Lab Environment
Lab 1

The lab exercises in this manual guide you through installing and using the product in a lab
environment. The lab environment uses virtual machines to emulate computers in a production
environment.
Understanding the Lab Network

The lab environment provides the following virtual machines, which you use to complete the lab
exercises:
ps-mgmt A Windows 2012 R2 virtual machine hosting the client applications
esxi5 An ESXi 5.1 virtual machine hosting the PlateSpin Server virtual machine and the
Windows and SUSE virtual machines used in migrations during the lab exercises.
Exercise 1.1 Log into the Lab Environment

Training can be held at various locations, and the way to log on varies by location. The following
tasks describe various ways to log onto the training environment.
If Logging onto TS Cloud

1. Log onto the Student Dashboard using the link that was sent to you.
2. Type your name, and click Done.
3. On the left side, click the top HTML link to start a browser-based connection to the VMs in a
VMWare Workstation interface. Please note that the way to release your cursor from any VM
varies by lab setup: either with Ctrl+Alt or with Shift-Alt.
4. Click the esxi5 VM, and then on the VM menu click Power > Power On. Wait until the VM
starts up before proceeding with the next step.
5. Click the ps-mgmt VM, and then on the VM menu click Power > Power On. Wait until the
VM starts up before proceeding with the next step.
6. On the VM menu for ps-mgmt, click Send Ctl-Alt-Del.
1
7. On the login screen, enter your credentials. Your credentials vary by virtual machine and by
lab exercise. For the purpose of this lab exercise, enter the following credentials:
 User Name: Administrator

 Password: Passw0rd
Note
The password includes a numeric zero (0) character in place of the letter “o.” Every time you
use this password, ensure you type a zero (0) character.
If the VM windows is too small, click a tab for a different VM, and then click the VM you want
to log onto.
8. If you get a message about wanting “to find PCs, devices, and content on this network”, click
No.
If Logging onto VMware Workstation

1. In VMware Workstation, click the esxi5 vm, and then on the VM menu click Power > Power
On.
2. In VMware Workstation, click the ps-mgmt vm, and then on the VM menu click Power >
Power On.
3. Hover your cursor over the desktop area of the ps-mgmt virtual machine, and press
Ctrl+Alt+Insert.
4. On the login screen, enter your credentials. Your credentials vary by virtual machine and by
lab exercise.
5. For the ps-mgmt vm, enter the following credentials:
 User Name: Administrator
 Password: Passw0rd
Note
The password includes a numeric zero (0) character in place of the letter “o.” Every time you
use this password, ensure you type a zero (0) character.
No.
Exercise 1.2 Launch the vSphere Client and Connect to the ESX Server
1. On the ps-mgmt vm, double-click the vSphere shortcut on the Desktop.
2. Log onto esxi5 using the following credentials:
 The IP address: 172.17.2.200

 User: root
 Password: Passw0rd (remember, always use a zero)
2
3. If a certificate warning appears, select Ignore.
4. If the Inventory icon appears then select it.
5. Expand 172.17.2.200 using the plus sign “+”
6. In this list you will see the VMs hosted on the ESX server (your ps-esxi5 VM). Keep the
vSphere client open (you can minimize it if you want). You will need to power on and off the
VMs in later labs.
Note
If your cursor gets stuck in the console of the ps-esxi5 VM, press ALT+SHIFT to escape out
of it.
3
Lab 2
Install PlateSpin Migrate

In this lab you install PlateSpin Migrate, and then log in with both the PlateSpin Migrate Client and
the PlateSpin Migrate Web Interface. In this lab you will do the following:
 Prepare the lab environment
 Install prerequisite software
 Install PlateSpin Migrate
 Launch the interfaces
Exercise 2.1 Prepare the Lab Environment

Note that throughout exercises in this lab, sometimes you will be opening and performing the
exercises on the ps-server VM console within the ps-mgmt VM console. Standard keyboard
shortcuts might not work. Also, you might need to use the console scrollbars to see elements on a
window.
1. On the ps-mgmt VM, start the vSphere client and log onto 172.17.2.200. For more
information about starting the vSphere client, see Lab 1, Exercise 1.2.
2. Switch to Inventory view if needed. Right-click ps-server in the vSphere client, and select
Snapshot > Snapshot Manager.
3. Select Start Lab 2, and click Go To.
4. Click Yes, and then click Close.
5. Right-click ps-server, and select Power > Power On from the drop-down menu.
6. If you get a yellow icon in front of the name then do the following:
a. Right-click on the ps-server virtual machine.

b. Select Open Console from the menu.
c. Select I copied it from the choices.
d. Click OK.
7. If not already opened, open the ps-server console by doing the following:
a. Right-click on the ps-server virtual machine.

4
8. On the VM menu in the ps-server VM’s console, click Guest > Send CTRL+ALT+DEL to
bring up the authentication dialog box.
9. Authenticate using the following:
 User: Administrator
No.
Note
Take a moment to scroll down in the vSphere console of the ps-server VM you just opened,
until you see its Windows icon in the task bar. At this point, you have the vSphere console of
the ps-server VM open inside of the VMware Workstation console of the ps-mgmt VM.
Both of these VMs are running Windows Server 2012 R2, so read the instructions carefully to
make sure you perform the requested operations on the right VM.
Exercise 2.2 Disable User Account Control (UAC)

1. On the ps-server VM , scroll down in the console (make sure you’re in the right console) to the
Windows icon in the task bar (you may have to scroll down to see it), click on it, and then
click Control Panel.
2. In the right pane, click User Accounts.
3. In the right pane, click User Accounts.

4. Click Change User Account Control Settings.
5. If needed, drag the slide bar down to the Never Notify setting, and then click OK. However,
for this lab this has already been done for you so you can click Cancel to close the window
and then close the User Accounts window.
Note: On windows 2012 R2, the “never notify” setting effectively disables UAC prompts
although UAC is not completely deactivated until you modify the registry. For the PlateSpin
Migrate installation to function, the “never notify” setting is sufficient. You do not need to
modify the registry. However, the setup program detects and warns you that UAC is
enabled. You can disregard the warning.
Exercise 2.3 Install Prerequisite Software on the PlateSpin Server

Note
Steps 1 through 8 configure access to the Windows 2012 R2 installation DVD to make sure
that .NET Framework 3.5 can be correctly installed in the ps-server VM.
5
1. On the ps-mgmt VM, right-click ps-server in the vSphere client, and select Edit Settings.
2. Click CD/DVD drive 1 on the hardware tab.
3. In the right pane, select Datastore ISO File and then click Browse.
4. Double-click datastore1 > ISOs.
5. Select en_windows_server_2012_r2_with_update_x64_dvd_4065220.iso, and

then click OK.
6. Select Connected and Connect at power on, and then click OK.
7. Open the ps-server console if it is not already open (right-click ps-server and select Open
Console), and then logon with following credentials:
 Note: To display the credentials fields, use your mouse on the Console menu and click
VM > Guest > Send Ctrl+Alt+Del
8. In the ps-server console (make sure you’re in the right console), click File Explorer (you
may have to scroll down to see it), and navigate to D:\sources\sxs. Make a note of this
path. You could also highlight the path, and then right-click and select Copy. You are going to
need this path later in this exercise.
9. Server Manager should have started automatically. If you closed it, open it again via its icon
in the task bar. In Server Manager on the Dashboard, click add roles and features.
10. Click Next until Features is highlighted in the left pane.
11. In the right pane, select the following features, expand to select all the sub-features, and
agree to install any prerequisite features when prompted by clicking Add Features.
 .NET Framework 3.5 Features (all)

 .NET Framework 4.5 Features (all)
 Windows Process Activation Service (all)
 XPS Viewer
12. In the left pane, click Role Services under Web Server Role (IIS). Add the following
required role services along with all their sub-role services as shown, and agree to
install any prerequisites when prompted by clicking Add Features.
 Web Server
 Common HTTP Features
o Default Document
o Directory Browsing
o HTTP Errors
o Static Content
 Health and Diagnostics
 HTTP Logging
6
 Request Monitor
 Performance
 Static Content Compression
 Security
 Requesting Filtering
 Basic Authentication
 IP and Domain Restrictions
 URL Authorization
 Windows Authentication
 Application Development
 .NET Extensibility 3.5
 .NET Extensibility 4.5
 Application Initialization
 ASP.NET 3.5
 ASP.NET 4.5
 ISAPI Extensions
 ISAPI Filters
 Management Tools
 IIS Management Console
 IIS 6 Management Compatibility
o IIS 6 Metabase Compatibility
o IIS 6 Management Console
o IIS 6 Scripting Tools
o IIS 6 WMI Compatibility
 IIS Management Scripts and Tools
13. Click Next.
14. In the next screen, on top, you now see a message that some features need to be installed
from an alternate source path. At the bottom, click the Specify an alternate source path
link and type or paste D:\sources\sxs\. This is typically found on the Windows ISO for your
operating system.
15. Click OK.
16. Click Install and wait until all the roles and features are installed. This might take a few
minutes. (Approx. 5 minutes)
17. Click Close.
18. In the Server Manager on the Manage menu, click Server Manager Properties.
19. Select Do not start Server Manager automatically at logon.
20. Click OK.
7
21. Close Server Manager.
22. In the vSphere Client, back on the ps-mgmt VM, right-click ps-server and select Edit
Settings.
23. Change the CD/DVD drive 1 back to Client Device, and click OK.
Exercise 2.4 Install PlateSpin Migrate

1. Make sure you are in the VMware console for the ps-server VM, open the File Browser via its
icon in the task bar, and browse to C:\PlateSpin Migrate\ClassFiles\Setup.
Double-click to run PlateSpinMigrateSetup-12.0.0.434.exe
2. Click “Run” if you get a Security Warning.
3. Click OK to extract the files to the default location. This may take a minute.
4. Click OK to select English as your default language.
5. Click Next. You can disregard the SQL warning and the UAC warning. You will install the
Express Edition of SQL Server next.
6. Click Next.
7. Select Install SQL Server Express.
8. Click OK.
9. Wait until the installation is finished before proceeding to the next step. (8-10 minute)
10. If the setup program window is not displayed, click the icon on the task bar to bring it in
focus.
11. Click Install PlateSpin Server.
12. Click Next.
13. Accept the license agreement and click Next.
14. Leave the authentication type set to SQL Authentication, and then click Next.
15. Click Validate Credentials, and then click Next.
16. Click Next on the Confirm SQL Configuration window.

17. Select Allow unsecured connections (HTTP) and click Next.
18. Click Next to accept the default destination folder.
19. Click Install. (8-10 minutes)
20. After the PlateSpin Server is installed, click Finish.
21. If the setup program window is not displayed, click the icon on the task bar to bring it in
focus.
22. Click Install PlateSpin Client.
23. Click Next.
24. Accept the License Agreement and click Next.
8
25. Specify any user name and organization name, and then select Anyone who uses this
computer (all users).
26. Click Next.

27. Click Next to accept the default Destination Folder.
28. Click Install.
29. Clear the option to launch the PlateSpin Migrate client, and then click Finish.
30. Close the PlateSpin Migrate setup program.
Exercise 2.5 Launch the Clients

This exercise demonstrates how to access the PlateSpin Migrate Client and the PlateSpin Migrate
Web Interface.
1. On the ps-server VM, click the Windows icon.
2. Click the arrow under the Desktop indicating new applications were installed.
3. Scroll to the right until you see PlateSpin Migrate Client under the PlateSpin Migrate
Client heading.
4. Click PlateSpin Migrate Client.
5. You will receive a prompt to activate PlateSpin Migrate. This has been done for you on a
different snapshot that you will use in the next lab. Click Cancel, and then click Close and
click Close again.
6. Click the X in the upper right corner to close the PlateSpin Migrate Client (make sure you
click on the right X – don’t accidentally close the console to the ps-server VM!). Note that you
can also launch the client from the desktop shortcut.
7. On the Desktop of the ps-server VM, double-click Firefox.
8. In the Address bar, type http://172.17.2.201/Migrate (this is the IP address of the ps-server VM)
9. Enter the following credentials, and then select Remember my credentials and click OK:
10. You will see a link to add your PlateSpin Migrate license. This has been done for on a different
snapshot that you will use in the next lab. You can close the PlateSpin Migrate Web Interface.
11. Close the ps-server console by clicking the X in the upper right corner.
12. With the vSphere client on the ps-mgmt VM, power off the ps-server VM and click Yes when
prompted.
Note
In this lab, you installed the PlateSpin Migrate Server and the PlateSpin Migrate Client on
the ps-server VM, and then you accessed the PlateSpin Migrate Server using that PlateSpin
Migrate Client. In all subsequent exercises however, you will access that same PlateSpin
Migrate Server from the PlateSpin Migrate Client that is already installed for you in the ps-
mgmt VM. We won’t access the ps-server via its console anymore.
9
10
Discover Source Workloads and Migration Targets
Lab 3

In this lab you use the web client to discover the ESX server, the fake physical target, and the Linux
and Windows virtual machines.
In this lab you learn how to do the following:
 Discover a Target Virtual Host
 Discover a Windows Source Server
 Discover a Linux Source Server

Note
The procedure for booting ps-server and w2k8r2 below differs from the procedure for
sles11sp3. You need to select I copied it for ps-server and w2k8r2, and I moved it for
sles11sp3.
1. Ensure you have the vSphere client open on the ps-mgmt VM. For more information about
starting the vSphere client, see Lab 1, Exercise 1.2.
2. Switch to Inventory view if needed. Right-click ps-server in the vSphere client, and select
Snapshot > Snapshot Manager.
3. Select Start Lab 3, and click Go To.
4. Click Yes, and then click Close.
5. Right-click ps-server, and select Power > Power On from the drop-down menu.
a. Right-click the ps-server virtual machine.

d. Click OK.
e. Close the console.
11
7. Right-click the sles11sp3 virtual machine.
8. Select Power > Power On from the drop-down menu.
a. Right-click the sles11sp3 virtual machine.

c. Select I moved it from the choices.
d. Select OK.
10. Right-click the w2k8r2 virtual machine.
11. Select Power > Power On from the drop-down menu.
a. Right-click the w2k8r2 virtual machine.

d. Select OK.
Exercise 3.2 Discover Target Virtual Host with the Web Client
In this exercise and most of the remaining exercises in the Lab Manual, you use the clients installed
on the ps-mgmt VM. This exercise shows you how to use the PlateSpin Migrate Web Interface to
discover a target host.
1. On the Desktop of the ps-mgmt VM, double-click Firefox.
2. In the Address bar, type https://172.17.2.201/Migrate to launch the PlateSpin Migrate Web Interface.
3. Click I Understand the Risks, click Add Exception, and then click Confirm Security
Exception.
4. Enter the following credentials, and then select Remember my credentials and click OK:
 User: Administrator
5. Click Remember Password.
6. On the Targets tab, click Add Target on the right side of the window. You might need to
scroll right to see the button.
7. Specify the following details:
 Type: VMware ESX Server
 IP Address: 172.17.2.200
 Username: root
12
8. Click Add on the right side of the window.
9. Watch as the target is added under the Last Refresh heading to the right of the window. It
should take a few minutes to complete.
Exercise 3.3 Discover a Windows Source Server

This exercise shows you how to use the PlateSpin Migrate Web Interface to discover a Windows
source server.
1. If the PlateSpin Migrate Web Interface is not already open, complete the following steps:
a. Start Firefox on the desktop of the ps-mgmt virtual machine.

b. In the Address bar, enter: http://172.17.2.201/Migrate
c. If prompted, authenticate using the following
2. Click the Dashboard tab.
3. Click Add Workload.
4. Enter IP Address 172.17.2.203
5. Select Windows.
6. Specify the following credentials:
 User Name: a\Administrator
7. Click Test Credentials.
8. Click Add Workload in the lower left pane.

9. On the Workloads tab, click the Adding Workload link.
10. On the Command Details tab you can monitor progress until the workload is added. The
workload should be added in a few minutes.
Exercise 3.4 Discover a Linux Source Server

This exercise shows you how to use the PlateSpin Migrate Client to discover a Linux source server.
13
1. Launch the PlateSpin Migrate Client using the shortcut on the desktop of the ps-mgmt VM.
2. In the lower right corner, double-click on Network Discovery: Enabled to disable

network discovery.
3. On the Actions menu, click Discover Details.
4. For Hostname or IP Address, type 172.17.2.204
5. For Machine Type choose Linux.
6. For Credentials enter the following:
 User Name root
 Password Passw0rd
7. Select Save (Encrypted Locally).
8. Click Discover.
9. Click Hide.
10. Click Close.
11. Click Jobs to track the progress of the discovery.
14
Configure and Run Migrations
Lab 4

In this section, you learn how to do the following:
 Perform a full replication with the Web Interface

 Perform a full replication with the PlateSpin Migrate Client
 Perform a cutover with the Web Interface
 Prepare an incremental replication
 Perform a cutover with the PlateSpin Migrate Client
Exercise 4.1 Perform an Initial Full Replication of a Windows

Workload with the Web Interface
This exercise does a live migration of a Windows 2008 R2 workload to a virtual machine running
on VMware.
1. If the PlateSpin Migrate web interface is not already open, complete the following steps:

2. On the Workloads tab, select W2K8R2.
3. Click Configure Migration.
4. Leave Initial Transfer Method set to Full Replication.
5. At the bottom, click Configure Migration.
6. Under Incremental Recurrence, click Edit, and select Daily.
7. Take a look in the Transfer Method section (don’t make any changes) and realize that you will
perform a block-based replication using the block-based transfer (BBT) driver, for the fastest
replications. This will require a reboot of the source workload, which will be executed during
the Prepare Replication step.
8. Under Replication Network, click Static and then set the following:
 Address: 172.17.2.207
15
 Subnet Mask: 255.255.255.0

 Gateway 172.17.2.2
9. Under Target Workload Settings > Network Connections, change the IP address from
172.17.2.203 to 172.17.2.207
10. Under Target Workload Test Settings > Network Connections, change the IP address
from 172.17.2.203 to 172.17.2.207
Note
In this case you are configuring the Replication Network Settings, the Target Workload
Settings and the Target Workload Test Settings with the same IP address. Note that all three
can be different, depending on needs and limitations of the environment. In our lab the
workload will always come up on the same network as the source, so the only constraint is
that the IP addresses used cannot be the same as the IP address of the source workload
(which will be up and running until the final cutover).
11. At the bottom of the window, click Save & Prepare.
12. Notice the warning about the source workload being rebooted, and click Execute. The
preparation should take about 5 minutes. When done, proceed with step 13.
13. Click Run Migration.
14. Don’t select any of the checkboxes. Click Execute and proceed to step 15.
Note
You don’t select any checkboxes because we don’t want to bring the source down yet. Right
now we are performing the first Full Replication, after which we have the ability to test the
replicated workload any number of times, before doing the final cutover. Until that final
cutover, the source workload has to be up and running to service the business users.
15. The initial replication will start and take about 15 minutes. Proceed to the next exercise so
that you configure both initial replications to run at the same time. Once the job for this initial
replication is complete, review the results to determine the following:
How long did the initial replication take to run? Should be about 15-30 minutes
How much data was transferred in total? Should be about 6.8 GB
Exercise 4.2 Perform an Initial Full Replication of a Linux Workload

with the Migrate Client
In this exercise you will perform a live migration of a SUSE Linux Enterprise Server 11 SP3
workload to a virtual machine running on VMware.
16
1. Switch to the PlateSpin Migrate Client.
2. Click Servers in the left pane.
3. In the far right pane, right-click sles11sp3, and click Refresh Details. Make sure to select
the sles11SP3 VM which is not listed under the ESX-1 hypervisor.
4. Click Refresh, and then when available, click Hide.
5. In the left pane, click Jobs to monitor the job progress. Wait until the details are refreshed
before continuing with the next step.
6. In the Migrate Client, click Servers in the left pane, and then click the New Job icon.
7. Under Source Hostname, select sles11sp3.

8. Under Actions, select Copy Workload.
9. Under Target Hostname, select ESX-1.
10. Click Advanced.
11. Under Job Configuration, click Access.
12. Specify the following credentials for the Source, and then click Test:
 User Name: root
13. Specify the following credentials for the Target, and then click Test:
 User Name: root
14. Select Save (Encrypted Locally) for both credentials.
15. On the Take Control tab, click Configure.
16. On the TCP/IP Settings tab, enter the following details:
 IP address: 172.17.2.208
 Subnet Mask: 255.255.255.0
 Default Gateway: 172.17.2.2
17
17. Click OK.
18. Click OK.
19. Under Network Configuration, click Guest NIC 1
20. On the TCP/IP Settings tab, change the IP address from 172.17.2.204 to 172.17.2.208 and
click OK.
21. Click Start.
22. Click Hide.
23. In the left pane, click Jobs.
24. Click the + sign to expand the job and observe the job details and progress.
25. The initial replication takes about 15 minutes. Once the job is complete, review the results to
determine the following:
How long did the initial replication take to run? Should be about 15-30 minutes
How much data was transferred in total? Should be about 4.8 GB
Exercise 4.3 Perform a Test Cutover of a Windows Workload with the

Web Interface
This exercise shows you how to perform a test cutover of a Windows workload.

2. On the Workloads tab, monitor W2K8R2. The status should be Replicated. If not, then
wait until the status is Replicated.
3. Select the W2K8R2 workload.
4. Click Test Cutover.
5. Leave Shutdown Target Workload unselected and unselect Perform Incremental

Replication
Note
The Perform Incremental Replication option applies to running a new incremental
replication right before the test, to make sure you have all the latest changes replicated from
the source workload to the target workload. Here we disable it to save some time.
18
6. Click Execute.
7. When the status of the workload has changed to User Testing Cutover, open the vSphere
client on the ps-mgmt VM and notice that the W2K8R2_VM is up and running, ready for
testing. You can open the console and do a quick login if desired.
8. Return to the PlateSpin Migrate web interface, and go to the Tasks tab.
9. Click Mark Test Success.
10. Click Execute.

11. Wait until the workload is back in the Replicated state.
Exercise 4.4 Perform a Cutover of a Windows Workload with the Web

Interface
This exercise shows you how to perform a cutover of a Windows workload.

d. In the Address bar, enter: http://172.17.2.201/Migrate
e. If prompted, authenticate using the following
2. On the Workloads tab, monitor W2K8R2. The status should be Replicated. If not, then
wait until the status is Replicated.
3. Select the W2K8R2 workload.
4. Click Run Cutover.
5. Leave Shutdown Source and Perform Incremental Replication selected, and don’t
select any other option.
Note
For the lab, we could again save some time by unselecting Perform Incremental Replication,
but when doing real migrations, it’s crucial to make sure you have the latest deltas before
cutting over. (For testing this is less important.) This is why we leave the option selected now,
even if this is only a lab.
6. Click Execute.
7. At the end of the cutover, the source VM will be powered down, and the target VM
(W2K8R2_VM) will be running in its final configuration. While the cutover happens, you can
continue with Exercise 4.5.
Exercise 4.5 Prepare a Linux Workload for an Incremental Replication

with Cutover with the PlateSpin Migrate Client
This exercise shows you how to prepare a Linux workload for an Incremental replication.
19
1. In the PlateSpin Migrate Client, in the Jobs view, wait until the initial full replication of the
Linux workload is done.
Note
The initial full replication leaves the target workload up and running, allowing you to test it.
After testing, you can choose to do any number of incremental replications without cutting
over, but you have to set up jobs to make this happen. When using the PlateSpin Migrate web
interface, this is all set up automatically. At cutover time, you will execute one final
incremental replication with cutover, as described in Exercises 4.5 and 4.6.
2. In the Servers view, in the far right pane, expand ESX-1, right-click the undiscovered
sles11sp3_VM VM under it, and select Prepare For Synchronization.
3. If needed, provide the credentials for the VMware target and select Save (Encrypted
Locally):
 User Name: root

4. Click Configure to configure the Take Control network. (Preparation requires booting the
workload in the Take Control environment.)
5. On the TCP/IP Settings tab, enter the following details:
 IP address: 172.17.2.208
 Subnet Mask: 255.255.255.0
6. Click OK.
7. Click Prepare.
8. Click Hide and go to the Job view to track the progress of the Take Control event.
9. Wait until the job ends, then proceed to the next exercise.
Exercise 4.6 Perform an Incremental Replication with Cutover of a

Linux Workload with the PlateSpin Migrate Client
This exercise shows you how to perform a cutover of the Linux workload.
20
1. In the PlateSpin Migrate Client, click the Servers view.
2. In the far right target pane, expand ESX-1 so you can see sles11sp3_VM, which now has a
target symbol in its icon.
3. Drag the sles11sp3 source workload (the one not listed under ESX-1) onto the prepared
sles11sp3_VM target under ESX-1, all in the far right pane. This will start the Server
Synchronization Job screen.
4. Under Job Configuration, select Access.
5. If needed, specify the following credentials for the Source, and then click Test and select
Save:
 User Name: root
6. If needed, specify the following credentials for the Target, and then click Test and select
Save:
 User Name: root
7. On the Take Control tab, click Configure.
8. On the TCP/IP Settings tab, enter the following details once more:
 IP address: 172.17.2.208
 Subnet Mask: 255.255.255.0
9. Click OK.
10. Click OK.
11. Under Network Configuration, click Guest NIC 1
12. On the TCP/IP Settings tab, change the IP address from 172.17.2.204 to 172.17.2.208 and
click OK.
13. Click on End States. Don’t make any changes, but note that the source workload will be shut
down. If this was not your final incremental replication (before cutover), you would unselect
this option.
14. Click OK.
15. Click Start.
16. Click Hide, and monitor the progress of the job in the Jobs view.
17. At the end of the cutover, you will find the source VM powered down, and the target VM
running its final configuration.
Exercise 4.7 Clean up your working environment for the next exercise
1. If the PlateSpin Migrate web client is not already open, complete the following steps:
21

2. On the Workloads tab, select the W2K8R2 workload.
3. Click Remove Workload.
4. Keep Preserve Source cleared, select Delete Target VM, and keep Do not remove
components selected in the list.
Note
Keeping Preserve Source cleared makes sure the PlateSpin Migrate Server removes all
information about the workload from its database. We keep Do not remove components
(Controller and BBT driver) selected mainly to save time for this Lab.
5. Click Execute.
6. Back in the PlateSpin Migrate Client, in the Servers view, right-click the sles11sp3_VM
target VM under ESX-1 and select Delete Virtual Machine.
7. For Credentials, if not already provided, type User Name: root and Password: Passw0rd and
click Test.
8. Click Delete.
9. Click Hide and track the progress of the job in the Jobs view.
10. When the job is done, click the Servers view.
11. In the far right pane, right-click ESX-1, and select Undiscover Server.
12. For Credentials, if not already provided, type User Name: root and Password: Passw0rd.
13. Click Undiscover.
14. Click Hide.

15. Switch to the Jobs view to monitor the jobs.
16. After the job is completed, close the PlateSpin Migrate Client.
22
23
Lab 5
Automate Migrations with the Command Line

Interface (CLI)
In this section, you learn how to use the command-line interface to discover a server, run a job
using an .INI file and use Windows scheduler to run a job from a batch file.
 Prepare the Lab Environment
 Configure the PlateSpin.Migrate.Console.config File
 Discover the Target Virtual Host from the Command Line
 Discover the Source Windows Workload form the Command Line
 Run a Migration Job from an .INI File

 Schedule a Migration Job with Windows Scheduler

This exercise prepares the lab environment for the Command-Line Interface lab. You will need only
ps-server and w2k12r2 running for this lab.
1. In the vSphere Client, right-click w2k8r2 and select Power > Power On.
Exercise 5.2 Configure the PlateSpin.Migrate.Console.config File

This exercise shows you how to configure the command-line executable to use the correct Migrate
server credentials.
1. On the ps-mgmt virtual machine, with Windows Explorer, browse to the C:\Program
Files(x86)\PlateSpin Migrate Client\CommandLine folder.
2. Open a command prompt by clicking the Windows icon in the task bar, and then click the
Search icon and type cmd, and press Enter.
3. Enter the following command:

cd "C:\Program Files <x86>\PlateSpin Migrate Client\CommandLine "
PlateSpin.Migrate.Console.exe encode /text=Passw0rd
5. Copy the output by completing the following:
a. Right-click the title bar and select Edit > Mark.

b. Click the first character in the encoded output.
24
Automate Migrations with the Command Line Interface (CLI)
c. Press Shift and hold, and click the last character of the encoded output. The encoded
password should be highlighted.
d. Right-click the title bar, and select Edit > Copy.
6. Leave the command line interface open, but switch to Windows Explorer, which should be
open to the C:\Program Files(x86)\PlateSpin Migrate Client\CommandLine folder.
7. Right-click PlateSpin.Migrate.Console.config, and select Open With.
8. Click Try an app on this PC.
9. Click Notepad.
10. In the PlateSpin.Migrate.Console.config file, highlight the encoded_password value in

the following line, which is going to look like a random string of letters similar to the encoded
password you just copied:
<add key="pspassword" value="encoded_password"/>
11. On the edit menu, click Paste.
Note: you must always encode the password.
12. Change the values in the following lines:

<add key="migrateServerURL"
value="https://172.17.2.201/PlateSpinMigrate/"/>
<add key="psuser" value="a\administrator"/>
<add key ="encoded" value="no"/>
Note: in the migrateserverURL you also added an “s” to https in addition to adding the
server IP address. Localhost is correct only if you are running the commands on the
Migrate Server.
13. Save and close the file.
14. Close Notepad.
15. Keep the command line interface open for the remaining labs.
Exercise 5.3 Discover the Target Virtual Host from the Command Line
This exercise shows you how to discover the ESX server using the command-line interface.

PlateSpin.Migrate.Console.exe ?
Note the help provided for the commands when no parameters are entered.
2. Enter the following command

PlateSpin.Migrate.Console.exe discover
Note the required and optional parameter descriptions.
3. Note the values for the following parameters for the ESX host. You will use these in the next
step:
 type - vmware_esx
 userName - root
25
 password - Passw0rd
 machineAddress - 172.17.2.200
PlateSpin.Migrate.Console.exe discover /userName=root /password=Passw0rd
/machineAddress=172.17.2.200 /type=vmware_esx
5. If it is not already open, open the PlateSpin Migrate Client.
6. Click the Jobs view and monitor the progress until the job is finished.
7. Click the Servers view and note that the ESX host and its VMs are discovered.
Exercise 5.4 Discover the Source Windows Workload

This exercise shows you how to discover a Windows server using the command-line interface.

PlateSpin.Migrate.Console.exe discover /username=Administrator
/password=Passw0rd /machineaddress=172.17.2.203 /type=windows
2. If it is not already open, open the PlateSpin Migrate Client.
3. Click the Jobs view and monitor the progress until the job is finished.
Exercise 5.5 Run a Migration Job from an .INI File

This exercise shows you how to configure and run a conversion (migration) job using an .INI file
and how to save the output of the job as a HTML, XML or TXT file
1. Open Windows Explorer.
2. Browse to the C:\Program Files (x86)\PlateSpin Migrate

Client\CommandLine\Sample INI directory.
3. Copy and paste Conversion-Windows.ini, and rename the copy Conversion-lab.ini
4. Open Conversion-lab.ini in Notepad.
5. Modify the values as follows. Note: Entered, selected, changed or new items are bolded. To
retrieve the <path to the first system volume>, open the PlateSpin Migrate Client if it’s not
already open and perform the following steps:
a. In the Servers view, right-click the W2K8R2 workload, click Properties, and then click
the View Source button.
b. Type Ctrl-F to bring up the search text box, and search for “System Reserved”.
c. In the line under the line containing “System Reserved”, select the volume mount path.
This path starts with \\?\ and ends with }.
d. Right-click the selection, and choose Copy. You can now paste this value for
VolumeToCopy in the [Volume1] section.
e. Click the X in the upper right corner to close the “View Source” window.
f. Click Close in the Properties window, and return to Notepad to continue editing your
Conversion-lab.ini file.
26
[Type]
conversion=x2v
[JobConfig]
Default=false
[Transfer]
TransferType=VSSBlockBased
LiveTransferEnabled=true
[Source]
Address=172.17.2.203
UserName=a\administrator
Password=Passw0rd
EndState=Donothing
TakeControl=static/dhcp
TakeControlAddress=
SubnetMask=
DefaultGateway=
DNS=
[TargetContainer]
Address=172.17.2.200
UserName=root
Password=Passw0rd
VirtualNetwork=VM Network
TakeControl=static
TakeControlAddress=172.17.2.207
SubnetMask=255.255.255.0
DefaultGateway=172.17.2.2
[NewMachine]
DisplayName=w2k8r2-2
DataStore=datastore1
ConfigPath=/w2k8r2-2/w2k8r2-2.vmx
InstallTools=true
NumberofCPU=2
Memory=4096MB
HostName=w2k8r2-2
ScsiType=LSILogicSAS
ResourcePool=
Workgroup=
27
Domain=
DomainUserName=
DomainUserPassword=
EndState=VMPowerON
UseThinDisks=true
[EthernetNic1]
DHCPEnabled=false
VirtualNetwork=VM Network
Address=172.17.2.207
SubnetMask=255.255.255.0
DefaultGateway=172.17.2.2
DNS=
[DriveGeneral]
Disk1=/w2k8r2-2/w2k8r2-2.vmdk
Datastore1=datastore1
[Volume1]
VolumeToCopy=<path to the first system volume>
FreeSpace=
MapTo=Disk1
[Volume2]
VolumeToCopy=C:
FreeSpace=
MapTo=Disk1
6. Save the file.
7. Close Notepad.
8. If it is not already open, then open the command prompt and enter the following command:
cd "C:\Program Files (x86)\PlateSpin Migrate Client\CommandLine "
9. Enter the following at the prompt:
PlateSpin.Migrate.Console.exe run
10. Note the available parameters.
11. Run the job like below, with the savejob parameter set. This will check the syntax, but does
not actually run the job. Rather than running it directly, in this lab will schedule the job
execution, in the next section. You should see a “Job Saved“ message.
PlateSpin.Migrate.Console.exe run /job="C:\Program Files (x86)\PlateSpin
Migrate Client\CommandLine\Sample INI\Conversion-lab.ini" /savejob=yes
28
Exercise 5.6 Schedule a Migration Job with Windows Scheduler

This exercise shows you how to use Windows scheduler to schedule and run a job from the
command-line.
1. Open Notepad. You can open Notepad by right-clicking the Desktop and selecting New >
Text Document.
2. Type the following line in Notepad:

"C:\Program Files (x86)\PlateSpin Migrate
Client\CommandLine\PlateSpin.Migrate.Console.exe" run /job="C:\Program
Files (x86)\PlateSpin Migrate Client\CommandLine\Sample INI\Conversion-
lab.ini" /output="C:\PlateSpin Migrate\ClassFiles\joboutput.html"
/format=html
3. Save-as the file on your desktop with the name ScheduledConversion.bat. Note: You need
to change the Save as type to All files.
4. Close Notepad.
5. On the Start menu, click Administrative Tools.

6. Double-click Task Scheduler.
7. In the left pane, right-click Task Scheduler Library and select New Folder.
8. Type Migrations and click OK.
9. Expand Task Scheduler Library, and then click the Migrations folder.
10. In the right pane, click Create Basic Task.
11. Type Migrate Lab, and then click Next.
12. Select One time, and click Next.
13. Specify a time five minutes from the time in the time notification area, and then click Next.
14. Select Start a program, and then click Next.

15. Click Browse and browse to the ScheduledConverison.bat file on your desktop.
16. Click Open.
17. Click Next.
18. Click Finish.
19. Wait a few minutes and return to the PlateSpin Migrate Client. If a command line interface
window pops up, you can close it.
Note
Since it’s easy to make typing mistakes, it’s possible that your command will not run
immediately. An easy way to debug it, is to open a command prompt, navigate to
C:\Users\Administrator\Desktop, and run the ScheduledConversion.bat job manually - but
with the /savejob=yes parameter specified. Once you think all issues are resolved (i.e. when
you get the « Job saved in » notification) you can remove the savejob parameter, and try to
schedule your job again. While debugging, the content of your batch file will look like this :
29
“C:\Program Files (x86)\PlateSpin Migrate

Client\CommandLine\PlateSpin.Migrate.Console.exe" run /job="C:\Program
Files (x86)\PlateSpin Migrate Client\CommandLine\Sample INI\Conversion-
lab.ini" /output="C:\PlateSpin Migrate\ClassFiles\joboutput.html"
/format=html /savejob=yes
20. Monitor the job in the Jobs view. Note: The job should take approximately 20-30 minutes to
complete.
21. Right-click the completed job and click Report.
22. Click Firefox.
23. View and close the report.
24. Open Windows Explorer.
25. Browse to C:\PlateSpin Migrate\ClassFiles\.

26. Double-click joboutput.html to view the output. Note: This file is the same as the report.
27. In the Migrate Client, click the Servers view.
28. Right-click w2k8r2-2 and click Delete Virtual Machine.

29. Type your credentials as follows:
 User Name root

 Password Passw0rd
30. Click Test to make sure your credentials for ESX-1 are correct.
31. Click Delete.
32. When the job has started, click Hide.
33. In the Jobs view monitor the job progress until the job is complete.
34. In the Servers view, in the right-click the W2K8R2 VM (not the one listed under ESX-1) and
select Undiscover Server.
35. Authenticate using the following and click Undiscover
 User: a\Administrator
36. When the job has started, click Hide.
37. In the Jobs view monitor the job progress until the job is completed.
30
31
Lab 6
Migrate to Physical Systems and Manage Drivers

In this exercise, you learn how to do the following:
 Register a physical machine as a target

 Upload drivers into the PlateSpin Driver Database
 Inject a driver into the RAMDisk
Exercise 6.1 Register a Physical Machine as a Target

In this section we will boot a new physical machine using the ISO to register it as a target with
Migrate. We are simulating the physical machine using a VM but the process is the same.
1. In the vSphere Client right-click the fake-physical virtual machine.
2. Select Edit Settings from the menu.
3. Select CD/DVD Drive 1.
4. Select Datastore ISO File.
5. Click Browse.
6. Double-click datastore1.
7. Double-click ISOs.
8. Select bootofx.x2p.iso.
9. Click OK.
10. Select Connect at Power On.
11. Click OK.
Note: You must do steps 15 and 16 within 20 seconds after step 14 or it boots incorrectly. If you
do not complete the next step in 20 seconds, power the VM off and on again, and try again.
12. Right-click the fake-physical virtual machine and select Power > Power On.
13. Right-click the fake-physical virtual machine and select Open Console.
14. If you get a yellow icon in front of the name, then select I copied it and click OK.
15. Click in the console window to make it active.
16. Type ps64 and press Enter.

17. For the PlateSpin Server enter 172.17.2.201
32
18. For the user name enter Administrator
19. For the password enter Passw0rd
20. If prompted to configure the network dynamically using DHCP, enter N
21. For the IP Address enter 172.17.2.205
22. For the Subnet Mask enter 255.255.255.0
23. For the Default gateway enter 172.17.2.2
24. Press Enter for Maximum Transmission Unit (MTU) to accept the default.
25. For the hostname enter fake-physical

26. Press Enter to accept the default PlateSpin Server Network.
27. Wait for the message “Job execution completed, with exit code 0”.
28. Close the fake physical virtual machine console. You might need to press Ctrl+Alt a few
times to release the cursor so you can click the X to close the console.
29. Open the PlateSpin Migrate Client on ps-mgmt virtual machine.
30. After a few minutes you will see the new fake-physical target in the Servers view.
Exercise 6.2 Upload Drivers into the PlateSpin Driver Database

In this exercise, you will upload both Windows and Linux drivers into the Driver Database.
Task 1 Upload a Windows Driver

First, you will upload a driver for Windows.
1. In the PlateSpin Migrate Client, select Tools > Manage Device Drivers.
2. Click Upload Drivers.
3. In the Driver Folder Path field, browse to and select C:\PlateSpin

Migrate\ClassFiles\drivers\EmulexScsi-Win2K3.
4. Click OK.
5. In the right pane, for the OS Types select Windows 2003.
6. For the Languages select English.
7. For the Hardware Manufacturer select Standard.
8. Click Upload.
9. Click Yes to the Device Drivers upload warning dialog.
10. Click OK on the Upload Succeeded message (this may take some time).
11. Click Close.
12. Now search for the driver in the database.
13. For the OS Type select Windows 2003.
33
14. For the Language select English.
15. For the Hardware Manufacturer select Standard.
16. In the box under the Vendor column in the Contains field, type ServerEngines.
17. Note the driver information in the Source column is the path from where you uploaded the
driver.
18. Close the Driver Manager.
Task 2 Upload a Linux Driver

The next task shows you how to upload a Linux driver into the database by creating a package. Note
that commands and paths are case sensitive so enter the text exactly as it is documented.
1. In the vSphere client, right-click sles11sp3, and select Power > Power On.
2. In the vSphere client, right-click sles11sp3, and then click Open Console.
3. Log on as root with the password Passw0rd.
4. Open a terminal window by right-clicking the desktop and selecting Open in Terminal.
5. Mount the ISO using the /mnt/ps directory that was created for you by entering the following
command:
mount -o loop /home/ClassFiles/software/bootofx.x2p.iso /mnt/ps
6. Enter mount to make sure the ISO is mounted. You should see a line at the end of the output
with “/mnt/ps” in it.
7. Copy the package files creation program into a working directory using the following
command:
cp /mnt/ps/tools/PackageModules.tar.gz /home/ClassFiles/Packages
8. Change to the Packages working directory using the following command:
cd /home/ClassFiles/Packages
9. Make sure the Package creation software is in the directory entering the ls command.
10. Extract the software in the compressed package creation file using the following:
tar -xvf PackageModules.tar.gz
11. Enter ls to make sure the software files have been extracted.
12. Enter modinfo cciss
13. Note the path to the driver and the version number.
14. On the Computer menu on sles11sp3, open the Nautilus file browser.
34
15. Click File System, and then browse to /lib/modules/3.0.76-0.11-

default/kernel/drivers/block/
16. Right-click cciss.ko and select Copy.

17. Using Nautilus, browse to /home/ClassFiles/drivers.
18. On the Edit menu, click Paste. The reason you are pasting this file into its own folder is so
you can build a driver package that contains only the cciss.ko driver and not all the drivers
found in the block directory. Also, we will use this driver in the next exercise.
19. Execute the following command to build the driver package (make sure you are in
/home/ClassFiles/Packages)
./PackageModules.sh -d /home/ClassFiles/drivers/ -o cciss-4.6.28-HP-
3.0.76-0.11-default.pkg
Note: You should get a message that the package was created successfully.
Note: You can copy/paste strings into this command after running the following
command in another terminal or terminal tab:
modinfo cciss | grep version
20. Check that the package was created by entering the ls command.
21. Copy the driver package to the Migrate Server for upload into the driver database:
a. Return to the ps-mgmt console.

b. Double-Click the WINSCP icon on the desktop.
c. For the File Protocol select SCP.
d. For the Host Name enter 172.17.2.204 (the sles11sp3 server).
e. For the Port Number leave the default port of 22.
f. For the User Name enter root.
g. For the Password enter Passw0rd.
h. Click Login.
i. If you get a warning dialog, click Yes.
j. In the left window set the directory to C:\PlateSpin Migrate\ClassFiles\drivers.
Note: You need to click on the path in the box above the left panel in order to change it.
k. In the right window set the directory to /home/ClassFiles/Packages.
l. In the right window click cciss-4.6.28-HP-3.0.76-0.11-default.pkg.
m. Drag the pkg file to the left window.
n. Close the WinSCP program, and then click OK.
35
22. In the Migrate Client select Tools > Manage Device Drivers.
23. Select the Linux Drivers tab.
24. Click Upload Drivers.
25. Browse to C:\PlateSpin Migrate\ClassFiles\drivers.
26. Select cciss-4.6.28-HP-3.0.76-0.11-default.pkg.
27. Click Open.
28. Ensure it shows the cciss driver.
29. Click Upload All Drivers.

30. Click Yes on the Device Drivers dialog.
31. Click OK on the Driver Upload Succeeded dialog.
32. Close the Linux Device Driver Uploader window.
33. Enter search criteria by entering cciss in the Driver Name.
34. In the text area under Contains in the column Kernel Version, type 3.0.76
35. Find the driver and see that the Driver Source says “Provided by User”
36. Close the PlateSpin Driver Manager.
Exercise 6.3 Inject a Driver into the RAMDisk

In this exercise, you will inject a driver into the ISO so it is available after booting the RAMDisk.
1. Return to the sles11sp3 console.
2. Make sure the ISO is still mounted on /mnt/ps using the following command:
mount
3. If it is not mounted, then mount it again using the following command:
mount -o loop /home/ClassFiles/software/bootofx.x2p.iso /mnt/ps
4. Change directory to /home/ClassFiles using the following command:
cd /home/ClassFiles
5. Copy the rebuildiso command to the current directory using the following command
(ensure you include the space and period at the end):
cp /mnt/ps/tools/rebuildiso.sh .
6. Enter ls to confirm the file was copied.
36
7. Rebuild the ISO file to include the new drivers in the drivers directory, using the following
command:
./rebuildiso.sh -i ./software/bootofx.x2p.iso -d ./drivers –m64
You should get the message that the ISO was built successfully.
8. Verify the driver is included in the ISO by running the following command:
./rebuildiso.sh –l –m64 –i ./software/bootofx.x2p.iso | grep cciss
The output of the command should look like this:
drivers/ThirdPartyDrivers/cciss.ko
9. Close the sles11sp3 console.
10. In the vSphere client, right click sles11sp3 and select Power > Power Off.
11. Click Yes.
37
Lab 7
Generate and Download Diagnostics

In these exercises, you learn how to generate logs to be used by your Customer Care Representative
to troubleshoot issues:
 Generate Diagnostics with the Migrate Client
 Generate Diagnostics with the Migrate Web Client
Exercise 7.1 Generate Diagnostics with the Migrate Client

1. Start the PlateSpin Migrate Client.
2. Click the Jobs view.
3. Right-click any job, and select Run Diagnostics.
4. Click OK.
5. Click the ZIP file link, and then select Save File.
6. Click OK.
7. Open File Explorer.

8. Browse to the Downloads folder.
9. The ZIP file is located in the Downloads folder. Typically you would upload this file by FTP or
possibly email it to your Customer Support Representative. For the purpose of this exercise,
do nothing.
Exercise 7.2 Generate Diagnostics with the Migrate Web Client

1. Launch the Migrate Web Client with Firefox.
2. Discover the w2k8r2 Windows source server like you did in Exercise 3.3.
3. Click the Workloads tab.
4. Click the link under the Status column for your newly discovered W2K8R2 workload (it
should say “Not Configured”).
5. On the Command Details tab, scroll down and click Generate next to Diagnostics.
6. The status next to the Generate link changes to Prepare for Download. When the status
changes to a Download link, click Download.
7. Click Save File, and then click OK.
38
Generate and Download Diagnostics
8. Open File Explorer.
9. Browse to the Downloads folder.
10. The ZIP file is located in the Downloads folder. Typically you would upload this file by FTP or
possibly email it to your Customer Support Representative. For the purpose of this exercise,
do nothing.
39

PlateSpin Migrate 12 Administration-Workbook - New

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PlateSpin Migrate 12 Administration-Workbook - New

Încărcat de

Drepturi de autor:

Formate disponibile

Contents

Connect to the Lab Environment

Understanding the Lab Network

ps-mgmt A Windows 2012 R2 virtual machine hosting the client applications

Exercise 1.1 Log into the Lab Environment

If Logging onto TS Cloud

2. Type your name, and click Done.

6. On the VM menu for ps-mgmt, click Send Ctl-Alt-Del.

 User Name: Administrator

If Logging onto VMware Workstation

5. For the ps-mgmt vm, enter the following credentials:

 User Name: Administrator

2. Log onto esxi5 using the following credentials:

 The IP address: 172.17.2.200

3. If a certificate warning appears, select Ignore.

4. If the Inventory icon appears then select it.

5. Expand 172.17.2.200 using the plus sign “+”

Install PlateSpin Migrate

 Prepare the lab environment

 Install prerequisite software

 Install PlateSpin Migrate

 Launch the interfaces

Exercise 2.1 Prepare the Lab Environment

3. Select Start Lab 2, and click Go To.

4. Click Yes, and then click Close.

a. Right-click on the ps-server virtual machine.

a. Right-click on the ps-server virtual machine.

9. Authenticate using the following:

Exercise 2.2 Disable User Account Control (UAC)

2. In the right pane, click User Accounts.

3. In the right pane, click User Accounts.

Exercise 2.3 Install Prerequisite Software on the PlateSpin Server

2. Click CD/DVD drive 1 on the hardware tab.

4. Double-click datastore1 > ISOs.

5. Select en_windows_server_2012_r2_with_update_x64_dvd_4065220.iso, and

10. Click Next until Features is highlighted in the left pane.

 .NET Framework 3.5 Features (all)

15. Click OK.

17. Click Close.

19. Select Do not start Server Manager automatically at logon.

20. Click OK.

21. Close Server Manager.

Exercise 2.4 Install PlateSpin Migrate

4. Click OK to select English as your default language.

7. Select Install SQL Server Express.

11. Click Install PlateSpin Server.

12. Click Next.

13. Accept the license agreement and click Next.

15. Click Validate Credentials, and then click Next.

16. Click Next on the Confirm SQL Configuration window.

18. Click Next to accept the default destination folder.

19. Click Install. (8-10 minutes)

20. After the PlateSpin Server is installed, click Finish.

22. Click Install PlateSpin Client.

23. Click Next.

24. Accept the License Agreement and click Next.

26. Click Next.

28. Click Install.

30. Close the PlateSpin Migrate setup program.

Exercise 2.5 Launch the Clients

1. On the ps-server VM, click the Windows icon.

4. Click PlateSpin Migrate Client.

7. On the Desktop of the ps-server VM, double-click Firefox.