Servus,
die Rolle brauchen sie nicht zwingend, ausser du hast deine names.nsf entsprechend angepaßt:
Preventing replication of policies to pre-Domino release 4.67a servers
Policy documents replicating from a Domino 6 server to a server earlier than Domino Release 4.67a can produce the error "Database has too many unique field names" repeatedly upon replication.
For Domino 6, a readers field ($PolRdrs) has been added to each of the policy forms in the Domino Directory. This field is blank by default, allowing all entities within a domain to have read access to the documents. Additionally, a new role, [PolicyReader], has been added to the ACL of the Domino Directory. To effectively stop the flow of policy documents to servers at levels earlier than 4.67a, complete these two steps:
1. Using Designer, open the Policy forms, set the default value of the $PolRdrs fields to [PolicyReader] role.
2. Assign the [PolicyReader] role to all entities (Servers, Administrators, etc.) within a domain that need to keep reader access to policy documents. Pre-Domino release 4.67a entities do not need reader access to policy documents.
Das Problem ist evtl der Punkt mit "Apply this setting" initially:
Set initial value -- You specify a default value for the field but the end-user has the option of changing this value. The setting will be set to this value once. If the end-user then specifies a value for a field with this setting, that value is saved and not overwritten by the value in the policy.
Normalerweise sollte die Einstellung bei jedem speichern oder ändern der Policy beim User eingetragen werden. Das ist sicher nicht immer der gewünschte Effekt, da der Benutzer die Einstellung ändern kann und bei einem erneuten Ändern des Setting Documents wird diese Änderung wieder überschrieben.
Wie hast du denn die Policy zugewiesen? Benutzerbezogen oder Organizational?
Grüsse
Christoph