A recent survey conducted before and after the launch of Windows 7 revealed that 20 percent of IT professionals polled have sped up their timetable for upgrading to Windows 7. Those polled said the operating system’s speed and user interface are the main reasons to upgrade.
 
But upgrading an entire business isn’t like flipping a switch, and being hasty will make your migration go south quickly. As with any journey, migration to Windows 7 requires a plan and preparation. Here are some guidelines to ensure a smooth ride:
 
Formulate a road map: Before you can successfully migrate to Windows 7, you need to know what is in front of you.  Haste to upgrade too quickly can be like a bird attempting to flee the nest before its wings are ready. Avoid looking for shortcuts, and start by assembling a team that represents key stakeholders such as IT operations, security operations, application testing and packaging, network...

GREED: Failing to run a test or pilot to test the migration

For any organization, upgrading operating systems can be exciting. But if the anticipation leads to an attempt at immediate adoption without first testing the deployment process, that greedy haste will cause headaches. If the process has any complications or glitches, going straight to implementation isn’t a shortcut, it’s a shortfall.

All it takes to overcome greed is a simple pilot test of the new operating system, applications and custom settings before a full deployment. The IT administrator should implement a pilot program to run the new system, see how it goes and make any necessary adjustments. The end result is a smoother migration, happier end users and less calls to the service desk.

The first aspect to consider is whether any necessary network changes are required to support the migration. You will need to implement the network changes identified...

Gluttony: Migrating more than you need to by not cleaning things up first

Organizations often use an OS migration as a time to evaluate the applications, software and other data files they have on the organization’s existing endpoints. They can also use this time to plan their go-forward imaging standards. Those organizations that don’t go through this evaluation and planning process may be migrating more than is necessary (gluttony) once they begin the migration process.

One of the first critical decisions will be determining the specific deployment standards and processes to be used during the migration and, optimally, on a go-forward basis. This could be a considerable undertaking depending on the organization and their existing processes. For example, some IT departments may manage 30+ images that quickly become a logistical nightmare, draining time and resources away from other, more critical issues. However that same...

PRIDE: Believing that the built-in security and backup technology is all you need

Many businesses operate under the assumption that built-in security and backup technology is enough to protect their information. To be truly protected against today's increasingly complex and organized cyber attacks, you need a comprehensive, integrated security solution that provides multiple layers of protection, in addition to scalable backup.

In 2008 alone, Symantec detected more than 1.6 million new malicious code threats worldwide, according to the Internet Security Threat Report XIV. This explosion in the number of malicious code threats, coupled with the continued trend towards Web-based attacks, reinforces the growing need for cooperative security and backup responses. Individual point products and add-on functionality are no longer sufficient to protect against today...