Archive

Posts Tagged ‘publishing’

Why does MS-Exchange calendar publishing with Limited details show the name of the organizer in the subject?

  1. Partial answer: Because the organizer name gets already put into the booking itself, before publishing  (I first thought it was put in by a bug  the publishing settings, where there is   supposed to be an option to enable/disable showing the organizer name ).  UPDATE: Another part of the answer: AddOrganizerToSubject is set to true on the mailbox (Doh! Hm, but why did this not seem to cause a problem before)?
  2. Booking:
  3. image
  4. Result (I saw the correct “whence”part of the subject briefly flickering up, but then the organizer name appeared in front of it):
  5. image
  6. Publishing Setting:
  7. clip_image001
  8. Published View (which is where we do not want the organizer to show):
  9. image
  10. clip_image003 2010 SP?.

How to publish an OWA calendar to the internet

  1. For lack of PowerShell access, we have to:
  2. sign in as the resource : image
  3. “click on publish” in the calendar’s context menu: image
  4. choose these settingsimage
    1. we do a lot of forensics and statistics, looking back throuhg the term, which is longer back than 3 months
    2. students do not need to book ahead at the beginning of the term for end-of-term projects, so we do not need 6 months forward;
  5. Result: image.

Protected: New resources mailboxes not visible in the GAL for student accounts in live@edu?

2012/02/09 Enter your password to view comments.

This content is password protected. To view it please enter your password below:

Exchange 2010 and Live@edu: How to use resource calendar publishing to implement a help desk timetable and signup sheet

2011/09/22 1 comment
  1. Calendar sharing with students that have only cloud accounts in  live@edu requires them to be mail-enabled users in on-premise AD and only works if a users privileged to share shares with individuals through the GUI (in our circumstances: no groups, no PowerShell access).
  2. Workaround to share resource calendar information is: publish calendars to the internet. This needs careful consideration of privacy issues, but Exchange 2010 provides you with a number of helpful options, including “availability only”.
  3. calendar-publish-permissions
  4. If you publish, you can easily generate the links from the resource mailbox name, and manage large sets of calendars e.g. in an MS-Excel Web app.
  5. As you can see in the below LRCTutor12 calendar subscribed to in either OWA or Windows Live, the Exchange 2010 ICS does not seem to provide the calendar name, users have to update it manually (maybe use the resource mailbox account name from the calendar URL).
    1. student-internet-calendar-in-owa-error_thumb[2]student-internet-calendar-in-windows-live-works_thumb[2] 
    2. If you “hack” resource calendars to be a help desk timetable (support personnel, like lab assistants/tutors, one calendar per language, sharing the support role), and have personnel update their availability with late-breaking changes through their Outlook calendars (“cancel this occurrence”) and automatically get these changes pushed out to all users over the internet.
    3. You can also “hack” a signup sheet “on steroids”:
      1. enforce a MaximumDurationInMinutes suitable for a sign-up appointment duration)
      2. set the AutomateProcessing option to AutoUpdate,
      3. accept the meeting requests of lab assistants/tutors at term start, so that they appear as solid blocks in the calendar, and advise clients trying to sign-up that only 1 client can sign-up during any given solid block with the office.
      4. Then ignore meeting requests of clients during the term (but communicate the rule to clients: only one client can sign up for support from the “office” during any given time slot. There is in my knowledge no way to set a number in Exchange 2010. Neither MaximumConflictInstances nor ResourceCapacity are applicable). The client meeting requests will remain tentative and appear hatched in the calendar for any other client to see.
      5. It is advisable to publish the calendar not with “Availability” only, but with “Limited Detail”, so that additional information (office hours dedicated to specific support topics/clinics, specific requests by clients) can be passed back and forth between support personnel and clients (and anything is better than “Free/Busy” which is especially misleading for such office calendars). Note that even if OrganizerInfo is included on-premise, it seems not included on calendars published to the internet (option “public”; “restricted” has not been tested), which makes Limited Detail possible in our environment.

    4. Publishing the calendar to the internet with “Full details”  could be used for passing additional information, like special handling instructions to student workers,
      1. like this: CIMG0008(this is the publically viewable HTML – oddly)
      2. This notes passing does not work with cloud-accounts that are subscribed to the calendar ICS that are not mail-enabled in AD: no notes field gets through to them in OWA) 
      3. But the one-size-fits-all approach is unsatisfactory. If the group of student workers is small, it could (once mail-enabled in AD) be shared the calendar with instead.
      4. incidentally, what happens with the organizer field under “full details”
    5. Ìt appears that a calendar can not simultaneously be published "public" and "restricted" (need to know the obscure URL), let alone with different levels of information included.