our customizations in the on-line version were wiped out in last thursday upgrade and we found out that MS does not backup up our config files. - can anyone get me information about how to backup up properly the on-line version of CRM hosted by MS so that we do not lose all our systems each time they upgrade the software?
There shouldn't be anything that the ops team does that should wipeout your ISV.Config changes. I fear that real issue may be someone in your org accidently importing a bad version of this file and wiping it out. most likely someone had a working "copy" that didnt include the ISV.Config changes and then did a full export/import to your online instance.
As for backing up your customizations, there are a few things you can do there. Probably the easiest thoguh woul dbe to periodically export all your customizations and store the resulting file somewhere. You would probably want to include the date int ehfilename so you can keep multiple versions. Then, in a sistuation like this, you could always load one of those files and import just the isv.config.Matt, MVP - Dynamics CRM
Hi Ed, can you please provide a little more context of what you mean by the customizations being wiped out? Were these published customizations or unpublished customizations? Also, did the CRM Online support team give you an answer that MS does not back up config files?
Thanks, ManishaManisha
Proposed as answer byJim Glass JrMonday, March 16, 2009 4:51 PM
Yes the answer came from MS support about not backing up our data or configs -
These were custom programs that are called from menu bar.
our menu items were replaced with "ISV" "test" " Web" and "both" - when you click on them all you get is a pop up "test " button. We can still get to our custom applications if you happen to know all the URLs and parameters to pass along (which were being pulled out of the crm system based on who you are). We are rewriting our ISV file to try and recover but we need to be able to protect ourselves from MS in the future.
There shouldn't be anything that the ops team does that should wipeout your ISV.Config changes. I fear that real issue may be someone in your org accidently importing a bad version of this file and wiping it out. most likely someone had a working "copy" that didnt include the ISV.Config changes and then did a full export/import to your online instance.
As for backing up your customizations, there are a few things you can do there. Probably the easiest thoguh woul dbe to periodically export all your customizations and store the resulting file somewhere. You would probably want to include the date int ehfilename so you can keep multiple versions. Then, in a sistuation like this, you could always load one of those files and import just the isv.config.Matt, MVP - Dynamics CRM
I appreciate the suggestions - we will need to do a bunch of stuff to get a comfort level again. In terms of the ISV.config file being changed. It was discovered after the system was down for the upgrade when we went in and validated that everything was still working. I'm sure it was possible that someone in my organization risked their job by violating change control procedures but the timing to the upgrade seemed pretty consistent. Only two individuals have those rights. Wouldn't the log files in the application indicate when the file was changed? Any idea how we could gain access to the audit logs?
Hi Ed, I talked to the CRM Online Operations and they said they were on top of your support request and probably have that fixed?Thanks,
Manisha Powar [MSFT]
