NetSUS 4.0.0 El Capitan

[g2oIT]

All,
Trying to figure out why 10.11 updates are not showing in my branches. Did an upgrade on NetSUS 3.0.1 to 4.0.0 runing the .run on an Ubuntu 14.04.3 LTS VM.

Do we need to manually add the Apple software update catalogs to the NetSUS, and if so, how can we do that?

[stevewood · Accepted solution]

@SeanHarsh you can use repoutil --configure to re-create the preference file that Reposado uses to generate the catalogs. You can find more info here: Reposado Preferences

You may also try upgrading NetSUS to 4.1, which is the latest. You can find info on how to upgrade at the bottom of this JAMF Nation post:

NetSUS 4.1.0 Update

[stevewood · Accepted solution]

@SeanHarsh you can use repoutil --configure to re-create the preference file that Reposado uses to generate the catalogs. You can find more info here: Reposado Preferences

You may also try upgrading NetSUS to 4.1, which is the latest. You can find info on how to upgrade at the bottom of this JAMF Nation post:

NetSUS 4.1.0 Update

[g2oIT]

Looks like it was a corrupt upgrade of 4.0.0 as a re-upgrade to 4.1.0 resolved it without repoutil.

Thanks!

[g2oIT]

Ok, so the NetSUS appliance is showing El Capitan updates available, but my test machine running 10.11.1 can not see the newly activated 10.11.5 update. A look at the catalog xml file for the branch on this system does not give me any indication that there are any new updates showing in there.

[g2oIT · Accepted solution]

Looks to be an issue with mod rewrite. You have to modify /etc/apache2/sites-enabled/000-default.conf and change:

<Directory /srv/SUS/>
    Options Indexes FollowSymLinks MultiViews
    AllowOverride None
    Require all granted
</Directory>

To:

<Directory /srv/SUS/>
    Options Indexes FollowSymLinks MultiViews
    AllowOverride **All**
    Require all granted
</Directory>

You then add an .htaccess file to: /srv/SUS/html/content/catalogs/

With contents:

RewriteEngine On 
Options FollowSymLinks
RewriteBase /
RewriteCond %{HTTP_USER_AGENT} Darwin/8
RewriteRule ^index(.*).sucatalog$ content/catalogs/index$1.sucatalog [L] 
RewriteCond %{HTTP_USER_AGENT} Darwin/9 
RewriteRule ^index(.*).sucatalog$ content/catalogs/others/index-leopard.merged-1$1.sucatalog [L] 
RewriteCond %{HTTP_USER_AGENT} Darwin/10 
RewriteRule ^index(.*).sucatalog$ content/catalogs/others/index-leopard-snowleopard.merged-1$1.sucatalog [L] 
RewriteCond %{HTTP_USER_AGENT} Darwin/11 
RewriteRule ^index(.*).sucatalog$ content/catalogs/others/index-lion-snowleopard-leopard.merged-1$1.sucatalog [L] 
RewriteCond %{HTTP_USER_AGENT} Darwin/12 
RewriteRule ^index(.*).sucatalog$ content/catalogs/others/index-mountainlion-lion-snowleopard-leopard.merged-1$1.sucatalog [L] 
RewriteCond %{HTTP_USER_AGENT} Darwin/13 
RewriteRule ^index(.*).sucatalog$ content/catalogs/others/index-10.9-mountainlion-lion-snowleopard-leopard.merged-1$1.sucatalog [L]
RewriteCond %{HTTP_USER_AGENT} Darwin/14 
RewriteRule ^index(.*).sucatalog$ content/catalogs/others/index-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1$1.sucatalog [L]
RewriteCond %{HTTP_USER_AGENT} Darwin/15
RewriteRule ^index(.*).sucatalog$ content/catalogs/others/index-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1$1.sucatalog [L]

These changes seem to fix the issue.

There are rewrite rules contained in the 000-default.conf file that are the same as what is in the .htaccess file we added that do not seem to work. As these lines seem to be out of the box, there may be an error there.