How to upgrade from XP, Server 2003 to Win 7, Server 2008 R2?

When applying new operating systems and applications, it is common for system administrators to postpone the application until SP 1 is released. Administrators have found many reasons to postpone upgrading from Windows XP to Vista and then to Windows 7. These reasons are: new operating systems require more powerful hardware, user interface modifications require user training, old-fashioned hardware and application compatibility issues.

Recently, it has been difficult to find device drivers and applications that are compatible with Windows XP. More importantly, Microsoft has ended its mainstream technical support for Windows XP and will end its extended technical support in 2014. The new PC defaults to Windows 7. Therefore, the administrator must support both operating systems. Since it is widely expected that Microsoft will release Windows 8 in October this year, can your enterprise be behind the operating system by 2 or 3 generations? Unless you are going to give up the rules of SP1 and then upgrade, it is now clenching your teeth to upgrade. It's time.

Server administrators are even more conservative. In this case, Windows Server 2008 R2 requires 64-bit hardware. The interface of this software is very different, which makes server administrators nervous. However, this latest server application is only compatible with newer operating systems. Microsoft ended its mainstream technical support for Windows 2003 in 2010 and will end its deferred technology implementation in 2015.

Here are six decisions you need to make before implementing an operating system migration:

1. Should I install a 32-bit or 64-bit operating system?

On the desktop At the computer level, there are not many benefits to installing a 64-bit version of Windows 7. The biggest reason to stick with the 32-bit version is that it's hard to find 64-bit drivers for older hardware. Some applications do not work properly in a 64-bit environment. Unless you don't need to support legacy hardware or you have specific requirements that can only be provided by a 64-bit operating system (such as addressing more than 3GB of memory), most of your desktop computers should use a 32-bit operating system.

There is no 32-bit version of Windows 2008 R2. You can run 32-bit applications, but 32-bit support is not installed by default.

2. Can you find compatible 32-bit drivers?

As mentioned above, you may find it difficult to find old-fashioned printers, scanners, and vending machines such as serial-based vending machines. 7 drivers. In fact, any new PC you purchase may not have a parallel port or a serial port. Make a list of these devices and decide whether to replace them or keep some XP computers running these devices.

3. Which applications need to be upgraded?

You can run Office 2003 on the Windows 7 platform. However, no one suggests that you run Office 2010 on the Windows XP platform. Develop a list of applications that need to be upgraded and remember that users need to be trained on new operating systems and applications.

On the server side, Exchange 2003 or 2007 needs to run on the Windows 2008 platform. This platform is required for the latest versions of SharePoint, SQL Server, and most other server applications. To reduce the impact on your business, you need to install a new server application on the new server and then migrate the user and user data on the old server to the new server.

4. Should you upgrade your software or update your hardware on existing hardware?

When upgrading your desktop operating system, you have two options: install new on your existing system. The operating system, or start updating with new hardware. The system requirements for Windows 7 exceed the capabilities of most PCs with Windows XP installed. Therefore, you need to enhance your hardware to upgrade. The same is true when Windows Server 2003 is the new operating system software.

Upgrading in the right place allows you to migrate user settings, application settings, and more legacy hardware settings to new hardware using Windows migration tools or after-sales tools. Most applications must be reinstalled. You must run Microsoft's Windows 7 compatibility testing tool to determine if the old application is running on the new operating system.

5. Is a virtual desktop infrastructure a viable alternative?

You can use the virtual desktop infrastructure to avoid buying new desktop hardware. Create a server application that can run virtual applications on Windows 7 and Windows XP desktops. Your users will access these environments using existing Windows XP machines. This will ensure that users transition to Windows 7 while continuing to access their familiar Windows XP desktops and legacy applications. The virtual desktop infrastructure requires server and network infrastructure, which can offset the savings in retaining legacy hardware. However, in the long run, virtual desktop infrastructure will simplify desktop management. Your users will experience an easier transition.

6. Should you invest in a migration tool?

The migration tool can transfer operating system settings, application settings, and some applications and drivers from legacy systems to new systems. Alleviate the pain of a lot of upgrades. Users can set up their own applications in dozens of hours, update dictionaries in word processing software, recreate macros, templates and tables, and more. Avoiding this loss of productivity can offset the cost of this tool