Test Layout

Whenever I'm doing new installs of Exchange, I'm annoyed when I need to figure out the .NET Framework version installed based on registry keys. You can see the documentation here: https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed  Just like the bad infomercial says: "There's got to be a better way!" This has bothered me for sometime and I considered writing a small script to query and display the version. Then I thought...that would be good if I put it in the PowerShell Gallery so that I could easily access it from anywhere. Then I thought...I'm probably not the first person to have this idea. In the PowerShell gallery, Joakim Borger Svendsen has been kind enough to create this for us as a module named DotNetVersionLister . He's also kind enough to keep it updated. There have been seven releases in 2017. On a computer that has Internet access, you can install directly from the PowerShell Gallery...

For the last couple of weeks I've been working with Windows containers using Docker. I ran into a severe problem with the networking. I created a transparent network on the host and rebooted. After reboot, the docker service wouldn't start and had the following error in the event logs: Log Name:      Application Source:        docker Event ID:      4 Task Category: None Level:         Error Error starting daemon: Error initializing network controller: error obtaining controller instance: failed to get endpoints from store: failed to decode endpoint IPv4 address ( ) after json unmarshal: invalid CIDR address: My first fix for this issue was to delete the following file: C:\ProgramData\docker\network\files\local-kv.db After this file was deleted, I was able to start the Docker service and it stayed running. That file was recreated when the docker service started and...