I’m not exactly sure why I haven’t encountered this problem as often as I have during the past deployments I’ve been involved in but I finally did earlier this month when one of our clients opened up a ticket to have this issue resolved. Problem
I received a escalated UM related ticket passed on to me this week because the colleague who was looking at the issue wasn’t a UM expert and while I was able to identify the issue immediately, I thought it’s worthwhile to write a post about
Due to the various OCS and Exchange UM services we had to change for client, a significant amount of changes were also required to their public certificates. I had to go through the exercise of using Go Daddy’s tools to regenerate an existing certificate to
It’s been awhile since I’ve done an OCS 2007 R2 deployment with the Tanjay / CX700 phones and to kick off the new 2011 year, we had a client who were previously using USB phones procured 10 Tanjays for boardrooms and select executives. What ended
We’ve finally completed a company wide migration from a Nortel BCM PBX to OCS 2007 R2 with Exchange UM as their auto attendant and voicemail solution just before the holidays and with migration of all the users to their new telephony solution comes a problem
I came across an error message today while enabling users for Exchange UM that I thought was worth writing a post about because the message tip didn’t seem to clearly communicate the problem (at least not to me). Problem You’ve been using the Enable-UMMailbox cmdlet
As easy as it is to assign an EUM attribute to a user who is not enabled for Unified Messaging through the Management Console GUI, this method isn’t too practical when you have to enable more than 50 people. So while going through a folder
For those who have implemented Exchange 2007/2010 Unified Messaging voicemail to operate with OCS 2007 and other phone systems (i.e. Cisco or Nortel), you may know that in order for the auto attendant to be able to look up users who do not have a
The client I’ve been working with recently piloted the following phones: Snom 300 – http://www.snom.com/en/products/ip-phones/snom-300/ Polycom SoundPoint IP 335 – http://www.polycom.com/products/voice/desktop_solutions/soundpoint/desk_phones/soundpoint_ip335.html The client’s feedback on the Snom 300 phone was that they did not like the form factor at all as they were used to
I’m not sure if it’s just me but I find the GUI to customize the business hours schedule from within Exchange 2007 and 2010 somewhat cumbersome to work with. This is especially the case when I’m working on projects for clients which are remote and
