Sign up today to participate, stay informed, earn points and establish a reputation for yourself!Sign up! or login
Here`s how to remove the `first execution` popups of Office 2013. This was very helpful with our labs and classroom computers since they also have DeepFreeze installed.
Once you have downloaded the version you need and extracted the templates, open the Group Policy Editor.
From here you will need to Expand "User Configuration" > "Policies" > "Administrative Templates".
Right Click on "Administrative Templates" and click on "Add/Remove Templates".
A window will appear for you to add or remote additional templates, click on the "Add" button.
Another window will appear that will allow you to browse to the file locations where templates are found, in this case it will be where you extracted the Office 2010 templates (these will be in the "ADM\en-us" where en-us is the language of office used). Also note you can choose all the files at once by holding the shift key.
Once the templates have been selected you can then click the Open button to close the file browse window, then click close on the "Add/Remove Templates".
Under the "Administrative Templates" you will now see an additional line "Classic Administrative Templates".
From here you will have all the options to modify Office 2010 and to disable the "Welcome to Office 2010" continue through the following locations: "Microsoft Office 2010" > "Privacy" > "Trust Center" and set "Disable Opt-in Wizard on first run" to enable.
A _REAL_ good how to can be found here:
Step by step guide to prepare source files, and to deploy Office 2013 using SCCM 2012.
I am trying to deploy Office 2013 MUI pack and online it says that you can use setup.exe /admin, this will open office customization tool. But in this case it's giving me an error saying "some files are missing". I can't figure out how to solve this problem. I can post screen shots if you want. Please help me out.
Thank you in advance.
We are working on a Managed Install of Office 2013. We created the adminfile and zipped it up in the Office Updates folder and uploaded the zip to the K1000. After forcing inventory, the client was not installing Office and the log on the client kept telling us that the file setup.exe was not found. After watching the downloads directory (c:\ProgramData\Dell\Kace\Downloads), on the client, we found that when the K1000 downloads the zip file and then extracts it, it does not automatically include the extracted folder in the path. We had to modify the command on the Managed Install to inlcude the path. So if your uploaded Office zip file was called office2013.zip your command in the managed install needs to be office2013\setup.exe . Also if you are using customization of Office, all you need to do is include the .msp file in the updates folder of Office. Office automatically looks in that folder for any files and will apply them. This will make you install command a little cleaner. I hope this helps.
For silent installation, run "setup.exe /admin" to create an msp file.
then in SCCM run setup.exe /adminfile "yourfile.msp" to silently install your customized installation.
I had difficulty creating the desktop shortcuts (it was giving me error: the start in field is incorrect). I surpassed the issue by putting in an open bracket " [ " in that problematic field.
I had problems with activation until I downloaded the updated OCT from Microsoft.
You download Office Professional Plus 2013 with SP1 from the Volume Licensing Service Center, extract, delete the folder called admin. You then download the updated OCT via the link above, extract, copy the admin folder and paste it into your Office Professional Plus 2013 with SP1 extraction. You then run your OCT, save your MSP, and deploy.
After I did this office activated correctly via MAK during install by using a AUTO_ACTIVATE 1 command in the OCT. Before doing this, the same command would not work. I was also having issues deploying the 32 bit version of office to some 64 bit OS, but after replacing the OCT with this new version those issues went away.
I found at nice litte script on Technet.
This vbs script exports installed office updates to at temp folder. Then it´s easy to copy the msp´s to the update folder.
Scroll down to: