I fixed it! In the comments of the UR1 installation blogpost of Kevin Holman, I saw a remark about having to wait about one hour before installing UR1. I reinstalled SCOM 2016, waited some time before installing UR1 and now everything is fine :).
On Thu, Dec 15, 2016 at 11:05 AM, David Biot <[email protected]> wrote: > I forgot to mention: I immediately installed UR1. > > On Thu, Dec 15, 2016 at 10:30 AM, David Biot <[email protected]> wrote: > >> I'm installing a new SCOM 2016 installation in a single-server setup, and >> i've crossed an odd issue. >> >> What I did: install SQL 2016, then install SCOM 2016 including all >> prerequisites. Then I added 20 agents. Nothing more. No new management >> packs. >> >> Now all agents are healthy. The management server itself is greyed out. >> However, the resource pools as well as the health service watcher of the >> management server are healthy. I've even waited a few days before touching >> the environment again, but nothing changed. >> >> I've looked in the OperationsManager log, but cannot find anything >> critical or related. So I'm a bit in a stalemate. I've done quite a lot of >> SCOM implementations in the past, however never a single-server >> implementation. Is there something specific I need to watch out for? >> >> Best regards, >> David Biot >> >> > >
