Enabling DHCP using PowerShell is very easy and can be accomplished in three lines of code. Yet for some reason many other online guides show the long way around. I previously posted about how to set static IP’s using PowerShell. This script to enable DHCP can be a complementary program inside an SCCM package to …
If your organization has computer labs which require static IP addresses, here is a very easy method to deploy static IP’s to each lab. Most labs will have some sort of numbering scheme as part of the computer name. We can take advantage of this in order to transform the computer number into an IP …
Programmatically Setting Static IP’s in a Computer Lab Read More »
I wrote this script to check for updates to some common software used in my organization. In order to do so, the script uses PowerShell to crawl the website of each piece of software so that it can get the software version number and download link. The script compares the version of the software it …
How to Crawl Websites to Download Software Updates with PowerShell Read More »
I wrote this script in order to extract MSP files from CAB files. The purpose of this in my case was to get Office updates that already existed in SCCM and to put their MSP files into the Office installation folder’s “updates” directory in order to have the updates automatically installed when Office is installed. …
This very simple PowerShell script can be used to set these options: DNS Suffix for this connection Register this connection’s addresses in DNS Use this connection’s DNS suffix in DNS registration I’ve seen many questions online on how to use a script to mark the two checkboxes in this “Advanced TCP/IP Settings” window. So here …
How to Set DNS Suffix and Registration using PowerShell Read More »
I wrote this PowerShell script for use as an application detection method inside an SCCM application. The SCCM application would set the network adapter configuration if it is not currently configured properly. This company has a special DNS setup for SCCM clients that is different than for non-SCCM clients. Here is the PowerShell code:
Contrary to popular belief, Dell’s CCTK tools (now called Dell Command Configure) do not have to be injected into WinPE in order to make changes to the BIOS during the WinPE phase of a task sequence. This applies both to SCCM and MDT task sequences. The benefit to not injecting CCTK into WinPE is that …
