Summary
You are unable to get any result or output recently and there are inconsistencies between the Active Directory (AD) export and the Outside Server Management (OSM) report and client export.
Machines that are visible in the active directory are not appearing in the OSM report.
Details
Below are some of the reasons as to why certain machines does not appear in the OSM:
- The machine is not part of the IP range specified in the advanced page of Outside Server Management.
- The machine has a running OSCE client.
- The machine is disabled from the Active Directory.
- The machine is not part of the Active Directory.
- It is possible that the AD tree has changed, so the tree structure kept in the OSCE DB doesn't reflect the latest structure on AD. AD sync is a must before doing query from Outside Server Management. Important: For OSCE 10.5, make sure to install hotfix build 1962 or higher.
- The machine is unable to connect to port 135.
To troubleshoot further, use either the ADSI or the ActiveDirecotryDumperv2.zip to investigate the issue.
To use the ActiveDirectoryDumper:
- Extract the file using the password “novirus”.
- Run the tool to get the AD infrastructure.
For further troubleshooting, send the output to Trend Micro Technical Support along with the ofcdebug.log while generating a list of the machines using the OSCE that has the issue. Ofcdebug is available through the CDT tool as well.
By design, Outside Server Management does not show clients which are managed by the OfficeScan itself.
