Hi all,<br><br>I recently built a Unity server for my @7k user WAN. I noticed that it created a subcontainer in my GAL's Recipients container called DistributionLists. This container currently contains only the Unity specific Unaddressed Messages, Unaddressed Faxes, System Event Messages and All Subscribers DLs.<br><br>This wouldn't be a problem, expect that my enterprise already has another container already named Distribution Lists (no space) in the GAL and I don't want my users to get confused. We usually put all DLs in that container. <br><br>Question: Do I NEED this new container as is? Can I rename it? Delete it? Hide it? What are the reprecussions?<br><br>Thanks in advance!<br><br>Myke<br><br>
First, as Im sure you know you cant move any object out of a container joys of a hard coded distinguished name in the Exchange directory. You have to delete them and recreate them in another container you dont want to do that here because there are references to these DLs in a few spots in the registry. You can root through and change them if you really want, but I wouldnt recommend it.
Yes, you can hide the DLs no problem just like you can hide subscribers so they wont show up in the address book. If this is a new install of 2.4.6 102 or later (which it sounds like it is) you should be cool. If its an upgrade you may need to check to see if the registry is properly configured to support hidden users and/or distribution lists (theyre set separately). Heres a link that covers that:
yes, you can rename their display name no problem we reference them by their distinguished name and their alias.
You can change which container Unity will use to create all new DLs added via the SA if youd like. In the registry under HKLM\Software\Active Voice\DalEX\1.0\DistributionLists youll see two keys of interest. One is called root which indicates which directory we start in dont mess with this unless you have to. By default this is the recipients container under the site. Then youll see a NewObjects key which dictates which container we create new DLs in. You can change this to any container under the root container. This wont, of course, help you with the three default DLs we add.
If those three DLs are really sticking in your craw, I can pull out all the places theyre referenced and you can change the NewObjects key, delete them from the container we make, create them again in the desired container and then update the registry to point to them. Id steer clear unless its a real crisis, though
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...