• Browse Blogs
  • My Blog
  • My Updates

+Tags Get help with tags?

  • View as cloud  | list

+ Similar Blogs

photo

Lotus Nut

111 Entries |  Chris Whisonant
Updated 
RatingsRatings 23     CommentsComments 157
photo

Erik Brooks

35 Entries |  Erik Brooks
Updated 
RatingsRatings 9     CommentsComments 92
photo

CrashTestChix

100 Entries |  Marie L Scott
Updated 
RatingsRatings 13     CommentsComments 226
photo

Patrick Picar...

62 Entries |  Patrick Picard
Updated 
RatingsRatings 2     CommentsComments 112
photo

Henning Schmi...

54 Entries |  Henning Schmidt
Updated 
RatingsRatings 1     No CommentsComments 0

+ Bookmarks

+ Blog Authors  

1 - 2 of 2
  • Previous
  • Next
  • Page   1

Caveat with AdminP Direct Deposit

Chad Scott |   | Comments (2)  |  Visits (890)
New to 8.x is a feature that allows AdminP requests to be created directly in the admin4.nsf of the server that will process the request. From Administration Help:
The Administration Process can deposit requests directly into the Administration Requests database (ADMIN4.NSF) -- The Administration Process can now deposit administration requests directly into a target server's Administration Requests database (ADMIN4.NSF) instead of depositing the request into a local copy of ADMIN4.NSF.
The direct deposit feature also applies on the client side. In particular, an 8.x client will attempt to deposit the Change HTTP Password in Domino Directory request in the administration server's admin4.nsf following a password change when synchronization is configured. In complex environments, regional clients and servers may not have a direct path to the administration server, causing the client to fail when attempting to create the request. In this case, you can use the ADMINP_DONT_ATTEMPT_DIRECT_DEPOSIT=1 parameter to instruct the client to bypass the direct deposit route and create the synchronization request in the home server's admin4.nsf. Replication will then carry the request to the administration server, allowing the process to complete successfully.
No RatingsRatings 0

Desktop settings are incorrectly reapplied at the client

Chad Scott |   | Comments (0)  |  Visits (390)
Be on the lookout for an issue where 8.0.x clients will reapply desktop settings even though the policy specifies that they should only be set initially. This is being tracked in SPR HYAI7DR4Z5 and has been fixed for 8.0.3. The issue does not impact 8.5.
No RatingsRatings 0

  • Previous
  • Next
Jump to page of 1
Skip to main content link. Accesskey S
IBM Lotus Connections Help Tools About