I’ve been meaning to write a blog post about an interesting challenge I faced a few months ago while doing a hardware refresh for a client with their Exchange 2007 environment. They had one hub
I’ve been working on a project for a client with Exchange 2007 Unified Messaging for the past 2 days as they prepare for two remote office deployments next week. Other than getting the NET VX1200
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
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
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
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
Unfortunately, the policy applied to my computer is set to overwrite logs which meant I wasn’t able to capture the local logs on my laptop in time to see what was written so the only
Ran into an interesting problem/discovery today while in the office when a colleague of mine was trying to assist someone in Montreal who had an issue. What he noticed was whenever he opened the registry
I ran into an interesting problem while performing a Nortel CS1000, NET VX1200 and OCS 2007 R2 integration for a client who are trying to have users slowly migrated to OCS. The problem happened when
We have an environment with a Windows Server 2008 R1 64-Bit SP2 server for a web application we host and during a recent maintenance window, one of the developers requested that we install .NET 3.5
