PSGM

Creating a self-signed wildcard certificate for server authentication in a Windows environment

We are increasingly using, or being required to use, SSL-encrypted sessions (or technically, TLS-encrypted sessions) for application services. In technical terms, because the Fully Qualified Domain Name (FQDN) in the Uniform Resource Locator (URL) used by a client to access a service needs to match the Common Name (CN) in the certificate used by that service, we potentially have a proliferation of certificates (at least one per server) that need to be available to clients

One approach to addressing this proliferation is to use wildcard certificates that match multiple FQDNs within a domain. Below is a discussion on generating self-signed wildcard certificates as a way of addressing this

What

PSGM

NTFS file system limitation

Problem description:

Under certain circumstances applications and utilities may fail with one (or more) of the following symptoms

• Error 0x80070299
• The requested operation could not be completed due to a file system limitation
• Insufficient system resources exist to complete the requested service

PSGM

Disk surprise removed

Problem description:

Under certain circumstances applications and utilities may fail with one (or more) of the following symptoms

• Event ID 157 - Disk # has been surprise removed. The original documentation for this message appears to be this blog
• Event ID 153 - The IO operation at logical block address xxxxxxxx for Disk # was retried. The original documentation for this message appears to be this blog

PSGM

Server on a stick

What is a "Server on a stick"?

It is the Windows server equivalent of the Windows consumer product feature "Windows To Go". Basically it is creating a Windows Server image on a bootable USB drive

Why?