Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I've set up CRM 4.0 and the install went off without a hitch following a bit of issue with .net framework 4 on the server. (solution uninstall and reinstall IIS, ASP.NET, etc.)
now that it's installed and i've created an organization through deployment manager we seem to be having issues connecting to it from a child domain
Org Display Name: WinxCRM 9.0
Org Name: WinxCRM90
Default Org: yes
server: xds-dc (10.255.255.254)
Parent AD Domain: WINX-CESD-US.LOCAL
Child AD Domain: CINGULAR-US.WINX-CESD-US.LOCAL
Password: <ActiveDirectory Password for Administrator Account>
Accessing CRM FROM: CINGULAR-DC (10.255.255.251)
Logged on to that DC (CINGULAR-DC) as: CINGULAR-US\Administrator
does anyone have an answer for this? I clearly have no idea what so ever
i had a possible thought...
if I take the following actions I can get into the CRM without issue:
1. Add CINGULAR-US.WINX-CESD-US\Administrator to the users in the WinxCRM 9.0 instance. Or,
2. login to CINGULAR-US.WINX-CESD-US.LOCAL as the administrator for WINX-CESD-US.LOCAL.
I'll be testing these theories in a few minutes
Update: when attempting to add a new user and entering cingular0us\administrator i get an error saying to reference the dynamics community or contact Microsoft support so simply adding the child domain users to the CRm instance is definitely out of the question
I officially have an answer for this. The solution came from Microsoft themselves. Here's what they had me do:
1. On the CRM server open the registry editor then navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM on the right hand side, find the DWORD value "AtuoGrouManagemet and switch it from 0 to 1
2. go to CRM and do Settings > Administration > Users > New > Multiple Users and follow the prompts
This fixed the problem
Business Applications communities