new feature sccm to remove CAS - how to handle package source site

halima_has 26 Reputation points

Hello ,
I plan to remove CAS to symplify sccm infrrastructure with a single primary standalone by using the new remove CAS feature.
according this doc
it's indicated : "Configuration Manager automatically handles package source locations for built-in packages, like the Configuration Manager client. Review all other content source locations to make sure they aren't using a share on the CAS."

so from my understand for non built in packages we need to migrate the packages source location (source path).
but nothing is specified for packages source site code (of non built in packages).
should we also migrate packages' sourcesite code from CAS to PRI primary standalone or is it automatically handlled by the remove CAS feature process ?

Microsoft Configuration Manager
0 comments No comments
{count} votes

Accepted answer
  1. Jason Sandys 30,936 Reputation points Microsoft Employee

    The site code is irrelevant. You simply need to update the source file location in the packages as necessary.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful