Creating and monitoring software updates
Software updates management has changed dramatically in CM12. Gone are the Update Repository, Update List, and Update Template nodes. The change is a reflection of the entire task of managing updates being simplified.
Updates have to be downloaded to a source location before they can be pushed out to DPs. On a server of your choice (yes, the primary or CAS is OK for this too), create a share for the patches, for example,
\\FileServer\Patches$. The share permissions will need your ID to write the patches and the primary site server's machine account to read them.
How to do it...
Now it's time to actually create a package of software updates that can be used to target clients. This can be done ...