You’ve followed all the best practices and documentation. Your eDirectory trees are healthy and replicating with no errors. Time is in synchronization and ndsrepair shows no errors or external references hanging out there.
So, what do you do when eDirectory gets a request to remove 20,000 members from a group and replicates the change to all of the replicas?
A simple shell script to back up all configured eDirectory instances.
New product update includes new AuxMap utility and several bug fixes.
The standard tool to do SecureLogin administration is iManager. This tip has some setup steps that are required, but not well understood, for this setup to work.
This tip explains how to use corporate redirection to manage SecureLogin configuration “one offs” without having to modify each user object individually.
Typically the process of developing and testing SecureLogin scripts is done directly on a development user id. When the scripts are complete and tested and ready to be used by the general community they need to be copied to one, or several different objects in the supporting directory. This doc shows a sample of how to script the deployment process to make it quick and consistent.
Here’s part 2 of Geoff Carman’s article on Load Balancing User Placement in GroupWise Post Offices.
Let’s face the fact, assigning iPrint printers in iManager, especially if the users are in a different container than the iPrint Printer, can become very tedious and time consuming. First you have to wait for the browse window to choose a printer, then wait for the browse window to browse for the users or groups, and finally select all of your users. Well what if you had 5 executives that needed to have access to every Xerox Printer in the organization and these printers existed in multiple containers? Let’s say there were 35 of these printers. This could take hours. I’ll demonstrate how to do it in less than 5 minutes.
Once in a while an issue comes up where application A gives some odd errors in eDirectory but those errors seem to be cosmetic as application A is still fine and works (unless you count the messages in ndstrace). What does this mean when you see a -714 from eDirectory while tracing LDAP that is talking about some “iterator”? What does an LDAP error 51 mean when everything still seems to return properly? Today I am going to try to share some information on Virtual List Views (VLV) by explaining what they are, how you can use them, and a few cases where they do not work with eDirectory.