I am honored to have been chosen as one of 50 World Champions of IBM Collaboration Solutions
Thanks to IBM for recognition and congratulations to all nominated.
The list is here http://www.ibm.com/developerworks/lotus/champions/
I am honored to have been chosen as one of 50 World Champions of IBM Collaboration Solutions
Thanks to IBM for recognition and congratulations to all nominated.
The list is here http://www.ibm.com/developerworks/lotus/champions/
From TN 1182264
This behavior can occur if you have not set the “Enforce server access setting” field to Yes. The default value is No, which does not apply the “Not Access Server” information to Web (HTTP) traffic. You must set this field to Yes to have the HTTP task honor the settings on the Security tab.
The “Enforce server access setting” field is in the Server document on the Ports -> Internet Ports -> Web tab. After changing the value to Yes, restart the HTTP task to apply the changes. In one particular case, the changes did not take effect with restarting the HTTP task, so the customer restarted the server.
Today i finished the setup of Sametime for a client in my city. The MS AD administrator asked about how to prevent users from loggin in based on a Group.
Sametime doesn’t have this kind of police. If you use the TN 1166845 the solution is to add a new attribute for every user. :-(.
This workaround doesn’t meet our requirements (restricting using groups). I change the LDAP search filter in stconfig.nsf from;
Search filter for resolving person names: (&(objectclass=organizationalPerson)(|(cn=%s*)(givenname=%s*)
(sn=%s*)(mail=%s*)))
Search filter to use when resolving a user name to a distinguished name: (&(objectclass=organizationalPerson)(|(cn=%s)(givenname=%s)
(sn=%s)(mail=%s)))
To:
Search filter for resolving person names: (&(objectclass=organizationalPerson)(memberOf=CN=GroupName,OU=OUName,DC=domain,DC=com,DC=br)(|(cn=%s*)(givenname=%s*)
(sn=%s*)(mail=%s*)))
Search filter to use when resolving a user name to a distinguished name: (&(objectclass=organizationalPerson)(memberOf=CN=GroupName,OU=OUName,DC=domain,DC=com,DC=br)(|(cn=%s)(givenname=%s)
(sn=%s)(mail=%s)))
Reboot the Sametime and it will work.
Yesterday i started installing the Sametime 8.5.x for 1200 users. The client will use virtually all the capabilities, audio, video, integration with Outlook and mobile clients.
Domino Administrator is not available in Brazilian Portuguese. Some Domino Administrators want to use Notes e Administrator in native language.
To change the Administrator (English version) to Brazilian Portuguese:
AltNameLanguage=pt
ContentLanguage=pt-BR
UserInterface=pt-BR
Using NotesDatabase.CreateDocumentCollection on an unopened database is known to cause a crash. This issue was reported to Quality Engineering as SPR# AGUD7LPRDW. For safety, use NotesDatabase.IsOpen to test before calling this method.
Dim coll As NotesDocumentCollection
if db.IsOpen Then
Set coll = db.CreateDocumentCollection
...
Other methods for creating empty collections, described in the Domino Designer wiki, are useful in earlier versions, but NotesDatabase.CreateDocumentCollection is faster.
The compat task does not accept tell commands according to the Domino Administration Help.
But if you want to stop compact task through a program you can use the command TELL COMPACT QUIT.
https://www-304.ibm.com/support/docview.wss?uid=swg21099361
This TN have useful information for troubleshooting general Lotus Domino server performance issues.
FromTN 1193738
To avoid possible server hangs or crashes, it is recommended that Fixup be performed outside business hours to avoid impacting users. However, if Fixup must be run during business hours, which is often the case, follow the steps below to minimize the impact:
1. Load the Fixup database.nsf -C -O against the file.
* -C will only verify the integrity of the database and report errors to the log (database is not modified).
* -O runs on an open database otherwise open databases will be skipped.
Note:
If you run Fixup on open databases, Fixup takes the databases offline to perform the fixup.
This is the default if you run Fixup and specify a database name. Without this option, when you do not specify database names, Fixup does not run on open databases.
Important: If the report to the log contains a problem that has never been seen before, do NOT attempt to run Fixup during business hours.
2. If you choose to run Fixup during peak hours, consider running Compact -C instead. This copy-style compaction is not able to copy damaged objects and is used to resolve database corruption issues. This results in less recoverable data but reduces exposure to failures related to Fixup.
3. Fixup is designed to recover corrupt data. This utility manages data in an invalid state but occasionally is unable to manage data errors which can result in server hangs or crashes. This is why running Fixup -C is recommended.
4. When running Fixup while in production, it is important to monitor its state. Fixup -L (with the -C -O) will log detailed information to the console on Fixup’s progress. If it is not making any progress (“Performing consistency check” is the first message reported), QUIT the Fixup process. Taking this action early may avoid a server hang.
5. Enable Transaction Logging. Transactional Logging provides improved data integrity, which reduces the exposure to corruption and eliminates the need to use Fixup on a regular basis.
Notes users receive messages with winmail.dat attachments. This occurs even though TNEFEnableConversion=1 is enabled on the Domino SMTP server.
From the TN 1441039
This issue is fixed in Notes/Domino 8.0.2 FP6, 8.5.1FP3 and 8.5.2.
Fix details: SPR# SAZR7V3ME6