Nerd blog

Use this script to cleanup WSUS server. I schedule it to run once each week:

I've created this PowerShell script to delete all email addresses from SpamTitan (API) global whitelist filter. Feel free to use it as long as you link to this article on your site or in your script:

I've created this PowerShell script to import email addresses into SpamTitan (API) global whitelist filter from a text file. Feel free to use it as long as you link to this article on your site or in your script:

I was really disappointed when my new Nexus 5X did not sync new e-mails and calendar entries from the web. I use these functions all day long and the device is useless if it does not update new items. I already began to install 3rd party apps, but then decided to look into the matter again: It seems to be a known bug that Google is investigating, but I couldn't wait for them to come up with a fix. I suspected the cause to be the Android 6 doze function (a battery saving function in Android 6) since my device hadn't updated the calendar for several hours (I could see that my account/calendar was last updated the night before at around 9 p.m.). To disable the calendar's (and a few other apps, but I suspect that the settings for the calendar is enough) battery save function use the settings: (The screenshots are in Danish, but I think you get the point)

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:*

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 Fil...

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).