After extracting the Office Customization Tool download, copy the Admin folder to your copy of Office 2013 setup and create a new Setup Customization File for Office 2013, by running: SETUP /ADMIN
#MICROSOFT WORD DEFAULT SETTINGS 2013 DOWNLOAD#
To create an Office Setup Customization, download the Office 2013 Administrative Template files (ADMX/ADML) and Office Customization Tool.
To manage an Office 2013 deployment, copy the Office source files to a folder and ensure you’ve downloaded the latest updates and service packs. Office 2013 customisation and deployment is already well covered in the documentation available on TechNet, so in this article I’ll only cover some highlights and recommendations. Note that if you are deploying Office 2013 with Click-to-Run (App-V), then this level of setting user defaults will not be possible. Use a policy only where settings must be enforced. I recommend carefully considering each user setting and setting it as a preference instead of a policy wherever possible. policies should reduce Group Policy processing time and thus logon time. Hosted desktop environments where user profiles might be managed with custom solutions might result in GPOs being processed at every logon, even though the GPO has not changed. This is an important distinction – a preference only needs to be set once and only requires processing at first run, whereas a policy has the potential to be processed at every logon. The main difference being that a preference is set only during the initial launch of an Office application, whilst a policy may be set on every logon (whether the user launches an Office application or not). Most of the Office user settings can be set as either a default/preference, by customising the Office deployment, or as a policy via Group Policy. User settings that might impact the default Office experience or may require special consideration in your environment, are worth investing in planning time because you’ll often have only one chance to get deployment right.
0 kommentar(er)
