Office 2010 Standard Product Key Good Migrations

[tools390]

SHARE: Digg Del.icio.us Facebook LinkedIn Twitter E-mail this informative article | Print content | Reprints | Further Programs & OS | SHARE: Digg Del.icio.us Facebook LinkedIn Twitter E mail this informative article | Print document | Reprints | Even more Applications & OS | Page 1 of 3 All right,Microsoft Office Standard, let's get this out of the way: server migration of any kind is fraught with the potential for headaches, trial and error, incompatibilities and worse. Expect the same when migrating environments to Microsoft's just-launched Windows Server 2008. Questions have emerged, such as how to upgrade existing servers to Server 2008 without breaking Exchange. Breaking Exchange? Yes, even Microsoft's own flagship enterprise e-mail technology could be a nightmare to migrate to the new platform if best practices aren't observed. Nevertheless, it is possible to migrate environments from Server 2003 to Server 2008. It's not easy, but it can be done successfully.
The CRN Test Center examined Server 2008 in the lab to develop a better understanding of migration issues specific to the platform. The Test Center also called on Carl Mazzanti, CEO of eMazzanti Technologies,Windows 7 X64, a Hoboken, N.J.-based VAR who has already begun successfully migrating customers to the Server 2008 platform, to find out how he's done it.
First,Microsoft Office Pro Plus, though, a note about Server 2008: Microsoft plans to closely integrate the platform with Hyper-V, which is still in beta testing for the next few months. In the Test Center, though, it's been a surprisingly useful, stable piece of technology. It has an insatiable thirst for memory, though, so even though it's not yet officially supported by Microsoft, VARs will need to keep hardware requirements top-of-mind as they enter this process. For now, here are five steps toward making life easier during Windows Server 2008 migration:
Assessment and Hardware PlanningAlthough there is a 32-bit version of Windows Server 2008, it won't support Hyper-V virtualization. Also, there's no migration path from 32-bit Server 2008 to 64-bit Server 2008—if VARs install the 32-bit version, they can't upgrade that server to the 64-bit version later on. Clearly, Microsoft is bent on kicking the market into 64-bit waters in one shot with Server 2008. That puts a clear wrinkle into migration planning for some enterprises and that means almost all enterprise assessments will need to take this into consideration. To help with that assessment, Microsoft has re-launched its Microsoft Assessment and Planning Solution Accelerator, originally deployed to the market for Windows Vista.
MAP needs to be run on at least the .NET 2.0 Framework, and the software tool supports Server 2008, Server 2003 SP2, Windows Vista and Windows XP. MAP is,Office 2010 Standard Product Key, at its core, an inventory collection tool and database; installation calls for deployment of SQL Server 2005 Express (it installs the light database on command if it's not already on the system).
The network assessment function in MAP is wizard-based and uses SNMP and Windows server protocols to evaluate hardware on the network that is capable of supporting Server 2008. The Test Center installed and ran MAP on virtual Server 2003 SP2 and Vista environments on the same network. It worked quicker on a Vista PC on the network. The conundrum of running MAP on Server 2008 is that it won't run on the 64-bit version of Server 2008, only a 32-bit version—not the most efficient way to deploy MAP. But the tool does its job on Vista and Server 2003 SP2 and can speed up the inventory and assessment process to give VARs additional time for other tasks.
Like with the Vista roll-out, Microsoft makes the entire migration process a lot easier for those deploying systems with Server 2008 factory-installed over those upgrading the software on the same box. For some VARs, system builders and their customers,Microsoft Office Professional 2010, it might provide the "here we go again" feeling of aggravation much of the market has felt with Vista migration.
Mazzanti said almost all of the deployment of Server 2008 he has done in its early stage has been with brand-new hardware. That may be a great deal more practical in many cases than trying to get one much more year out of that old box in the back room. In any event, though, he said, memory can't be ignored.
"We maxed it out," Mazzanti said. "Exchange 2007 will use as much memory as you give it." In most cases, maxing out means 32 Gbytes of memory.
Next: Staging 1 | 2 | 3 | Next >>