Login to Reply
Problems configuring the CRM Outlook client? Use the wizard!
FAQ About Technical SupportOnline | On-Premise
FAQ About Billing
Implementation Guide
Microsoft Dynamics CRM Developer Center and SDK
Over a year ago, the company I'm working for switched their CRM user domain from A\john.doe to B\john.doe
I'm attempting to import an existing CRM 4.0 organization utilizing the deployment manager on the CRM box.
The user mapping and AD updates are successful for most of the enabled users; however this process takes around 12-15 min per user which is killing me since it runs for 8 hrs before it fails. Here is an example of the log (I took out the actual user names)
17:46:46|Verbose| Update Active Directory properties for entry {0}|
17:46:46|Verbose| Populate with user
17:46:46|Verbose| Updating membership
17:46:46|Verbose| Old account {0}| A\john.doe
17:46:46|Verbose| Adding new account {0}| B\john.doe
17:46:46|Verbose| Found dn {0}| CN=John Doe,OU=Migrate,OU=GalSync,OU=a,DC=ad,DC=b,DC=com
17:46:46|Verbose| Update completed
17:46:46|Verbose| User added successfully to the OU groups in Active Directory
It does this for every user until ultimately failing due to a time out issue. Does anyone know a workaround on this? I've tried updating the Reg Key, imported using existing mappings, tried to manually map the users...and still get a sql time out issue
Any help would be greatly appreciated
Mike
There is a reg key setting called OptimizeOrgImport that you can apply:
support.microsoft.com/.../977867
And also an update rollup for CRM 4.0 that addresses the long lookups for ad records. You didn't mention what update rollup you're using, but try to use the most current UR and do this again. Some folks mention setting the SQL Timeouts may help, but I don't think it directly addresses the issue; these reg keys are SQL Timeout and OLEDBTimeout
I think that's expected, and that's what you have to do - create an AD account to map those users to. There is no workaround for that.
However, you can use a user mapping file - it's pretty easy to create - especially if you have that number of users. I've had to create one before for 300,000 users and it works fine, but don't expect it to perform any better.
Don't forget to mark the answer to the post!
"CRM 4.0 organization utilizing the deployment manager on the Sql box."
I meant to say utilized the deployment manager on the CRM box, sorry for the confusion.
Thanks Michael,
I attempted the reg key setting and changed the value to 1 as suggested. I did 2 processes
1) I chose automatically map users and the import ran much quicker. This however caused it to blow up on users who were not mapped (did this one by one)
2) I had to then choose manually map users and set a mapping of the user in question to a test user account I created...this in fact worked, however you cannot map multiple users to the same account.
Do you know if there is a work around this? Or would I have to manually map the failed users to custom test accounts I have to create? This could take a very long time since we are talking about hundreds of users with no mappings. It would be great if I could map multiple users to 1 custom test account.
Any further suggestions would be great