Tue Mar 09 16:29:51.273 CCMLAB,TEST PH,4569,TESTPH4569
I can import existing AD accounts via the SA just fine; I can create new subscribers via CSV just fine, but I cannot import existing subscribers whatsoever. I've run SysCheck and all my permissions are fine...am I missing something obvious here?
This is on a test lab, and we are performing a new install (wiping out 3.1.5 and doing a fresh install of 4.0(3)) with 600+ existing AD/Exchange users next week...this is not something I want to run into on the production box.
Which was very helpful - the DTMF access ID's that CUBI said were duplicates were listed in the SQL table, and when I used CUDLE, it did say they were global subscribers.
I also noticed that before I wiped out the previous Unity box, I did not delete the Unity Locations folder in AD (it said in the Uninstall Unity instructions that it was optional). I was poking around in Global Subscriber Manager and saw that all of the users that were not listed as subscribers on the Unity box were listed under the "Default (Primary)" listing of GSM. So, I went in, deleted the old Locations file, and imported the subscribers I was having problems with manually.
Still, odd. If anyone can shed some light on this, I'd appreciate it.
Re: Cannot Bulk Import Existing AD/Exchange Mailboxes into 4.0(3
Removing the Locations folder is optional, but removing the location objects in that folder is not - the dialog at the end of Uninstall lists a few objects you need to be sure to delete and that's one of the. The new uninstall I posted today actually deletes it for you in 4.0(2) installs and later to avoid this type of thing.
If you had done an uninstall of your previous system it shouldn't have behaved like you describe unless you did the "skip doh removal" stuff - I see this most often with sites that do a "yank and install" reinstall - the existing subscribers are still "Stamped" as Unity users and they are set to reference the primary location object (i.e. one of the objects in that locations folder). When you install the new Unity server the directory monitor finds all these users and locations in the directory and pulls them into the global tables - it assumes there is another Unity server installed it needs to know about. If you'd had them in a dialing domain (i.e. you configured a dialing domain name on the primary location object in the directory) it'll assume these are users that we can't have conflicting IDs for - hence the conflicts reported by CUBI.
However, you probably didn't have a dialing domain setup so I'm not sure if that's what was happening or not - it could be that the CUBI application is being too aggressive when checking for duplicates (i.e. not restricting itself to members of the dialing domain) - I'm not sure, I'd have to look at the system.
But regardless, that's why the IDs were in that table - the users were still stamped as subscribers in the directory - if you'd done a full uninstall they would have been cleaned of those properties and that wouldn't happen.
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: email@example.com 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 ...