After releasing a couple of betas over the last week I have made some more changes to the Update Client Setting Priority Tool.
The major change is that the Tool now supports the amendment of SCEP policies.
In Configmgr 2012, if you create custom Client Settings a priority is assigned to the policy. This priority can be amended in the ConfigMgr console by right clicking the setting and choosing Increase or Decrease Priority.
If you are dealing with an environment with that contains many custom Client Settings then this can become a labourious task to adjust the priorities one click at a time.
To allow for bulk update of the Priority I have created the 'Update Client Settings Priority Tool'.
The complete script can be downloaded from the Technet Galleries here.
The Site Server hostname and Site Code need to be entered into the UpdateClientSettings-v1.0.ps1 script.
#Set ConfigMgr site info$SiteServer = "<Site Server>"$SiteCode = "<Site Code>"
For this example I want to adjust the Priority for SCEP Settings to '2' and Software Updates to '3'.
Run the UpdateClientSettings-v1.0.ps1 script.
Edit the relevant Client Settings Priority to the required Priority. Click Update.
Click Ok when complete.
The Client Settings Priority will be updated accordingly.
If duplicate values are entered in the Priority field then you will be warned.
Also the Default Client Settings priority is 10000. Custom client settings cannot be entered with a value equal or higher than this value. If you update with this value all other priorities will be updated but you will be warned about this value.
As mentioned with this release amending SCEP priorities is now supported. This works in exactly the same way as client settings.
Classy, I like :-) Want to give it a new skin? turn it into a .Net 4 EXE, I guess since it is all PowerShell it isn't suited, but if you want to convert this let me know and I'll introduce you to the tools and get you on your way mate
Sounds good Rob. Let's have a chat.
Powered by Zimbra