Dec's Dom Blog

1 - Agree with Eileen - that is how we do it. You just have to make sure that AdminP and the Domino Directory are replicating properly to those sites.

2 - A few years ago, I set up RnR for a company that had six locations; all rooms were categorized by the facility's street address, making it easy for users to determine which rooms were available at their site. The primary reason they wanted it centralized was that they would frequently have cross-site conference calls, and centralization allowed them to simultaneously book a conference room at each site involved in the call. One flaw in this approach, though: If each room being booked could hold 10 people, and someone wanted to hold a 3-site meeting with 5 people at each site, RnR would reject each of the room invites, because it saw 15 attendees and considered each room to be overbooked... it didn't assume an even distribution of attendees per room or prompt the chairperson to specify.

3 - Well it makes sense to have them seperated per site , as long as the set up and configuration is all done via the NAB, then international users can all book rooms internationally yet you can enforce local controls.

Way I used to do it before and still do it

4 - I prefer to just have one RnR database. That's the way I initially set it up at my company. But after getting some specific workgroups using RnR some people wanted separate databases so that they wouldn't have to weed through other reservations just to see theirs.

So now I have 4 RnR databases. One has 3 rooms at one location, two have 1 room each, and the 4th has 29 rooms at 9 different sites. It's the one I will create all new rooms in if the people don't ask for it to be in a different database.