Is Windows 7 keeping you up at night? According to an IDC research paper, around 50% of all business users will be using Windows 7 before the end of 2010. Gartner has predicted that one-half of large organizations will skip Windows Vista and move directly from Windows XP to Windows 7.

When you start thinking of migrating, you know that user settings will trouble your mind. If you want to make sure end-user productivity doesn’t go down during the migration process, take a look at RES PowerFuse. Not only for this migration, but for all future migrations. Once you’ve decoupled the user settings from the rest of your infrastructure, you will never want to go back!

RES Software tips for succesful migration:

• Analyze compatibility of hardware from a central location

If the hardware doesn’t comply with the minimum requirements for Windows 7, it is better to wait until the computer can be written off as new PCs would then have Windows 7 installed as standard. Then, as soon as it’s clear how many PCs are suitable for Windows 7, a realistic plan can also be drawn up.

•  Map out critical applications based on their use

Most migrations are based on the number of applications installed, whereas what really matters is which applications end-users actually use. With RES PowerFuse you can easily get this information.

• Standardize before migrating
  

After taking an inventory it is wise to set up a standard desktop for your users and leave its personalization as late as possible. This way, you have a standard desktop which is easy to migrate and the users still have one of their own. By separating the desktop’s personal settings from the way you offer the desktop – centrally or locally, or based on Windows Vista or Windows 7 - the migration is considerably simplified. RES PowerFuse decouples the personalised user workspace from your underlying infrastructure. Any changes you make in OS will not have an effect on personal settings.

• Formulate a realistic migration plan
  

Most organizations decide upon a gradual rollout because the so-called ‘big bang’ implementation isn’t a practical option for them. The gradual rollout requires the creation of a realistic scenario. The order in which the migration is to proceed and how much effort this is going to require from the IT department need to be clearly formulated. A logical procedure also needs to be drawn up (which you would prefer to automate) in order to keep track of which upgrades have taken place and in which order. Also, when it is not clear which patches have been installed on a PC, it is impossible carry out this routine job efficiently. In the migration scenario you also need to be prepared for set-backs, so it is wise to make sure that upgrades can be reversed should you encounter problems along the way.

• Make personnel available for extra support

 A migration process usually means staff will have extra questions that need answering. Make sure that the helpdesk is prepared to deal with this. Remember that feedback from staff can be useful in detecting and resolving problems early on.