Posted inWindows Server

Enable NTFS long paths GPO in Windows Server 2022, 2019 and Windows Server 2016

With Windows Server 2016 released, we can finally lift the idiotic 260 characters limitation for NTFS paths. In this post I'll show you how to configure the "Enable Win32 long paths" Group Policy, and how to make the "LongPathsEnabled" change in the Windows registry. The NTFS long paths GPO is also still required for Windows Server 2022 and 2019.
20/10/2016Posted inWindows Server
Posted inWindows Server

KMS Migration from 2008 R2 to Windows Server 2012 R2 and KMS Activation Known Issues

How to migratie an Windows Server 2008 R2 KMS to Windows Server 2012 R2, for volume activation of Microsoft products? On a new KMS server? You don't, apparently there is no Windows Server 2008 (R2) KMS to Windows Server 2012 R2 migration. There is no way to automatically transfer your KMS role along with the products its activating to another server. Luckily Charity Shelbourne wrote up a handy how to for this task.
02/06/2016Posted inWindows Server
AppCmd introduction and examples
Posted inWindows Server

AppCmd introduction and examples

AppCmd.exe is a command-line utility to manage Windows Server IIS 7+ web servers. The AppCmd command is your one-stop-shop for administering Windows Server IIS web servers. In combination with WinRM it’s your Swiss Army knife for your daily routine. This post introduces appcmd and provides you with a lot of helpful appcmd examples.
17/05/2016Posted inWindows Server
Posted inWindows Server

SQL Server versions list

An unofficial build chart lists all of the known SQL Server Service Packs (SP), Cumulative Updates (CU), patches, hotfixes and other builds, including builds of MS SQL Server 2019, 2017, 2016, 2014, 2012, 2008 R2, 2008, 2005, 2000, 7.0, 6.5 and 6.0 that have been released.
11/12/2015Posted inWindows Server
Posted inWindows Server

RewriteProxy with .htaccess in IIS

Rewrite and proxy HTTP requests in IIS using a .htaccess. In my case scenario, I had to proxy requests in IIS, because a website was moved from web server A to B, and the DNS wasn't updated yet. All HTTP requests for the moved website are handled in IIS' Default Web Site; that's the wildcard host, and the original host no longer existed there. We needed to match our website and proxy those requests to the new IIS web server. This can either be done using a proxy with IIS URL Rewrite, IIS Application Request Routing (ARR), or a .htaccess file handled by Helicon Ape.
08/10/2015Posted inWindows Server