Symetrik Domino Consulting

Archive for the ‘Tricks’ Category

This is a simple, but effective tip. Any time you change your policies, make sure that your changes have replicated across all servers.

You should then issue “Drop All” at the server console. Any active clients will automatically re-connect to the server forcing them to authenticate, and thus pulling down the new policies.

Today, I wanted to add a new field to our person document form in our directory for our internal VOIP telephone extensions. There are alot of people out there now using VOIP, but the problem is that our users don’t know what the extensions are for people in other sites/locations. If they would use the VOIP extension instead of dialing the long distance number, we could save alot of money.

I created a field called OnNet, refreshed the design of the NAB, populated the field with some actual data, and then went to test it out. Works great.

However, our corporate accessible directory is a web application on a Linux box that performs LDAP queries to Domino.

If I authenticated to LDAP, I could see all of the person document fields with a LDAP browser including OnNet and the data, but if I don’t authenticate, I can only see the domino fields (or LDAP attributes) that are specified in the * server configuration document. Read the rest of this entry »

In a recent disaster at our organization, we had to restore the program directory of a server. Since someone built the server with the default d:\lotus\domino and d:\lotus\domino\data, the outsource host facility restored the whole d:\lotus directory and it took us 4 hours waiting while the server was down.

This highlights some points that I always try to make about Domino disk installation: Read the rest of this entry »

I know in R8 this works much differently, you can now select a message, hold the shift key, and then scroll way down the view and click a second message to select all messages in between. Great!

However, in R6.5.x and below (not sure about 7) selecting hundreds of documents at a time can be time consuming.

Say for example, your log.nsf or one of your mail.boxes becomes corrupt, and you have event triggers setup for corrupt databases – you can get a hell of a lot of notification messages in just a few minutes.

This morning I came in to find 7000 notification messages that one of the mail.boxes was corrupt on one of my servers. Read the rest of this entry »

Today is Tuesday, but it seems like Monday. Mostly, because I took a day off yesterday, but also because I’ve had problem after problem that seemed to have no simple solution:

First, there was a server that was upgraded over the weekend. For some strange reason, it had been generating false alarm HTTP probes.

The probe has timed out for the following statistic: QOS.HTTP.Pass2/Domain.PASS-5Q852E.ResponseTime

Second, a user was complaining that they received a “Mail Encryption Failure” popup box and with the error message “If you choose to continue sending, the following recipients(s) will receive an unencrypted copy of the message.” when trying to send encrypted messages.

Third, a regional admin was complaining that he didn’t have access to any of the mailboxes in a folder on a remote server. Read the rest of this entry »