![]() ![]() By no means do I completely understand why Microsoft chose to use the relationships I am about to describe, and some of what I have witnessed defies explanation. Most of this I have pieced together through experience and reading a handful of blog posts. In these cases, it is not uncommon for a salesperson to “return home.” The IT staff will need to create a new user account if the old one was deleted.Īnother scenario I have come across is when an Active Directory account needs to be deleted and recreated and a CRM user was already added using the first account. Companies in competitive vertical markets often swap employees, particularly sales representatives. If the employee never returned this would not be an issue. The appropriate CRM recommendation is disabling the user. Active Directory user accounts can be deleted. In a perfect world, all instances of the user should be deleted. An IT department may choose to delete user accounts when a person leaves the company. ![]() The precipitating event is deleting an Active Directory account of a CRM user, whether the user is enabled or disabled. There are several scenarios that can create this mess. Potential Hazards of Deleting an Active Directory Account Corrupted CRM user and Active Directory connections are one of these things that, in my opinion, becomes ridiculously complicated to deal with. Enter the user’s domain name, email address, populate a few other fields and the new user is ready to go.Īs with many automated processes, we generally are ignorant about what goes on behind the scenes until something goes wrong. Setting up a user in CRM is quick and simple. One of them is the ability to use existing Active Directory accounts for single sign-on. There are many advantages to Dynamics CRM on-premise. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |