How to Migrate from Windows XP to 7, and from Server 2003 to 2008 R2 - denneysoperypear

When it comes to adopting new operating systems and applications, common practice among system administrators is to delay adoption until the release of the first service pack. Admins found plentitude of reasons to put off moving from Windows XP to Windows Prospect, and then to Windows 7: The new operational systems demanded more confident computer hardware, the user interface changes required user training, and in that location were compatibility issues with legacy hardware and applications.

These years, it's becoming rugged to find device drivers and applications compatible with Windows XP. More significantly, Microsoft has terminated mainstream support for Windows XP, and figurative support ends in 2022. Late PCs go with Windows 7 aside default option, so admins must support both operating systems anyway. And with Microsoft widely expected to ship Windows 8 in October, can your business afford to be cardinal surgery ternion OS generations buttocks? Unless you intend to fructify aside the inaugural-service-bundle off rule, information technology's time to bite the bullet and move forward.

Server admins are even more conservative. In this case, Windows Server 2008 R2 requires 64-bit hardware, and the interface is just different enough to make them nervous. The modish server applications, however, are compatible only with the newer operative arrangement. Microsoft over mainstream support for Windows 2003 in 2010, and extended bread and butter ends in 2022.

Here are the peak six decisions you'll need to make earlier embarking on a migration:

1. Should you install the 32-bit version or the 64-bit variation?

At the desktop layer, there are a couple of advantages to installing the 64-minute interpretation of Windows 7. The biggest reason to stick with the 32-minute version is that you might have difficulty finding 64-bit drivers for legacy hardware. And some applications put on't function well in a 64-bit environment. Unless you'rhenium positive you won't need to bread and butter legacy hardware, Beaver State if you have specific needs that can be filled lonesome by a 64-bit Operating system (addressing much 3GB of Aries the Ram, for illustrate), you should set up most desktops with the 32-bit OS.

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

2. Canful you line up compatible device drivers?

As we've already mentioned, you might have difficulty finding Windows 7 drivers for legacy hardware, ranging from old printers and scanners to specialized tools such as point–of-sale devices that depend on legacy serial ports. In fact, whatsoever new PCs you acquire probably won't even be outfitted with parallel or successive ports. Make a list of these devices and decide whether you'll replace them or retain some Windows XP computers to bear on running them.

3. Which applications wish need upgrades?

You can run Office 2003 on Windows 7, only no one would advocate running Billet 2010 happening Windows XP. Make a list of the applications that will demand to embody updated and remember that users will call for preparation on both the new operating system and the new applications.

On the host lateral, Exchange 2003 or 2007 will run on Windows Waiter 2003, simply Exchange 2010 requires Windows 2008.The same is true for the latest versions of SharePoint, SQL Host, and most some other server applications. To reduce the impact on the enterprise, you might desire to install new servers along with the new host applications, and so migrate users and their information from the old server to the new.

4. Should you upgrade in place, or start fresh?

When upgrading desktop systems, you have two choices: Install the new OS in an existing system, or start fresh with new hardware. Windows 7's system requirements are beyond the capabilities of just about PCs that came with Windows XP installed, so you power involve to strengthen the hardware to elevate in place. The same is geographical of servers chisel in service when Windows Server 2003 was newfangled.

Upgrading in lay out enables you to transfer user settings, application settings, and more from the old hardware to the new victimisation the Windows migration instrument or aftermarket tools. Most applications will have to be reinstalled, and you'll want to run Microsoft's Windows 7 compatibility tester to determine if any of the old applications will have problems running happening the new OS.

5. Is virtual screen background infrastructure a viable alternative?

You can ward of acquiring new background hardware by deploying virtual desktop infrastructure (VDI). Tack together a waiter coating that runs virtual iterations of some Windows 7 and Windows XP desktops, and your users will use their existing Windows XP machines to access these environments. This testament help them passage to Windows 7 while ensuring continued admittance to their intimate Windows XP desktops and bequest applications. VDI will require server and networking infrastructure that will likely offset the nest egg realized by retaining your old desktop ironware. In the long run, however, VDI will simplify background management, and your users will experience an easier transition.

6. Should you empower in migration tools?

Migration tools can ease the pain of a tidy sum advance by transferring OS settings, application settings, and even some applications and drivers from old systems to new ones. Users buttocks spend wads of hours place setting prepared their applications just the way they wish, updating dictionaries in word processors; recreating macros, templates, and forms; and so on. The cost of much tools could be offset by avoiding such productiveness going.

Source: https://www.pcworld.com/article/469340/how_to_migrate_from_windows_xp_to_7_windows_server_2003_to_2008_r2.html

Posted by: denneysoperypear.blogspot.com