I am getting below error on Share Point 2013 MP when i am configureing the SharePoint 2013 MP. it says our services account doesnot exisit. whereas this account exisist and has been configured as RUN AS account in Scom. Secondly our all sharepoint machines are appearing as unidentified. and 2 machine are showing in sharepoint server farms i am also attaching the screen shot also

The Event Policy for the process started at 4:58:30 PM
has detected errors in the output. The 'StdErr' policy expression:

.+

matched the following output:

Account sppsadmin doesn't exist

Failed to find RunAs account sppsadmin

Command executed: "C:\Windows\system32\cmd.exe" /c powershell.exe -NoLogo
-NoProfile -Noninteractive "$ep = get-executionpolicy; if ($ep -gt
'RemoteSigned') {set-executionpolicy remotesigned} & '"C:\Program
Files\Microsoft System Center 2012 R2\Operations Manager\Server\Health Service
State\Monitoring Host Temporary Files 15341\5528145\AdminTask.ps1"'
'Microsoft.SharePoint.Foundation.Library.mp.config'"

Working Directory: C:\Program Files\System Center Management Packs\

One or more workflows were affected by this.

Workflow name: Microsoft.SharePoint.ConfigSharePoint

Instance name: Microsoft SharePoint Farm Group

Instance ID: {6CB0A80D-D833-26EA-13C1-0CA48A57F5E2}

Management group: PPLSCOM2012

Error Code: -2130771918 (Unknown error (0x80ff0032)).

Hi,

Are you using default run as account for monitoring configuration or configured a run as account for monitoring SharePoint 2013?

If you are using default run as account, has your default run as account the local admin privilege on the SharePoint box?

If you are using dedicated run as account, is your account has local admin privilege on the server and the read only privilege on the SharePoint farm?

We have run as account in local admin as well as read only rights of share point farm.

We have run as account in local admin as well as read only rights of share point farm.

Hi,

Could you please set the execution policy as "all signed" instead of "remote signed"and then execute the query. It is just to check once if the policy set is creating some kind of issue.