{"id":326,"date":"2011-07-30T12:15:24","date_gmt":"2011-07-30T11:15:24","guid":{"rendered":"http:\/\/emtunc.org\/blog\/?p=326"},"modified":"2017-02-27T14:55:27","modified_gmt":"2017-02-27T14:55:27","slug":"set-a-room-mailbox-to-show-details-of-a-meeting-in-its-calendar-office-365","status":"publish","type":"post","link":"https:\/\/emtunc.org\/blog\/07\/2011\/set-a-room-mailbox-to-show-details-of-a-meeting-in-its-calendar-office-365\/","title":{"rendered":"Set a Room Mailbox to Show Details of a Meeting in its Calendar &#8211; Office 365"},"content":{"rendered":"<p>You may notice that meetings with a &#8216;Room&#8217; mailbox will by default only show a &#8220;Busy&#8221; status.<br \/>\nMany, including the organisation I work for, wish to have (at the very minimum) the following displayed in the Room&#8217;s calendar:<\/p>\n<ul>\n<li>Organiser of the meeting, and<\/li>\n<li>The subject of the meeting<\/li>\n<\/ul>\n<p>Below I will demonstrate how to set the permissions so that all meetings (except those explicitly marked as &#8216;Private&#8217;) publicise the above details to all who view its calendar.<\/p>\n<p><!--more--><\/p>\n<ol>\n<li>First make sure you have the remote signed execution policy set to true. You can do this by running PowerShell in admin mode and running: <strong>Set-ExecutionPolicy RemoteSigned<\/strong><\/li>\n<li>Next, run the following to authenticate your self and import PowerShell commands to your local session:<\/li>\n<\/ol>\n<pre class=\"lang:ps decode:true\">$LiveCred = Get-Credential\r\n$Session = New-PSSession -ConfigurationName Microsoft.Exchange-ConnectionUri https:\/\/ps.outlook.com\/powershell\/ -Credential $LiveCred -Authentication Basic -AllowRedirection\r\nImport-PSSession $Session<\/pre>\n<h2>Set the Room calendar to show &#8216;limited details&#8217; by default<\/h2>\n<p>We will do this using the <a title=\"Set-MailboxFolderPermission command reference\" href=\"http:\/\/technet.microsoft.com\/en-us\/library\/ff522363.aspx\" target=\"_blank\">Set-MailboxFolderPermission<\/a> command. Click the link to see the full list of parameters you can pass in to the command. We will be using &#8216;limited details&#8217; for the AccessRights variable.<\/p>\n<pre class=\"lang:ps decode:true\">Set-MailboxFolderPermission -AccessRights LimitedDetails -Identity Room:\\calendar -User default<\/pre>\n<h2>Set the Room calendar to show the &#8216;Organiser&#8217; and &#8216;Subject&#8217; of the meeting<\/h2>\n<p>We will do this using the <a title=\"Set-CalendarProcessing command reference\" href=\"http:\/\/technet.microsoft.com\/en-us\/library\/dd335046.aspx\" target=\"_blank\">Set-CalendarProcessing<\/a> command. Click the link to see the full list of parameters you can pass in to the command.<\/p>\n<pre class=\"lang:ps decode:true\">Set-CalendarProcessing -Identity testroom -AddOrganizerToSubject $true -DeleteComments $false -DeleteSubject $false<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>You may notice that meetings with a &#8216;Room&#8217; mailbox will by default only show a &#8220;Busy&#8221; status. Many, including the organisation I work for, wish to have (at the very minimum) the following displayed in the Room&#8217;s calendar: Organiser of the meeting, and The subject of the meeting Below I will demonstrate how to set [&hellip;]<\/p>\n","protected":false},"author":32,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"categories":[1],"tags":[47,37,42,48],"class_list":["post-326","post","type-post","status-publish","format-standard","hentry","category-tech","tag-administration","tag-office-365","tag-powershell","tag-room-mailbox"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p1trTO-5g","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts\/326","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/comments?post=326"}],"version-history":[{"count":4,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts\/326\/revisions"}],"predecessor-version":[{"id":2493,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts\/326\/revisions\/2493"}],"wp:attachment":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/media?parent=326"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/categories?post=326"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/tags?post=326"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}