Like every other software in Microsoft’s recent wave of releases, Office 2013 has an extensive amount of literature and reference materials on deploying the software suite for various scenarios. You can find most of what you need here (http://technet.microsoft.com/en-us/library/cc178982.aspx) along with the necessary deployment guide. However, going through the steps in this article could help you prepare for an even smoother Office 2013 deployment.
The first thing you should do is to make a plan of deployment. To put it in the most simplest of terms: Take stock of what you have, map out what you want to do and fill in the steps for what is in between. This includes listing down what related hardware and software you have on hand and which computers are going to run Office 2013.
Bear in mind that the download itself is quite large at about 750 or so megabytes (which isn’t as bad as a full DVD, but would still take some time to download). Also, once it is installed, it should take up about 4GB worth of hard disk drive space so make sure that your targeted machines have enough space available to take it all and still have enough space for the cache and other important programs.
Once you have a plan of deployment with your targeted goals in place you can start filling in the stuff in between with stuff such as Volume Activation, DNS settings and other important numbers.
2. Figure out how you want to Setup
Microsoft have already included a tool just for this called the Office Customization Tool which you can use to customize the setup of the Office 2013 deployment. Decide if you have the time to do it yourself or if a silent install is the way you’d like to go instead. Once you’re ready with your choice of MSP image files you can go to the next step.
3. Configure Communications and Security in your setup
Don’t forget that with these tools you can also setup and configure your communications and security for your setup before the actual roll out. This not only helps you build a more secure setup but also solves one less problem for you down the road. For communications you might also want to check out your previous Outlook and Exchange profiles so you can set up the new Office 2013 ones accordingly. Make sure that you’ve set up your Config.xml file as well.
4. Don’t Chain
Rather than do a chain install, deploy Office 2013 from a deployment management system because it is more reliable that way (if something goes wrong during a chain install everything gets interrupted and you won’t find out about it until later). In this case Microsoft have already provided some in the form of Microsoft System Center 2012 Configuration Manager or the Microsoft Systems Management Server (SMS) 2003. Other sites have shown step-by-step guides on how to do this with the Microsoft System Center 2012 Configuration Manager (http://myitforum.com/myitforumwp/2012/09/13/office-2013-part-1/) or even with Group Policy computer startup scripts (http://technet.microsoft.com/en-us/library/ff602181.aspx).
5. Begin from the beginning
When you’re ready to start, just open a network installation point and follow through with the usual process of running Setup, checking prerequisites, reading XML data, building the feature tree, creating a local installation source on the user’s computer, installing Office, applying the customization file and applying software updates.
Learn more about Office 2013, here.