Virtual Central Site Server CPU/RAM/Disc Load During Big Client migration

I want to show you some performance status from a real world migration when 5000 new SCCM clients were added to a hierarchy where all SCCM site servers are running on Virtual VWware platform.

All Primary Child Site Servers has 4 CPUs and 8 GB RAM and the Central site Servers where all the pictures below come from has 12 GB RAM.

SQL 2008 is only allowed to use 2 CPU's (read more).

Memory usage duing initial first discovery and HW/SW Inventory.

CPU usage duing initial first discovery and HW/SW Inventory.

And last picture shows Disc usage duing initial first discovery and HW/SW Inventory.

Virtual servers are doing a good job and this same Central site servers has now >40'000 active clients and is still in good shape.

Please use the below comment link if you want to ask something?

SCCM client installation fails - Error 1603

  I am right now doing a big server migration from SMS2003 to SCCM2007 and in some countries the installation fails with an general error code 1603.

To solve this I added this one line to my client installation cmd file right before ccmsetup.exe command line:

If exist %windir%\system32\atl.dll %windir%\system32\regsvr32.exe %windir%\system32\atl.dll /S

Enable 2 CPU's for SQL2008 on SCCM Central site

As default all available CPU's are managed by SQL and on one of my customers Virtual Windows 2008 R2 x64 server (Central site with 40000 clients) i have seen that CPU0 is running very high 80-90% and CPU1 around 50% and the last two barely at all.

Default setting as above!

After my change in SQL2008 Server Management Studio.

This was the dramatic change. CPU0 was down to normal and could execute more SCCM processes and CPU3 and 4 was forced to run SQL2008R2.