In Office 2013 is was possible to automatically activate it after install by using a property called AUTO_ACTIVATE in the Office Customization Tool (OCT) (to start the OCT, you just need to run the setup for the Office installation like this: 'setup.exe /admin' - you don't need to download the OCT). It doesn't work in Office 2016. I solved it by running the OCT and doing this instead: If you want to know how the make the install completely automated, read on: I modified these settings: Save the .MSP file in the Office installation folder under \updates\. All .MSP files in this folder, is used during installation. If files exist in this folder, and you run setup.exe, the 'normal' Office installation will use the settings under \updates\ (the settings modified in the .MSP file created in OCT).
I have tried several times to make my domain controller not log logon and logoff events in the security log. But it seems to ignore the settings in the domain controller group policy. I now use Auditpol in stead - that works (thanks Morgan J ): To disable all logon and logoff messages in the security log use (in an elevated command prompt): auditpol /set /category:"Logon/Logoff" /success:disable & auditpol /set /category:"Logon/Logoff" /failure:disable It is also possible to just disable the logon messages by using the subcategory switch: auditpol /set /subcategory:"Logon" /success:disable & auditpol /set /subcategory:"Logon" /failure:disable To view the current settings, run: auditpol /get /category:*
When running a CU on an Exchange hybrid setup the installation failed because services were disabled. This script will make sure every 10 seconds that Exchange services are not disabled during installation.