The error indicated above is most definitely a permissions issue, no doubt about it. Either the user was found in the directory and the services account you have configured does not have rights to update the object or the folder the user was attempted to be created in does not have rights. There are few other possibilities and none of them related to DiRT. DiRT simply preps the SQL database and then calls the SQLSyncSvr service to take care of the user sync. this is the same service used to import and create all objects in AD. So if you're getting that error, that account is having a problem with the object/location involved - or there's a conflict with object types somewhere in AD or the like.
Check the SQLSyncSvr log in the \commserver\logs\ folder and see if it gives you some clues - you'll see it searching for objects and finding them and/or not finding them and attempting a new create.
Try manually importing a user that failed for instance - or on your new install try creating a new user/DL in question via the SA (it will use the same service) and see if you also get an error. Invariably it turns out to be an issue importing users from a folder that was not included in the permissions wizard run or the like. I've see that many, many times...
The old unity server was once integrated to octel using unity bridge. Even though the bridge is no longer in use, the DiRT restore was trying to restore data that need the schema to be extended for unity bridge.
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...