Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
it looks like I made a bit of a mess up in my production environment. While attempting to deploy another product which requires an AD schema edit (Live communication server 2005), that failed and I’d like to start over with a different version of LCS namely 2007, however that won’t let me install it because of the failed schema update from 2005. So, in an attempt to learn from my mistakes I just want to start with a clean forest, with a clean AD schema and back up before I make any changes. The only problem is, I want to take my CRM database and all of the customizations and such with me. The problem with all of this is that by creating a whole new AD structure, the old CRM database and related files will not work as they need the specific groups set up with the specific SIDs prior to the recovery. The question is: 1) is it possible to recover CRM from a broken AD environment to a fresh AD? 2) If so, what are the steps needed to do this?
it is important to recognize that I am running CRM version 4.0 with no updates. The reason for no updates is that I couldn’t find the updates.
As you probably have reasons for using such "ancient" technologies like CRM 4.0 and LCS I'm just gonna go straight to the point.
1. Install a new instance of CRM 4.0 to the same "Rollup" level as your current content db is running now within your new clean AD/forest.
I assume your setting up a new SQL with the same version/update level.
2. Inactivate the Organization in the old installation via Deployment Manager.
3. Make a backup of your <Org>_MSCRM content db and restore it to the new SQL instance in the new AD.
4. Perform an Import from Deployment Manager on the new CRM 4.0 installation.
If you haven't missed any customizations(.dll) from your old installation it should now be setup and working in your new domain.
Thank you for the response, I am truly appreciative of your understanding in the situation. I am going to try exactly what you said and once everything turns out, that should do the trick. I would sure love to get my hands on the update roll ups for CRM… However, they just don’t exist anymore.
And yes, there are quite a few medical reasons why I’m still using what by today’s standards is ancient technology. The first reason, is that I don’t do change very well thanks to autism and other medical conditions, the next reason is that because all of my appointments are scheduled through CRM including critical medical appointments… I really don’t like to change or risk anything when it comes to health information.
Should there be any problems, I will follow up. But if all goes well, I shall mark your solution as the answer.
Edit: I still run xp, server 03, and win7 in VMs on my windows 8/8.1 laptops and still use "modern" conveniences like an iPhone 12s (more than one), AirPods Pro, (Apple Watch),, google pixel 4a, verizon, Samsung Galaxy, MacOS, iPad Pro 12.9 inch tablet, and many others too numerous to name here.. so I'm not totally in the stone age. However due to my absolute reliance on this "ancient" technologies for medical reasons; the only role windows 8/8.1 really plays is as a "launcher" of sorts for VMware workstation 14, office 2003 or 2007 apps, FileMaker Pro 12, and a web browser (and occasionally the odd "modern" program that refuses to run in my rats nest of VMs such as Sims 3.)... and from the road I just take my laptop with me or remote into it via TeamViewer or whatever thus I can have an always-familiar desktop environment that doesn't cause an absolute meltdown...
Further Ive given colleagues, support staff, and even my fiancee remote access to this strange ensemble of VMs to get their work done in managing me... so yes, a lot truly is riding on what most would call an "oddity" or "just a lab" for me these old systems rarely if ever let me down, will never change, and support my entire world.
and before I get the security guy in the back... no, I don't do online banking from this odd mess (remote into the laptop from where ever (doctors office, the train, a clients office, etc.), then RDP from the laptop into an windows 2003 terminal server to get access to my mission critical apps (internal exchange, IM, CRM, etc.) and all the VMs are backed up regularly and passwords changed frequently through AD policy... so it's not "I'll never get hacked..." but rather "it's enough to keep the casual internet troll, or punk script kiddie out; any determined attacker can get physical access to the laptop, try hard enough/long enough, etc. so backup and backup some more"
Just wanted to post a quick update here and say that I’ve restored the database onto the new SQL server, had a bit of trouble getting reporting services and a few other things going. As of the time of this writing, I am installing CRM on the new server and plan to do the import. If all goes according to my plans, we should be able to have CRM back up and running.
The only thing that concerns me, is the users in the old CRM system have different SIDs then the users in the new system. As to say that the new active directory is going to have different security IDs for the user objects and what not than the old active directory environment. And for most things, the security identifiers are what is used on the backend to identify a specific user. again, I may be reading more into this than necessary, but just a thought that came up while I’m waiting for paint to dry. And as we all know, deleting users from CRM is near impossible from the web interface, and as a result there of I’m wondering how that would fly?
But, if all goes according to plan (knock on wood… ) Things will be off and running.
Thank you all for the help! This did the trick, and my production CRM database is back online. You are awesome.
I'm glad to hear that! It's one of the few CRM 4.0 environments still standing strong then and you're not the only one left as I personally know one more still running in production.
Have a nice weekend!
Business Applications communities