These postings are provided "AS IS" with no warranties, and confer no rights.
The following information is for example purposes only. Do not rely on this information for a production deployment. These are meant to show the areas you should test for when evaluating ConfigMgr client activity impact on your network before going into production. The results are specific to the below ConfigMgr configuration and will vary from environment to environment.
UPDATE (22/04/2013): The System Center 2012 Configuration Manager version of this post can be found here: http://aka.ms/pwlunk
To perform this sort of testing you can use NetMon 3.3, and the Top Users Netmon Expert. Basically, the process is:
For more information on Netmon traffic tracing see the following:
Client to Server Bytes
Server to Client Bytes
Policy Polling Request
Software Update Scan (Regular)
Software Update Scan (Fresh AU DB)
Hardware Inventory (Delta)
Hardware Inventory (Empty)
Software Inventory (Empty)
Hardware Inventory (Full)
Software Inventory (Full)
Software Distribution Policy Poll (Advert Download)
Notes on Test Configuration
Note on SUP/WSUS traffic: Below is some additional (though less comprehensive) testing performed for this information.
This post was contributed by Saud Al-Mishari, a Premier Field Engineer with Microsoft Premier Field Engineering, UK.