| T O P I C R E V I E W |
| JSCLMEDAVE |
Posted - 09/24/2010 : 11:09:15 AM
We have found numerous PCs that for whatever reason do not have the SCCM client installed.
Due to the number of PCs we want to break them into chunks so that we do not inundate the network.
I was asked to find out the size of the payload to a single PC so that we could determine how many machines we would plan to do at a time with out stressing the network or bandwidth.
I Googled this for a couple hours yesterday and to my surprise found very little.
Aidan brought up a good point -
"God only knows how much. That'll depend on the machine, any "management packs" that are installed on the management server, etc."
- Aidan Finn
I did find this info -
Directory of C:\SMS Tools\ccmsetup
05/20/2008 06:00 AM 611,360 ccmsetup.exe
1 File(s) 611,360 bytes
Total Files Listed:
1 File(s) 611,360 bytes
0 Dir(s) 7,172,091,904 bytes free
Directory of C:\SMS\bin\i386
05/20/2008 06:00 AM 611,360 ccmsetup.exe
1 File(s) 611,360 bytes
Directory of C:\SMS\Client
05/20/2008 06:00 AM 611,360 ccmsetup.exe
1 File(s) 611,360 bytes
Total Files Listed:
3 File(s) 1,490,208 bytes
0 Dir(s) 53,363,924,992 bytes free
This file is part of Systems Management Server. Ccmsetup.exe is developed by Microsoft Corporation. It’s a hidden file. Ccmsetup.exe is usually located in the %SYSTEM% sub-folder and its usual size is 236,544 bytes.
Description: ccmsetup.exe is located in a subfolder of C:\Windows\System32. Known file sizes on Windows XP are 258,048 bytes (53% of all occurrence), 267,488 bytes, 602,624 bytes, 504,696 bytes.
I feel there has to be a way to test this prior to pushing out to over a thousand PCs. Right? I am just at a loss on how to go about getting a good baseline for the payload size and BW it will take up.
If I could get that for a single PC, I would then be able to take those findings and figure out what it should be for the numbers we have.
Any help will be greatly appreciated... |
| 5 L A T E S T R E P L I E S (Newest First) |
| Jake Mueller |
Posted - 10/18/2010 : 4:03:21 PM
whoops, I think there is an old business email in my registration here....
Sorry about that
|
| JSCLMEDAVE |
Posted - 10/18/2010 : 10:16:42 AM
We sorted this out. Broke the PCs into 100 EA collections and are kicking it off manually. |
| JSCLMEDAVE |
Posted - 09/24/2010 : 1:33:14 PM
Jake, tried to send you some info that I cannot post and your email bounced... |
| JSCLMEDAVE |
Posted - 09/24/2010 : 12:36:08 PM
Multiple Domains and Sites involved. I am not sure the procedure they normally use for the location of the install file but I will ask.
Over 2500 PCs ranging from Win 2000 to XP SP3. |
| Jake Mueller |
Posted - 09/24/2010 : 11:57:00 AM
CCMSETUP actually is going to pull the client install files from the nearest management point, or whichever source for client files you specifiy in the command line (CCMSETUP /source:<sourcepath>)
Since I have to manage 300+ secondary sites most of which are on sub-T1 connections, I'm acutely aware at all times of network load. I have done client pushes from my central site and ended up getting a Network Engineer's attention, even at a site on multiple T1s.
I think it would be wise to specify a local source containing the installation files, then ensuring that the CCMSETUP command line references that source.
When you say you are concerned about network bandwidth, are these WAN sites or are you worried about saturating local LAN traffic? |
|
|
