Migration from R5 to R6 and ACL

I don’t really know where to put this, but can not find anything about this.

We are in the middle of a migration from R5 to R6. Currently all clients are still R5 using the R5 mail template.

We have converted the Domino Directory and now all servers are running R6.5.5 Compact has been run so the server databases are ODS43

In general all things are fine. The servers have been migrated for anything between 4 - 8 weeks.

This is the current query.

In a mail file a user has given delegation rights to a colleague to read his calendar. (Via the Tools/Delegation section)

If the colleague tries to create a local replica, one of two things happen.

  1. He gets not authorised. This may also happen if he already had a local replica.

  2. He creates the local replica, but when he looks at the ACL on the local machine, the ACL settings have changed.

Default is now Designer

The original owner is not listed.

The colleague is now manager with deletion rights.

However, further replication does not synchronise the ACL.

If we do this with a user that has a R6 client, then you are unable to see the ACL on the local replica. Which is the way I expected it to work.

Are we missing something in the migration. We have followed the Red book “Upgrading to R6”

Subject: Migration from R5 to R6 and ACL

Clive,

I have done many upgrades and I not come across this issues before. I just finished migrating from Exchange to Notes and 5.13 to 7.0X. Not issues. However, please look at your Mail Template and check the ACL in the mail template.

But the most likely issues is if you have any User Setup policies. Check to see if you have any policies…

Subject: RE: Migration from R5 to R6 and ACL

Hi. Thanks for your suggestions.

There are no user profiles involved.

The ACL for the template is still correct.

Just to clarify.

When you create a new replica, it should take the ACL of the originating database, but in this case, it creates a completly different ACL, similar to if you had selected Copy database. ie it changes and makes the creator of the replica database the manager, and default is designer. The ACL of the originating database does not change.