"Making second attempt within a few minutes of a failure will usually yield a successful scan."
That right there would tell you the basic prerequisites for a remote patch scan are in place. Something in your environment may be causing the initial machine resolution to fail. We're going to need logs from the attempts before we can offer ideas on what it may be.
1. Please open the Protect GUI and then go to Tools > Options > Logging and change logging to “All” for both user interface and services.
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.
a. Focus on one of the machines, create a Machine Group for it and add valid credentials to it. Attempt to scan the machine until it works.
b. Before the scan, verify that you can connect to the machine with this command from the CMD prompt: net use \\machinename\IPC$ Do you see any errors? Take a screenshot.
c. Before the scan, start a ping -t against the target machine to see if there are any timeouts. Take a screenshot.
7. Collect the logs from the Logs folder mentioned earlier in step 4 and any screenshot you have. (please zip if possible)
8. Zip everything and attach to the case.
Support Portal: https://support.shavlik.com/CaseLogging.aspx
Let me know if you have any questions.
Thanks Charles. I may have had a small breakthrough on this. The problem might be related to some settings related to our WAN optimizers and Active Directory. I need to do a little more testing and will be back in touch with either the solution or logs for support to review.
OK, thanks for the heads-up! A solution would be great if you come across one I'm sure it would help others in the future.
The problem still isn't solved, and the ball is still in my court. The 9.2 scheduler mess has me distracted from this particular issue for now.
Thanks for keeping me posted!
Make sure that nslookup forward and reverse are working for IP address of the server.
Before the scan, verify that you can connect to the machine with this command from the CMD prompt: net use \\machinename\IPC$