I have been trying to import a large number of users from an Active Directory 2003 environment and Exchange 2003 environment into the integrated Unity 4.0.5 system. In attempting to do this I have been using the Bulk Import Exchange tool in the Unity Toolbox. When I run the tool I receive an large number of errors about each subscriber account to be imported.
Record=0, Column=5, Fieldname=CN, Error=Invalid character(s) in string - please refer to the documentation to see which characters are allowable in this field (regex=([[:alnum:]]|\x26|_|'|\-|\.| |/)*).
I'm unable to import any of these users. I've confirmed in Active Directory that the Phone Number field does not contain the user's last name as shown in the error message. I'm unable to figure out where this extra information is coming from and why it is continually being appended to the records. It is my hope that I will not have to perform the bulk import via a CSV file or by adding them one at a time. Does anyone have any ideas on how to remediate this issue?
I ultimately opened a TAC case on this and the TAC engineer said the problem was that the Bulk Import tool was not configured to import users that are in a Last Name first format in Active Directory. The solution was to convert the entire directory to read First Name and then Last Name. So the comma in the import confused it but every effort I made to adapt the directory export to fit didn't work. I have to assume that this is due to the nature of the integration. If we were just importing a list of users then it probably wouldn't be an issue to just change the record ordering. I hope this helps.
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...