Welcome to Community Answers



  • 112 reputation
  • 5 answers, 1 selected
  • 1 questions, 1 solved
  • Member for 1 years, 20 days
  • 924 profile views
  • Last seen 3 days ago


Total 112
15 Jun, 2017 Best answer answer
15 Jun, 2017 Selected answer AD Topology Discovery does not run SCOM 2016
14 Jun, 2017 Commented In our test enviroment we have already the "new" ad ds mp and got an topology. In our production we use the old AD MP and got now topology.. I did the same overwrites but no topology ... After a little search i found this and will give a try: The issues with the Topology Views of the Active Directory Management Pack is resolved. As part of the troubleshooting process Microsoft wanted a workflow analyzer installed on the management server, this utility needed .Network Framework 3.5 installed as part of the installation. Once this was installed all the topology views started discovering the AD objects within a few minutes. However, this was never documented anywhere in the Microsoft documentation, below is what they had as a requirement for the management server, they talk about .Net Framework 4 but not 3.5. In addition, I’m not sure as to how the installation would have proceeded with the install if all the pre-requirements weren’t met. It must be a bug or a mystery. Management Server • Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space. • Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server 2012 Core Installation. • Processor Architecture: must be x64. • Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0 • Windows Remote Management: Windows Remote Management must be enabled for the management server. • .NET Framework 4 is required. For more information, see the following document: o.NET Framework 4 redistributable package


10 votes received 90/100 9up 1down
4 votes casted 100/100 4up 0down

Top Answers

No answer posted yet!

New questions