IBM Support

Lotus Domino 8.5.1 Administrator Help Errata

Technote (troubleshooting)


Problem

Some information in the Domino Administrator 8.5.1 Help is either incomplete or inaccurate.

Resolving the problem

The following topics in the Domino Administrator 8.5.1 Help have either incomplete or inaccurate information. The corrected information is provided here.

Tip You can click a topic title to see the original 8.5.1 topic in the Information center.




Adding update kits to the Smart Upgrade application

In this topic, the following statement was omitted from the "Allowed Users & Servers" field description:

If the "Allowed Users & Servers" field is left blank, the Smart Upgrade kit will be applied to all Notes users in the Domino domain.



Access level privileges in the ACL

In future releases of this topic, the following additional paragraph will appear just after the following Note:

Note: Users who have this privilege can modify or delete any shared folder, view, or navigator in the database, regardless of whether they created it. Use caution when granting this privilege.

Use similar caution when assigning this privilege to a server. For example, in a hub-and-spoke configuration, a spoke server typically has Editor access; if it also has this privilege in its ACL entry, the potential exists for replication back to the hub to affect the following design elements: views, folders, shared columns, and navigators. If you want your hub server to control all design elements, do not grant this privilege to spoke servers.

For more information, see the following article on the Lotus Notes and Domino wiki:
Preventing spoke servers from modifying design elements on a hub server

