But my question is if there is a way to clear and pull down the policies to one indiviual client without updating the policies on the server. (I have clients where updating the policies on the server doesnt force the reload in the client). I want to sort off reset and clear the policy pull-down process.
I recently discovered that archive policies are not actually applied to mail files by the client. They are applied by the administration process on the server.
I knew that the mail policy was stored in the mail file also. But it makes perfect sense that the archive profile is also stored there, as you could archive from your iNotes interface.
And I think that you should look at it like these profiles are stored in the users mail file. Because it must still be applied by either the notes client or the server that you connect to to use your iNotes.
The question is if the archive policy is stored by adminp or it is stored when the compact -A is run.
And my need to clear and re-pull all policies from the server stands.
Subject: Archive policy uses dynconfig, not adminp
And compact -A will run archive functions – but has nothing to do with the application of archive policies. To clear out all policy data for a particular user, you can open the hidden $Policies view in the client’s local names.nsf (via ctr-shift - View - Goto), and delete all docs there. These include all policies – not just archive policies – and will be repopulated when the client next pulls down any policy data. Note that mail policies use the server’s adminp task to write to mailfiles; archive policies use the client’s ndynconfig. Dynconfig is triggered by the user’s authentication with home server – and it should detect the missing policy data and replace it – if not immediately, then at some point within the day.
And just to be sure, you might want to run the Admin client’s policy synopsis for this user (if you haven’t already) – to confirm that your understanding of this particular user’s policy assignments matches Domino’s.
sorry if my answer was not clear. the archive policy is stored in each individual mail file - you can see it in the profile documents. the operation that puts it into each mail file when you create/edit an archive policy is the administration process. hope that is clearer.