Deploy Microsoft Office (2016) with GPO

I struggled a bit with finding the right solution to deploy Office 2016 to my users.

I found that running the setup.exe was not really possible as I was forced to use a .MSI-file.

I ended up with making a .BAT-file that started the install, when the user logs on to Windows. It only runs on the machines that I choose and only runs if Office 2016 is not already installed on the machine.

I created a group policy that ran a logon script (my .BAT-file) and linked it to the GPO where all users are located.

My .BAT-file:

@echo off
cls

 REM *** [GROUP/DEPARTMENT NAME] ***
if %computername%==PC1 goto checkVersion

 REM *** [OTHER GROUP/DEPARTMENT NAME] ***
if %computername%==PC2 goto checkVersion
if %computername%==PC3 goto checkVersion
if %computername%==PC4 goto checkVersion
if %computername%==PC26 goto checkVersion
if %computername%==PC27 goto checkVersion
if %computername%==YOU-GET-THE-POINT goto checkVersion

goto end

 :checkVersion
if exist "C:\Program Files (x86)\Microsoft Office\Office16\WINWORD.EXE" goto end
\\[PATH TO NETWORK SHARE HERE]\setup.exe

 :end
When all machines have Office 2016 installed, I will delete the .BAT and group policy.

Kommentarer

Send en kommentar

Populære opslag fra denne blog

Microsoft Office 2016 and the AUTO_ACTIVATE property

Billede
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).
Læs mere

Disable logon and logoff events (event id 4624, 4625, 4634 (and all the other ones...))

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:*
Læs mere

Enable OpenELEC SSH login with keys, and without password, disable local SSH password

1) Connect to OpenELEC using ordinary SSH with user 'root' and password 'openelec' 2) Change directory to .ssh/: cd .ssh/ 3) Generate a pair of ssh keys: ssh-keygen -t rsa Accept all default settings by pressing [ENTER]. If you are asked to to overwrite id_rsa press 'y' and [ENTER]. 4) Copy the content of the public key ('id_rsa.pub') into 'authorized_keys': cat id_rsa.pub >> authorized_keys 5) Copy 'id_rsa' to the device that you want to log into OpenELEC from, e.g. your mobile phone. 6) Setup the connection on your device using the private key ('id_rsa'). You still need to use the username 'root'. You can rename this file and give it a more useful name. Make sure that you are able to log in without using the password! 7) To disable the local password on OpenELEC/KODI, open settings in KODI and select "Services" on the left hand side. Here you can disable SSH password.
Læs mere