If you are trying to deploy a click-to-run (C2R) version of Office 2013/365 then it’s time to forget everything you knew about deploying office and start from a clean slate!
Due to Office 2013’s Cloud-based nature it is set up a bit differently to the traditional CD/MSI approach. This is fine if it’s your personal copy but what about deploying it to an whole office of PCs?
IT pros have been using the Microsoft Installer (MSI) technology for years to silently install Office programs. You can use a mix of existing switches to update and patch Office installations using Group Policy, scripts, Office Customization Tool (OCT) or the Microsoft Deployment Toolkit (MDT). However, Microsoft, in their wisdom, decided to offer a brand new deployment methodology for Office 2013, Click-To-Run. There is still an MSI version out there but it is only available for the Volume Licensed customers, which means, if your business was used to buying the much cheaper Product Key Card (PKC) licenses, you are stuck with C2R. Oh, and by the way, WSUS can’t be used to update it either.
We came across this issue when we purchased and job lot of PKCs for Office Home and Business 2013. This includes Outlook, Word, Excel, PowerPoint and OneNote. This seems like an ideal buy for most small businesses as it includes all of the core Office apps that your average user would need. However, when it comes to deploying, customising and activating it is about as far from business-ready as you can get! I struggled for weeks trying to get things working correctly to allow a smooth integration with our Windows 7 deployment, I did finally get there, but I hit so many brick walls I almost gave up trying. The worst part is when you get a stock “You should buy Volume Licenses” response… erm yeh, I wish I knew that 3 months ago before the money was spent.
So here is my ultimate guide to installing, customising and activating Office 2013 C2R editions. It’s not going to be pretty but it will get you someway to a mostly automated and controlled deployment. It is specifically tailored towards Office 2013 Home and Business but should work for any Office 2013 C2R version that needs to be deployed in a Windows Domain