I came across an Exchange 2007 server with CAS, Hub Transport and Exchange UM roles installed that consistently had event ID: 2501, 2604, 2601 from source MSExchange ADAccess logged every 14 to 16 minutes. The events are as follows: Error: Event ID 2501 Process MSEXCHANGEADTOPOLOGY
This was one of the problems I’ve come across a few years back when I did my first Exchange 2007 Unified Messaging deployment and since I’m currently on a Exchange UM project, I thought I would take this opportunity to mimic the error: The format
I seem to come across this 4 or 5 times each year during my Exchange UM deployments and I find that I always forget the answer having to look into my old notes so I figure I should take the time to write a post
I’m not sure if this is a but or not but I ran into an minor annoyance today while configuring auto attendants within Exchange Server 2010 RTM (Version 14.0 – Build 639.21). The AA’s aren’t going to be live just yet so I created around
The following is a perfect example of the smallest misconfiguration on my part in something seemingly so trivial can cause calls to fail. I’d have to say that what tipped me off was a problem I had before with another integration which I wrote a
I’m sure a lot of Exchange UM professionals out there already know this but in case the person reading this doesn’t: Ever wonder where Exchange 2007 pulls the Extension Configuration value when you’re enabling someone for Exchange Unified Messaging? The screen I’m referring to is
I believe most Exchange professionals out there already know about the way of testing Exchange 2007 or 2010’s hub transport server’s delivery by simply creating an email file and dropping it into the C:Program FilesMicrosoftExchange ServerTransportRolesPickup folder for delivery but there was this one day
This problem is similar to the problem in my previous blog post: Transferring calls from Exchange UM AA or OCS to PBX – Gateway Passed # Matters found here: https://blog.terenceluk.com/2010/08/transferring-calls-from-exchange-um-aa.html Problem – External user calls in via PSTN with a blocked number Call Flow External
Here’s another interesting problem I came across awhile ago. During New Orleans TechEd and CS 14 training, I actually asked the Microsoft representatives about manipulating SIP addresses and REFER fields and got different answers. From New Orleans, they said that there’s more control and might
I ran into an interesting issue while integrating Exchange Unified Messaging’s Auto Attendant with OCS and PBX. After setting up everyone who was still living on the BCM’s EUM attribute to include the following string: xxx;phone-context=LocationProfile.domain.com … I noticed that when I called into AA,
