Hardware Failure on Server holding Management Point - Here is an Easy Fix!

One Customer had a hardware failure on a really old SMS2003 server holding Management Point (MP) and Distribution Point (DP) roles.

Since the HW were really old and soon to be terminated I installed MP and DP roles on Primary Server and asked network team to change the DNS record for the broken server to point out the Primary Server.

Even if clients/agents should go to AD and check for the MP role I have seen that many clients need to be restarted before they do and above goes much faster than wait to all 10'000 clients to get restarted.

Just a small tip :)

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