kgorczewski has a good point and the safest approach.
However in a big environment recovering AD accounts is a regular thing which is my case. In practical terms you can't import a database every time you need to recover an account that may have been deleted, you could but wouldn't be practical this only applies
to accounts that have been deleted and were disabled in CRM and you need to enable them in CRM the below process wouldn't work in this case if the account is enabled the below process is enough in most cases.
You just need to recover one sys admin account, and after this you can recover all the others using CRM itself by:
- opening their user profile in CRM
- change the username to a dummy account and revert it back to the original user account this will update the SID's
but you can only do this as sys admin so you need to recover one account. Also to make sure the account you recover is not out-of-sync or in some weird state (which is not) you may just want to the same above process to the account you recovered with the
database direct SQL update using the other sys admin accounts just recovered via CRM.
Visit my blog for CRM material, improving performance, kerberos, IFD, development tips, etc. :) http://quantusdynamics.blogspot.com
