mauriciolazo

Hi everyone, Just wanted to share that, in my case, after incresing server resources, some things changed but nevertheless the compsumption was still there. After reviewing the logs from SQL server, we identified that a replication session from the CAS server over to its instance was completely stuck and consuming a lot of CPU resources. Just like any other Microsoft producto, we rebooted the SQL server that holds the instance, and everything is running smoothly again, we are doing some analysis to determine what caused that in the first place, but nothing has come up yet. Just wanted to share this, it may help someone. Regards,

Hello everyone! Just a quick question. So if the information for Management Points can only be published to the domain where the MP belongs to then how can the clients from other domains identify the intended Site Server to manage them? In my specific case, SCCM 2012 hierarchy is trying to take control over the clients from another domain where SCCM 2007 was running but it is disabled (not uninstalled, just fully disabled), and my main problem is that the clients are still rotating their management point from what I specify in the installation command, to the former SCCM 2007 Management Point. Thank you to everyone for the clarifications and tips in the previous posts.

pretty much, there is no detailed guide, although the guide provided by Peter van der Woude is really excellent in pointing you in the right direction. Take his steps, apply them to your situation. It can be summarized like this: - Communications between the intended management point and the "other domain" clients - The SCCM administrator account from your current domain has admin permissions on your "other domain" (meaning it has the permissions that Microsoft documentation asks for a SCCM admin) - The sccm admin account and the servers accounts have full control over the "System Management" container in your "other domain" active directory. - You have enabled "System Discovery" in your current domain, and also added the "other domain" to be discovered. (With this task it may not be a good practice to just add "theotherdomain.com" to the system discovery, it would be best to add specific containers or groups in order to have a more granular approach in finding clients) There are other permissions that Microsoft documentation and also several tutorials here can help you out in order to take control over the clients in another forest wether if it is untrusted or not. Peter van der Woude even has a tutorial to take control over clients in Workgroups!! That's fantastic! Anyway, what I wrote were really simple steps to get you going.

Thank you Anyweb! As you stated, I was looking in the wrong place, at Monitoring main Tab. Thank you again.

Replying weeks later after last message, but wanted to share my experiences. I had exactly the same issue with a different setup: - 1 Central Administration Site - 2 Primary Sites that are also Distribution Points. - 1 Primary Site dedicated to Internet Based Client Management Total amount of clients to be managed are around 4000. The issue we had is that, I was preparing SCCM to install SP1, so I performed all the task for this update, and managed to install it on CAS server, but didn't run these other tasks on Primary Sites. Then, 2 weeks later, we have a spike in SQL instance, RAM and CPU consumption, between 80% and 90% all the time. Reading through the documentation we found 2 things: - What Aurock stated previously, that Update summarization was set to every minute (in his server was at every hour, in mine it was at every minute!). It shouldn't have taken that much amount of resources, since a summarization and consolidation of updates is sent to the DB, and not the updates per se, nevertheless, it was taking a bit of resources. - In Microsoft Documentation, it states that for a CAS server, it needs to have a MINIMUM of 8GB of RAM reserved just for that instance and its processes, and since I'm sharing that instance with another platform, I had just 6 GB of RAM reserved for CAS and also, the instance did not had a limit on memory usage (one of those -prerequisite check- warnings when you are installing SCCM). SQL server requirements for SCCM 2012: http://technet.microsoft.com/en-us/library/gg682077.aspx#SQLDBconfig All this combined, gave the SQL server a huge consumption on RAM and CPU resources. Hope this helps somehow.