Updating downlevel os configuration
I guess summer time means “time to cleanup/fix all the broken clients” :-)A couple of years ago I create another similar script for CU updates: https://gallery.technet.microsoft.com/SCCM-Creating-Collections-f334c7f0 but this time I wanted to make the script simpler, fully automated and only create the collections that was needed by the customer.
This script will pull a list of all the client versions from the SCCM site server, and create a collection…
command to update your private candidate configuration.
When you do this, your private candidate configuration contains a copy of the most recently committed configuration with your private changes merged in.
What could prevent KB2999226 from installing as part of the runtime?
Today I got a call from a System Center Configuration Manager (SCCM/Config Mgr) customer that wanted to automate the creation of device collections for each SCCM client version, that was in their environment.Hyper-V in Windows Server 2012 R2 is already full of functionality, and for those of you who don’t believe it is already production-ready, I suggest taking another look at this current technology.If you are running Hyper-V already, using another hypervisor but are looking to switch, or perhaps partially switch, now is the best time to start checking it out.I've run the command prompt as administrator and the following is what I get when trying to run the script.By now, you’ve probably already heard, seen or even played with one of the technical Windows Server 2016 previews. Hyper-V 2016 will bring lots of enhancements and new functionality that will improve your data center and solve some of the limitations you might be experiencing.