SCCM makes use of several files on the file system (usually in the INBOXES tree) to actually trigger various actions within the system. Many of these extensions are highlighted in the registry under the HKLM\SOFTWARE\Microsoft\SMS\Triggers\key.
For reference purposes, I’ve pulled out several here.
Read more…
Every year, the Barnes & Noble store at our mall allows a nonprofit to come in and wrap gifts for donations. So, you can purchase your gifts and get them wrapped, all in one go.
If you have disabled an IPv6 tunnel using the netsh command-line tool, the IPv6 interface will be successfully removed. However, the client will continue to register that interface’s IPv6 address with the DNS server until the server is rebooted.
To work around this issue, simply stop and restart the dnscache service (DNS Client service). This service is the one that actually registers names with the DNS server. Restarting it will cause it to re-inventory the interfaces and stop uploading old data.
This post has to deal with getting rid of the old, expired updates. Microsoft will replace its updates with newer versions and there is no need to continue to replicate, advertise, or even store old versions since the clients will not install them anyway.
If you end up using my method, you’ll end up with a slew of update lists and packages, one per month. Sometimes, it is convenient to roll those up into an annual list/package and deploy that to end users.
Once you have an update list created (either manually or via the script noted in Part 1, you’ll need to deploy them. In order to do that, you can use the Deployment Templates built in to the ConfigMgr console. If you need to deploy to several collections at once (or with slightly different settings), you’ll need to run through the deployment wizard multiple times. I’ve developed this script to help make that process a bit more efficient.
Collecting and deploying software updates on the server is a regular task (at least monthly) and somewhat tedious. To assist with this process, I’ve developed a handful of scripts that help to automate some of this work.
In this first article, I want to share a script that I use to actually create the update list. This script will search for updates that have not yet been deployed and that are actually required by at least one client system (so you need to usually wait a day or so for inventory of any new updates to be gathered).
There are times where it is advantageous to deploy software updates for a ConfigMgr client from the command-line. You may be telnetted/SSH’d into a command-window or you might be managing a Server Core edition of Windows Server. I’ve authored a script that can be used to manage your ConfigMgr software updates on the client.
The title is a bit of a mouthful, but here I’m talking about AD RMS templates and how to distribute them to client computers.