Client Management Suite

 View Only

Sample Windows 7 Migration Process 

Sep 30, 2011 04:38 PM

Here is an example you could follow to help with your Windows 7 Migrations. I had written this as a base process for my own Migration and it helps to have the plan set in stone! Feel free to copy it, modify and tailor it to your specific migration and this should help at the least!

Example Windows 7 Deployment Process

Preflight checklist

Note: The following sections will be performed by the PC technicians for the following day’s deployments.

  1. Verify names quantity and names of computers scheduled for next day ( can be on a shared calendar).  Send the users a reminder email that they are to be upgraded the next day.

Note: If number is insufficient for expectations make some calls / check lists to see who can be scheduled.

  1. Check applications list for scheduled migrations making sure path and process for installs is known. 
  2. Check computer for name and add to Altiris DS if needed Verify size and % of hard drive in use
  3. Check (Driver DB or HIIS if applicable) to verify if Windows 7 drivers have been captured for specific hardware model.

Note: If the drivers for this model have not been captured, plan on capturing them once computer is reimaged.

  1. Create Post-it for each with username at top and any other information gathered this is important.

(optional / creation of Helpdesk incident)

Customer Hand-off

  1. Customer brings machine to the NOC or is contacted to remind them.
  2. Verify Password for AD and Mail (possibly the same) Explain that post re-image we will assist in changing password but with password we can verify functionality. Store the password in secure location not on network.
  3. Set expectation of when system should be ready and verify preferred method of contact.

Image Procedure

  1. Make a note about the software applications that will need to be installed after Windows 7 is deployed.
  2. Perform Personality capture to package server and name package for the computer name.
  3. Use the Altiris PC Transplant (PCT) utility with the template.  Need to define path to tool or the DS job name.
  4. Pull out hard drive and replace with the (new drive) correct size leaving at least 20% available when possible.
  5. Label HDD that was removed with computer name and a note that it has not been backed up.
  6. Use the Altiris Deployment Console to Image computer
  7. Verify the computer is in the DS Console
  8. Deploy either the x86 or x64 based Windows 7 Image (x86 is to be used for "incompatible" models only).
  9. Manually rename the computer before joining domain.
  10. Follow a naming convention.
  11. (Example) Username7-M for laptops
  12. (Example) Username7 for desktops
  13. If the machine is x64 incompatible model, then; Username7x86
  14. Use Altiris DS job to join computer to domain
  15. Job: Add Local Administrators
  16. When prompted add the user’s name to local admins group
  17. Reboot computer
  18. If the computer needs group specific or department specific software, use Altiris DS Console to run sequential install job
  19. Install specific user applications
  20. Use DS to push applications in the Console.
  21. Find software installation files in the server share for any applications that are not packaged in Altiris.
  22. Restore the personality capture for this computer.
  23. Login with the end user’s credentials
  24. Setup Mail client
  25. Connect the old hard drive to the computer
  26. SATA laptop drives can use SATA to USB Dongle
  27. IDE drives can also use a dongle cable
  28. Desktops should be be able to be connected with a standard cable. 
  29. Copy over user data that was not copied by PCT profile capture. Basically anything in the root of the C: drive that looks like user generated data.
  30. Disconnect hard drive
  31. Start back-up  of original hd with name and day in naming convention. 
  32. Update Spreadsheet with information of drive backed up, which drive it was backed up to, and the date.

Delivery Process.

  1. Contact user to return computer.
  2. Review with end user the applications and data migrated and that their Hard drive image will be stored for no more than 2 weeks.
  3. Offer to assist in PW change; and if done, cache profile again after the password change.
  4. Verify that PCT captured printers and re-connect these printers to the new print server prior to launching print job. And delete the xp printers
  5. Ask if customer has any Scanners or peripherals at their desk they may need help configuring for new OS.  Provide assistance where required.
  6. Offer to assist with first boot at their desk. (It is likely they will need assistance in setting up their dual monitor settings)  Ask if user has questions.

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Related Entries and Links

No Related Resource entered.