SCOM -SCVMM Post Integration Warning Alerts

Question

HI
Recently we integrated SCOM 2012 and VMM 2012 as per this blog-
http://blogs.technet.com/b/kevinholman/archive/2012/08/21/integrating-vmm-2012-and-opsmgr-2012.aspx#comments
It was a success! However, there are lot of warning alerts popping up from most of windows computers
Monitor - Run As Account Verification
Context:
Date and Time:
2/19/2015 10:33:54 PM
Log Name:
Operations Manager
Source:
HealthService
Event Number:
7015
Level:
1
Logging Computer:
gooroo1.opsmgr.com
User:
N/A
Description:
The Health Service cannot verify
the future validity of the RunAs account OpsMgr\SCVMM_Int for
management group OM12. The error is Logon failure: the user has not
been granted the requested logon type at this computer.(1385L).
Event Data:
<
DataItem
type ="
System.XmlData "
time =" 2015-02-19T22:33:54.3992478-08:00
" sourceHealthServiceId
=" A425A7F1-84CD-A2F8-B2F6-82FAEED9CF46
" >
<
EventData
>
< Data
> OpsMgr
</ Data >
< Data
> SCVMM_Int</
Data >
< Data
> Logon failure:
the user has not been granted the requested logon type at this computer.
</ Data
>
< Data
> 1385L
</ Data
>
< Data
> OM12</
Data >
</ EventData
>
</ DataItem
>
Run as account for VMM is OpsMgr\SCVMM_Int which is distributed for "Less Secure" (By default) and the corresponding profile is set to "all targeted objects" as per blog.
Does anyone know how to fix this?
regards
Guru
Gururaj Pai

Answer 1

Verify the user that used in integration is add to local administrators of SCVMM Server. Also did you check comment of Kevin in your link related to this issue "It is my opinion that this account should not be set to “less secure” which will distribute
the credential to all healthservices in the management group. I will research if we can limit the scope and distribution. Less Secure is not a good option for most customers and I am not sure why the product chose this for a default. This will cause a large
number of alerts to be sent from all your SCOM agents, where this credential cannot “Log on locally”. Generally, your SCVMM service account does not need, nor will it have, “Log on Locally” rights to all managed agents. If you see a ton of those alerts after
configuring SCVMM integration – this is why.
I personally recommend to set this to more secure, and then distribute the credential to all Hyper-V servers, the VMM server, and the SCOM server."
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"Mai Ali | My blog:
Technical | Twitter:
Mai Ali