Before we continue though, I will take a moment here to outline how the deployment will be implemented. Don't zip the folder just zip the files in the folder. I tried to run the script manually on one of my clients, and ended up with an error Clients need admin rights to uninstall current version. It already had an admin folder, so I deleted it. Or if I am missing something else, please explain. To start this tool start setup. You can After downloading, extract them into your Group Policy Central Store.
If you have a folder that contains the office files the zipping wasn't performed as suggested. Office 2013 and Lync are the only managed installs that are giving me fits like this. I noticed the other script did have it. Here is what I have found and done. I have yet to find a method that successfully performs a complete uninstall before the new install begins. This will ensure that setup. I appreciate all the help.
Prep the Content If your Office 2013 installation files are not currently on a network share, copy them to that location now. After the system is imaged, the user is prompted to activate Office at first run. The process is quite similar to deploying office 2010 but I have received a lot of questions about the small differences between the versions. When setup runs, it uses the very first msp file that it finds in the updates folder so it needs to be the customization file, the rest of the msp files it will run after the programs are installed. So it seems that I have been creating more work for myself going via this route but I thought it would work but just couldn't get the parameters right.
Thanks for the advice and help. Hi, for those of you having issues with the installation batch file shown above, try this. Learn additional functionality around what Microsoft Office can offer by visiting Microsoft Virtual Academy and completing the course. I took your advice and used the msiexec with the uninstall file as the first line of my script followed by the second line to run the Office 2013 install which I configured to remove Office 2010. If both of these files are in their correct locations, setup.
Do not modify anything below this line. Can I use sub-directories in the Updates folder to get around this? Mike Hey Mike โ that solution should work fine. Or maybe I should make all the necessary changes to the config. I downloaded the 32bit installer, created my msp with configurations, and zipped them all up. I am trying to add the retail versions of Office 2013 to the applications store. You have been a great help and I can't wait to get home and play with this.
Would clearly have to be run manually on affected computer to avail of this Such a great post! This will rearm the office activation and prevent any pop-ups on first run once the image is deployed. Hello, Thank you so much for putting this together! This is the section where the administrator can make changes to the default user experience: When saving your customization file, you can choose to save it to the Updates folder where it will run automatically, or. I am thinking that the retail versions just do not support any kind of unattended installation. So, we have finished Task Sequence configuration, and now are ready to deploy Office 2016 on client computers. Check yourself, you should see the setup. You will need to perform some additional actions.
Double click on Shutdown and then select Show Files. You will likely want to configure a few settings such as autorecover times, default file types, etc with Group Policy Administrative Templates. You can optimize it a bit by change the first line to call the Lync uninstall file on the computer. The end result was I was able to point the Setup to the local directory and pull the edition that I needed. Call that command instead of your network uninstall command. I thought it should uninstall the 2010 version first without prompting? Thank you for your assistance.
This tool enables administrators to create a. If you insist on zipping the folder you will have to put the complete path in the installation command. Running an inventory on the systems shows the apps installed. You could also Make a share on your server, point the xml to the share and just push out the setup. Or are there problems in the script? Leave on the default of Full set of source files. Office 2013 was introduced to address this need and has been received well by system administrators alike. Where do you find the missing admin folder? All you need in the Office install folder is the extracted files from the admin tools.
Switch to tab Task Sequences and select an entry Install Applications. Tick I accept the terms of the License Agreement and change the Display level to None. So you mentioned that I should place the config. I enetered the Same serial key as my office 2010 profeesional plus that is already installed on my laptop. I have put my personal network path for installation file inside. Kind Regards Morten Leth Hi Morten, many thanks for your response to my post. I would love to share the package I made but I don't know where I could host it.
Click on Picture for Better Resolution We will need to copy this folder to the office 2013 sources files. In Command line field enter the name of Office 2016 setup file setup. The status of each setting will vary dependant on the environment. What I discovered is that even though the install occurs silently in the build process, Office thinks that it is a new install after the image is applied. Right click and create a new text document. There is one file 'Microsoft Sharepoint Workspace 2010' and a folder called 'Microsoft Office 2010 Tools'.