Applies to LANDesk Management Suite 9.0
This article discusses many topics related to provisioning. It is recommended to read and understand all the Provisioning Basics and Provisioning Tips and Tricks in the Provisioning Launch Page located here:
The specified document was not found.
XP to 7 Migration Scenario
With the emergence of Windows 7 and the end of support announcements by Microsoft migrating from Windows XP to Windows 7 is becoming more and more of an issue in many environments. Many times people want to know what the LANDESK provisioning process can do to help them accomplish that. The answer is: Pretty much all of it.
The problem is that there is so much you can do with it that it can become difficult to design and implement the migration path that you would like. This document attempts to combat much of that problem. It has the migration process broken out into logical steps, and each step will have information and/or 1 or more sample templates that show some of the more common options that can be used to create an end to end migration process. Each template provided here should be completely self contained and modular, meaning where there is more than one way to accomplish a task you should be able to choose which option you would like to use and plug it in with any of the options from the previous and following steps.
If anyone has any steps or samples that they would like to provide please mention that in the comments, or e-mail them to mach6@landesk.com with a clear explanation of what they are/what they do. I believe this article can be a great opportunity to leverage the knowledge and expertise of the Community so we don't all need to recreate the same process.
XP to 7 Migration Steps Overview
I have divided up the XP to 7 migration process into approximately 7 steps. These steps are:
- Capture user profiles from the existing machine
- Get into Windows PE to continue
- Deploy Windows 7 (with HII)
- Post Imaging Customizations (such as join the domain, etc.)
- Install Software
- Detect and install patches
- Deploy the previously captured image
Some of these steps can be moved around, but this basic outline should provide an idea of what challenges need to be overcome, as well as provide an organized method of solving individual problems that work together to form a complete solution, rather than a single overwhelming task.
XP to 7 Solutions and Information
Choose an adventure for each step. If you choose adventure 1a that does not mean you need to stick with 2a, 3a, etc. Each step should allow you to mix and match to custom build the process that will work best for you in your environment. Some steps (in particular 4) can have multiple adventures chosen, depending on your needs.
1 - Capture Profile
Adventure 1a. Using LANDesk Profile Migration
Information:
The specified document was not found.
Sample Template:
Profile Migration Templates for Provisioning in LANDesk 9.0
Adventure 1b. Using Microsoft USMT
Sample Template:
Provisioning - Steps to use User State Migration Tool (USMT) to capture a profile
NOTE: This document was originally written for LDMS 8.7 and may not be current. I have some USMT sample templates that will be tested and released in the near future.
2 - Get into WinPE
Adventure 2a. PXE Boot
Information:
This option requires a PXE Representative to be deployed on each subnet and for every computer that will be migrated to have PXE Boot be the default boot option.
Adventure 2b. VBoot
Sample Template
The specified document was not found.
Note: As of 9.0 SP2 this sample template will no longer be needed, as the reboot action will have a Vboot reboot option. Please read the attached document for important warnings about using Vboot.
3 - Deploy Windows 7 (with HII)
Adventure 3a. Image Deploy
Information:
The specified document was not found.
Sample Template:
Advanced Windows Image Deployment Provisioning Templates - Windows XP, Vista, 7
Adventure 3b. Scripted Install
Sample templates will be coming soon. A fairly simple Scripted Install with HII process has been made possible as of 9.0 SP1. An article will be created in the coming days to show the process. That article will be linked here.
4 - Post Imaging Customizations
Adventure 4a. Install LANDESK Agent
Information:
Create and use a "provisioning agent" for end to end provisioning
Adventure 4b. Join Domain
Information:
Use Join Domain Action
Adventure 4c. Any other custom type actions
Information:
This can be any other action that would need to be done to "customize" the environment. Usually this would be done through a batch file or script, but can also be a series of individual actions. Some examples and best practices will be coming soon, including how to run different customizations depending on the manufacturer/model of the computer.
5 - Install Software
Adventure 5
Information:
Use the distribute software action.
Sample Template:
Deploying Multiple Software Distribution packages at one time, and in a specific order
6 - Detect and Install Patches (use provisioning agent with provisioning Scan and Repair Settings)
Adventure 6
Information:
Detect and Install Patches within Provisioning
How to use Custom Groups to quickly bring a Computer up to date.
7 - Restore profile (must use same method as capture)
Adventure 7 a. Using LANDesk Profile Migration
Information:
The specified document was not found.
Sample Template:
Profile Migration Templates for Provisioning in LANDesk 9.0
Adventure 7b. Using Microsoft USMT
Sample Template:
Provisioning - Steps to use User State Migration Tool (USMT) to capture a profile
NOTE: This document was originally written for LDMS 8.7 and may not be current. I have some USMT sample templates that will be tested and released in the near future.
Conclusion
The documents and sample templates provided should allow for each step of the migration process to be tested independently, and then put together in fully functional master template. If anything is missing, incorrect, or doesn't work please add a comment or e-mail me at mach6@landesk.com.