Are there any values available to be able to start calculation for client traffic (I know amount of traffic does depend on various factors). For instance packet size for client contacting the management point, metering, hw /sw inventory (even if nothing has changed) and so. It is not a lot for a single client but maybe huge if multiplied by several thousand clients. Thanks

Hi, To prevent the Inventory agent from deleting inventory xml files from the client; create a file called archive_reports.sms and place it in the hardware inventory temp folder %systemroot%\system32\ccm\inventory\temp\. This can be very useful when you want to track the size of each inventory file. This will ensure that inventory files are not deleted which makes it very easy for you to track the size. Once you are done testing, remember to delete the file. I would test it for a few days, this leaves you with multiple files.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

I think it's said that the average is less than 5Mb per client but it really depends on what you enable in AI. Some of that stuff can cause inventory to grow. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

As for actual policy, the usual number i see is that policies are not more than 10KB; that means 10KB per client, per policy polling period.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Hi Jason, so those 10KB per client wil be traffic from/to the Management Point at the primary site. Do you know if using a Proxy Management Point in the secondary site will reduce the amount of traffic for clients being within the secondary site ? I guess not as the policy will be downloaded always from the Management Point at the primary site - right?

Hi tiz.A I quote the technet documentation : "A proxy management point is a management point installed at a secondary site which acts as a proxy for the default management point at the secondary site's parent primary site. In general, proxy management points are used to avoid excessive bandwidth usage over slow network links between clients located within the boundaries of a secondary site and the default management point located at the parent, primary site. As the number of clients located with the secondary site's boundaries increases, so does the amount of network bandwidth used by clients to communicate with the primary site's default management point. Depending on the network links in place, there may be a point at which the traffic becomes too much for a slow link to handle without installing a proxy management point at the secondary site. Proxy management points do not directly respond to client policy requests. All client policy requests are sent to the default management point at the primary site. However, proxy management points do cache policy bodies downloaded by clients. If the policy body for a requested client policy has already been downloaded by a secondary site client, the policy body will be sent from the proxy management point to the secondary site client. Otherwise, the client will download the policy body from the default management point at the primary site and the proxy management point will cache it for future client policy body requests." You can find more informations on http://technet.microsoft.com/en-us/library/bb693472.aspx Best Regards, Jean-Sébastien Jean-Sébastien DUCHÊNE - www.windowstouch.fr - Microsoft Student Partner (MSP), MCITP Enterprise Desktop Support Technician 7/Enterprise Desktop Administrator 7, MCTS Configuration Manager/MDOP

Hi, You can use the capacity planner tool to evaluate network usage, but you must customize in "Assumptions". http://myitforum.com/cs2/files/folders/utilities/entry112970.aspx BL

How about this info.... http://blogs.technet.com/manageabilityguys/archive/2009/11/19/client-network-traffic-tests.aspxwde