Skip to main content
Question

Security Update 2020-002 for Mojave on NetSUS

  • April 21, 2020
  • 1 reply
  • 11 views

Forum|alt.badge.img+3

Is anyone having issues getting the security update 2020-002 for Mojave to detect correctly? I have removed the download cache from the server via shell and forced it to re-download the content by running a sync. I also have verified the product ID for both 10.13 and 10.14 exist in the .sucatalog file.

When I remove my CatalogURL from the SoftwareUpdate plist, it detects that it is needed directly from Apple.

1 reply

Forum|alt.badge.img+3
  • Author
  • New Contributor
  • May 5, 2020

Come to find out, this is not just for 2020-002 but is also affecting other security updates like 10.15.4. I modified our Catalog url to be in line with the following link to point to the full path including /content/catalogs/others/. If I do just the default branch without the branch name, ALL updates get advertised to systems even though some are not enabled. If I point the CatalogURL directly to the Branch (_PROD.sucatalog), I back to where it doesn't advertise recent security updates.

Does anyone know of a way to "reset" the software update server to "start over"?