Certifications
Categories
RSS
Tuesday, March 23. 2010
Help! My Outlook 2010/Exchange 2010 calendar is on auto-pilot. It rejects and accepts meetings without asking me!
Exchange 2010 introduces a Calendar Assistant, which can be handy for automatically marking incoming meeting requests a tentative, and other very handy functions that can execute out side of the client side experience.
In this one particular scenario, embarrassingly, was my own mailbox for a few days.
I had no control over meeting requests. They were getting rejected and accepted without me ever seeing the request come in.
I checked my phone for any strange settings.
I checked over the Calendar Assistant and disabled it completely, from the Outlook Web App control panel and in Powershell just to make sure it was "super disabled".
Calendar items kept auto-answering for me so I had to dig deeper, into a section I rarely go into unless the mailbox is setup as a resource.
Lo and behold, somehow and at some point, all of these items had been clicked on within my Outlook profile.
I don't know if I did this on accident one night or my kids got into my Outlook settings (never underestimate the comedy gold that can come from smart 8 year olds) with that said:
As you can see, these options were what was killing my Calendaring. Very "stupid user" to not check this spot first but it was originally acting like something the Calendar Assistant was doing and I had forgotten about the resource room settings being buried in Outlook 2010.
So, I got to wear the dunce hat for the day. Maybe me posting this will avoid some other dunce hats getting passed out to others. It was definitely a 'palmface-slap' moment when I discovered the root cause.
In this one particular scenario, embarrassingly, was my own mailbox for a few days.
I had no control over meeting requests. They were getting rejected and accepted without me ever seeing the request come in.
I checked my phone for any strange settings.
I checked over the Calendar Assistant and disabled it completely, from the Outlook Web App control panel and in Powershell just to make sure it was "super disabled".
Calendar items kept auto-answering for me so I had to dig deeper, into a section I rarely go into unless the mailbox is setup as a resource.
Lo and behold, somehow and at some point, all of these items had been clicked on within my Outlook profile.
I don't know if I did this on accident one night or my kids got into my Outlook settings (never underestimate the comedy gold that can come from smart 8 year olds) with that said:
As you can see, these options were what was killing my Calendaring. Very "stupid user" to not check this spot first but it was originally acting like something the Calendar Assistant was doing and I had forgotten about the resource room settings being buried in Outlook 2010.
So, I got to wear the dunce hat for the day. Maybe me posting this will avoid some other dunce hats getting passed out to others. It was definitely a 'palmface-slap' moment when I discovered the root cause.
Interesting VoiceCon announcements about OCS Wave 14 (CS 2010?)
Some new information about OCS "v.Next" came out today at VoiceCon. Unfortunately they are in press release form but I've distilled down some of the technical items.
#1. 3 new headsets/devices from Polycom, which will definitely help fill the gap for community area/kiosk phones and non-tethered scenarios. Read about it here.
Highlights from that announcement that I am excited about:
Polycom CX500 IP phone - designed for use in public areas such as lobbies, break rooms or hallways (No PC required!)
Polycom CX600 IP desktop phone - delivers rich presence and exceptional voice quality to a mid-range desktop phone ("Tanjay"-lite, sort of)
Polycom CX3000 IP conference phone -- provides outstanding voice quality and rich presence for more productive and efficient conference calls and is the only conference phone currently optimized for Microsoft Communicator "14" ("RoundTable"-lite, sort of)
The CX500 fills a gap I've experienced with OCS rollouts that required a common area phone without a PC attached to it. It could be a break room or conference room or security phone. Having a computer with a headset or full blown "Tanjay" phone didn't make sense in those scenarios.
I'd gladly review any of those phones if Polycom wants to send me a demo unit.
#2. Better branch survivability with the updated gateways, plus more. Read about it here.
Highlights from that announcement that I am excited about:
More partners joining the market making OCS products and solutions. Of particular note are the survivable branch appliances, which will definitely help remote office and branch office deployment scenarios greatly.
E911 service support - this can be a deal breaker under certain scenarios in the USA, so I'm happy to see support for this added. The way it ties into OCS is also very straightforward and clever.
Contact center, call accounting, and recording solutions - These 3 items have always been a weakness to the OCS voice platform. The products either didn't exist or they were in the early stages of production. It is great to see some more options and features for those companies that require these solutions for a full deployment.
As soon as I am able to, I will be posting plenty of OCS v.Next items - this is just the beginning!
I haven't been this excited about a new release of a Microsoft product in a long time and I have a feeling it is going to surprise a lot of people with the new capabilities!
#1. 3 new headsets/devices from Polycom, which will definitely help fill the gap for community area/kiosk phones and non-tethered scenarios. Read about it here.
Highlights from that announcement that I am excited about:
Polycom CX500 IP phone - designed for use in public areas such as lobbies, break rooms or hallways (No PC required!)
Polycom CX600 IP desktop phone - delivers rich presence and exceptional voice quality to a mid-range desktop phone ("Tanjay"-lite, sort of)
Polycom CX3000 IP conference phone -- provides outstanding voice quality and rich presence for more productive and efficient conference calls and is the only conference phone currently optimized for Microsoft Communicator "14" ("RoundTable"-lite, sort of)
The CX500 fills a gap I've experienced with OCS rollouts that required a common area phone without a PC attached to it. It could be a break room or conference room or security phone. Having a computer with a headset or full blown "Tanjay" phone didn't make sense in those scenarios.
I'd gladly review any of those phones if Polycom wants to send me a demo unit.
#2. Better branch survivability with the updated gateways, plus more. Read about it here.
Highlights from that announcement that I am excited about:
More partners joining the market making OCS products and solutions. Of particular note are the survivable branch appliances, which will definitely help remote office and branch office deployment scenarios greatly.
E911 service support - this can be a deal breaker under certain scenarios in the USA, so I'm happy to see support for this added. The way it ties into OCS is also very straightforward and clever.
Contact center, call accounting, and recording solutions - These 3 items have always been a weakness to the OCS voice platform. The products either didn't exist or they were in the early stages of production. It is great to see some more options and features for those companies that require these solutions for a full deployment.
As soon as I am able to, I will be posting plenty of OCS v.Next items - this is just the beginning!
I haven't been this excited about a new release of a Microsoft product in a long time and I have a feeling it is going to surprise a lot of people with the new capabilities!
Search this blog
Links
My e-mail address
Exchange:
Hotfix Tracker (All products)
OCS:
OCS 2007 R2 Documentation Collection
Office:
Office Cumulative Updates Site
Windows:
Other:
