![]() ![]() ![]() Thus, you MUST do a server to server migration from Windows 2003 32-bit to Windows 2008 R2 64-bit. For organizations that have been running 32-bit Windows for years and frequently just did an inplace upgrade from older to new versions of the operating system, Windows 2008 R2, being 64-bit does NOT provide an inplace migration path from 32-bit anything to Windows 2008 R2. So why is Microsoft providing “free tools” and “free guidance” on how to migrate to Windows 2008 R2? The big reason is that Windows 2008 R2 is a 64-bit ONLY operating system. ![]() With Windows 2008 R2, Microsoft shipped the product with a series of free migration tools PLUS they setup a Web URL where you can download new migration best practice guides and conversion tools (see ).Īnd these aren’t the typical Microsoft guides that are 300 pages of junk, the guides are very step by step prescriptive and where applicable, there are utilities they provide for free that is part of the migration process. In the past, any time a new Windows operating system came out you had to manually migrate server configuration settings and data, or go out and buy a 3 rd party tool to assist with the migration or do an inplace upgrade and bring along a lot of operating system "baggage" with your migration just to preserve your application configuration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |