I am running SCOM 2012 RTM and noticed that after my RMS box is rebooted druing its regular schedule the "System Center Management Configuration service" will not start. I have to go to services open the Log On tab and set the password every time after reboot. My guess is SCOM is changing the credentials. I have looked under "Run As Accounts" and can't seem to find where this setting may be. I am running both System Center Management Configuration service and Data Access Service under a domain account (same account for both). Once the password is set the service starts up fine until I reboot again a week later! This is quite annoying!! I am also running into the same problem with my Data Warehouse server running reporting services - that one is also running under a domain account but a different one. Does anyone know how to fix this issue??

pls check whether configuration service account, data access service account and reporting service account password never expired option is enable or not. By default, windows AD domain default policy has password expire policy. You should enable password never expire option for service account. Roger

pls check whether configuration service account, data access service account and reporting service account password never expired option is enable or not. By default, windows AD domain default policy has password expire policy. You should enable password never expire option for service account. Roger

Thank you for the reply. The account is not an issue here. I am not actually changing the password in AD, I am simply entering the same password into the service log on credentials. I did check the accounts per your suggestion and they are non expiring. I think SCOM is changing the credentials somehow...

Thank you for the reply. The account is not an issue here. I am not actually changing the password in AD, I am simply entering the same password into the service log on credentials. I did check the accounts per your suggestion and they are non expiring. I think SCOM is changing the credentials somehow...

Found the issue. Our Group policy was restricting which accounts can run as a service. Added the service IDs to GP and problem was resolved.

Found the issue. Our Group policy was restricting which accounts can run as a service. Added the service IDs to GP and problem was resolved.