Any one know if (and how) SMS 2003 is really bandwidth senstive???

I've used other technologies relying on BITS (SUS) and found it still takes down our frame relay (over ATM) sites because of the way it determines the available bandwidth.

Basically it uses the clients bandwidth (10MB) to determine how much it should use (say 2%) which equates to 200kbps over a 128k fram link. Presto, everyone else at the site drops their terminal services connections back to here.

I've been away from SMS 2003 for a few months evaluating LanDesk 8 and was wondering if anyone had actually tried SMS 2003 in production yet before I thow in the towel and go LanDesk. Thanks. DB.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


My first question is, have you talked to Microsoft about this issue? I am sure you are not the first person to have this scenario.
Answered 03/28/2004 by: nwalton
Yellow Belt

Please log in to comment
What Senders have you configured? Secondary Sites? Remote Distribution Points?... SMS has many ways of dealing with bandwidth sensitive environments, especially SMS 2003.

As for your BITS issue, MS wont be able to help you because that is by design. BITS works ont he client side to make sure that other processes(apps) that need to use the Network connection can, so when the SMS client senses that somethign else needs the ntwk connection it scales back.

Answered 03/30/2004 by: mattw112
Yellow Belt

Please log in to comment