Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.
Windows 7

Sin #5: Sloth - Avoiding the 7 Deadly Sins of Windows 7

Created: 09 Nov 2009 • Updated: 03 Jun 2014
CEwing's picture
0 0 Votes
Login to vote

SLOTH: Being lazy with your migration, not preparing your applications or capturing the right setting and personalities of your endpoints

During a migration you should never forget that corporate computer users don’t like change. End users want to start up their computers and see exactly what they expect—the same printer and network settings, background pictures, Internet favorites, and everything they’ve personalized in their most-used enterprise applications. Every Windows 7 migration needs to ensure that the user experiences less disruption and less negative impact during the process.

Successful migration to Windows 7 is possible, but it doesn’t happen by chance. Laziness in preparing applications or capturing settings for each client will leave IT lacking at the time of migration. And no one wants end users complaining to management and damaging the overall perception of the process (just wait for our blog on Wrath in a few days). Those IT administrators that are lazy with their migration or don’t prepare adequately will run into problems and increased costs associated with higher service desk volume and non-productive employees.

That is why the successful transfer of each computer and end users’ unique network, operating system, application and data settings, along with other customizations is the one thing that will make or break an OS migration. Capturing these settings and applying them to the Windows 7 environment is a necessary requirement to maintain productivity and accelerate acceptance.

The good news is that much of the heavy lifting in personality migrations can be automated with the right tools. The right tool should allow you to collect the following items and encapsulate them into a single template for the migration that is independent of hardware: 

  1. Capture global settings that comprise all Desktop, Network, Microsoft Outlook, or Microsoft Outlook Express mail settings
  2. Transfer an application’s settings and data files for common enterprise applications and facilitate the transfer for custom or other applications
  3. Capture data files and folders that may exist on the user’s computer

Heading off these potential problems with a bit of preparation will greatly ease the transition. Good techniques will keep end users happy by providing them with a new OS, but also with familiar settings, icons, and data to keep them working. At the end of the day this will keep employee productivity high through the migration and raise your overall ROI.

Group Ownership: