![]() xml from the "Share" server on a command prompt -Ĭ:\>c:\Office\Setup.exe /Downlaod c:\Office\download.xml xml needed to Download the Install files (i called it "download.xml") - about 1.1GB - I used this. If I had more time to play with an automation process I would have but I'm a 1 man show here so. I only have 75 PCs and 6 different departments so it's not too bad. I decided to touch every machine for the Uninstall / Install, doing one department at a time. Here is a site that explained it pretty well. If you are installing on a "bunch" of PCs then it is best to download the install files to a network share and then Install the app from there. There are a couple of things you have to do to get this working the way you want. It's Stupid simple and I wish I had found it at the beginning. xml editor just for use with the Deployment Tool See it Here Opens a new window. xml file right and finley found this Microsoft. xml file to add/remove features and options. The deployment tool works in conjunction with an. ![]() Having said that, I still have to Uninstall Office 2013 and then Install Office 2016 CtR (these two can run side by side if desired) and both can be done via scripts but very differently, the big difference here is CtR uses a "Deployment Tool" rather than an. ![]() Our upgrade will be to Office 365 Pro Plus (aka Office 2016) via "Click-to-Run" which is very different from Office 2016" standalone" - Click-to-Run is a subscription version of Office 2016 that comes with Office 365. We have "Office 365 for Education and Faculty" AND Office 2013 "standalone". For the benefit of others, this is what I ended up with.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |