Resource Scheduler for Outlook/Exchange migration flow

These go through the flow process for how we migrate data from PeopleCube Resource Scheduler for Outlook/Exchange into Exchange 2007.

This is an excellent overview of scheduling resources in Exchange 2007.

Phase I: Resources scheduled via Outlook



Resource accounts MUST:

• Exist and be mail-enabled in Exchange 2007 and Active Directory


• Be configured to process meeting requests


• Client (that's you) must provide a map between RSOE resource name and Exchange Resource alias/email address
  

Testing and Use:

Service Account defined with impersonate + send-as permissions

• Test this in a lab prior to running in production


• Sumatra code will run on a 32-bit machine (NOT on a 64-bit server)


• Code will use Exchange Web Services through an Exchange 2007 CAS


• End Users use Outlook 2007


• Meeting updates:
  a) Accepted as part of Exchange 2007 features,
  b) might remain in all end user’ inbox post-update and will not be removed


• The Sumatra process:
  a) will not check for resource double-booking or conflicts
  b) will work on CURRENT meetings only – it will skip expired/completed meetings as determined by RSOE’s meeting end date
  c) will not configure Exchange resources with settings to ensure resource will behave as RSOE resources (i.e., you control the process by provisioning your resources as you want beforehand)
  d) Responses from Exchange’s Resource management will remain in the meeting organizer’s inbox
  e) Note: Outlook-booked meetings are defined as those meetings, found in the user’s Exchange "Calendar" folder, that have an "RSOE" meeting tag (The tag is attached to the meeting as a hidden MAPI code.)

Phase 2: Scheduled via the Web

PROCESS ASSUMPTIONS:
See assumptions from Phase 1.
Phase 2 should be run after phase 1 completes
The Sumatra process:

• Creates a meeting with the name "RSOE_Migrated" in the organizer’s calendar. The meeting with have the resource as the only "attendee". All Direct-booked meetings will be created as one-time meetings.
• Does not check for double-booking or conflicts (That's what Exchange is for).
  For the resource: If a conflict exists, Exchange will decline the meeting request
  For the meeting organizer: A "double booked" meeting will be added to the end-user’s calendar
• Works on CURRENT meetings only – it skips expired/completed meetings as determined by RSOE’s meeting end date
• Does not attempt to link or match this meeting to an existing meeting in the
  organizer’s calendar
• Note: direct-booked meetings are defined as those meetings in booked in RSOE that do not have an outlook "RSOE" tag.
• Responses from Exchange’s Resource management will remain in the meeting organizer’s inbox
• Meeting times are recorded in RSOE as the server’s "local" time, and will be added to the meeting organizer’s calendar in the "local" time and time zone (even if the meeting organizer is in a different time zone.)