Actually, I’m certain you wouldn’t. Accounts created solely for administrative and functionality purposes do not require a license. This is very clearly stated in the licensing rules from IBM. That’s why you don’t have to license development signature IDs, or LDAP logins, or special accounts for LEI, or anything that’s not associated with a *person*. You are required to buy licenses for human beings, be they employees, contractors, vendors, partners, suppliers or customers. You are not required to buy licenses for computers.

@Fred - in the past, I’ve seen stand-alone calendar files (without any associated Person or Mail-in Database Documents) used for simple room booking management because of inherent issues with the old R&R (pre-ND7) implementation. In addition, by making these stand-alone calendars Mail-in Databases, it is then possible to perform busytime look-ups again them and check for availability, thus providing very similar functionality to the old R&R system.

The new RnRMgr functionally is significantly better, and I agree that it totally elevates the need for these stand-alone calendars, however it can become a time consuming and complex task, to not only migrate all of the calendar data across, but also to educate users about the changes. In my experience, this can only practically be performed after the upgrade (ie once the new RnRMgr is available), as a follow-on piece of work. I trust this now makes a little more sense?

Why collect busytime info for mail-in databases?
If it’s for Rooms & Resoruces, the new RnRMgr takes care of that (but you do need to upgrade design of the Resource databases to the new Design.

Fred

Thanks for your suggestion, I’ll try that next time . . .

Thanks for your feedback and for your excellent suggestion.

This would filter out ALL protected group documents…