SCOM MP Config.xml is reverting back after changing. How to fix.

I have finally gotten the SCOM MP installed and running after fixing the DCOM issue which is referenced in the Orion documentation and not the MP Config doc. Events are rolling and we are needing to do changes to via the Orion Management Pack Configuration wizard (OMPCW) to remove/ add more devices for management.

We are running SCOM 2007 r2 on Server 2008. Orion is up to the latest rev, SW MP ver is 1.1

After the initial install I noticed that it places the config.xml file in a windows protected folder on c:\ProgramData. I ran the OMPCW to make the changes and it replaced the config.xml file as it should, but within a minute the old file came back. I verified by reading the config.xml. After some research I found that Windows protects the files in this folder and any changes to the files in this folder are automatically replaced with the original.

To validate even further:

- I uninstalled the MP from the SCOM Server, It left the folder and all the files in the ProgramData folder after the uninstall. So I made a copy and deleted the contents of the Orion Management Pack for OpsManager 2007 folder. I then waited several minutes to see if file protection would replace them and it did not.

- Reinstalled the MP on SCOM and ran through the OMPCW which only placed files in the ProgramData folder after I finished the OMPCW. The config.xml was 1161KB.

- I went into the SCOM MC and nothing was there – after several minutes still nothing.

- I restarted the Orion MP Service ( after closing the SCOM MC) and went back into the SCOM MC and all the devices I specified in the OMPCW we starting to roll in. Good everything was working and except that I now need to go back and make a change in the OMPCW.

- I launched the OMPCW and unselected several devices and noticed that when the wizard finished the new config.xml file ( 1162 KB) was there. About a minute later Windows replaced the file with the 1161 KB config.xml file.

- As a test I deleted the config.xml file from the C:\ProgramData\SolarWinds\Orion Management Pack for OpsManager 2007 folder and a minute later it was automatically back ( 1161 KB).

So it seems the only way to change the config is to uninistall and reinstall the MP on Server 2008 because of the way Windows Resource Protection works on server 2008.

http://msdn.microsoft.com/en-us/library/aa382503(VS.85).aspx

Any way to fix?

Find more posts tagged with

scom_2007_mp

Accepted answers

moorebj

Found a fix thanks to support - but a few things need to go in the configuration guide.

- Stop the Orion MP Service prior to running the OMPCW - this will keep windows file protection from reverting the config.xml - your milage may vary as I am running server 2008.

- Yout can edit the Config.xml file directly as it will pull in all configured node into the file. Here is an example line. Where it says false change to true also make sure the service is stopped. I have not tried this on server 2008 so I am not sure what WFP will do.

- I deleted a ton of devices out of Solarwinds because I am switching all servers from SW to SCOM. After three days the servers I have deleted from SW are still showing up in the config.xml file I was thinking the Orion Database Changes in the OMPCW would control this ( I set mine for 4 hours because I was making changes). So I ran the OMPCW as above and the configurationwizard.log shows the following

2010-04-19 09:22:31,407 [1] INFO DatabaseDifferential - Removed node: DC01 (6) . - This is great but I was expecting this to be automatic.

I need more detail on what Orion Database Changes actually does.

- Log files for the MP are located here C:\Users\Public\Documents\SolarWinds\Orion Management Pack for OpsManager 2007.

- DCOM rights are mentioned in the ORION configuration guide about System Center but are not mentioned in the MP Configuration Doc.

- Best practice is to Run the OMPCW as administrator. Right click and use Run as administrator at least on Server 2008.

All comments

moorebj

BTW, I forgot to mention.

I ran through the install on the SCOM 2007 Server as an admin and also ran the OMPCW as an administratior

moorebj

More troubleshooting and maybe a workaround.

-I Ran OMPCW by run as administrator and made changes which showed a changed in the size of the config.xml file. A minute later it changed back to the old file.

- Tried the above again - BUT immediately after the OMPCW finished and before windows could replace config.xml I restarted the Orion MP Service (in windows services) and the file did not get replaced and the changes are staying.

So looks like a process needs to be put in place to recycle the service after running OMPCW as this fixes two issues.

moorebj

Found a fix thanks to support - but a few things need to go in the configuration guide.

- Stop the Orion MP Service prior to running the OMPCW - this will keep windows file protection from reverting the config.xml - your milage may vary as I am running server 2008.

2010-04-19 09:22:31,407 [1] INFO DatabaseDifferential - Removed node: DC01 (6) . - This is great but I was expecting this to be automatic.

I need more detail on what Orion Database Changes actually does.

- Log files for the MP are located here C:\Users\Public\Documents\SolarWinds\Orion Management Pack for OpsManager 2007.

- DCOM rights are mentioned in the ORION configuration guide about System Center but are not mentioned in the MP Configuration Doc.

- Best practice is to Run the OMPCW as administrator. Right click and use Run as administrator at least on Server 2008.

MarieB

Hi bj--

Thanks for posting the information!