Featured Post

Three Basic Ways of Dealing with Double-Booked Resources in the Sumatra cmdlet

There are three basic ways of automatically dealing with double-booked resources in the Sumatra cmdlet suDoubleBookedMeetings. You guys wo...

Thursday, April 28, 2011

Progress on migrations to Google Calendar

We're kind of psyched because we've made the first real progress on Oracle Calendar / Meeting Maker / Zimbra full-state migration to (*shudder*) Google Calendar.
Check out this screenshot from our latest tech:

The important thing is the yellow highlighting. Yep -- we got attendees in with their responses.
Now we're working on the mappings and recurrences. So those of you out there stay tuned -- there is light at the end of the tunnel

Monday, April 04, 2011

Creating a Room in Office 365 Beta

Working in Office 365 Beta we found it very simple to set up users but a little confusing to set up a Conference Room. So we're documenting the process here. First create the room as though it were a regular old user, like so (you could do all this through PowerShell but I like the simplicity of the Office 365 Admin interface): Now use PowerShell to set up your session: $LiveCred = Get-Credential This will prompt you for your admin credentials on Office 365. Follow this with the next two commands: $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic –AllowRedirection and Import-PSSession $Session You are now ready to rock and roll by changing your “room” into a ROOM. This PowerShell command will now transform the ID into a Room. Set-Mailbox room222 –Type Room Check this by trying to add it in Outlook: And we’re certain that it is now behaving like a room! Since you’re here you might as well also configure the room as you wish. My preference for daily use (though for a calendar migration you’d want to turn OFF AutoAccept): Set-CalendarProcessing -AutomateProcessing:AutoAccept -DeleteSubject:$FALSE -AddOrganizerToSubject:$TRUE -AllowConflicts:$TRUE -EnforceSchedulingHorizon:$FALSE Wash, rinse, and repeat for any other resources you need. When done, be a good doobie and disconnect PowerShell from Office365: Remove-PSSession $Session