In my experiences in deploying Office Products I have found that I deploy my office products in a combination of ways from seen here to fit the educational environment I find my environment more consistent and stable.
Before I deployed Office 2013 I asked myself the following questions?
1.) Do I have the proper licensing for Office 2013?
If the answer was yes then proceed to question # 2. If your answer was no then get legal and legit with your Microsoft Volume licensing agreement..
2.) Should I include Office 2013 on my deployment image?
My answer is no. Although some may contradict what I say. Let Group Policy do the work for you.. It also allows your image to be productivity package independent..
3.) Do I need to remove previous versions of Office before deploying Office 2013?
If you build your Group Policy deployment package of Office 2013 correctly then no..
4.) Why should I deploy Office 2013 via a GP instead of including it in a image?
Duh…. Time, time, time and effort.. Do you want to re-image a computer just for the sake of changing productivity suits? For some environments this cannot only be network intensive, but labor hour intensive as well.
In my searching of the internet I did not find one article that I really liked that provided a clear solution to deploying Office 2013 via a GPO. So I decided to use a combination of the following articles to deploy Office 2013 successfully..
For the base deployment of Office 2013 follow these steps:
To customize Office 2013 after the intial install (aka remove the annoying features that prompt users for responses such as the Office welcome screen.) follow these steps:
If you wanna get creative and you have XP and Windows 7 workstations in your environment and since Office 2013 cannot be installed on Windows XP then use a WMI filter in GP to target only your Windows 7 workstations: