Domino 9 und frühere Versionen > ND9: Administration & Userprobleme

ID-Vault // SelfService Passwort Reset

<< < (2/3) > >>

typeOneg:

--- Zitat von: Tweeks am 07.08.13 - 15:19:44 ---Die einfachste Möglichkeit eine Policy zu pushen ist, die Policy-Dokumente aus der lokalen names.nsf zu löschen und den Client einmal neu zu starten.
Dann MUSS der Client sich ja die Einstellungen neu vom Server holen.

MfG
Matthias

--- Ende Zitat ---


Ja, wobei selbst dann die Policies nicht immer greifen. Könnte man das Löschen der Policy-Dox in der lokalen names.nsf in einen Button verpacken, den man den Usern per Mail schickt? Bin mehr der Admin als der Developer :-)

ascabg:
Hallo,

Klar kannst Du das.



Andreas

m3:

--- Zitat von: typeOneg am 07.08.13 - 14:51:09 ---aha....hatte ich dann nur einen Denkfehler?

D.h., wenn ich den SampleAgent in der pwdresetsample.nsf so


--- Zitat ---Call Session.ResetUserPassword("", "", "test")
--- Ende Zitat ---

automatisch laufen lasse, wird bei allen Usern am Server, wo der Agent läuft, als Notes-Kennwort "test" gesetzt?

--- Ende Zitat ---
Wie Andreas schon meinte, das wird so nicht klappen. Hol Dir einen Dev dazu, fuer den sollte das trivial sein ...

m3:
Und weil ich es gerade gefunden habe:


--- Zitat ---How do policies get pulled and applied on the client?
When the client authenticates with the users home server, it sends over a hashed value that indicates what policy information it thinks it has stored locally.  The server calculates a similar hashed value for what it thinks the client should have.  If those values do not match, then the server tells the client that it need to refresh it's policies.  At this point, the client launches the dynamic configuration process, Dyncfg.exe, passing it flags on the command line that tell it to pull policies.  Dyncfg uses the NAMEGetPolicy API, which asks the server to calculate the effective policy for the user, and then stores the effective policies locally in the clients NAMES.NSF database.  You can see your locally cached policy documents by opening the hidden $Policies view (via Ctrl-Shift View\Go To).  After pulling and applying the policies to the client, Dyncfg stores off the new hashed value that it got from the server, to be sent back to the server during the next authentication, which starts this whole process over again.

So what info is encoded in this hashed value?  Previous to R8.5 and dynamic policies, it was simply the last modified time of the $Policies view in the server's NAB.  With the introduction of dynamic policies, the hash was expanded to include any group or user names that caused a policy to be assigned to the user, as well as the last modified time of the $Policies view.  So, if any policy info changes on the server, or the user is assigned to any new groups that cause a policy to be assigned to them, then the hash will change which will trigger the client to pull new policies.  Note that on the Domino server, we rely on the Update task to update the views in the NAB once per minute.  If this doesn't happen, then the $Policies view won't get updated, the code won't know anything has changed, and no policy changes will get pulled to the client.  This is a very common cause of policy problems on test machines.

How to I force the client to pull policies?
Part of the hashed value is the last modified time of the $Policies view in the Domino Directory on the server.  So modifying any policy or policy settings document (e.g., simple edit and save) and updating the $Policies view should cause the client to re-pull policies when it next authenticates with the server.  To make that happen, you can disconnect the client by hitting Ctrl-F5 and then reconnect to the server in any way (e.g., open any database on that server).  There have been some bugs where this process breaks down and policies do not get pulled.  We've fixed them as we've found them, the most recent fixes going into R8.5 (as of 7/1/2008).
--- Ende Zitat ---
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/domino-policies-faq

typeOneg:
werd' mal mit unserem businesspartner quatschen :-)

Navigation

[0] Themen-Index

[#] Nächste Seite

[*] Vorherige Sete