There are numerous options available for this document check TechNet for a detailed reference on how to build this file if you are licensed only for Click-to-Run. \\server\share\Office15\setup.exe /config \\server\share\Office15\ProPlus.WW\config.xmlįor the Click-to-Run version of Office 2013, you need to build a configuration.xml document - not to be confused with the config.xml used above. Then you can kick off the installation in the script using a command like this: You need to make sure that file contains the following lines: For MSI-based Office 2013, you use a config.xml file that resides on that network share that acts as an answer file. Since you are installing upon computer startup in the context of a system account that has no way to get interactive input from a user, you must deploy a silent installation so that no user intervention is required. Write a script that kicks off a silent installation of Office 2013.If you are licensed only for the Click-to-Run version of Office, then use the Office Deployment Tool for Click-to-Run to bring the files down to a central network share. For MSI-based Office, just copy all of the files up to the share. Verify that any computers that are targets for the deployment can access the share and also give Read rights to the Authenticated Users group. Copy the Office installation files to a network share.To get started using this procedure, follow these steps: You have to use a script to manage this process. Group Policy doesn't know how to handle that, at least from an installation perspective. The overarching setup executable is just that - an EXE, not an MSI. You can't use the traditional software installation capabilities of Group Policy because Office 2013 Pro Plus uses multiple MSI files for all of the code versus one single MSI file for the whole suite. What's different about Office 2013 compared with previous versions of Office? For one, there are a couple of different Office 2013 editions - the Click-to-Run edition, which streams the program files down to local computers, and a traditional Microsoft Installer (MSI)-based version that is available only to volume-license customers.
You also get the benefit of using the tools included with the Windows client and Windows Server licenses you already paid for, with no additional deployment software costs. The computer startup script runs in the context of the Local System account, which does have unfettered access to protected areas, so the installation can proceed apace. SCCM 2012 is appropriate for both PCs and VDI System Center Configuration Manager has updated enterprise asset management featuresĪlternatives to Microsoft Office offer flexibility to mobile users
Microsoft helps one Office 2013 customer with its migration Microsoft's free Office 2013 Resource Kit is useful for deploymentįAQ: Why do Group Policy settings matter?
0 kommentar(er)
