1 Reply Latest reply on Feb 23, 2015 7:23 AM by cwinning

    Laptop Scanning



      I've just begun to work with Shavlik and wanted to throw a few questions out to ya'll and see what people had to say.

      I'm trying to figure out a way to reliably scan laptops which are on/off at random times of the day and physically scattered wherever people decide to take them. It'd be nice to do this scanning in a way without having to coordinate times with everyone who has a laptop so I can figure out when I can scan/deploy patches. The current strategy I have is to install an agent on each particular laptop that ideally would automate scanning and patching whenever the laptop is turned on. I'm also encountering errors 261 and 235 often when I scan laptops, and I think the error 235 alert is trivial as the machine is probably just turned off, and that the error 261 is due to the machine being connected wirelessly or through a VPN, and not through ethernet. I have checked the inbound port rules on several machines and they have all been configured to allow ports 139/445. Just curious if anyone else has encountered or has experience with this and if there are any tools in Shavlik I can take advantage of to make this easier.



        • 1. Re: Laptop Scanning
          cwinning CommunityTeam



          The Protect Agent is your best option for laptops that are on off the network or are not on a wired LAN.  With the Agent, there is a built-in mechanism to run jobs when a network change are detected to capture agents that on on and off network.  You can also enable the option 'Run on boot if schedule missed' for laptops that are powered off at the schedule scan/deployment times.  You could also look into the Cloud Agents.


          Although we don't recommend non-agent scans against machines through a wireless connections, it should work as long as the connection is solid.  Also, VPN connections will cause longer scan times and combining a wireless connections over a VPN is a troubled mix.  We have worked with customers that encounter issues with scanning through VPNs.  Verify name-IP resolution, attempt to telnet to the target from the Protect service over ports 139/445.


          Let me know if you have questions.