What is the "Roaming User" feature of Notes/Domino 6.0.1 and above? How is it implemented?
I. Roaming User feature defined
II. How to implement Roaming User feature
III. Frequently asked questions about Roaming Users
A. Notes 6.x Client
I. Roaming User Feature Defined
Roaming User functionality is new to Notes Client and Domino Server; it was introduced with the Notes/Domino 6.0.1 release.
A Roaming User is a user who has the ability to access Notes from more than one Notes Client within a domain, while keeping their customized settings and personal information the same across all Notes Clients. Data for these users replicate between the user's machine and a roaming user server, where these files are stored. By default, the roaming user server is the user's home or mail server, but can be any server within the domain that is selected by the user's Administrator. When a roaming user logs on from a different Notes client, it will automatically retrieve the user's ID file (user.id), Personal Name and Address Book (names.nsf), Bookmarks (bookmark.nsf) and Journal (journal.nsf) from the roaming user *server. Any changes the user makes in these files at one client is replicated up to the roaming user server. This enables the roaming user to have a consistent experience from any Notes Client.
The Roaming feature utilizes features/functions already present within the Notes/Domino 6.x or higher codestream, such as Client Replication, Client-to-Server Replication, Server-to-Server Replication, Cluster Replication and Failover within a Cluster, and Admin Proxy actions. A single Notes client and a multi-user Notes client can both be used for roaming purposes. The client code itself does not roam; therefore, you are required to have a Notes 6.x Client installed on each workstation that is expected to be used for roaming.
II. How To Implement Roaming User Feature
Refer to the documents below for information on implementing the Roaming User feature as well as other tasks and general information/background.
What Information Replicates to the Roamed Notes Client from the Roaming Server? [# 1102575]
What Notes.ini Values Are Stored and Replicated in the Personal Address Book for a Roaming User? [# 1085717]
III. Frequently Asked Questions about Roaming Users
A. NOTES 6.x CLIENT
What concerns should I have if I plan to roam both Win32 and Macintosh clients together?
- Password Keychaining
If you are a Roaming User who is set up to work on a Macintosh, and you make a password change with password keychaining enabled, you see an "Error: "Wrong Password.." message indicating that the wrong password has been provided.
- User Dictionary
You cannot use the same User Dictionary for both a Macintosh and Windows clients. The User.dic file will roam only among workstations using the same native platform.
- "Notes with Internet Explorer" Browser Selection
The 'Notes with Internet Explorer' Internet Browser option in the Location document (in the Personal Address Book) is a Windows platform only option. This browser choice is not supported on Macintosh. Therefore, there are certain circumstances in which the user may have a problem with the Browser field value in their Location document.
If a Roaming User has a Notes Client on both Windows and Macintosh systems, they will also run into this problem if their Browser option is set to 'Notes with Internet Explorer'. Because the Personal Address Book is stored on the server for Roaming Users, the Browser option will replicate to all of the user's Notes Clients. Therefore, it is recommended that Roaming Users select a different browser option which is compatible on all Client platforms.
If a Setup or Desktop Policy Settings document uses the 'Notes with Internet Explorer' browser option, a numeric value will be displayed on the user's Macintosh Client in the Internet Browser field of the Location document. This will prevent the user from launching URL links from within the Macintosh Notes Client because the browser value is invalid. To correct this, simply edit the Location document and select a valid browser option for Macintosh.
Separate Location documents for use with the MAC and PC should be included. This will help to avoid the problem caused due to the 'Notes with Internet Explorer' Internet Browser option in the Location document (in the Personal Address Book) being a Windows platform only option.
- Some User Preferences Do not Currently Roam
At this time, there are three user preference settings that have been identified not to replicate during roaming between Macintosh and Windows 32-bit operating systems: "Right Double Click", "Monochrome Display" and "Keep Workspace in Background". Refer to the document, "Some Preferences Do not Take Effect When Replicated to Roamed Notes 6.x Client" [#1106930] .
- Prompted for Password Twice
This issue occurs only on a new roaming client setup on a Mac. After setup completes and replication for roaming on startup completes, the user will be prompted again for their password. However, subsequent launches of the client will prompt the user only once for their password.
Which Notes Client install should be used when considering or implementing Roaming User?
Although a single and multi-user client install can be used to implement the roaming user feature, there are some important considerations to make before installing the Notes Client and/or implementing this feature.
Why does my Home Page display errors when I attempt to roam at another machine?
If a roaming user has their Personal Journal and/or another roaming database other than their Personal Address Book displayed on the Welcome Page, the following error may display after roaming to a new machine for the first time:
"Unable to load frame's content: Database is not fully initialized (It does not contain any views). You will have to use 'Replicate...' on the 'File - Replication' menu to initialize it."
For more information on this issue, please refer to the document ,"Error: "Unable to Load Frame's Content..." Attempting to Load Notes 6 as a Roaming User" [# 1106959]
Why might I have a problem trying to connect to my server from a roamed client?
If the Notes Client requires a Connection document to access the roaming server, the user may be unable to upgrade the client to roam if the Domino Server name specified in the Connection document differs from its machine name, or the server that is being accessed exists in a different network or domain.
Also, make sure the Home/Mail Server field on the Servers tab of the current Location document contains the complete host name. For example, if your LAN Connection document contains "serverx.ibm.com" in the Destination Server Address field, your current Location document should contain "serverx.ibm.com" in the Home/Mail Server field.
In addition, if the user has multiple Notes Clients that point to different network drivers, the user may not be able to connect to the roaming server from one of their machines. For example, if machine1 has LAN0 set to TCPIP and machine2 has LAN0 set to NETBIOS, there may be problems once the Personal Address Book replicates to the other machine from the roaming server.
In this case, once the Personal Address Book replicates down to the other machine, it will no longer be able to connect to the roaming server because the network address will be in the format of the other machine's setting (TCPIP or NETBIOS - whichever Client names.nsf file replicated to the server).
Can I request a name change if I am roaming?
If you are a roaming user and you need to request a name change, contact your Notes/Domino Administrator so that they can perform this request using the AdminP task against the Domino Directory directly. Requesting a name change through User Security (File --> Security --> User Security) is not supported for Roaming Users.
Why does the replication message on client shutdown not mention "roaming"?
After upgrading to a Roaming User, you notice that the following message displays when Notes Client shuts down:
"Send data to servers (update servers with changes made to the local databases)?"
There appears to be no indication in this message that this has anything to do with roaming. This message is the standard message that will display whenever you have "Replicate on Shutdown" selected. A Roaming User might have other databases, not just roaming databases that he/she wants replicated at shutdown. For more information refer to the document, "Notes Roaming User: Shutting Down Notes the "Send Data to Server" Message is Unclear" [# 1096359].
Do full text indexes roam?
No. If a user creates a full text index on any of their local databases that either replicate as part of roaming or have been added to the primary databases for roaming, the full text index is not replicated to the roaming server along with the database. Therefore, when a user roams the user must create a new index and subsequently update it after replication from the roaming user server. Refer to the document, "Notes 6.0.1 Roaming User: Full Text Indexes Do not Roam " [# 1087747].
Do Private Views/Folders roam?
No. Because private views/folders can be stored in the Desktop6.ndk file which does not replicate for roaming purposes, a Roaming User may find that a private view/folder is not available for a database at another machine. When a user creates a private view in a database and the option, "Create Personal Folders/Views" is not a selected preference/right for that user in the Access Control List (ACL) of the database, the private view is stored in the user's desktop file, which does not roam.
To work around this issue, the Designer of the database must enable the option "Create Personal Folders/Views" in the database ACL to allow private views/folders to roam (to be stored in the actual database itself instead of the desktop.) For more information refer to the document, "Notes 6.0.1 Roaming User: Private Views Stored in DESKTOP.DSK Do Not Roam" [# 1087127].
Can I use a different name for my local bookmark database if I roam?
No. One of the primary databases that Roaming Users replicate among the roaming clients/workstations is called Bookmark.nsf. If you have renamed this database, this feature will not operate successfully. If the database has been renamed, please rename this database back to its original name of "bookmark.nsf" at the operating system level.
In addition, if you had renamed this database in previous releases of Notes and have subsequently upgraded to Notes 6.0.1, then you may see that this custom file name was entered into your Location document as well. Edit your Location document, go to the Advanced tab, and if a "Bookmarks filename" field exists, ensure that this file name is also changed to the default value of "bookmark.nsf". After you have corrected that field and saved the Location document, that field will become hidden.
Does my Mail Signature file roam with me?
Starting in Notes 8.5, the Mail Signature file is stored in the mail file rather than on the local workstation. This ensures the same signature is available from any system that accesses the mail file. In this way, the Mail Signature effectively roams.
In previous versions of Notes, the Mail Signature file is stored locally and does not roam. To work around this limitation, you will need to either store this file on floppy to use it when working remotely, or individually place it on each workstation that you roam from.
Refer to the document "Notes/Domino Roaming User: Signature Files Do Not Roam" [# 1085328].
How do I Set up Archiving for my Roaming Users?
If your end-users are utilizing client-based archiving, then have these users create an archiving profile to a local archive and archive only at their primary roaming workstation.
Note: If you plan to implement a multi-user install and also utilize one of the roaming cleanup options, then you should not archive locally to the workstation. What can happen is that if the Admin has selected a cleanup option for your multi-user install, your Notes \Data directory for that install can be completely removed from the workstation; as a result, the subsequent "notes\data\archive" directory will also be removed. It is recommended to archive to a selected drive/location that is separate from the location of this local Lotus Notes client type install. This is not an issue for the single Notes Client install as the cleanup options cannot be used for that type of install; therefore, the archive can be maintained locally at the default or preferred drive selection on that workstation.
How can I access the Help Text when I switch IDs on a multi-user install? Text is missing.
You may find that if you decide to switch to another user ID on a multi-user install (File --> Security --> Switch ID), that the context sensitive Help text (the topic called "Sharing a Computer with other Users") is not available should you click on the question mark icon in a dialog or press F1. Instead,cancel out of all open dialog boxes, select Help > Help Topics from the menu, and in the Contents view click "Getting Connected", and then click "Setting Up as a Roaming User."
Why do some preferences not take affect when I replicate to my roamed client?
You may need to shut down and restart your roamed Notes Client once you have replicated to it in order for your preference changes to take effect. For information on this issue, refer to the document: "Some Preferences Do not Take Effect When Replicated to Roamed Notes 6.x Client" [# 1106930]
Is there any change as to how read/unread marks function when roaming?
No changes have been made to the architecture/functionality of read/unread marks in Notes 6.x specific to how the Roaming User feature operates. The underlying purpose of the Roaming User feature is to enable users to operate on a much more remote basis, while also giving them the same Notes Client look and feel on any workstation as they would experience on their primary workstation. Through replication of settings and local data, users are now able to be more productive knowing that their latest accomplishments will be available to them at any location.
Initial Read/Unread mark concerns will likely arise as more end-users are introduced to this ability to roam amongst clients that are not their primary workstations (especially if some of the workstations are not used very often). Most scenarios/issues reported on read/unread marks should be reviewed first against existing technotes which discuss aspects of unread marks on both client and server that have already been reported, discussed, and may have been addressed prior to the introduction of this feature.
The "desktop" is one of the files used in handling read/unread marks. However, Roaming Users do not replicate this file because it is not one of the required databases needed to replicate for roaming purposes. For more information on read/unread marks, please see the following technotes:
"Unread Mark Problems in Clustered Environments" [# 1100309]
How will changes to my local user ID be affected when I roam?
When the Administrator selects to "roam" a user, he/she can select to store the user's id within their Personal Name and Address Book. This database is replicated to the roaming user server by default. In this manner, any changes to the user's local id, such as importing new certificates or adding/deleting secret encryption keys, is automatically replicated up to the roaming user server as part of that database. Therefore, any changes to this user id is made available via Roaming User's use of replication to any other roamed client for that user. Otherwise, the update to their local id will have to be done manually at each client workstation that they use.
Note: If you are a roaming user and your user.id file is busy when scheduled replication attempts to replicate a change to this file, then it will not be updated with the change. You will need to make the change manually to this file after it is closed.
What happens to my Toolbar/SmartIcon settings should I roam?
In Notes 6, the Toolbar feature replaces the Notes R5 SmartIcon feature. SmartIcon sets as well as any SmartIcon custom buttons are converted into Toolbars upon upgrade of the client to Notes 6. Each client (Domino Administrator, Domino Designer and Notes Client) maintains its own set of toolbars, providing the ability to have different toolbars and layouts for each one. At this time, SmartIcon sets are converted only into the first client that runs after Toolbars have been enabled. However, you can "import" a SmartIcon set into another client via Toolbar Preferences.
SmartIcons in releases prior to Notes 6 Client are external files (SMI files) that are local to your machine and contained all of your SmartIcons. Toolbars are not external files, but instead are contained within the bookmarks database, or "bookmark.nsf". Since the Bookmark database is one of the default databases that Roaming Users replicate, your Toolbar settings within the Notes Client will roam with you.
Why does each roamed client open the About Database document?
When a Notes database property is set to show the "About Database" document (shown below) when the database is opened for the first time, it causes the "About" document to be displayed each time a user roams to a new machine, for every database the user opens that has this property set. This database property is stored in the user's desktop file, which does not roam.
Refer to the document, " "About Database" Doc Displays Every Time Roaming User Opens Db on a New Machine" [# 1094286].
Why do some of the icons not appear for my bookmarked databases upon roaming?
If you bookmark some databases without opening those databases first, then when this bookmark list replicates to a newly roamed machine as part of the bookmark database, only the names of those bookmarked databases may appear, and not their respective icons. The database icon will display correctly once the database is opened on this new machine. As a workaround, open any bookmarked database prior to roaming to a new machine.
Do I need to have a multi-user installation in order to roam?
Quite simply, No. The "multi-user" feature is also new to Notes 6 but accomplishes the same goal in Notes R5.x, also known as the "shared" install.
What if I want to print labels or print using the "Documents Style" option when I roam?
If you plan to print using this option and select to "Print Multiple Documents on each Page" while you are roaming, open the local replica of your address book to use this option instead. Also, if you plan to print labels from your Personal Address Book, use your local replica.
Roaming User feature and Sametime Instant Messaging Services in Notes 6.5.x
The Notes 6.5x codestream implements Sametime Instant Messaging (IM) functionality within the Notes Client. As such, there are a few concerns if a user will be set up to roam as to whether their server and/or client will be upgraded to that Notes/Domino version.
B. DOMINO 6.x SERVER
|Critical Importance||Major Importance||General Information|
Can you become a Roaming User with a flat user id?
No. Only those users who have a hierarchical ID (e.g., CN=Jane Doe/OU=East/O=Acme) can be upgraded or registered to roam. Please contact your Notes/Domino Administrator to have your user ID recertified to a hierarchical format if you desire to use the Roaming User feature.
For further information on recertifying an ID from flat to hierarchical, please see the topic called "Upgrading a User Name from Flat to Hierarchical" in the Lotus Domino 6.x Administrator Help Guide.
How do Policy/Policy Settings documents affect a Roaming User?
A Policy document is composed of one or more (five total) Policy Settings documents: Registration, Setup, Desktop, Mail Archiving and Security. This Policy document, therefore, identifies a collection of individual policy settings, and these individual settings define a set of defaults that are applied to a user or groups of users that are assigned this Policy within their Person document. Once a Policy is in place, you can easily change a setting across your users.
A user can be set up or defined as a "Roaming User" by default through the use of a Registration Settings document. Create or edit an existing Registration Settings document and on the Basics tab under Roaming Options, select "Roaming User". Fill in the subsequent roaming options as appropriate. However, you cannot change a user's roaming status simply by de-selecting this field. You would need to make that change manually to the user's Person document with the Administrator Client's Roaming Tool.
For further information on creating a Registration Settings document, please see the topic labelled "Creating a Registration Policy Settings Document" in the Lotus Domino Administrator 6.x Help Guide. If you are a service provider, "Roaming Users" is not supported for hosted organizations.
Note: Setup Policies are not supported for Roaming Users. During a new client setup for a Roaming User, policy settings would be copied down to the client, then the roaming databases would be replicated down. The majority of policy settings are stored within the roaming databases; therefore, replication of the existing roaming databases will overwrite the newly copied down policy settings. A Desktop Policy contains the same fields used in a Setup Policy and can be used instead. (SPR# DPAT5FGQ9E)
Why can't I roam successfully through my Passthru server?
Roaming User upgrade is not supported on a Client that is configured to access the Roaming server via a Passthru server. If a user with this configuration has initiated a Roaming upgrade, they will receive a prompt to upgrade to Roaming on that Notes Client. They should decline the upgrade on this machine to prevent configuration problems. The user can successfully upgrade on other Notes Clients that access the Roaming server directly.
Can I change the option to store the user's ID in their Personal Address Book?
To change the storage of a Roaming User's User.id file, the user will need to be downgraded first. Then, when the user is upgraded to roaming, the user's ID storage option for roaming can be changed via the Roaming Upgrade Tool. The option "Store User ID File in Personal Address Book" can be enabled to store the ID in the Personal Address Book, or turned off to require the user to carry their ID on diskette.
Why does an upgrade request to roam remain at an "in progress" state?
When upgrading a user from non-roaming status to roaming, the Notes/Domino Administrator is provided with the option of specifying a unique folder path for the user's roaming files. This path must be relative to the Data directory on the roaming server, and should not begin with a leading '\" (slash) or driver letter. The results of this action will cause the roaming upgrade to fail and leave the user in an "In-progress" state in the Roaming tab of the Person document for the target user.
If I already "upgraded" a user to a roaming state, can I select a "clean-up" privilege later?
This scenario can happen if the requirements of a Roaming User suddenly change. Say, for instance, the user was already "upgraded" to a Roaming User, but no roaming clean-up privilege was selected because this user never accessed Notes through a workstation with a multi-user installation. This user travels to their destination and there are delays in setting up a temporary workstation on-site. No laptop was brought because of guarantees that equipment was readily available upon arrival.
The roaming feature generates a local *.cln file containing a date for the cleanup to occur for the respective roaming user on a given workstation. This file is generated only once and cannot be modified outside of the feature. Therefore, the only workaround that can be offered is for the Notes Admin to downgrade the user from roaming and when that process has been successfully completed, then upgrade the user to roaming again and this time select the cleanup option desired for that user. It should also be noted here that should a cleanup selection already exist for the roaming user, the same downgrade and upgrade workaround must be used to change any present cleanup selection. It is not supported for the Notes Admin to simply edit the Person Document of the user and select a new one from the drop-down menu. If this was attempted, it would only affect new client setups for that user where the *.cln file would be generated, however it would have no affect on existing setups and their respective *.cln files.
An enhancement request was submitted to remove the ability to edit this field as it is unfortunately misleading on its intended benefit.
Account Documents supplied through a Setup/Desktop Policy can duplicate for a Roaming User
This scenario can happen if the user is roaming to a workstation with a new setup. It will only occur upon the first roam to that new workstation. If the user roams to another new workstation, then the issue could recur. This issue is currently under investigation by Quality Engineering. From initial testing, it is believed that the issue occurs because the first time the policy runs, it will add the indicated account documents to this user's new Personal Address Book for that client install. The Dynamic Client Configuration (DCC) code will run, pull down the assigned Policy for that user, update any required views and files as designed, and supply an entry in that local client's Notes.ini file indicating that execution. At a workstation where the client has not been run before for this user, there will be no existing Notes.ini file for this client.
As the new client setup executes, it populates any required local client files, brings down the user's respective roaming databases, and finally populates the new Notes.ini file. As there is no pre-existing line entry in the client's Notes.ini file that DCC previously ran at this install, and because DCC activity logged within the Notes.ini file is not replicated by default as part of the roaming feature, DCC now executes and pulls down the required Policy for this user. This causes the additional account documents to be generated. At present, there is no check performed on whether these account documents pre-exist before adding them, so duplication can occur. This issue has not been presently witnessed at a workstation used by a non-roaming user. This issue is also documented separately via the following technote:
"Roaming User w/Desktop Policy: Multiple Account Documents Created After New Client Set Up" [# 1195871]
Why does AdminP report an error when I attempt to downgrade a roaming user?
When a user is downgraded from roaming to non-roaming, you may notice the following AdminP request error in the "Errors\All Errors by . . ." views of the Administration Requests database:
"ROAMING\<user roaming directory>\journal.nsf;
Error: The mail file specified for this person in the Domino Directory does not exist on this server."
Action: Get Replica Information for Deletion
Name(s) acted upon: <username>/<domain>
Action requested by: <username>/<domain>
Server responding to request: <servername>/<domain>
Start time: 08:14:30 AM 12/18/2002
End time: 08:14:30 AM 12/18/2002
Databases processed: None
Errors: Title: File name: ROAMING\<user roaming directory>\journal.nsf; Error:
This issue occurs only if the user does not have a roaming Personal Journal database (Journal.nsf). Trying to re-process the request will fail with the same error. At this time, the workaround is to click the 'Remove from View' button to remove the invalid error from the view.
Can I use enable Password Checking on the server if I have Roaming Users?
Yes. Please refer to the following technote for details and issues that can occur:
What fields can I modify for roaming purposes through the user's Person document in the Domino Directory?
You cannot manually edit a field supplied value on the Roaming tab of a User's Person document. Any change required to a roaming feature variable displayed as part of the user's Roaming Profile upon the Roaming tab of that user's Person document (or hidden within the document properties of this document) must be made by downgrading the user and then upgrading them with any new roaming selections desired. This process will ensure the successful handling and resetting of any roaming-related variable values.
The Roaming Replica Servers field and Roaming Server field can be changed only via an Administration Process. To change these fields, the Notes/Domino Administrator must downgrade the Roaming User and, using the Upgrade Tool, specify different values for these fields. A server listed in the Roaming Replica Servers field can be used as a failover server during setup of a roaming client if the Roaming Server is not available. The servers to fail over to during Roaming User setup must be listed in the Roaming Replica Servers field. However, if a Roaming User wants additional servers for roaming database failover, strictly for the purposes of replication, replicas can be manually created on other servers.
Keep in mind that these additional replicas will not be used during Roaming User setup if the Roaming Server or Roaming Replica Servers are not available. Notes will not upgrade the first or subsequent client machine to roaming using the value in the Roaming Replica Servers field; the Roaming Server must be available.
What settings are required if users both roam and use DOLS?
The Notes/Domino Administrator must edit the Domino Off-Line Services (DOLS) Security Policy document contained in the Doladmin.nsf database and "enable" the Roaming Users option, as follows:
1. Open Domino 6.x Administrator.
2. Click the Configuration tab.
3. Click Off-line Services/Security (view).
4. On the Basics tab, go to the Roaming Users field. Select this box to set the Domino Server to behave appropriately with Roaming Users who access the subscription. This will override the Security Policy for Roaming Users. The server will recognize the user as a Roaming User, ignore the current security policy, and find the user's ID on the user's home server and download it.
Can a non-Notes or Internet user become a Roaming User?
No, because Internet-only or web users do not have Notes IDs. Roaming Users are required to have a Notes ID.
Can I select a group of users to "upgrade" and "downgrade" at the same time?
No. You cannot assign and remove roaming profiles simultaneously. Instead, you will be presented with a dialog box shown below to indicate which option, "upgrade" or "downgrade" you would like to implement. Beside each is the number of respective user Person documents to either "upgrade/assign" or "downgrade".
What causes a Roaming User's files to replicate down from the server?
Only the Notes Client configuration will trigger a roaming user's roaming files (i.e. names.nsf, bookmark.nsf and/or journal.nsf) to replicate down from the server to the local machine. A roaming user cannot move to another machine, with Lotus Notes already configured, and get their roaming files to replicate down automatically.
Option to not include distribution lists when printing
Expand/Limit Names field contents when printing
When printing memos or Calendar entries, users can now specify whether to print the contents of the entire "To:" or "cc:" fields, or to limit it to three lines. This feature is also available to users as a roaming preference.
Summary of Related Documents:
What Information Replicates to the Roamed Notes Client from the Roaming Server? (# 1102575 )
What Notes.in Values Are Stored and Replicated in the Personal Address Book for a Roaming User? (# 1085717)
Some Preferences Do not Take Effect When Replicated to Roamed Notes 6.x Client (# 1106930)
Error: "Unable to Load Frame's Content..." Attempting to Load Notes 6 as a Roaming User (# 1106959)
Notes 6.x Roaming User: Shutting Down Notes the "Send Data to Server" Message is Unclear (# 1096359)
Notes 6.0.1 Roaming User: Full Text Indexes Do not Roam (# 1087747)
Notes 6.0.1 Roaming User: Private Views Stored in DESKTOP.DSK Do Not Roam (# 1087127)
Notes 6.0.1 Roaming User: Signature Files Do Not Roam (# 1085328)
Some Preferences Do not Take Effect When Replicated to Roamed Notes 6.x Client (# 1106930)
Unread Mark Problems in Clustered Environments (# 1100309)
|Messaging Applications||Lotus End of Support Products||Lotus Notes||6.5, 6.0.1|