恩？报错了

防火墙 干掉试试，可以就找下相应的端口开启下，不行的话，就要进行进一步的troubleshooting

依旧不行，尝试手动

最后发现是管理员权限问题，就是要选择Other user account来输入管理员账号密码

Management Mode 可以选择Agent 和 Agentless

成功发现添加后切换到Administration

VMM和Operation Manager连接的前置条件

https://technet.microsoft.com/en-us/library/hh882396.aspx

发现好像还没完全结束么

在虚拟机上单击右键，打开Properties页中的Security，勾选Allow this agent to act as a proxy and discover managed objects on other computers

点击Discovery wizard,继续用Automatic discovery添加其他的VM，没在域里面的机器无法发现，没开机的，DNS不正确的都无法侦测到，所以DNS的维护很重要

接下来是安装agent的时间

Troubleshooting思路

Report Server (SSRS) cannot connect to the report server database.

SQL server Troubleshooting的思路

Explanation

The SQL Server Report Server service cannot connect to the report server database. This error occurs during a service restart if a connection to the report server database cannot be established. Conditions under which this error occurs include the following:

• SQL ServerDatabase Engine service is not running when the Report Server service starts.
• The connection to the Database Engine service fails because remote connections or the TCP/IP protocol is not enabled.
• The report server database is not configured correctly.
• The service account is not configured correctly, or the account no longer has permissions on the report server database. This can occur if you do not use the Reporting Services Configuration tool to set up the account or the report server database.

User Action

Start the Database Engine service if it is not running and check that remote connections are enabled for TCP/IP protocol.

Use the Reporting Services Configuration tool to configure the report server database and service account.

登录SQL服务器，发现TCP/IP里面的IP2，也就是IP v4出于Active，但enabled没有开启，改下再试试呗

记得要重启服务，SQL server services里面的SCOM服务

https://social.technet.microsoft.com/Forums/systemcenter/en-US/bff8a86b-a0f3-4d2e-8681-cffa23315fef/the-pool-managing-the-instance-is-not-available-or-the-location-monitoring-object-cannot-be-found-?forum=operationsmanagergeneral

尝试了下这段描述，虽然并没有找到链接问题的报错，死马当活马医了。

A little more digging in event logs shows that there are actually some SQL connectivity issues. Also, the SCOM server is showing as "Not Monitored" under discovered inventory.

Solution:

The issue lays with the connection string that SCOM uses to talk to the SQL server. Although the instance name is required during setup, it seems to be messing with the connection after setup.

To fix:

Navigate toC:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server

Open (as administrator) ConfigService.config

Edit the following lines, removing the \INSTANCENAME values so that only the SQL ser

System Center Operation Manager添加监控VM及troubleshooting思路