I have a new 4.02 server running in the site housing all the mailboxes now. I need to decommission the 2.4.6 server. I know how to remove its presence from Exchange, but do I need to do anything to remove its presence from Unity. Just to fill you in, this 2.4.6 server was a demo box that was doing UM, but we are taking it out now that 4.02 is in place so there is no Unity "network" going on here. Any help would be great, I want to try to leave Exchange clean when we get rid of this. This is Exchange 5.5 and NT 4.0 domain.
It's a little dusty but it works reasonably well - it'll remove the properties from users in the directory as well as removing most objects added to the directory - for shared items such as distribution lists and the like you may have to delete them yourself when it's done.
My only concern is that since the 4.02 server is in place and all the subscribers have been deleted from the 2.4.6 and all have had properties removed and reimported to the 4.02 server, will this tool remove anything from the directory that the 4.02 needs?
The goal is that I want to remove this 2.4.6 server and keep everything that is on the live 4.02 server in tact.
No, it wont kill anything not directly related to the local 2.4 installation - but if you're worried about it you can manually remove everything from the directory on your own - there's instructions for most of that in the help file for the uninstall tool itself. If you've already removed the properties from users all you really need to do is get rid of the the objects under the Unity folder other than the location objects - all the other items under there are not used in 3.x and later and can be deleted. That's the only other things in the Exchange directory that 2.x sticks in ther other than user properties and distribution lists.
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...