If you have followed my guide for automating the Sccm primary site server install, you have a quick way to deploy SCCM. Now it’s time to automate the configuration. In this post, the Software Update Point (SUP).
In this one, we install and configure Wsus on a server. This is a supplementary post to the SCCM Configure SUP post.
As my recent posts indicate, I have been exploring networking related tasks in PowerShell. Sticking with that theme, I thought it would be nice to play with an actual firewall in my lab. With that being said, lets get into the OpenWRT setup on Hyper-V.
With all the benefits that DHCP has to offer, it would be crazy if we needed to put a DHCP server in each network we setup. With this post, I will go through the steps of getting your Windows DHCP server working across whatever networks you want.
Setting up a DHCP Windows server is made very easy in PowerShell. In this post, we use PowerShell to setup a DHCP server, and do some additional configuration. This will ultimately lead to faster server builds, as the IP configuration will automatically be taken care of!
In this post, I will be deploying RRAS (Routing and Remote Access Server). More specifically, I will utilize the 'routing' component of RRAS.
Create a VM from a sysprepped image with 1 line of code.
I wanted a simple command that would give me the basic subnet information I commonly want. Identifying the Network ID was tedious, as was converting an IP / Subnet to CIDR notation and vice-versa. Now I have one command that can do it all.
I have covered working with passwords in PowerShell in a previous post, but wanted to go over some more advanced options.
Building and rebuilding labs is something I do frequently. Active Directory is one the biggest requirements for a Windows lab. This means constantly installing AD Forests with the same configurations. Automating this with PowerShell is pretty straightforward, but Dsc can make it even more so.