Hi peeps I am after a little guidance if possible. We cached down Office 2010 to a secondary site of approx 1000 clients. The network guys unplugged the SCCM server as the switch on the secondary site went up to 52% utilisation...There is a 100mb connection to the switch for the secondary server. The network team are pointing the finger at SCCM but we have never had a problem in the past with this site. Is there any way from the sccm side i can gather the amount of data that was sent out. I am open to ideas to Kindest regards KevKev :)

Which traffic causes the 52% utilisation? Clients to secondary site? Have you advertised Office 2010 to all those 1k clients?Torsten Meringer | http://www.mssccmfaq.de

Hi Torsten We advertised Office 2010 to the 1k clients with a mandatory schedule in the future to cache the package down first before executing. So i guess it would be the package caching to the clients... Thanks Kev :)

Hi peeps I am after a little guidance if possible. We cached down Office 2010 to a secondary site of approx 1000 clients. The network guys unplugged the SCCM server as the switch on the secondary site went up to 52% utilisation...There is a 100mb connection to the switch for the secondary server. If you're talking about seoncdary to client communication like office 2010 package then check out IIS logs whether clients are downloading package from the secondary server DP and that caused the issue or not. Your seocndary server and clients are in LAN? Or Are you talking about package replication from primary site to secondary site caused the WAN traffic issue? If so, you can enable bandwidth throttling for that secondary server.Anoop C Nair - @anoopmannur MY BLOG: http://anoopmannur.wordpress.com User Group: ConfigMgr Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

We advertised Office 2010 to the 1k clients with a mandatory schedule in the future to cache the package down first before executing. So i guess it would be the package caching to the clients...v :) So that's 1k clients downloading a huge package ... 52% utilisation on the switch is not too bad then.Torsten Meringer | http://www.mssccmfaq.de

Hi Anoop It was the clients downloading from the secondary that caused the issue...They are on a LAN I already throttle the bandwidth traffic the WAN linkKev :)

Hi Torsten I take it they wont download all together but by the number of concurrent packages set. This is what the DP is set to atm Concurrent distribution settings Max number of packages 6 Max threads per package 30 Retry setting Number of retries 10 Delay 60 Multicast retry settings number of retries 3 Delat before retrying 1 Send package from nearest site in hierarchy (ticked) Would you say this is acceptable?? Thanks KevKev :)

These are the settings for distribution manager. Not for the client download.Anoop C Nair - @anoopmannur MY BLOG: http://anoopmannur.wordpress.com User Group: ConfigMgr Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Sorry those settings were for the Primary The secondary is set to Concurrent distribution settings Max number of packages 3 Max threads per package 5 So would all the clients download the large package at the same time?? I thought these settings control how many packages deploy to clients at a time? Thanks KevKev :)

For clients you can try this (note I've never used it) BITs throttling settings http://technet.microsoft.com/en-us/library/bb633140.aspxAnoop C Nair - @anoopmannur MY BLOG: http://anoopmannur.wordpress.com User Group: ConfigMgr Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Concurrent distribution settings Max number of packages 3 Max threads per package 5 So would all the clients download the large package at the same time?? I thought these settings control how many packages deploy to clients at a time? Yes, all clients will start downloading as soon as they received the policy. The settings mentioned above control the behavior of distmgr (the component that distributes packages from the siteserver to DPs).Torsten Meringer | http://www.mssccmfaq.de

Do you know of any implecatiions for using Bits on the client side? Ah i thought that it was DP sending to clients setting, Torsten.. thanks very much Kev Kev :)

I didn't see any implications other than some delay in the deployments and download :)Anoop C Nair - @anoopmannur MY BLOG: http://anoopmannur.wordpress.com User Group: ConfigMgr Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Is there a way then to limit the amount of packages that get sent at a time to clients for large scale distributions?? Thanks so much guys for your help KevKev :)

For clients you can try this (note I've never used it) BITs throttling settings http://technet.microsoft.com/en-us/library/bb633140.aspxAnoop C Nair - @anoopmannur MY BLOG: http://anoopmannur.wordpress.com User Group: ConfigMgr Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Concurrent distribution settings Max number of packages 3 Max threads per package 5 So would all the clients download the large package at the same time?? I thought these settings control how many packages deploy to clients at a time? Yes, all clients will start downloading as soon as they received the policy. The settings mentioned above control the behavior of distmgr (the component that distributes packages from the siteserver to DPs).Torsten Meringer | http://www.mssccmfaq.de