(PMR #78440)



Built-in and custom Server.Load scripts

In the future, this topic will include descriptions for the following three built-in scripts:

The topics describing those scripts are linked at the bottom of this topic; they are missing only in the table listing the scripts.


Calling a transform file during Notes silent install

This topic contains a typographical error in a command example in the following step in the procedure:


2. Run the following command:
setup.exe /s /v"TRANSFORMS=LotusNotes.smt /qb+"

The correct command is:

setup.exe /s /v"TRANSFORMS=LotusNotes.mst /qb+"


(SPR #SCHH7YY6ML)


Collecting detailed information from user calendars


Steps 3 and 4 in the following section of this topic are incorrect. The corrected text is shown.

To collect detailed calendar information from user calendars

  1. From the Domino Administrator, click the Configuration tab.
  2. Choose Server - Configurations.
  3. Select the Server Configuration document you want to modify Select the * [All Servers] Configuration Settings document, and click Edit Configuration.
  4. On the Basics tab, click the check box "Use these settings as the default settings for all servers." The feature to collect detail information is only available on the All Server Configuration document. This check box must by selected to display the field "Extract calendar details."

(SPR #BKAN7WCTKS)


Compact options

The following table row is incorrect as of Domino release 8.5.2 FP2:

Keep or revert database to previous format -R Compacts databases without converting to the current release file format of the server that stores the databases or reverts databases in the current release file format to the previous release file format. For example, on Domino 6 and more recent servers, this option compacts Domino 5 databases without converting them to the Domino 6 file format and converts Domino 6 databases to the Domino 5 file format. This option uses copy-style compacting.

There are now two different options for reverting ODS format, as follows:

Revert database one level back based on current release of server -r Compacts databases and reverts them to one release earlier than the current release file format of the server that stores the databases. For example, on Domino 8.5.2 FP2 and more recent servers, this option compacts Domino 8 databases and converts them to the Domino 7 file format. This option uses copy-style compacting.
Revert database one level back based on current release of specified database -R Compacts databases and reverts them to one release earlier than the current file format of the databases themselves. For example, on Domino 8.5.2 FP2 and more recent servers, this option compacts Domino 8 databases and converts them to the Domino 7 file format, converts Domino 7 databases to Domino 6 databases, and so on. This option uses copy-style compacting.

(SPR#THIO8SZ6UN)

The following section on the DAOS option for Compact needs clarification of behavior when the option is turned off, as well as when it is turned on.

Compact - DAOS

In addition to enabling the Domino Attachment and Object Service (DAOS) property to consolidate new attachments in a database, you can use the following Compact option to move attachments in existing documents into the DAOS repository while performing a copy-style compact. This option is not available for in-place compaction.

Option Command-line equivalent Description
Use Domino Attachment and Object Service -c -daos on|off When set as on, moves attachments from existing documents to the DAOS repository and then compacts the database. When set as off, moves attachments back into the database .NSF file.

Configuring custom data directories for multi-user install or upgrade on Windows or Citrix

In this topic, there is a syntax error in the following sample:

setup.exe /v "SETMULTIUSER=1 MULTIUSERBASEDIR=C:\LocalAppDataUsers\!USERNAME!
MULTIUSERCOMMONDIR=C:\LocalAppDataCommon"


There should not be a space after /v.

The corrected sample syntax is as follows:

setup.exe /v"SETMULTIUSER=1 MULTIUSERBASEDIR=C:\LocalAppDataUsers\!USERNAME!
MULTIUSERCOMMONDIR=C:\LocalAppDataCommon"


If installing on a Citrix system, the additional property CITRIX=1 must also be used.

setup.exe /v"SETMULTIUSER=1 MULTIUSERBASEDIR=W:\
MULTIUSERCOMMONDIR=c:\Notes\common CITRIX=1
"


Considerations for installing and deploying Notes on Citrix

Considerations for installing and deploying Notes on Linux

Considerations for installing and deploying Notes on Windows

Considerations for installing and deploying Notes on Mac OS X

Several Lotus Notes platform and version restrictions exist regarding double-byte and special characters use in installation directory names. The "Considerations for installing..." topics contain the following bullet, which should be updated to provide details on platform and version-specific characters:

  • The installation path cannot contain special characters such as # or $.

The specific character restrictions, based on Lotus Notes platform and version, are as follows:

Windows platform and Lotus Notes

The install source path cannot contain double-byte characters or any of the following characters:
" | * ? < > ! # % ;

The install destination path cannot contain any of the following characters:
 " | * ? < > ! # % ;

Linux platform and Lotus Notes

The install destination path cannot contain any of the following characters:
 \ ; : % # < > , " ! | ?

Mac platform and Lotus Notes

The install source path cannot contain any of the following characters:
: " < > ! # % ' = ;

The install destination path cannot contain any of the following characters:
: " < > ! # % ' = ;



Controlling the size of the log file (LOG.NSF)

In future releases of the documentation this topic will include the following caution:

CAUTION: Leaving the logging level set to verbose can degrade server performance over time.

(SPR #PHEY8HNL49)



Controlling Widgets and Live Text access using Domino policy

Controlling Widgets and Live Text access using Eclipse preferences

These topics incorrectly state that replication of the widget catalog takes place every 24 hours. In fact, replication of the widgets catalog takes place according to the Notes 'Normal' priority level.

See the following technote for more information:

How often does the local Widgets catalog replicate automatically?

(SPR #RSSA8DMHPB)

Additionally, the following corrections are required to bring both topics up-to-date.
  • In the "Enable provider IDs for widget addition" section, there are additions to the list of widget types and to the corresponding default listing that follows.

      com.ibm.notes.toolbox.provider.NotesViewPalleteProvider

      com.ibm.notes.toolbox.provider.NotesFormPalleteProvider

      com.ibm.rcp.toolbox.web.provider.WebServicesPalleteProvider

      com.ibm.rcp.toolbox.feeds.FeedPalleteProvider

      com.ibm.rcp.toolbox.google.provider.internal.GooglePalleteProvider

      com.ibm.rcp.toolbox.prov.provider.ToolboxProvisioning

      com.ibm.rcp.toolbox.search.provider.SearchPalleteProvider

      com.ibm.rcp.toolbox.ca.provider.internal.CAActionPalleteProvider

      com.ibm.notes.toolbox.provider.XPagesPalleteProvider

      The default is as below:

      com.ibm.rcp.toolbox.google.provider.internal.GooglePalleteProvider,com.ibm.rcp.toolbox.web.provider.WebServicesPalleteProvider,com.ibm.rcp.toolbox.feeds.FeedPalleteProvider,com.ibm.notes.toolbox.provider.NotesViewPalleteProvider,com.ibm.rcp.toolbox.prov.provider.ToolboxProvisioning,com.ibm.notes.toolbox.provider.NotesFormPalleteProvider,com.ibm.rcp.toolbox.search.provider.SearchPalleteProvider,com.ibm.rcp.toolbox.ca.provider.internal.CAActionPalleteProvider,com.ibm.notes.toolbox.provider.XPagesPalleteProvider

  • In the "Enable provider IDs for installation/execution" section, there are additions to the list of widget types and to the corresponding default listing that follows.

      com.ibm.notes.toolbox.provider.NotesViewPalleteProvider

      com.ibm.notes.toolbox.provider.NotesFormPalleteProvider

      com.ibm.rcp.toolbox.web.provider.WebServicesPalleteProvider

      com.ibm.rcp.toolbox.feeds.FeedPalleteProvider

      com.ibm.rcp.toolbox.google.provider.internal.GooglePalleteProvider

      com.ibm.rcp.toolbox.prov.provider.ToolboxProvisioning

      com.ibm.rcp.toolbox.search.provider.SearchPalleteProvider

      com.ibm.rcp.toolbox.ca.provider.internal.CAActionPalleteProvider

      com.ibm.notes.toolbox.provider.XPagesPalleteProvider

      The default is as below:

      com.ibm.rcp.toolbox.google.provider.internal.GooglePalleteProvider,com.ibm.rcp.toolbox.web.provider.WebServicesPalleteProvider,com.ibm.rcp.toolbox.feeds.FeedPalleteProvider,com.ibm.notes.toolbox.provider.NotesViewPalleteProvider,com.ibm.rcp.toolbox.prov.provider.ToolboxProvisioning,com.ibm.notes.toolbox.provider.NotesFormPalleteProvider,com.ibm.rcp.toolbox.search.provider.SearchPalleteProvider,com.ibm.rcp.toolbox.ca.provider.internal.CAActionPalleteProvider,com.ibm.notes.toolbox.provider.XPag esPalleteProvider

  • In the "Restrict extension point IDs for installation/execution" section, an identifier is removed.

      Notes and Expeditor provide the following identifiers, and many others:

      com.ibm.rcp.ui.shelfViews, com.ibm.rcp.textanalyzer2.Dictionaries, com.ibm.rcp.search.engines.searchEngines, com.ibm.rcp.search.ui.searchBarSets, com.ibm.rcp.content.contentTypes, com.ibm.rcp.annotation.regex.regexTypes

  • In the "Enable extension point IDs for installation/execution" section, a default list item is removed and an erroneous example is replaced by an accurate example.

      You can restrict this list or add to it. Use a comma to separate items in the list. The default is as below:

      org.eclipse.ui.popupMenus,com.ibm.rcp.content.contentTypes,com.ibm.rcp.annotation.regex.regexTypes,com.ibm.rcp.ui.shelfViews,org.eclipse.ui.views,org.eclipse.ui.viewActions, com.ibm.rcp.textanalyzer2.Dictionaries ,com.ibm.rcp.search.engines.searchEngines,com.ibm.rcp.search.ui.searchBarSets

      For example, if the policy setting "Restrict extension point IDs for installation/execution" is Enabled and "Enable extension point IDs for installation/execution" is set to "com.ibm.rcp.content.contentTypes", then widgets containing regular expression recognizers (com.ibm.rcp.annotation.regex.regexTypes) would not be allowed to be installed/provisioned.

      For example, the following settings specify that widgets will be able to contribute content types but not any other extension point.

      com.ibm.rcp.toolbox.admin/toolboxdynamicExtPtIDs=com.ibm.rcp.content.contentTypes

Finally, the following, additional corrections are required to bring only the "Controlling Widgets and Live Text access using Eclipse preferences" topic up-to-date.
  • In the "Enable extension point IDs for installation/execution" section, a default list item is removed and an erroneous example is replaced by an accurate example.

You can restrict this list or add to it. Use a comma to separate items in the list. The default is as below:

org.eclipse.ui.popupMenus,com.ibm.rcp.content.contentTypes,com.ibm.rcp.annotation.regex.regexTypes,com.ibm.rcp.ui.shelfViews,org.eclipse.ui.views,org.eclipse.ui.viewActions, com.ibm.rcp.textanalyzer2.Dictionaries ,com.ibm.rcp.search.engines.searchEngines,com.ibm.rcp.search.ui.searchBarSets

For example, if the policy setting "Restrict extension point IDs for installation/execution" is Enabled and "Enable extension point IDs for installation/execution" is set to "com.ibm.rcp.content.contentTypes", then widgets containing regular expression recognizers (com.ibm.rcp.annotation.regex.regexTypes) would not be allowed to be installed/provisioned.

For example, the following settings specify that widgets will be able to contribute content types but not any other extension point.

com.ibm.rcp.toolbox.admin/toolboxdynamicExtPtIDs=com.ibm.rcp.content.contentTypes

Finally, the following, additional corrections are required to bring only the "Controlling Widgets and Live Text access using Eclipse preferences" topic up-to-date.

  • In the "Enable the display of Live Text in the Notes document" section, the description of the setting when disabled is corrected.

    This corresponds to the "Enable Live Text" policy setting.

    If this setting is disabled, then the Live Text preference panel is hidden from the user. Live Text is disabled and the "Enable Live Text" option on the Live Text preference panel is not selected by default.

    com.ibm.rcp.toolbox.admin/toolboxenableRecognizers

    Options are =true and =false. The preference default is true.

  • In the "Restrict the installation of widgets to specific widget types (provider IDs)" section, a missing setting is added (part A) and, later in the section, an example is corrected (part B).

  • A.
    Restrict installation and update of widgets to specific types (referred to as provider IDs). This corresponds to the Restrict provider IDs for installation/execution policy.

    com.ibm.rcp.toolbox.admin/toolboxrestrictProviderIDs

    Options are =true and =false. The preference default is false.

    B.
    For example, to restrict the user such that they can only install Notes view-type widgets (from a non-catalog source), add the following entries:

    com.ibm.rcp.toolbox.admin/toolboxrestrictProviderIDs=true
    com.ibm.rcp.toolbox.admin/toolboxinstallProviderIDs=com.ibm.notes.toolbox.provider.NotesViewPalleteProvider
    com.ibm.notes.toolbox.provider.NotesViewPalleteProvider



Creating a child policy document

Step 5 in the following section of this topic is incorrect.

5. In the Policy Name field select one:

  • Organizational policy -- enter the name of the organizational unit , followed by the Organization or the Organizational unit that displays in the Parent Policy field . For example, if */Acme is in the Parent policy field and you want to create a child policy for the Sales/Acme organization unit, enter Sales /Acme . When the policy is saved, the name will be */Sales/Acme.
  • Explicit policy -- enter a name for the child policy followed by the text that displays in the Parent policy field . For example, if the Parent policy field is /Contractors and you want to create a child named Short term, enter Short term /Contractors . When the policy is saved the name will be /Short term/Contractors.

The corrected text is as follows:

5. In the Policy Name field select one:

  • Organizational policy -- enter the name of the organizational unit. For example, if */Acme is in the Parent policy field and you want to create a child policy for the Sales/Acme organization unit, enter Sales. When the policy is saved, the name will be */Sales/Acme.
  • Explicit policy -- enter a name for the child policy. For example, if the Parent policy field is /Contractors and you want to create a child named Short term, enter Short term. When the policy is saved the name will be /Short term/Contractors.

(SPR #YGAO8MAD8B)



Creating a desktop policy settings document

On the Widgets tab, in the "Enable provider IDs for widget addition" section, there are additions to the list of widget types and to the corresponding default listing that follows.

com.ibm.notes.toolbox.provider.NotesViewPalleteProvider

com.ibm.notes.toolbox.provider.NotesFormPalleteProvider

com.ibm.rcp.toolbox.web.provider.WebServicesPalleteProvider

com.ibm.rcp.toolbox.feeds.FeedPalleteProvider

com.ibm.rcp.toolbox.google.provider.internal.GooglePalleteProvider

com.ibm.rcp.toolbox.prov.provider.ToolboxProvisioning

com.ibm.rcp.toolbox.search.provider.SearchPalleteProvider

com.ibm.rcp.toolbox.ca.provider.internal.CAActionPalleteProvider

com.ibm.notes.toolbox.provider.XPagesPalleteProvider

The default is as below:

com.ibm.rcp.toolbox.google.provider.internal.GooglePalleteProvider,com.ibm.rcp.toolbox.web.provider.WebServicesPalleteProvider,com.ibm.rcp.toolbox.feeds.FeedPalleteProvider,com.ibm.notes.toolbox.provider.NotesViewPalleteProvider,com.ibm.rcp.toolbox.prov.provider.ToolboxProvisioning,com.ibm.notes.toolbox.provider.NotesFormPalleteProvider,com.ibm.rcp.toolbox.search.provider.SearchPalleteProvider,com.ibm.rcp.toolbox.ca.provider.internal.CAActionPalleteProvider,com.ibm.notes.toolbox.provider.XPagesPalleteProvider

(SPR #HHIE8LR9P2)

In addition, this topic incorrectly states that desktop policy settings are not supported in IBM Lotus iNotes; they are. For more information, see the Domino 8.5 Administrator topic Desktop policy settings supported in Lotus iNotes.



Creating a Directory Assistance document for a Domino Directory or Extended Directory Catalog

This topic incorrectly states that the Basics tab of the Directory Assistance document includes the field "Attribute to be used as name in an SSO token."

However, when the Domain type is Notes, this field is not relevant and does not appear. The value LTPA_Usernm is used by default, without administrator intervention.




Creating a Lotus Symphony Settings document

The second row of the table in Step 4 of this topic mentions a field "Allow Symphony."

This field is no longer in the Lotus Symphony settings document.

(SPR #FBUE84KPZD)



Creating a mail policy settings document

In Step 5 of the Creating a new mail policy settings document procedure, the following table row is incorrect and will be removed. There is no $DSFAdmin NOTES.INI setting in the current release of Domino.

Deliver spam messages to the Junk folder This setting displays only if you have added this setting to your NOTES.INI file: $DSFAdmin=1.

Choose one:

  • No -- Default setting. Spam messages are not automatically delivered to the user's Junk folder.
  • Yes -- Spam messages are automatically delivered to the user's Junk folder.


Creating an activities policy settings document


The document in the Domino Directory covered in this Help topic, formerly called Activities Settings, is now called Connections settings, and has different options.

Note When you use a policy document to define the Connections server configuration, not all authentication types are available from the policy form. For example, you cannot define a policy document for an IBM Connections server that is configured to use Domino single sign-on. For information about other ways to define the IBM Connections server, see the following article on the Lotus Notes and Domino wiki:

Using INI settings to configure the IBM Connections features that are available in the IBM Lotus Notes client

The corrected topic content is:

Creating a Connections settings document
Create a Connection Settings policy document to define a user's Connections server and assigned port, and whether the user names, passwords, and activities data are to be encrypted with SSL.

Connections policy settings are not supported by IBM® Lotus® Domino® Web Access.

1. Make sure that you have Editor access to the IBM® Lotus® Domino® Directory and one of these roles:

    • PolicyCreator role to create a settings document
    • PolicyModifier role to modify a settings document
2. From the Domino Administrator, select the People & Groups tab, and then open the Settings view.

3. Click "Add Settings," and then choose Connections Settings.

4. On the Basics tab, enter the name and description of the Connections settings document you are creating.

5. In the Connections Options section, complete these fields, and then click Save and Close.

Field Action
Connections Server URL Type the URL that Notes users need to access in order to work with their connections on the Connections server.

Tip: The URL is the full Web address of the Activities feature on the Lotus Connection server, including the protocol. Add a backslash before each colon.

Example: https\://exampleservername.com/activities

Authentication Type Select a form to specify the type of authentication your Connections server uses:
  • J2EE Form
  • TAM (Tivoli Access Manager) Form
  • Site Minder Form

Note: In this release TAM SPNEGO and Sun Access Manager Form are not yet supported.
Authentication URL Type the URL that Notes users need to access in order to authenticate with the Connections server.

Note: The default port is 443; if you are running Connections on a different port, replace that value in the URL.

Example: https\://exampleservername.com\:443/activities/j_security_check

(SPR #ADOS84JM5A)


Creating an archive policy settings document

This topic includes a note that archive settings are not supported in IBM Lotus Domino Web Access. For releases prior to Domino 8.5.1, archiving policies were not supported. However, beginning with Domino 8.5.1, IBM Lotus iNotes supports archive policies. For complete information on how to set up archiving in Lotus iNotes, see the Domino 8.5 Administrator topic "Setting up archiving using policies and configuration settings."


(SPR # KSAA83C9US)



Creating and modifying groups

This topic states that there are limits to the possible number of nested groups, but this is no longer true on the Domino server, and errors with more than 20 nested groups can also be prevented when Notes client users mail to them by using a local domain name.

For details, see the following technote:

Limits on Nesting Groups in Domino 6

(SPR # ASHH8FMCUA)



Creating a security policy settings document

In releases since Domino 8.5.1, on the Password Management tab of the security policy settings document, there is no longer a field called Enable Notes single logon with Workplace Rich Client (prior to 8.0 only). Lotus Workplace is no longer supported.

As of Domino 8.5.3, there is a new field Enable Windows single sign-on for Standard Notes Client to support integrated Windows authentication (using SPNEGO/Kerberos) for Eclipse-based features and products such as Widgets and Live Text, Feeds, IBM Connections, Composite Applications, Sametime, and Symphony.

Note: IWA authentication cannot be used as an authentication mechanism for Notes client startup.

For details on integrated Windows authentication (IWA) see the following technote:

Integrated Windows authentication (IWA) for Eclipse-based components within Lotus Notes


Creating Site Profile and Resource documents

This procedure should have a new paragraph after the first bulleted list, as follows:

Note The name of a room or resource is limited to 100 characters.



Creating Site Profile and Resource documents
Editing and deleting Resource documents

Both of these topics should contain information on options for limiting future and repeating room/resource reservations. These options are useful to prevent users from scheduling single meetings so far in advance, or so many repeating instances of a single meeting, that resources may be wasted due to later schedule changes. Options are in the Resource document under the Owner options section under "Limit the Advance Reservation of this Room/Resource."


This information will be added to the documentation in a later release. For full information on the options, see Technote #1217144 In 7.x and above, administrators can limit how far in advance resource reservations can be created.


Creating the widget catalog
This topic incorrectly states that replication of the widget catalog takes place every 24 hours. In fact, replication of the widgets catalog takes place according to the Notes 'Normal' priority level.

See the following technote for more information:

How often does the local Widgets catalog replicate automatically?

(SPR #RSSA8DMHPB)


Customizing the columns in the Files tab


The item "Space Used" in the bulleted list is incorrect. There is no longer a Space Used column.

For more information, see DAOS and the Space Used Column in the Lotus Notes and Domino wiki.



DAOS Manager Tell commands

The following row of the table in this topic is incorrect. The corrected text is shown.

Command Result
Tell DAOSMgr Prune

Tell DAOSMgr Prune number of days old

With no argument, displays the current setting for "Defer object deletion for n days," also known as the deferred delete interval, that was specified on the DAOS tab of the Server document.

With the argument 0, immediately deletes all DAOS unreferenced objects.

With the number of days old argument, immediately deletes all DAOS unreferenced objects that are older that are older than the argument, temporarily overriding the delete interval specified in the Server document.

Caution Objects that have not been backed up since the specified duration last prune operation are at risk of being unrecoverable lost when you run with either 0 or a shorter number of days than the default interval .



Default Domino SSL trusted roots

The table of trusted root certificates is out of date. To see the list of certificates for your current Domino server release, choose File - Open - Lotus Notes Application, open the certsrv.nsf file in your server's data directory (this is the Server Certificate Admin database), and in the navigation on the left, select View & Edit Key Rings.

For more detailed information, see technote #1268695.


Detecting when a mail file exceeds its quota

In a future release, the following sentence in the fourth paragraph of this topic:

When setting a mail file quota, be sure to consider the additional space required for the file's full-text index.

will be clarified as follows:

When setting a mail file quota, be sure to consider the additional server space required for both the quota and for the file's full-text index.

(SPR # DAGL8QU7S6)



Directory assistance and client authentication

In this topic, the following illustration is missing from the Information center:





Directory services terms

The name of the template is misspelled in the Contacts section of this topic. It is the PERNAMES.NTF template.



Domino server commands

If you follow the link to Show Stat DAOS in this topic, the table of DAOS statistics in the linked topic is inaccurate. The following is an expanded table:


Statistic

Description

DAOS.DIT.Delete

The number of NSF files that have been removed from the DAOS catalog

DAOS.DIT.Find

The number of NSF files searched for in the DAOS catalog

DAOS.DIT.InsertUpdate

The number of NSF files inserted or updated in the DAOS catalog

DAOS.DOI.Delete

The number of attachments that have been removed from the DAOS catalog

DAOS.DOI.Find

The number of attachments that have been searched for in the DAOS catalog

DAOS.DOI.InsertUpdate

The number of attachments whose information has been added or updated in the DAOS catalog

DAOS.Engine.Catalog

Reports whether the DAOS catalog is synchronized.

DAOS.Engine.Encryption

Reports whether encryption is enabled for DAOS NLO file encryption

DAOS.Engine.Status

Reports whether DAOS is enabled.

DAOS. Object.Attach_DAOSCreate

The number of attachments created in DAOS.

DAOS. Object.Attach_DAOSOptimizedCreateLocal

The number of attachments that did not need to be copied between Notes applications located on the same Domino server (for example, copied from MAIL.BOX to a recipient's mail file) because the objects already existed in the DAOS repository. This statistic shows intra-server savings from optimization of object copying.

DAOS. Object.Attach_DAOSOptimizedCreateRemote

The number of attachments on the server that did not need to be sent over the network from remote clients or servers because the objects already existed in the DAOS repository. This statistic shows inter-server savings from optimization of object copying.

DAOS. Object.Attach_NSFCreate

The number of attachments created in the NSF because they did not qualify for storage in DAOS, typically because they were smaller than the DAOS minimum object size.

DAOS. Object.Attach_TotalCreated

Total number of attachments listed by the Object.Attach_DAOSCreate, Object.Attach_NSFCreate, Object.Attach_DAOSOptimizedCreateLocal, and Object.Attach_DAOSOptimizedCreateRemote statistics.

DAOS.Object.CloneDeclined

The number of times a DAOS network optimization request was denied

DAOS.Object.CloneRequests

The number of times a DAOS network optimization request was attempted

DAOS.Object.Delete

The number of attachment delete requests for attachments stored in DAOS

DAOS. Object.OptimizedCreateLocalSavingsMB

The total savings in MB for objects that did not need to be copied between databases on this server (intra-server savings from optimization of object copying).

DAOS. Object.OptimizedCreateRemoteSavingsMB

The total savings in MB for objects that did not need to be to be sent over the network from remote clients or servers (inter-server savings from optimization of object copying).

DAOS.Object.Realloc

The number of times an attachment has been reallocated (related to modifying the content of the attachment)

DAOS.Object.Share_Existing

The number of times an attachment was received and matched an NLO file existing in the repository

DAOS.Object.Share_New

The number of times an attachment was received and did not match any NLO file existing in the repository

DAOS.Object.Share_Total

The number of references added to attachments

DAOS.Object.ZeroRead

The number of times the zeroth (0th) byte was read from an NLO file

DAOS.Object.ZeroWrite

The number of times the zeroth (0th) byte was written to an NLO file

DAOS.Registration.Add

The number of NSF files that were enabled for DAOS and registered with the DAOS catalog

DAOS.Registration.Check

The number of NSF files whose DAOS dbheader information was compared with the information stored in the DAOS catalog for that NSF file

DAOS.Registration.Delete

The number of NF files deleted that were participating in DAOS

DAOS.Registration.Transfer

The number of NSF files renamed or moved

DAOS.Registration.Update

The number of times information about the NSF file was updated in the DAOS catalog

(SPR #TSHI8WW2U2)




Domino server installation

This topic should have a link to the following topic:

Installing Domino on IBM i systems


Domino's On-Disk Structure

The following section of this topic is changed as of Domino release 8.5.2. The corrected text is shown.

Reverting back one ODS level

You can revert a database either back to the level before a specific release of Domino, or back to the level before the current level of the selected database.

To revert based on release, you need to set one of the NOTES.INI parameters that control creation of new databases at a specific ODS. Then you use compact with the -r option, which determines an ODS one level earlier than the one specified by the NOTES.INI parameter.

To revert back one ODS level before a specific Domino release:

This procedure assumes the Domino server or client where the NOTES.INI parameter is set is running 8.5 or later.

  • Set one of the following parameters in the NOTES.INI file on the Domino server or the Lotus Notes client:

    Table 1. ODS reversion details for compact -r
    When the NOTES.INI parameter is New databases are created at Compacting with -R reverts to
    Create_R85_Databases=1 ODS50 ODS48
    Create_R8_Databases=1 ODS48 ODS43
    no parameter ODS43 ODS41
  • Use the compact -r command as shown here:

    compact -r database name


To revert back one ODS level before the release of the specified database:
  • Use the compact -R command as shown here:

    compact -R database name

    Table 2. ODS reversion details for compact -r

    If the specified database is Compacting with -R reverts it to
    ODS50 ODS48
    ODS48 ODS43
    ODS43 ODS41

(SPR # THIO8SZ6UN)


Examples of using NOTES.INI variables with IPv6

The syntax in Step 3 of this topic is incorrect.
Step 3 syntax should be as follows:

TCP_EnableIPv6=1

TCPIP=TCP, 0, 15, 0

TCPIP6=TCP, 0, 15, 0

PORTS=TCPIP,TCPIP6

TCPIP_TCPIPADDRESS=0,9.33.162.84:1352

TCPIP6_TCPIPADDRESS=0,[fe80::209:6bff:fecd:5b93]:1352

SMTPNotesPort=TCPIP,TCPIP6

(SPR #YGAO7XXL6P)



How replication works in a cluster

The following paragraph in this topic is no longer accurate. The "deletion" check box setting is not ignored, and does have an affect on cluster replication.

In addition, the Cluster Replicator does not honor the settings on the Advanced panel in the Replication Settings dialog box. Therefore, you cannot disable the replication of specific elements of a database, such as the ACL, agents, and design elements. The Cluster Replicator always attempts to make all replicas identical so that users who fail over do not notice that they failed over.


(SPR #YMAA8WC8AP)



ID Vault FAQs

The following FAQ needs clarification:

Are the benefits of an ID vault available for users who switch IDs?

Yes, but before an ID can be acquired from the vault, a user must enter a password or the current ID, as usual when switching IDs.


(SPR #KSAA82Z67X)



Improving UNIX server performance

This topic will be updated in a future release of Help, as follows. The NSF_Buffer_Pool_Size_MB section is obsolete (you should normally not need to change this setting), and two other sections will contain new information as shown in red. The final section on Disk I/O tuning is unchanged.

Improving UNIX server performance
Tips for improving UNIX server performances are as follows.

NOTES.INI settings

Most NOTES.INI settings that affect IBM® Lotus® Domino® server performance apply to all UNIX® platforms. Examples are:

  • CREATE_R85_DATABASES=1 - Enables the latest ODS level, and its features on new databases.
  • CREATE_R85_LOG=1 - Makes transaction log file handling more efficient. Transaction logs must be recreated for the setting to take effect.


NSF_Buffer_Pool_Size_MB

Many machines that run UNIX have very large amounts of physical RAM. Use the parameters NSF_Buffer_Pool_Size_MB or PercentSysAvailable Resources to control how much memory Domino is allowed to use. Each Domino instance on a UNIX machine can reference a maximum of 4GB of RAM.

Disk and memory requirements

When a UNIX system runs Domino server software, the server must have enough disk space for program and data files and enough memory to handle swapping and the number of processes. You can also change several system parameters to improve server performance.

On Linux systems that are used for mail servers or applications where more than a few hundred databases are to be opened at one time, it is advisable to increase the file limit from its 1024 default value. You can modify this value by editing the file /etc/security/limits.conf . The entry should be for the nofile item.

Example:

@notes soft nofile 60000

@notes hard nofile 80000

In this example, the limit is set for a group in which the user who is running Domino is a member. The limit can also be set, if desired, to the user who is running Domino. The soft and hard values in this example may vary to meet the needs of your system, as long as they are large enough to stay below the file limit.

Other memory and network tuning parameters on Linux that help Domino run more efficiently are set by a program which automatically runs at the startup of the Domino server.



Installing Domino on IBM i systems

In a future release of the documentation, this topic will include a path to upgrading instructions for IBM i, similar to the following:

For details about installing a new release of Domino and upgrading servers on IBM i, including command examples, see Lotus Tech Note Domino 8.5 for i: Installation and upgrade.




Managing the attachment storage repository

This topic's procedure states that restarting the Domino server is sufficient after a repository move, and under most circumstances it is. However, if the API is initialized at the time by some background process, restarting the server may not be sufficient to re-initialize the DAOS repository location. There are also other steps not mentioned in the current version of the topic.

In future releases of the documentation the topic will contain the following information:

Before you begin

Back up all data in the DAOS repository before moving it.

Note: It takes a longer time to move the repository to a separate physical drive than to a different directory on the same drive, so plan accordingly.

Also, the end of the procedure will have additional steps and information as follows::

7. Update the value of DAOSBasePath if that setting appears in the server's NOTES.INI file.

8. Edit the daos.cfg file and update the value of the PATH field to match the new location of the repository.


    The PATH statement appears in the file somewhere around line 35; it is the only occurrence of the term PATH in the data section of the file. For example, it may appear on a line like this:

    <CONTAINER ID="9C92854208308CB78525788500701A69" PATH ="c:\daos\" DESC="" STATE="1" FILECOUNT="23" MAXBYTES="-1" BYTECOUNT="0" LASTMODIFIED="04/25/2011 16:41:05" INDOUBT="0" LASTSCANNED="05/03/2011 16:24:27">

9. Restart the machine on which the Domino server is running, and then restart the Domino server.




Mapping the DB2 ID to a Notes ID in the Domino server's Domino Directory

In the following paragraph, this topic refers to a design element called "Domino Access View." The element is actually called "DB2 Access View."


Use the Domino Administrator to map an individual Notes user to a specific DB2 user name. If an explicit mapping of a DB2 user to a Notes user does not exist, you can set up a default DB2 user name that can be used in place of an explicit DB2 user mapping. This default DB2 user mapping is sufficient when working with most query views, but cannot be used with Domino DB2 Access Views. When querying a DAV, you must use an explicit user mapping.


Modifying whether the Domino server is installed as a service or an application

This topic was erroneously placed in the table of contents as a subtopic of "Installing Domino on UNIX systems," despite its focus on Windows. It will appear elsewhere in a future release of the documentation, and is re-titled "Starting Domino as an application or a Windows service."



N8Mail Initialization workload

In this topic, the following table row is no longer accurate and will be removed:

NormalMessageSize Enter the size of the body of the message. Recommended value is 10000.



Performing a Notes silent install on Windows

The following command example in this topic is incorrect:

setup /s /v"SELECTINSTALLFEATURES=Activities,Sametime,CAE /qn"

The correct command is:

setup /s /v"SELECTINSTALLFEATURES=Activities,SametimeUI,CAE /qn"

(SPR #SCHH7YY5RZ)



Processing administration requests across domains

The following statement in this topic is incorrect. The corrected text is shown.
...

For Rename requests going to another domain, there must be appropriate cross-certificates between the two domains. Additionally, the Domino Directory Directories of both the originating and destination domains must either have all Certifier documents, with the certifier's public key, for the organizational structure represented in the name change request , or it must be able to access those Certifier documents from a trusted Directory specified via Directory Assistance .

Tip Copy the necessary set of Certifier documents from the originating domain to the destination domain. However, keep in mind that documents copied in this manner may need to replaced later if newer certifiers are used.

(SPR # NMDL86MGX7)




Pushing notes.ini settings or location document settings

Step 10 in the procedure in this topic is incorrect. Enabling the enforce option is not a required step. In future releases of the documentation the procedure will end as shown below:

9. Click OK and Save & Exit.

Note: To remove a known NOTES.INI variable name/value pair, specify the applicable name pair in the Item and Value fields and click Remove.

Result

The value pair is pushed to overwrite any other previously set value for the named Item (NOTES.INI setting variable) value.

What To Do Next

If you use hierarchical policy structures (parent and child), also enable the Enforce option.

(SPR #CAKH8DYPLC)



Reducing Notes startup time using GNOME for auto-start on Linux

This topic contains inaccuracies concerning the Lotus Notes preloader. The revised topic title and content are as follows:

Reducing Notes startup time for Linux users
The Linux platform Notes install package contains a ntspreld.sh script that, when enabled, reduces Notes client startup time after the first operating system startup.

This procedure uses the supplied ntspreld.sh script, which calls the ntspreld program to preload several key libraries used by Notes to reduce Notes startup time. When enabled, Notes will automatically preload several libraries to reduce its startup time.

  1. Install or upgrade Notes on the Linux platform client but do not start Notes.
    Note: If Notes is running, shut it down.
  2. Navigate to the Notes install directory, for example /opt/ibm/lotus/notes and locate the ntspreld.sh script.
  3. Switch to root user and enable (or subsequently disable) the script.
    Note: You must run the script as the root user to add the preload command to the /etc/rc.d/after.local or /etc/rc.local files. The script /opt/ibm/lotus/notes/ntspreld.sh cannot be added as a startup program; it must be
    executed as root to either enable or disable the preloader as follows:
    /opt/ibm/lotus/notes/ntspreld.sh -enable
    /opt/ibm/lotus/notes/ntspreld.s
    h -disable
  4. Once the script is enabled, the preloader will run whenever a Notes user logs in, until the root user runs the -disable program.
  5. Restart the Notes client.


Removing features from the Notes install kit using a supplied tool

There is old link data in two locations in the topic "Removing features from the Notes install kit using a supplied tool" .

The links in the following Note are out of date:

      Note You need the externally available zip232xN.zip and unz552xN.exe from ftp://tug.ctan.org/tex-archive/tools/zip/info-zip/WIN32/] to run the tool. [
Replace the Note content with the following corrected text: Similarly, the links in the Step 6 content are out of date:
      6. Open the readme file associated with the trimUpdateSite.exe and obtain the zip232xN.zip and unz552xN.exe from ftp://tug.ctan.org/tex-archive/tools/zip/info-zip/WIN32
Replace the Step 6 content with the following corrected text:
      6. Open the readme file associated with the trimUpdateSite.exe and obtain the zip232xN.zip and unz552xN.exe from www.sfr-fresh.com/windows/misc



Rename person - name change refused

In this topic, the Result section under the Reinitiate rename in Domino Directory section is incorrect. The corrected text is shown.

Result: Reinstates the name change that was originally initiated by the Administrator. At some point, the client user is again notified of the proposed name change and should accept the change by clicking Yes in the "Accept Name Change" dialog box.

(SPR # DPBE7ZWFCK)



Restricting mail routing based on message size

Step 7 in this topic requires this additional Note for clarification.

  • On Domino SMTP servers you can use the ESMTP SIZE extension to prevent inbound transfer of messages that exceed the specified maximum message size. You can also use the outbound ESMTP SIZE extension to configure Domino to honor size restrictions on a target server when transferring outbound SMTP mail.

    Note SMTP transfer-encoded sizes of messages are larger than the Notes size of a message. For example, a message with a binary attachment that is base64-encoded is approximately 25% larger on transfer, and this larger size will be used in maximum size calculation.


(SPR #J CAL85ELRB)



Roaming users

[In a future release this topic will be entirely revised as follows, and re-titled "Understanding roaming users."]

Users who access IBM Lotus Notes from more than one Notes client can access their customized settings and personal information automatically from any Notes client in the domain by becoming roaming users.

When a roaming user logs on from any Notes client, the user's ID file is accessed from the local file system, from the Contacts application, or from the Domino ID vault, according to how the administrator has configured the user account.

Note: It is recommended that both Domino and file-server roaming users take advantage of shared login and the ID vault to roam the ID file. Roaming users configured to store the ID File in the Contacts application (formerly the Personal Address Book), a method used before ID vault became available, cannot use either Notes Single Logon (NSL) or shared login features. The ID vault is not supported with Notes Single Logon (NSL).

Data for roaming users replicates between the user's client system and a roaming server, where the user's roaming-enabled files reside. The user's roaming-enabled files include contacts, bookmarks, notebook or journal, feeds subscriptions, and roaming data which stores roamed Eclipse plug-in data and settings. Any changes the user makes in these files replicates back to the roaming server, giving the roaming user a consistent experience from any Notes client.

For the Notes standard client configuration, a roaming user can take advantage of either Domino server roaming or file-server roaming. Use the registration process to register a user as a Domino server roaming user. Use the Roaming Settings policy document to set up Notes standard configuration users for file-server roaming.

When upgrading to or downgrading users from Domino server roaming, use the roaming tools available from the Domino Administration client, People and Groups. When upgrading to or downgrading from file server roaming, use policies. You can also temporarily disable and re-enable Notes roaming user status for a specific client using NOTES.INI settings.

Switching user IDs, either by selecting File -> Security -> Switch ID, or by selecting a Location document that switches to another ID, is not recommended for roaming users. Switching user IDs can cause unintentional user downgrade from roaming, especially when the ID being switched to is the primary ID file of a different roaming user. In a multiple-user installation, every user ID enabled for roaming should have its own associated Windows login profile.

When a roaming user starts one of the IBM Lotus Symphony editors before starting Notes, in a single Notes session, some Notes preferences become unavailable for roaming in that Notes session. To ensure that all possible Notes preferences are available for roaming in the current Notes session, advise users to start Notes before starting Lotus Symphony.

See the related topics for additional details on the roaming user feature.

Related information
Disabling and re-enabling Notes roaming user status on the fly
Lotus Notes Roaming User Quickstart Guide
Demo: Configuring File Server for a Notes Roaming User
List of Notes.ini variables that roam and what they control

(SPR #IWER8JBLG4)



Running Compact using a Program document

In future releases of the documentation, the "Server to run on" field in the table under step 4 of this topic will have the following description:

Server to run on Enter either the full hierarchical name of a server on which Compact should run, or an asterisk (*) to run the task on all servers.

Note Qualified wildcards and group names are invalid in this field.



(SPR #ENOR8FUK6L)


Securing Internet passwords

Step 2 in the following section of this topic is incorrect. The corrected text is shown.

For existing Person documents

1. From the Domino Administrator, click People & Groups, and select the Person documents that you want to upgrade to a more secure password format.

2. Choose Actions - Upgrade Internet Password Format . Upgrade to More Secure Internet Password.

3. If all servers in the Domino domain run release 8.0.1 or above, select "Yes - Password verification compatible with release 8.0.1 and above." Otherwise select "Yes - Password verification compatible with release 4.6 and above."

3. If all servers in the Domino domain run release 8.0.1 or above, select "Yes - Password verification compatible with release 8.0.1 and above." Otherwise select "Yes - Password verification compatible with release 4.6 and above."


Selecting server components to include in health reports

Step 2 in the following section of this topic, as well as in the section "To reset server component select to automatic," is incorrect. The corrected text is shown.

To select server components to include

1. From the IBM® Lotus® Domino® Administrator, click the Server - Monitoring tab.

2. From the menu, choose Monitoring - Display Switch to Health Reports, and then open the Configuration view.


Server.Load

This topic needs the following information added:

Caution Server.Load and the Lotus Notes client should not be running concurrently on the same machine.



Setting a schedule for Updall in a Program document

In future releases of the documentation, step 4c in the procedure will have the following information:

In the Server to run on box, enter either the full hierarchical name of a server on which Updall should run, or an asterisk (*) to run the task on all servers.

Note Qualified wildcards and group names are invalid in this field.


(SPR #ENOR8FUK6L)



Setting up a condensed Directory Catalog

Because of limited views and performance issues, IBM no longer recommends deploying condensed directory catalogs on Domino servers, as described in the following section. This section will be removed in a future release of the documentation. Use only extended directory catalogs on Domino servers.


Step 5: Set up servers to use the condensed Directory Catalog



Setting up a database ACL for server-to-server replication

In future releases of this topic, the following paragraph will appear just before the first table:

Furthermore, in a hub-and-spoke configuration, the potential exists for replication back to the hub to affect the following design elements: views, folders, shared columns, and navigators. To prevent the spoke servers from replicating design elements changes to the hub. de-select the privilege Create shared folders/views in the ACL entry for each spoke server.

For more information, see the following article on the Lotus Notes and Domino wiki:
Preventing spoke servers from modifying design elements on a hub server


(PMR #78440)


Setting up the Mail Journaling database

Information in one of the rows of the table is incorrect. The corrected text is shown.

Encrypt on behalf of user If you specified "Copy to local database" as the journaling method, enter the fully qualified Notes Name of the user whose certified public key Domino uses to encrypt messages added to the database. To ensure privacy, consider creating a special user ID for reviewing journaled messages, and protect the ID with multiple passwords.

To encrypt messages sent to a mail-in database, enable encryption on the Administration Basics tab of the Mail-in database document.


(SPR #UTOO7UD53V)



Setting up the Resource Reservations database

The following statement in this topic is incorrect:

After you create Site Profile and Resource documents, the Schedule Manager tracks the free time of a resource the same way it tracks free time for users.

The correct statement is:

After you create Site Profile and Resource documents, the Room & Resource Manager (RnRMgr) tracks the free time of a resource.

Note In release 7.0, the Schedule Manager used to track free time for resources, but in releases since, it handles only users' busytime.

In addition, after the Resource Reservations database is created, for proper operation of rooms and resources, you must enable the following agents in the database.

Procedure

  1. Make sure you have Domino Designer available, open the database, and select View - Agents to open Designer.
  2. Select and enable each of the following agents. When prompted for a server name, enter the name of the server where the Resource Reservations database resides, and click OK.
  • Autoreminder
  • Purge Documents (Auto)
  • RenameReservations and SendNotice
  • Update Blocker Documents




Setting user access rights to edit and delete reservations

This topic, as written, may imply that only an Editor access level is necessary to delete a reservation from the Resource Reservations database.

In fact, both at least Editor access level (with deletion rights) and the CreateResource role are necessary for anyone to delete a reservation, whether the person is a requestor, a resource owner, or a manager of the database.

The topic will be clarified in a future release of the documentation.

(SPR # KTOT88HQ5Q)


Sources for improving server performance
The related topic link to the NotesBench Consortium in this topic is no longer useful. See the following article for performance information using NotesBench measurements:

IBM Lotus Domino 8.5 server performance



Specifying server settings for attachment consolidation

The information in this table row for the DAOS base path option is inaccurate. The corrected text is shown.

DAOS base path The full or relative path to the attachment repository. If you enter a relative path, such as DAOS, the default is to a relative path within the Domino data directory.

Important Despite the default, it is highly recommended that you specify a full path outside of the Domino data directory.

Example on Microsoft® Windows®:

C:\DAOS

Example on Linux® (SLES 10) or IBM® i:

/local/DAOS

If the directory you specify does not exist, Domino creates it for you.

Note Make sure that the Domino administrative user has file-access permissions in the directory appropriate to the server's operating system.

In addition, the topic states that the default for the field "Minimum size of object before Domino will store in DAOS" is 4096 bytes. As of Domino 8.5.2 that default is 64000 bytes.

(SPR #CMCY8AUK7U)


Streaming cluster replication

The following section of this topic contains erroneous information and should be deleted.

    Domino enables SCR when the following sequence of events occurs:
    • A database is opened
    • Cluster replication replicates a change to another Domino (current-release) clustered replica
    • All references to the database are closed
    • A database is opened
    • On future changes in the database that needs to replicate, SCR replicates the change to the other Domino (current-release) servers.



Table of Domino naming requirements

The requirement for a Domino domain name is not as limited as the topic states. In a future release of the documentation it will change as follows:


Name Characters Tips
Domino domain 31 maximum
  • This is usually the same as the organization name.
  • Use a single word, which may include alpha characters (A - Z), numbers (0 - 9), and the ampersand (&), dash (-), space ( ) , or underscore (_).You may also include international characters, but they are not recommended or guaranteed to work..



The Domino Attachment and Object Service (DAOS)

This topic states that the value for the field Store file attachments in DAOS" can be "NSF," but that is no longer accurate. The field's possible values are "Enabled" and "Disabled." "NSF" was an early equivalent of the value "Disabled." It meant that attachments are stored in the Notes database (as they are by default) instead of in a separate object repository (which is what DAOS does when enabled).




Tools and preferences for debugging in the Domino Administrator

The commands described in this topic are actually available from the Domino Designer client, not the Domino Administrator. This topic will be removed from future releases of Domino Administrator documentation; for information, see the Lotus Domino Designer documentation.



Typical administrative tasks and their equivalent Domino commands

The following table row in this topic contains a mistake in the last column:

Remove a Domino server CFGDOMSVR To remove the DOMSERV1 server, type:

cfgdomsvr server(domserv1) option(*delete)

The correct command is:


cfgdomsvr server(domserv1) option(*remove)




Updating the design of an enabled agent
This topic needs to include the following note.

Note: This topic describes behavior that occurs only when using the Convert or Design tasks in Domino Administrator to update the design of a database or databases. Selecting either the File > Application > Replace Design or the File > Application > Refresh Design command in the Notes client does not preserve the enablement status of agents already in the design.

(SPR #NNAI7YH2XH)



Upgrading mail files with the mail conversion utility

Performing a Lotus Notes Mail template language conversion on a Linux platform Domino server

There was an omission in this topic which restricted ability to perform a Lotus Notes Mail template language conversion on a Domino server running on Linux.

The following example, illustrating how to use the convert tool to upgrade to the German Language Pack, is correct for a server running on Windows:

load convert -g"German" TestMail.nsf * mail85_en_de.ntf

However, if you use that command example to request a conversion on server running on Linux, you will see an error similar to the following:

The language option specified -- '"German"' -- is not valid or not a supported language. The correct format for the -g option is:
-g'Language'.

The suggested use of single quotes does not work either.

Corrected example syntax for a the mail template language conversion request on a Linux platform server is as follows (this example uses the supplied mail85.ntt mail template):

load convert -gGerman TestMail.nsf * mail85.ntf

On the Linux server, do not use quotes of any kind around the requested language name.

(SPR #DSAS862NQC)



Using administration roles in the Domino Directory ACL

The following text in this topic requires the following addition shown in red to be correct:

  • Modifier roles apply only to administrators who have Author access. Administrators who have Editor access or higher automatically can modify all documents except Policy documents, for which even administrators with Editor access require the PolicyModifier role.

(SPR #ASHH8RVGGQ)




Using database design compression

Step 4 in the following procedure is not necessary to compress new design elements.

To compress new design elements in a selected database

1. From the Domino Administrator client, select File - Application - Properties.

2. Click the Advanced tab. (The icon on this tab is a beanie.)

3. Click "Compress database design."

4. Run a copy-style compact to compress the design by entering this command:

load compact -c filename.nsf

To compress existing design elements in a selected database

In addition to enabling compression for new design elements, you can also enable compression for existing design elements in a specified database by running a copy-style compact on the database. Enter this command:

load compact -c filename.nsf


Using load convert to convert non-mail databases

One of the examples in the topic is incorrect because of an extra space character before *.nsf. The corrected example is shown here in red.

You can also convert an entire directory as shown in this example,

load convert -d doclibrary\*.nsf  newtemplatename

  • Where doclibrary\*.nsf represents the name of the directory being converted and all databases in that directory.
  • Where newtemplatename is the name of the template that creates the type of database to which you are converting all databases in the named directory.

(SPR # TITH7XJD5G)



Using Notes shared login to suppress password prompts

In this topic, this item in the final bulleted list is not accurate; see the modified version below.

  • Shared login-enabled IDs that are stored in a Notes ID vault can be used from more than one Microsoft Windows computer without requiring users to make copies of the ID file. To use an ID on more than one computer when a Notes ID vault is not used, a user clicks "Copy ID" in the User Security dialog box to make a new, Notes-password-protected copy of the ID file. When the user runs Notes using the copied ID on another computer, the user's effective policy determines if the ID will be enabled for Notes shared login.

  • To use a Notes shared-login ID on more than one computer, a user clicks "Copy ID" in the User Security dialog box to make a new, Notes-password-protected copy of the ID file.  When the user runs Notes using the copied ID on another computer, the user's effective policy determines whether the ID will be enabled for Notes shared login.
    It is possible to use the ID Vault to move a Notes shared-login ID from one system to another, but all of the following requirements must be met:
    1. The Notes shared-login ID stored in the ID vault must have a password associated with it.  Often this is not the case, because Notes shared-login IDs on a user's computer do not have a password. 
    2. The owner of the ID must know the password associated with the copy of the Notes shared-login ID stored in the ID Vault
    3. The user must be performing a Notes setup on the new system where the ID will be used, or the NOTES.INI file on the new system where the ID will be used must contain entries specifying the owner of the ID and the location where the ID should be stored.

(SPR # DJAG85BLW2)


What's new in IBM Lotus Domino Administrator and Server 8.5.3?

Under Security - new features, the following item is inaccurate: The new field Don't prompt for a password from other Notes-based programs (reduces security) in the Security settings policy document is actually on the Password Management > Password Management Basics tab.

In addition, an ID Vault a Security policy can now prevent password prompts from other Notes-based applications. Notes client users are able to select the option Don't prompt for a password from other Lotus Notes-based programs (reduces security) in their login and password settings. In this release, you as the Domino administrator can enable this option for multiple users in the Security policy, ID vault tab, Password Management Basics tab.

Under Lotus iNotes - new features, the following item is not accurate; this support is not actually in release 8.5.3.

Support for importing contacts from non-English CSV files

Users exporting contacts to a non-English CSV file can then import that data using the iNotes Import Contacts feature.

Under Lotus iNotes whitelist for file attachments, two additional settings are required to implement the whitelist:

  1. Use a desktop policy to apply the following NOTES.INI parameter to client users:

    EnableWhiteList=1
  2. Use a policy to set the Format for incoming messages field in users' Person documents to "Prefers MIME."

(SPR #AKNX8XCT9U)

Related information

Lotus Domino Documentation

Document information

More support for: IBM Domino
Administration

Software version: 8.5.1

Operating system(s): Windows

Software edition: Edition Independent

Reference #: 1406523

Modified date: 01 November 2010