Asset Management Suite

 View Only

Migrating to Windows 7: Focus Points 

Sep 19, 2011 03:08 PM

I recently gave a presentation on this at the Symantec User Group (Phoenix). I would like to share this with all of you in the Symantec community and have converted it from the "Death by Powerpoint" to an article for all to enjoy.

I like to highlight four main categories to focus upon to ensure a good migration experience. The categories are:

  • Evaluating Hardware
  • Determining Application Compatibility
  • Creating and Deploying your Windows 7 Image
  • What you should migrate

I will take these main categories and break down all of the pain points and necessities you may or may not have considered to ensure your migration is successful and thorough. Be sure to remember, that not only is every situation unique and may require other strategies, but you may have different or better tools in place to get the job done the best way for your environment. I mainly try to focus upon best practices and to refrain from environment specific techniques to so the knowledge is useful for all viewers.

Hardware

Refreshing hardware can make migrations easier, here are some things you may want to consider when choosing either to refresh or to use in place hardware while migrating to Windows 7:
  • Machines can be prepared and ready for file migrations
  • No need for spare hard disks or server storage
  • Allows company wide hardware standardization
  • Windows 7 requires more resources than XP or Vista

When choosing your desired Windows 7 version, going to x64 bit may be a good idea rather than to tackle an x64 migration later in the future. I will lay out some pro's and cons when you are choosing between x86 or x64 Bit:

Windows 7 x86

Pro's

  • OS consumes less RAM vs. x64
  • Applications are more likely to be compatible
  • In place hardware is likely compatible
Cons
  • x86 can only utilize less than 4GB of RAM
  • The OS is slower than x64 bit technology
  • It is outdated and you will likely be migrating to x64 at a later time

Windows 7 x64

Pro's

  • You can use up to 192GB's of RAM!
  • x64 bit applications run much faster

Cons

  • x86 Drivers do not work!
  • Not many benefits when hardware is 4GB's or less RAM
  • Applications likely to be incompatible
  • Not all software is available in x64 yet

Determining Application Compatibility

First thing first is to be sure to test ALL of the applications that are used in your environment on your desired platform in which to migrate!

What are the options when applications are NOT compatible?

  • Look into virtualization. Multiple vendors offer a Virtualization platform to put you apps into a layer not requiring a certain OS to be in place.
  • Microsoft provides "Windows XP Mode" which is a virtual machine it could be loaded upon
  • You can install the software on a terminal server for whomever needs the software
  • Look for alternative applications or newer versions from the same vendor

Creating your Windows 7 Image

When you start building your Windows 7 Image, be sure to consider the following:

  •  WSIM and Sysprep.XML Unnatend Files
    • With WSIM you can customize the image OOBE settings through sysprep
    • Unattend.xml has options from your Task Bar shortcuts to your ODBC settings
    • You can add Automatic logins through the Sysprep Unattend file  
  •  Customizing Settings
    • For Hardware Dependent Imaging, load all drivers for existing hardware
    • Create your ideal "Profile" and use the COPYPROFILE parameter in your Unattend.XML file
    • Create your local logins, set passwords, permissions
    • Remote Settings, System Restore, DAgent and AClient settings
    • Power settings, Page file, IE Settings
    • For Hardware Dependent Imaging, load all drivers for existing hardware
  • Applications
    • Minimize application installs to "Core" applications for a Thin Image if you are having a massive deployment schedule
    • Some applications may require your settings to come later and cannot be capture in a default profile
    • Install applications for a steady network location for repairing later if needed

Using Altiris DS to Capture and Deploy

Here are some highlights to consider while creating and capturing your image:

  • Be sure to use "Audit Mode" with CTRL + SHIFT + F3 for image creation (Can also use Sysprep.exe -audit)
  • Wipe paper trails and settings from the Image like IE history, network shares
  • Wipe Temp directories
  • Capture the Image prior to booting to the OS
  • Resealing your image can save lots of time for simple fixes
  • Create "Post Imaging" Jobs for departments or groups in order to have a seamless user migration installing their specific required apps
  • You can consider having "Fat Images" which are tailored to groups or to departments with all of their necessary software

What to Migrate, Tools and Testing

Determining what you can leave behind is a great start to cleaning your users machines and your environment. Some tools can help automate this task but sometimes it is best done with the human eye for quality assurance.

  • Using PC Transplant
    • If you use PC Transplant, bandwidth must be a consideration to ensure files are transferred in a timely manner
    • Do not capture EVERYTHING, be sure to assess what is necessary and what is not necessary to bring
  • Profile Folder Migration
    • Try and leave personal files behind, notify users to copy what they want to keep beforehand such as Pictures,Videos and I-Tunes
    • Check the Root of C:\ for folders and files
    • Some applications store necessary settings in profiles, be sure to capture what you need to
  • Using .BAT files, Login Scripts, GPO, and Altiris DS to "finish the job"
    • Use these resources to remap users printers and network drives
    • Create department or group specific application installs rather than put the applications on a Fat Image

Testing your Migration Plan

  • How many machines can you do in a day?
  • Do you have spare hardware just in case?
  • Be sure to plan accordingly for little impact, sometimes only a few per department should migrate at the same time

Your unique migration: Assess and plan accordingly to your specific environment!

Be sure to evaluate the tools you have in place and what works best for you. Some environments may have shared workstations, roaming profiles and do a full hardware refresh which can change the rules of the game. Bandwidth can be an issue and you may want to set up an Isolated LAN in your environment to get better imaging times or perhaps you may need an Altiris DS that can be mobile for remote offices.

Whatever your specific case may be, be sure to have enough resources to get the job done, underestimate how much you can get done in an allotted amount of time to reach goals. Consider getting help if you are over your head, a contractor may cost money but it might cost you more if the plan does not go accordingly!

TEST TEST TEST, you can never have assurance without knowing your plan works before implementation, this is the most important thing you can do prior to migrating and do not underestimate its value!

Did this Article help you? I would love to hear your feedback!

Q & A

I would love to share more with you however I wanted to stay open minded and specific to categories all could benefit from. If you have any questions or comments be sure to let me know and I would be obliged to help you!


 

 

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

Sep 20, 2011 01:07 PM

Thank you sir! I tried to do my best to ensure a non environmental-biased guideline for all to utilize for their specific migrations.

Sep 20, 2011 12:36 PM

Great stuff!

Related Entries and Links

No Related Resource entered.