CAS OS Patching for the remote db and the sccm server
<section class="comment-content comment">

Hi,
I have a query on software patching of CAS and its remote SQL server.

If CAS cannot manage client and there is no DP and MP, how do I do software update on the CAS server and its remote SQL server?
Is it better to upgrade from primary sites to CAS rather than freshly installed CAS as the standalone primary site will be converted to a child primary site and therefore able to manage and do software update on itself and the remote SQL server?

Thanks in advance.

</section>
August 28th, 2015 6:13am

 as the standalone primary site will be converted to a child primary site 

I don't get the problem. You cannot convert any sites in CM12. Are you asking about how to patch the CAS plus SQL server using the existing hierarchy?
Free Windows Admin Tool Kit Click here and download it now
August 28th, 2015 6:28am

In SCCM 2012 R2, when you upgrade the standalone primary site to become a CAS, it will become a child primary site under the CAS isn't it?
August 28th, 2015 7:24am

In SCCM 2012 R2, when you upgrade the standalone primary site to become a CAS, it will become a child primary site under the CAS isn't it?
The only thing you can do is add a new (and only new) CAS as the parent of an existing stand-alone primary site. I think this is what you are trying to say but what does that have to do with patching anything?
Free Windows Admin Tool Kit Click here and download it now
August 30th, 2015 10:10am

My patching point is referring to OS software deployment using WSUS. Let say my existing primary site code name is SC1 and it is join to the new CAS at another location and CAS site code name is CA1.

How do I deploy OS software deployment for patching on the CAS server itself and its remote SQL server if it is based on sccm agent which points to the site code individually.

If I am not wrong, the CAS server will also be install with agent when installed on the CAS and registered with its site code. Will the existing primary site able to patch the 2 servers?

August 30th, 2015 10:11pm

That is incorrect. A CAS does not and cannot manage client agents -- even the one installed on itself. If you want it managed, it must be managed by a primary site.

Why do you want a CAS at all though? DO you truly have more than 150,000 managed client systems? If not, you shouldn't be considering a CAS as there is no other valid technical reason for one.

Free Windows Admin Tool Kit Click here and download it now
August 30th, 2015 10:41pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics