We'll first need to know what version of Unity and what mail store is Unity connected to. If the system were connected to E2K, option one is pretty safe as long as you are at 3.1.3 or higher. With E2K, Unity operates with objects like containers, distribiution lists and subscribers as GUIDs and GUIDs won't change even if the name changes.
It sounds like this system is E55, and unfortunately, Unity doesn't get to operate on E55 directory objects as GUIDs.
Let us know what version of Unity and what mail store Unity is connected to. If it is E55, I think the best thing to do is have TAC assist in making the configuration changes.
Renaming the container that contains the distribution lists in E2K is fine to do (as long as you are at least 3.1.3). Renaming the distribution list names themselves could be problematic. The Notifier references the PDL to send NDRs to by name in the registry (under the Notifier hive). There is a chance that other Unity components also reference the system PDLs by name. If there is a site that wants to change the name of Unity system PDLs, I'd think I'd ping TAC first.
I wouldn't do that for the Unaddressed messages DL since this is referenced internally by it's name - this is an important DL since it's where all the messages from outside callers that Unity can't deliver for whatever reason go to... if this link is broken you can risk losing messages which is not a good thing.
You can always hide the DLs in the address book if they're causing a customer stress... I'd strongly reccomend taking that route with the Unaddressed Messages DL.
The DISPLAY name is fine... you can change that to whatever you want... it's the mail alias that you need to leave alone - this is what's referenced in the registry by the process that cleans out the Unity Messaging System account's box (the guy that forwards messages to the Unaddressed Messages DL as necessary). As long as you just fiddle with the display name, this is not a problem.
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...