This can be a little tricky to understand but if you look at the example script below you should get the idea. This is done before any user interface is shown so can successfully be used to set the options that hide the first run dialogs. When a user runs an Office application it checks to see if it has previously migrated these settings before and if not it creates the relevant keys in HKEY_CURRENT_USER. The 15.0 part refers to Office 2013 / Office 365. Then under this key make another key called Create and under this create the registry settings that you want to set in HKEY_CURRENT_USER. You can even have multiple different names for different groups of settings. The M圜ustomSettings part of the key can be anything you like. HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\15.0\User Settings\M圜ustomSettings
HKLM\SOFTWARE\Microsoft\Office\15.0\User Settings\M圜ustomSettings In summary, you create keys under HKLM in the following locations (depends on the OS and version of Office): OS Version There is no worthwhile documentation of this process except on this Deployment Guys blog post. To get this to work we can use a little known feature of Office which allows you to specify some HKEY_LOCAL_MACHINE keys that are automatically migrated into HKEY_CURRENT_USER when an Office application is first run for that user. Unless you set them from a user-side login script or Group Policy then they won’t apply to each user that logs onto the machine. If you try and set them at the end of your installation they usually won’t work as the installation is likely to be done under an admin account. The problem with this is that these keys are all user settings. HKCU\Software\Microsoft\Office\15.0\Common\qmenable HKCU\Software\Microsoft\Office\15.0\Common\PTWatson\PTWOptIn HKCU\Software\Microsoft\Office\15.0\Common\General\ShownFileFmtPrompt HKCU\Software\Microsoft\Office\15.0\Common\General\shownfirstrunoptin HKCU\Software\Microsoft\Office\15.0\FirstRun\disablemovie HKCU\Software\Microsoft\Office\15.0\FirstRun\BootedRTM To disable all these screens we need to configure the following registry entries: Registry Key Thanks EU!Ī useless tutorial about OneDrive and forcing the user to set critical options like “ribbon background”. I believe this screen only appears on EU machines. There isn’t a non-IT user alive that has any idea which of these options is correct.
#Word without office 365 license
The usual annoying license agreement and questions about auto updates and product improvement that no user will care about or fully understand.
The customer was happy with the “default” settings that Office comes with, but when the user first runs Office there are numerous screens that popup which they wanted to suppress (with the exception of the Office 365 sign-in screen).
#Word without office 365 install
In a recent assignment I needed to create an Office 365 package that would install silently on in various scenarios: However, when using the “Click-to-Run” version of Office 365 there is no way to use the OCT so user settings can only be configured using Group Policy. msp file that can be used during setup to apply custom user settings. Secondly, by using the Office Customization Tool (OCT) to create an. Firstly, by using Group Policy (the recommended way). With a standard local installation of Office 2013 this can be done in two ways.
#Word without office 365 how to
This post shows how to automate the numerous “first-run” dialogs that are shown when a user runs an Office 2013 or Office 365 application for the first time.
0 kommentar(er)
