So with the RTM of Windows Server 2016, with it comes official support for docker; and with that - containers. Awesome. In this post, we’ll talk about container introspection, via the Docker Daemon / API. First and foremost, I’m not going to get into the nitty gritty of installing and configuring docker.

Another little tidbit I cam across in setting up a Raspia Raspberry Pi 3 (model b) for use in a kiosk setting (actually just an always on system monitor, but same idea). After X minutes, the screen blanking setting will come into play;

Here’s one little trick that I recently came across when performing a DPM 2012 R2 redirected SQL recovery.

So here we go. A finalized script that will create the VPN profile, as necessary, for Meraki VPN deployment. This should enable complete deployment of a Meraki VPN profile to clients, using just PowerShell 4.0 and enable split tunneling.

Well, humble pie time. But this is good stuff here. Turns out I missed one little teeny tiny flag in the Add-VpnConnection cmdlet. Oops. But this is good!

Grumble. We’re in the process of replacing our infrastructure with Meraki products - in fact, we’ve been extremely pleased with this so far. Except for that one thing. Deploying the Client VPN sucks.

Scenario: The development team needs periodic copies of all databases in a protection group distributed to a share across a site link.

Dashing.io; super cool, and pretty fly. Easy enough to configure a quick and small linux VM to host it. But how about pushing data to it, from Powershell? The key is Invoke-RestMethod- Let’s look at two of the simple built in widgets:

So I’ve been working through the process of putting together a new Windows 8.1 image for OSD Deployment within our organization.