RUS not working after 3.1.5 Unity Install, Exchange2K
It appears that after a 3.1.5 Unity installation in an Exchange 2000 environment that the Recipient Update Service has quit functioning properly. Mailboxes can be added in Exchange, but are not stamped by the RUS, and are not functional as a result. I am now being questioned about the AD schema extension that was performed at install, and what AD attributes Unity either creates or modifies, and what all of that has to do with the operation of the RUS. Anyone run into this before? Thanks in advance...Pat
Re: RUS not working after 3.1.5 Unity Install, Exchange2K
Thanks Jeff, I found the ldif log already...the whitepaper I had seen before, but hadn't thought to dig it up again. I will work with the customer to try to resolve from a Micro$oft perspective, I have found numerous TechNet articles pretty much outlining the same symptoms and suggested fixes. Most have to do with permissions issues in AD. Don't know if the customer has tried to rebuild the RUS yet, but I have found the list of permissions needed for proper RUS operation and will try to verify that first. Thanks for the response! Pat
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...