Two weeks ago we had LANDesk installed at our company. The installer helped us setup and deploy the agents with the Management Console. It was going fine for the 2 weeks I slowly deployed the agents every night to 145 computers on different subnets that share the same T1 line. Then all of a sudden our network line to the locations started to drop big time. We found out the agents were setup in the Schedule-driven scan of Patch and compliance scan section to start deploying on this specific day with autofix checked off as well. Our T1 line can’t handle this many requests at once. The installer said to reboot the core server that didn’t work. The T1 line went back to normal while the core server was off. Then I called LANDesk they told us to try renaming the patch folder on the core server that didn’t work. I think all the locations are trying to send back all the vulnerability scans, and we need a way to slow it down. To temporality fix this issue we used ISA to blocked the ports to the LANDesk core server. Then I deployed a new agent to all the locations that wouldn’t scan or do an autofix. We unblocked the ports, but the line started to drop immediately again. I know when I deployed the new agents they weren’t able to send requests back to the core server while it was blocked, but it said it was successful. I’m not sure how whole process of client agent to core server process works, but I need to come up with a solution.
↧