Protect would normally use whatever the OU returned which is usually FQDN. If FQDN fails to resolve then Protect will try netbios and finally IP if we have it. The only way we are going to be sure what is happening behind the scenes is to look at the logs capturing the scan attempt.
Use the following instructions to capture the issue:
1. Please open the Protect GUI and then go to Tools > Options > Logging and change logging to “All” for both user interface and services.
a. If you are unable to set logging via the GUI see this doc: http://community.shavlik.com/docs/DOC-22938
2. Close the Protect GUI.
3. Stop the following services
a.Shavlik Protect Console Service
b. ST Remote Scheduler Service
4. Delete all the logs from
a. Windows 7, 8, 2008, 2012 & Vista: C:\ProgramData\LANDesk\Shavlik Protect\Logs
b. Earlier OS’s: C:\Documents and Settings\All Users\Application Data\LANDesk\Shavlik Protect\Logs
5. Start the console service and open the Protect GUI.
6. Attempt to reproduce the issue. Please document steps to reproduce.
a. Collect the logs from the Logs folder mentioned earlier in step 4 (please zip if possible)
7. Zip the logs. You can attach the logs to a case created by using the Support Portal.
Let me know if you have any questions.
Scan logs have been uploaded.
We are connecting to your OU via LDAP and your AD is returning machine name and not FQDN. The scan therefore is using machine name and it fails since you cannot resolve the machines by machine name. Not much we can do here to force your AD to give us FQDN instead of machine name. I know Protect 9.1 would fail over from FQDN to Machine Name to IP address, but it wouldn't fail up to FQDN from Machine Name. So an upgrade from 9.0 to 9.1 may or may not help you.
Workaround would be to manually add machines to Machine Group by FQDN.
Thanks for your help.