So, I was trying to clean up a few errors, and I changed one of my RunAs accounts (the Data Warehouse Action Account) to only be distributed to management servers, instead of just putting it on Less Secure. But the moment I did this, half the serves in the domain started throwing this error at me: An account specified in the Run As profile "Microsoft.SQLServer.SQLDefaultAccount" cannot be resolved. This condition may have occurred because the account is not configured to be distributed to this computer. To resolve this problem, you need to open the Run As profile specified below, locate the account entry as specified by its SSID, and either choose to distribute the account to this computer if appropriate, or change the setting in the profile so that the target object does not use the specified account. Note: you may use the command shell to get the Run As account display name by its SSID. I immediately swapped back over, but the error persists, which is beyond me, because this should have re-distributed the account credentials to all the servers in monitoring. The Data Warehouse Action Account is being used in the SQL Server Default Action Account profile

Try to delete and rediscover 1 or 2 Servers from SCOM console and see if it updates. Also you can try to repair the SCOM agent installation in one or two serves. If the issue gt resolved by any of the above then you can plan for rest of the servers.

I actually just closed the alert, and now all the computers just report a healthy state, nothing to see in the health explorer. I have no idea if I actually fixed the problem, all I know is that technically it should be fixed.

Hi, this problem is related to the changes applied in your Run As account and to resolve this problem you must configur the Run As account to be distributed in this computer and to do this take a look at this link : http://www.systemcentercentral.com/Forums/tabid/60/categoryid/4/indexid/82644/Default.aspxOussama Oueslati | System Engineer | vNext Consulting

Here is some information that may help you. A workflow in a management pack has three components - a data source, a condition, and a write action. It is the write-actions that interest you in this thread. In a defined rule, for example, the workflow defintion may say "save this result to the operational DB as well as the DW" - this means any workflow on an agent can require access to the data warehouse to write data. So by using the option "More Secure" you ended up hosing a lot of your agent based work-flows. They may have unloaded even and now require an agent restart. You'll have to just check each one and see the failed workflow report for each agent to see how broad the impact is. When using "more secure" credential distribution, you volunteer to enter the name of every computer that needs each specific credential. Typically you will want to scope this decision to your DMZ and other untrusted zones. But those agents will need the normal OM write accounts in nearly every case since each workflow may need to store data... Microsoft Corporation

Here is some information that may help you. A workflow in a management pack has three components - a data source, a condition, and a write action. It is the write-actions that interest you in this thread. In a defined rule, for example, the workflow defintion may say "save this result to the operational DB as well as the DW" - this means any workflow on an agent can require access to the data warehouse to write data. So by using the option "More Secure" you ended up hosing a lot of your agent based work-flows. They may have unloaded even and now require an agent restart. You'll have to just check each one and see the failed workflow report for each agent to see how broad the impact is. When using "more secure" credential distribution, you volunteer to enter the name of every computer that needs each specific credential. Typically you will want to scope this decision to your DMZ and other untrusted zones. But those agents will need the normal OM write accounts in nearly every case since each workflow may need to store data... Microsoft Corporation

Hi, Please also check the Run As Accounts and Run As profiles seetings referring to the methods in the following post: Configuring Run As Accounts and Profiles in R2–A SQL Management Pack Example http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx Hope this helps. Thanks. Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.