search cancel

Bandwidth Throttling doesn't work when downloading packages via https


Article ID: 161842


Updated On:


IT Management Suite


Network tools determined that bandwidth throttling settings, defined in the Agent Configuration Policy, were not being obeyed. The outlying client agents were using all available bandwidth to download packages.

It was determined that throttling settings were only being ignored when attempting to download via HTTPS.


The HTTPS URL ws being treated as "automatic" because the speed test to "/Altiris/NS/Agent/ConnectionTest.asp" via port 443 was failing with error 404. Therefore the agent logic caused the download process to  assume the default speed. A follow up test is not performed by the agent.



This issue has been addressed in the ITMS 7.6 HF1 release.
In the case this article was original based on, HTTP was the preferred method, but the HTTPS links were available and all clients had the server's certificates available.

Prior to ITMS 7.6 HF1, if HTTPS is not a requirement then a workaround would be to eliminate HTTPS codebases. Attached to this article is a "Run SQL on Server" task that, when imported and scheduled to run hourly, will remove any HTTPS download codebases and leave only HTTP and UNC sources.




Applies To

Symantec Management Platform 7.5 SP1 HF5


Remove HTTPS Codebases for Packages.xml get_app