Microsoft Publisher 2016 Microsoft Publisher 2016 16.0.4266.1001 This policy setting controls whether the specified Office application notifies users when unsigned application add-ins are loaded or silently disable such add-ins without notification. This policy setting only applies if you enable the "Require that application add-ins are signed by Trusted Publisher" policy setting, which prevents users from changing this policy setting. If you enable this policy setting, applications automatically disable unsigned add-ins without informing users. If you disable this policy setting, if this application is configured to require that all add-ins be signed by a trusted publisher, any unsigned add-ins the application loads will be disabled and the application will display the Trust Bar at the top of the active window. The Trust Bar contains a message that informs users about the unsigned add-in. If you do not configure this policy setting, the disable behavior applies, and in addition, users can configure this requirement themselves in the "Add-ins" category of the Trust Center for the application. Disable Trust Bar Notification for unsigned application add-ins This policy setting controls whether add-ins for this applications must be digitally signed by a trusted publisher. If you enable this policy setting, this application checks the digital signature for each add-in before loading it. If an add-in does not have a digital signature, or if the signature did not come from a trusted publisher, this application disables the add-in and notifies the user. Certificates must be added to the Trusted Publishers list if you require that all add-ins be signed by a trusted publisher. For detail on about obtaining and distributing certificates, see http://go.microsoft.com/fwlink/?LinkId=294922. Office 2016 stores certificates for trusted publishers in the Internet Explorer trusted publisher store. Earlier versions of Microsoft Office stored trusted publisher certificate information (specifically, the certificate thumbprint) in a special Office trusted publisher store. Office 2016 still reads trusted publisher certificate information from the Office trusted publisher store, but it does not write information to this store. Therefore, if you created a list of trusted publishers in a previous version of Office and you upgrade to Office 2016, your trusted publisher list will still be recognized. However, any trusted publisher certificates that you add to the list will be stored in the Internet Explorer trusted publisher store. For more information about trusted publishers, see the Office Resource Kit. If you disable or do not configure this policy setting, this application does not check the digital signature on application add-ins before opening them. If a dangerous add-in is loaded, it could harm users' computers or compromise data security. Require that application add-ins are signed by Trusted Publisher Trust Center Block application add-ins loading This policy setting disables all add-ins for the specified Office 2016 applications. If you enable this policy setting, all add-ins for the specified Office 2016 applications are disabled. If you disable or do not configure this policy setting, all add-ins for the specified Office 2016 applications are allowed to run without notifying the users, except if application add-ins are required to be signed by Trusted Publishers. VBA Macro Notification Settings This policy setting controls how the specified applications warn users when Visual Basic for Applications (VBA) macros are present. If you enable this policy setting, you can choose from four options for determining how the specified applications will warn the user about macros: - Disable all with notification: The application displays the Trust Bar for all macros, whether signed or unsigned. This option enforces the default configuration in Office. - Disable all except digitally signed macros: The application displays the Trust Bar for digitally signed macros, allowing users to enable them or leave them disabled. Any unsigned macros are disabled, and users are not notified. - Disable all without notification: The application disables all macros, whether signed or unsigned, and does not notify users. - Enable all macros (not recommended): All macros are enabled, whether signed or unsigned. This option can significantly reduce security by allowing dangerous code to run undetected. If you disable this policy setting, "Disable all with notification" will be the default setting. If you do not configure this policy setting, when users open files in the specified applications that contain VBA macros, the applications open the files with the macros disabled and display the Trust Bar with a warning that macros are present and have been disabled. Users can inspect and edit the files if appropriate, but cannot use any disabled functionality until they enable it by clicking "Enable Content" on the Trust Bar. If the user clicks "Enable Content", then the document is added as a trusted document. Important: If "Disable all except digitally signed macros" is selected, users will not be able to open unsigned Access databases. Also, note that Microsoft Office stores certificates for trusted publishers in the Internet Explorer trusted publisher store. Earlier versions of Microsoft Office stored trusted publisher certificate information (specifically, the certificate thumbprint) in a special Office trusted publisher store. Microsoft Office still reads trusted publisher certificate information from the Office trusted publisher store, but it does not write information to this store. Therefore, if you created a list of trusted publishers in a previous version of Microsoft Office and you upgrade to Office, your trusted publisher list will still be recognized. However, any trusted publisher certificates that you add to the list will be stored in the Internet Explorer trusted publisher store. Disable all with notification Disable all except digitally signed macros Disable all without notification Enable all macros (not recommended) Check spelling as you type This policy setting allows you to configure options for spelling errors. If you enable this policy setting, you may choose one of these options: - Check spelling as you type: This option is checked. - Hide spelling errors: This option is checked, but "Check spelling as you type" is unchecked. - Both: "Check spelling as you type" and "Hide spelling errors" are both checked. If you disable or do not configure this policy setting, the "Check spelling as you type" option is checked. Check spelling as you type Hide spelling errors Both Checks/Unchecks the corresponding UI option. Custom Disable commands Disable Items in User Interface Enter a command bar ID to disable General Left to right Miscellaneous Predefined Right to left Save Security Publisher Options Advanced Complex scripts Proofing When selecting, automatically select entire word This policy setting allows you to disable any command bar button and menu item with a command bar ID, including command bar buttons and menu items that are not in the predefined lists. If you enable this policy setting, you can enter an ID number to disable a specific command bar button or menu item. If you disable or do not configure this policy setting, all default command bar buttons or menu items are available to users. When set, Publisher will show a prompt to the user to start the Printer Setup Wizard when a new printer is found. Prompt user to setup printer This policy setting allows you to disable specific command bar buttons and menu items for Publisher. If you enable this policy setting, you can enter an ID number to disable a specific command bar button or menu item. The ID number needs to be in decimal (not hexadecimal). Multiple values should be separated by commas. If you disable or do not configure this policy setting, the predefined list of command bar buttons and menu items are enabled for Publisher. Send entire publication as a single JPEG image Enable incremental publish to Web Save AutoRecover info every (minutes) This policy setting allows you to specify the Save Autorecover interval in minutes. If you enable this policy setting, you may specify the Save Autorecover interval in minutes (valid range: 1-120). If you disable or do not configure this policy setting, the interval specified in the UI will be used. Show ScreenTips on objects Automatically switch keyboard to match the language of surrounding text Automatically substitute font for missing East Asian characters Set default text flow direction This policy setting allows you to set the default text flow between Right-to-Left (RTL) and Left-to-Right (LTR). If you enable this policy setting, you may choose whether text will flow RTL or LTR. If you disable or not configure this policy setting, the default text flow setting is used. Left-to-Right Right-to-Left When disabled, fatally corrupt files are prevented from opening. When enabled, the user is warned but may choose to open the file.By default, fatally corrupt files are prevented from opening. Prompt to allow fatally corrupt files to open instead of blocking them Use sequence checking Add double quotes in Hebrew alphabet numbering Allow background saves Automatically hyphenate in new text boxes Checked: Adds double quotation marks ('') to Hebrew numbering. | Unchecked: Does not add double quotation marks ('') to Hebrew numbering. Checks/Unchecks the option ''Automatically hyphenate in new text boxes''. Default Publisher direction Allow text to be dragged and dropped Microsoft Publisher 2016 Prompt user when reapplying a style Specifies the default layout orientation. Use Chinese font sizes Turn off drag preview This policy setting allows you to determine whether Publisher shows a semi-transparent drag preview or a simple outline of the object when the object is dragged. If you enable this policy setting, only the outline of the object is shown while being dragged. This is the recommended setting for older machines because of the resource requirements of this feature. If you disable or do not configure this policy setting, a semi-transparent drag preview of the object is shown while being dragged. Use XPS-enhanced print path This policy setting allows you to use XPS-enhanced print path when available. If you enable or do not configure this policy setting, the XPS print path will be used. If you disable this policy setting, the XPS print path is not used. Display Developer tab in the Ribbon This policy setting controls whether the Developer tab will be displayed in the Ribbon. If you enable this policy setting, the Developer tab will be displayed in the Ribbon. If you disable this policy setting, the Developer tab will not be displayed in the Ribbon. If you do not configure this policy setting, the Developer tab will not be displayed in the Ribbon, but its visibility can be changed via a setting in the application Options dialog box. Customize Ribbon Number of publications in the Recent Publications list This policy setting specifies the number of entries displayed in the Recent Publications list that appears when users click Open on the File tab in Backstage view. If you enable this policy setting, you can specify the number of entries to be between 0 and 50. If you set the number to 0, all pinned and unpinned entries are hidden. If you disable or do not configure this policy setting, a maximum of 25 items will be displayed in the Recent Publications list. Note: If you want to prevent items from being added to the Recent Publications list entirely, you can enable the "Do not keep history of recently opened documents" Windows policy setting. Number of folders in the Recent Folders list This policy setting specifies the number of unpinned entries displayed in the Recent Folders list that appears when users click Open or Save As on the File tab in Backstage view. If you enable this policy setting, you can specify the number of unpinned entries to be between 0 and 20. If you set the number to 0, all pinned and unpinned entries are hidden. If you disable or do not configure this policy setting, a maximum of 5 unpinned items are displayed in the Recent Folders list. Note: If you want to prevent items from being added to the Recent Folders list entirely, you can enable the "Do not keep history of recently opened documents" Windows policy setting. Show the New template gallery when starting Publisher Use type and replace When formatting, automatically format entire word Publisher Automation Security Level This policy setting controls whether macros opened programmatically by another application can run in Publisher. If you enable this policy setting, you may choose an option for controlling macro behavior in Publisher when the application is opened programmatically: - Low (enabled): Macros can run in the programmatically opened application. - By UI (prompted): Macro functionality is determined by the setting in the "Macro Settings" section of the Trust Center. - High (disabled): All macros are disabled in the programmatically opened application. If you disable or do not configure this policy setting, Publisher will use the default Macro setting in Trust Center. Low (enabled) By UI (prompted) High (disabled) Disable commands Default Publisher direction Block all unmanaged add-ins This policy setting blocks all add-ins that are not managed by the "List of managed add-ins" policy setting. If you enable this policy setting, and the "List of managed add-ins" policy setting is also enabled, all add-ins are blocked except those that are configured as 1 (always enabled) or 2 (configurable by the user) in the "List of managed add-ins" policy setting. If you disable or do not configure this policy setting, users can enable or disable any add-ins that are not managed by the "List of managed add-ins" policy setting. List of managed add-ins List of managed add-ins This policy setting allows you to specify which add-ins are always enabled, always disabled (blocked), or configurable by the user. To block add-ins that are not managed by this policy setting, you must also configure the "Block all unmanaged add-ins" policy setting. To enable this policy setting, provide the following information for each add-in: In "Value name," specify the programmatic identifier (ProgID) for COM add-ins. To obtain the ProgID for an add-in, use Registry Editor on the client computer where the add-in is installed to locate key names under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Publisher\Addins or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Publisher\Addins. You can also obtain the ProgID of an add-in by using Office Telemetry Dashboard. In "Value," specify the value as follows: To specify that an add-in is always disabled (blocked), type 0. To specify that an add-in is always enabled, type 1. To specify that an add-in is configurable by the user and not blocked by the "Block all unmanaged add-ins" policy setting when enabled, type 2. If you disable or do not enable this policy setting, the list of managed add-ins is deleted. If the "Block all unmanaged add-ins" policy setting is enabled, then all add-ins are blocked. Disable the Office Start screen for Publisher This policy setting controls whether the Office Start screen appears on boot for Publisher. If you enable this policy setting, users will not see the Office Start screen when they boot Publisher. If you disable or do not configure this policy setting, users will see the Office Start screen when they boot Publisher. Note: This policy setting is overridden by the policy setting "Microsoft Office 2016 > Miscellaneous > Disable the Office Start screen for all Office applications" if that policy setting is set. Personal templates path for Publisher This policy setting specifies the location of a user's personal templates. If you enable this policy setting, users will see any templates they have saved in the specified location in the custom templates tab on the Office Start screen and in File | New and when saving a template their default folder will change to be the specified location. If you disable or do not configure this policy setting, users will not see templates they have saved in the custom templates tab on the Office Start screen and in File | New and when saving a template their default folder will be their document save location. Default tab to show in Publisher on the Office Start screen and in File | New This policy setting controls what displays as the default tab in Publisher on the Office Start screen and in File | New. If you enable this policy setting, you can choose one of two options to become the default tab on the Office Start screen and in File | New: * Built-in – Users will the see built-in templates tab as the default tab in Publisher on the Office Start screen and in File | New. * Custom – Users will the see custom templates tab as the default tab in Publisher on the Office Start screen and in File | New when templates exist (this can include Custom XML programmed templates, templates in the Workgroup templates path, templates in the Personal templates path, or SharePoint templates). If you disable or do not configure this policy setting, users will see the Featured templates tab as the default tab in Publisher on the Office Start screen and in File | New Featured Built-in Custom File tab | Export | Publish HTML Web tab | View | Web Page Preview File tab | Share | Email File tab | Share | E-mail Preview Developer tab Developer tab | Code | Macros Developer tab | Code | Macro Security Developer tab | Code | Visual Basic Developer tab | Add-Ins | COM Add-Ins File tab | Options Enter a command bar ID to disable Default Publisher direction Minutes (range 1-120): List of managed add-ins Personal templates path Default tab