SCSM SP1 CU2 Installation Error _StoreActionsAccount
As I was installing CU2 lately on a SCSM management server of one of our customers I experienced a strange error. Since I did not find much about this error on the internet I wanted to share the error and solution in case anyone else came across the problem. I was able to successfully update the Data Warehouse management and Self-Service portal servers, without any issues. However, on the primary management server the update failed and provided the following error.
After some troubleshooting I realized that the System Center Management service was stopped for some reasons and could not be started. Instead it provided the following error message:
The System Event Log showed the following error
After I compared some Registry Keys with a running SCSM installation I recognized that there were some missing on my system. Namely the Registry Key for the Management Group was missing. I imported the key form a running system and changed the name of the key to the name of the Management Group and also the Management Group ID.
Both, name and ID can be found by querying the SCSM database. Just select top 1000 rows from dbo.MOManagementGroup table to get management group name, id and also SCSM admin group of your SCSM installation.
**EDIT: **Importing the registry keys from another system may not be enough to get the System Center Management Service up and running properly. I was told by a Microsoft Support Professional that the WindowsAccountLockDownSD entry, which is located in the specific management group key, contains binary data which varies from system to system. **Do not override this key if it already exists. **If it doesn’t and you import it from another system you may end up by getting the following error in event log:
The Management Group failed to start. The error message is The environment is incorrect.(0x8007000A). A previous message with more detail may have been logged.
My Registry entry now looked basically like the following
Unfortunately importing the Registry entry for the Management Group was not enough because after another restart of the System Center Management service I got the following message in Operations Manager Event Log followed by an error that no Management Group could be started.
I remembered another Registry Key called Approved AD Management Groups which I’ve seen when I was exporting the previous one. After checking on my other SCSM installation I recognized that there exists the same key but the value EnableADIntegration is set to 1 instead of 0.
This finally did the trick. After setting EnableADIntegration to 1 I was able to successfully start the System Center Management service and to install Service Manager 2012 SP1 CU2.