blog.colemberg.ch

cm12 policy files are splited in Assigment and Body

—

by

mirko colemberg
in

In this Post i will show you the management from the new Policy Files that reach the Client as a destination via Management Point after a polling Interval.

The Client Poll’s for new Policy’s at the Management Point, the Management Point send’s this to the Site Server/Database, the Site Server Creates Policy Files to deliver this to the client.

But Wait, there is nomore one File, now it is splited in Two, a Assigenment and a Body File!!!

The Assignement File; are everytime created from the Database and it is individuel for every Client, that means that the file change on every request his header, why: there is every time a request from a diffrent client name 😉

The Body File; Contains the actual policy settings to be applied to the client. Thats for all Clients the Same content.

The Body File is generation once by the first request and will be saved on the management point cache for every next request.

There are two things to know now:

1. If you would like cleare the cache on the Management Point you have to stop the Management Point Provider, the easyst Way is to do this with the Config Manager Service Manager.

2. If you change fast a deployment (that generates Policy files) maybe you have wait that the management point know this and send the new body file or you can stop and start the Management point provider to clean it that the body file generats newly.

 

Hope that haelps to understand more the Management point and the Job with the Policy files.

Test it befor us it! No warrenties…

Comments

2 responses to “cm12 policy files are splited in Assigment and Body”

  1. Andrew Craig Avatar
    Andrew Craig

    Hey Mirko, how are you? This post is very good, and i need a little more information if you have it… Are the assigned policies stored in the sql db? and retrieved and compiled by the MP and then sent to the client via mp outboxes? I have a client who had 300 assigned deployments and for testing i moved it to another collection so it should only receive around 10 assigned deployments. Question is how to really check that everything is up to date? policyspy shows the policies on the computer, they look correct. the c:\windows\ccm\temp has a lot fewer files in it so that looks ok, but in respolicymap table in the db i still see far too many references. Apart from restarting the mp, which would clear the mp cache like you said, is there a process to clean up the db? or is it not necessary? Not sure if there is a built-in maintenance task for this… My concern is that if the mp compiles all these policies for the client and then the client discards them later that the performance will be affected. Ah ha, i have answered my own question… “IsTombstoned”!!! Ok so no problem. Hey, i have written the whole thing here, it seems a waste to delete it now, maybe it will help someone understand the policy story better GLG Andy ::))

  2. mirko colemberg Avatar
    mirko colemberg

    Haha, thats OK.

    On the MP is only the Body for a Policy, the Assigenment is on every ask from a Client on a MP created from the Database. If you reboot the MP there is only clear the Body pice from his Cache.

    Hope it helps also 😉

Leave a Reply

Follow

Get every new post delivered to your Inbox

Join other followers:

%d bloggers like this: