Roaming of further dbs buggy?

HCL Domino Domino Forum
1

Following situation (Clean up option of roaming is disabled):

  1. user A has roaming enabled and configures his first notes client => standard roaming dbs are in the local directory of first XP-Client

2)A adds a new db (discussion) to roaming directory on server and logs off (XP/Notes)

  1. A goes to another XP-client, starts notes and has to configure second notes-installation on that client => roaming dbs (including discussion) are replicated to that client locally

  2. A adds another db (library) from second XP-client to roaming directory on server and logs off

  3. A logs on to first XP-Client/Notes (configuration not necessary - see step 1), dbs are replicated locally (including discussion) BUT NOT THE LIBRARY

So is this intended: when you have clean-up option disabled, only dbs that are created on that client are roamed to that client? DBs created on other clients are not roamed.

Tried it with clean-up enabled: it works. ALL dbs are roamed to every XP-Client.

Obviously when you dont clean-up, the replication information is still there and doesn’t update even if there is a change in the roaming directory on the server.

Or am I missing something?

2

Subject: Roaming of further dbs buggy?

Hello Christian!

I did some testing with the roaming user feature during the last few days.

Obviously, the problem is that replicas of additional databases in the user’s roaming directory are created locally on the Notes Client only during client setup. This happens for example

(a) if a Notes client is started for the first time or

(b) if a Notes client is restarted after clean-up has deleted that user’s private data.

From what you described, this is exactly what happened in your case. So it’s not the clean-up option that enables the replication of additional databases. It’s the fact that after clean-up has run, the Notes client setup will run the next time the client is started (be aware, that clean-up only happens on Notes clients that were installed as “multiple user clients”).

If setup doesn’t run, the client only replicates the databases which already reside in the local data directory (i.e. the client simply does what it is told by the location document).

I’m not sure if that’s “working as designed”…

Regards

Alex