Office 2010 Deployment: How Do I Get There?

If your enterprise is planning a Microsoft Office 2010 migration, or is in the beginning stages of deployment, you are most likely interested in possible contingencies or problems you may have with broken files. In this article, we will help organizations answer the critical question in the upgrade process “How do I get there?”

Choose the deployment approach that best fits your business environment, is our first advice. Organizations may choose between a big bang– all departments at the same time –, departmental, or phased rollout approach.  It all gets down to understanding how your organization functions, what is the level of deployment– whether Office 2010 is domestically or globally deployed –, and what are the right tools and methods used. Keep in mind that your objective should be to stay on time, on budget, with minimal impact on user.

There are five critical steps for organizations upgrading to Office 2010 that can ensure the success of the deployment process:
1.   Plan and discover your environment

At this stage, organizations discover their network landscape through files and applications inventory and compatibility. This way, they know how much remediation they are going to need, and make deployment estimates or “order of magnitude”.
2.   Scope your project

Which files that are going to be problematic, and impact your deployment project timeline and cost? Organizations define the quantity of files that require remediation and validate assumptions made in the first planning phase. This is the moment when organizations can start requesting new funding for the deployment, if necessary. It is also the best moment to “do the housekeeping”, and remove the old archived files and applications that nobody uses anymore, further reducing costs and time.
3.    Convert and migrate

At the conversion and migration stage, the bulk of files and applications are converted in a “factory setting”, while broken files are promoted to help desk or central service for remediation. It can take the longest time getting the files and applications migrated and ready to go to user acceptance training.
4.    Test

Often overlook and underappreciated, testing is a strategic step to making sure that critical applications and files are working properly, as intended. Organizations are advised to go through methodical end user acceptance training with a representative sample se, in order to try to head off any problems as best they can.
5.    Roll out

The roll out or converting to production stage means that all departments in the organization have successfully moved to the new platform, and desktops are converted in full production mode. At this stage, users can still address link issues.
To accelerate the deployment process for your organization and remediate arising Office files issues while staying on time and on budget, we are also recommending the OfficeConverter automated solution.