Let's say we have RunAs Profile "Unix Action Account" We have RunAs Account User1 User1 added to "Unix Action Account" profile and associated with group "Group1". Let's say Group1 has 7 subgroups and 50 Unix computers . Each Unix computer has thousands of hosted objects. Do we have any limitations for number of implicit objects we have in "Group1"? i'm asking this because since some moment we started receiving hundreds alerts like: Event Type: Error Event Source: HealthService Event ID: 1106 Date: 4/18/2011 Time: 5:32:38 AM Computer: COMPUTER Description: Cannot access plain text RunAs profile in workflow "Rule/Monitor", running for instance "object" with id:"{0A6BD39A-2AD1-8191-8688-BBB8FD118C55}". Workflow will not be loaded. Management group "MG_GROUP" Event Type: Error Event Source: HealthService Event ID: 1107 Date: 4/18/2011 Time: 5:53:49 AM Computer: COMPUTER2 Description: Account for RunAs profile in workflow "Rule/Workflow", running for instance "object" with id:"{EE7C41D7-4C6A-5C69-BCD9-A8332329D52A}" is not defined. Workflow will not be loaded. Please associate an account with the profile. Management group "MG_GROUP"

Guys. Thanks for replies. But you all missed. "since some time". It used to work but suddenly stopped. We just added a couple of new computers into group which is associated with RunAs Profile. We did not touch RunAs Account/Profile itself at all. Current scheme is as follows: Basic RunAs Account -> User1 entity Group -> Group1, this groups contains Unix Computers, group was created from SCOM GUI if it's important. RunAs Profile -> Unix Profile, standard one. AKA Unprivileged one. Unix Profile has single record of User1 which associated with Group1 PaulD

Hi Pavel! Did you ever get rid of it, i have the same issue with runas profile and Event 1106 Cannot access plain text RunAs profile in workf... . Things were working smoothly, ant then suddenly don't.

You could still check out the references here http://www.bictt.com/blogs/bictt.php/2011/05/30/scom-trick-16-1106-event. And i also ran into this where it was not a new install and something changed (suddenly as well). Had to do some fooling around to get it back up and running again, but these posts certainly got me on my way at the time.Bob Cornelissen - BICTT (My BICTT Blog) - Microsoft Community Contributor 2011 Recipient