In the past I didn’t post a lot of code here and used the great embedded JavaScript feature of Github to use Gist’s directly here.
I still like that feature, but I also found some issues with that approach. For example: AMP didn’t display and external JavaScript by default. So I decided to post the code local again and just display a link to the Gist behind it.

The WordPress native Code function didn’t work a expected, and most of the Plugins are complex and bring a lot of functions that I didn’t like. So I started to create my own Visual Studio Code (the editor of m choice) extension that could do that for me. As soon as the first (very crappy) alpha version was ready, a friend told me: “Great idea, but why the hell not use“.

After a quick look at descided, to stop the extension experiment, because is awesome. In the last few days I started to update, most of the old posts and embedded Gists are replaced by embedded code fragments.

The Microsoft Skype for Business Client first tries direct connection for the Session Initiation Protocol (SIP) traffic. After it gets time-out, the client will use a proxy proxy server, id exists. This could causes noticeable delays when you sign in the client, especially if the client tries to connect to Skype for Business Online.

Microsoft published some Updates and a UC Lobby Blog article about that. There is also a Support article about that.

In the UC Lobby Blog article contains a the following:

reg add HKCU\Software\Microsoft\UCCPlatform\Lync /v EnableDetectProxyForAllConnections /t REG_DWORD /d 1 /f

Read More

Exchange Server

Microsoft announced that they deprecated the support for the SmartScreen Antispam content filters for Exchange Servers. This script uninstall the old and retired SmartScreen Antispam Agents from the local Exchange Server.

There are known issues with the SmartScreen AntiSpam content filters if you run Exchange 2016 on Windows Server 2016. So removing them might be always a good idea if you want to have a stable Exchange.

The Script removes the following AntiSpam Agents:

  • Content Filter Agent
  • Sender Id Agent
  • Protocol Analysis Agent

Before running the script and remove the AntiSpam Agents listed above, you should consider a solid alternative solution. There are several good on Premises Solutions available, and there are even more Cloud Services, including Microsoft’s own Exchange Online Protection (EOP). This could be handy if you have Office 365, you just change/tweak the Mailflow and your Mailboxes are protected.
My favorite solution is a CentOS based Linux Box running Postfix, SpamAssassin and MIMEDefang. I use this together with some AntiVirus solutions to scan all inbound and Outbound mails. However, this is just my personal favorite because it’s very reliable and flexible, but I know that many prefer a all-in-one solution running on Windows. Again, there are a lot of great solutions out there!

Read More

By default the Active Directory related commands search for a best domain controller. This is great, but by default, I want them to make use of the closest one. Read More

I use PowerShell Web Access a lot while commuting and traveling. That comes handy, because I don’t need a working VPN and with an App (comes free from Sapien) even triggering some long-running scripts from the iPad out of a Hotel room as no longer a pain. And it doesn’t use a lot of data.

Here is a little function to tweak the web-based PowerShell window rendered by the gateway:

function Set-PSWAWindowSize
			Reformat the Window for PowerShell Web Access
			This function reformats the PowerShell Web Access windows style to fit a bit better.
			PS C:\> Set-PSWAWindowSize
			I use PowerShell Web Access a lot while traveling. That comes handy, 
			because I don't need a working VPN and with an App (comes free from 
			Sapien) even triggering some long-running scripts from the iPad out of 
			a Hotel room as no longer a pain. And it doesn't use a lot of data.
			Author: Joerg Hochwald -
			This script is public domain! IT COMES WITH NO WARRANTY!
	[CmdletBinding(SupportsShouldProcess = $true)]
	param ()
	if ($pscmdlet.ShouldProcess('PowerShell Window', 'Tweak it for PSWA usage'))
		# Get the BufferSize
		$bufferSize = $Host.UI.RawUI.BufferSize

		# Tweak the BufferSize
		$bufferSize.Width = 180
		$Host.UI.RawUI.BufferSize = $bufferSize

		# Get the WindowSize
		$WindowSize = $Host.UI.RawUI.WindowSize

		# Tweak the WindowSize
		$WindowSize.Width = 180
		$WindowSize.Height = 40
		$Host.UI.RawUI.WindowSize = $WindowSize

And there is a Gist for this.