I recently upgraded SEPM to version 11.0.6 MP3 (11.0.6300.803) and added the client installation to one of my sites. Initially, one client started downloading files and was upgraded over the course of a few hours. I monitored network traffic during this time and did not see any significant changes in bandwidth usage, so I assumed that the client download/installation was using the same bandwidth throttling settings I have set in my LiveUpdate policy for this site.
Later in the day (after normal business hours), this changed drastically, as all of the online client machines attempted to download the new client from the SEPM server. This completely saturated my the data connection (a T1 connection) to this site and it stayed that way all weekend. None of the clients have completed the upgrade after approximately 48 hours of network saturation. I removed the client installation packages from the site with no change. I rebooted the server with no change. In order to stop the downloads and saturation, I had to stop the WWW and SEPM services on the server. If I start those services again, the clients appear to pick up where they left off and saturate the connection again.
Now I'm stuck with the services shut down, so clients are not getting defiition updates, I can't access the SEPM console, etc. Is there a way to cancel those client istalls? Or is there some sort of time out, so if I leave the services on the server shut down a certain amount of time, the client will stop attempting to download files?
I know I can use IIS on the site's local server to set up the client download and plan to do that in the future. If I implement that now and re-publish the client installation package with the url to the local site, will the clients that are currently downloading from the SEPM server get this update and change their download location to the local site?
Thanks in advance for your help.