現在EC2上にインストールされたIISをDiscoveryしようとしております。
Windows:ClassifyでWindowsのバージョンは分類できているのにそれ以降のプローブがなぜか実行されないままDiscoveryがcompletedになってしまいます。
原因が不明なので助言いただきたいです。
以下windows:Classifyの入力結果になります。
I am currently trying to Discovery IIS installed on EC2.
The Windows version is classified in Windows:Classify, but for some reason the probes after that are not executed and the Discovery is completed.
I am unsure of the cause and would appreciate your advice.
The following is the result of the windows:Classify input.
<results probe_time="15180" result_code="0">
<result>
<Win32_ComputerSystem>
<Domain>WORKGROUP</Domain>
<Name>EC2AMAZ-C986L8A</Name>
</Win32_ComputerSystem>
<Win32_OperatingSystem>
<Caption>Microsoft Windows Server 2022 Datacenter</Caption>
<Version>10.0.20348</Version>
</Win32_OperatingSystem>
<Registry>
<entry key="HKEY_LOCAL_MACHINE">
<entry key="SYSTEM">
<entry key="CurrentControlSet">
<entry key="Services">
<entry key="Tcpip">
<entry key="Parameters">
<entry key="Hostname">
<value>EC2AMAZ-C986L8A</value>
</entry>
</entry>
</entry>
</entry>
</entry>
</entry>
</entry>
</Registry>
</result>
it appears that the return isnt meeting the full classification criteria. I think it might be the osfullname that might not be catching as you can see in the screen shot that ALL must be met. Without meeting the complete classification then it will not trigger the pattern and probes that you want to capture the IIS application..
Windows 2022 Serverの関連リストのトリガータブに、元々は何もレコードが入っていなかったため、手動で以下二つを追加しました。すると、Discoveryの結果が変わりました。
The Triggers tab of the Windows 2022 Server related list originally contained no records, so I manually added the following two. This changed the Discovery results.
Oddly you seem to be missing the Application Dependency Mapping (ADM) probes, be sure to add them..
