To accomplish what you want is not really all that difficult but it is a manual (or scripted) process. Essentially, you will need to export your endusers from the CUCM to a text file. You can do this using the AXL/SOAP interface or you can leverage BAT export. I am guessing the latter would be more suited to your needs.
Then you will need to normalize the data that is exported to line up with a CSV format that can be used by an AD import tool or shell (i.e. powershell) script. At a minimum you will need the first name, last name, userID, telephone number. An e-mail alias may also be needed depending on what you are doing.
If you are unfamiliar with how to import records into AD, then I suggest you take a look at this:
http://technet.microsoft.com/en-us/library/bb727091.aspx
You will also want to consider your OU structure when start going down this road. I also recommend that you look at this as a stop gap measure. Your strategic objective should basically be to import/normalize the data for users in AD and CUCM. Once you do this, then you should transition CUCM to using DirSync. The eventual goal would be to have AD be the root for all user provisioning. If you can get there, then your CUCM and CUPS server will always be in-sync since they would both be leveraging your AD environment.
Now, I am assuming based on this thread that your AD environment doesn't already contain the user IDs that you are leveraging in the CUCM. This would only be the case if your AD is greenfield. If your users have user IDs in AD and they have CUCM IDs as well, then you will need to take some additional measures to match and normalize the data so that (a) you avoid unnecessary duplication and (b) you avoid overwriting or deleting a user ID that you may be using. You also may have extension and device associations in CUCM that you want to keep. The worse case is that you DO have users using both AD and CUCM and you want to change CUCM to use the AD user IDs. In this case you still need to export the users. Identify the CUCM-User_to_AD-User relationship, update your userIDs as stored in the CUCM export file. Then you can use this file either to create new CUCM users that match their AD equivalent IDs OR do a DirSync (which deletes the old CUCM-User) and then a bulk update to re-establish device associations. This can get quite involved and there are plenty of variables that come into play that I can't account for in this thread.
If you are comfortable with AD, BAT, DirSync, etc. then you should be able to accomplish what you need with proper planning. If you are not comfortable with these topics, then I recommend you consider finding someone who is to assist.
HTH.
Regards,
Bill
