Client Settings - Set Priority Level
I have a need to set a priority level for a Client Settings Policy. I realize that I can increase or decrease each policy but I would like to set one policy to Priority "9999". Basically I have a need to have a second default Client
Setting and currently I can only give it the lowest priority of the client setting that I have created, say priority 83. However I still want this policy to be second in line if someone create a new policy down the road and does not increase their new
policy above the secondary default policy leaving this newly created policy with a priority of 84.
July 31st, 2013 3:47pm
It's not going to be second in line. If you have a custom policy applied to a collection, anything set in that policy overrides the default policy. If it's deployed, it is the one and only policy applied. If there are no custom client
settings deployed to a collection, that's when the default is applied.
Free Windows Admin Tool Kit Click here and download it now
July 31st, 2013 3:51pm
I understand that, in my scenario this situation will not apply.
July 31st, 2013 3:54pm
If someone creates a new policy and deploys it but does not increase the priority above the one you already had set, it will not apply anyway. It starts at 1 and goes down from there. But, only for policies that have been deployed. You
can't create a secondary default policy. The default policy is the only one that does not have to be deployed and is automatically applied. Am I understanding your question?
Free Windows Admin Tool Kit Click here and download it now
July 31st, 2013 4:07pm
If it's deployed, it is the one and only policy applied.
No. All policies that are deployed will be merged. The priority is used for conflict resolution.
July 31st, 2013 4:11pm
I do not belive you are understanding my question I believe you are reading in to my situation to much. I do not care how it will work or what will be applied, all I want to be able to do is set a policy with a priority of 9999, is that possible?
Free Windows Admin Tool Kit Click here and download it now
July 31st, 2013 4:22pm
If it's deployed, it is the one and only policy applied.
No. All policies that are deployed will be merged. The priority is used for conflict resolu
July 31st, 2013 4:40pm
I do not belive you are understanding my question I believe you are reading in to my situation to much. I do not care how it will work or what will be applied, all I want to be able to do is set a policy with a priority of 9999, is that possible?
AFAIK, the answer is no.
Free Windows Admin Tool Kit Click here and download it now
July 31st, 2013 4:43pm
Even from a PowerShell cmd or a manual back-end work around?AFAIK, the answer is no.
July 31st, 2013 4:46pm
I do not belive you are understanding my question I believe you are reading in to my situation to much. I do not care how it will work or what will be applied, all I want to be able to do is set a policy with a priority of 9999, is that possible?Not that I know of unless there is an SDK hack out there that I don't know about. But, I doubt it. What I was getting at was: why would you want one that has a 9999 priority? I'm just curious as to what your goal is. I didn't really understand that part.
Free Windows Admin Tool Kit Click here and download it now
July 31st, 2013 4:48pm
I need Software Updates & Endpoint enabled on the default policy for OSD reasons but can not have it enabled as we need to allow control for areas to Opt in to Software Updates or Endpoint so I need a secondary policy to disable them for all system.
I can do that with a low priority policy except someone else can come in creating another policy later and not understand that they need to be in front of the secondary default policy so i want to set it to 9999.
July 31st, 2013 4:55pm
AFAIK, the answer is no.
Even from a PowerShell cmd or a manual back-end work around?
Again AFAIK, still no. Even if there was some hack you could put in place, you'd then be in an unsupported configuration and wouldn't be eligible for official support should you ever need it.
I'd put a very specific name on the policy and educate anyone else who has rights to create client settings. If you name it something like 'THIS POLICY MUST BE THE LOWEST PRIORITY OR ELSE I'LL CHASE YOU AROUND AND BEAT YOU WITH A RUBBER HOSE' should hopefully be enough to clue in anyone who isn't familiar with your set
Free Windows Admin Tool Kit Click here and download it now
July 31st, 2013 7:46pm
This topic is archived. No further replies will be accepted.
Other recent topics
