Any server in a remote location can be used to host ZENworks Satellite and Content Repository on an NSS Volume. This enables optimization of hardware resources and network bandwidth.
OES 2017 SP1 as Satellite Server
The OES Server is running.
NSS volumes are mounted on the OES Server.
ZENworks Primary Server is running.
Few bundles are created and are available on the ZENworks Primary Server.
Discover and deploy ZENworks Agent on an OES Server by using ZENworks Configuration Management. To add the OES Server as a Satellite:
Log in to ZENworks Control Center.
Click Server Hierarchy > Action > Configure Satellite Server.
Browse for and select the OES Server to be added as a Satellite Server.
Select Content from the Satellite Server Roles list.
Click Configure.
In the Settings tab, change the port number from 80 to any other port which is not used for content and/or collection HTTPS requests. (Port 80 is used by the OES services).
In the Content Replication tab, select the Use Parent Primary Server Only as the content replication method and save the changes.
NOTE:You can also create a Closest Server Rule (Network Environment/Location) for agents to receive content from the Satellite Server.
Click Configuration and select the Satellite Server that has been configured.
Click Details and navigate to the Content tab.
Select the bundles and policies which need to be included for content replication.
In Server Hierarchy, click the arrow icon to navigate to the Satellite Server.
Select the Satellite Server, click Actions and select Configure Satellite Server.
In the Satellite Server Roles panel, click the Configure link for Content.
In the Configure Content Role panel, click Edit to configure the interval for content replication or create a new schedule by adding a new interval.
Click Edit to configure interval, throttle rate, duration, and schedule type for content.
Check the privileges of the content repo folder in the default location.
Navigate to the following directory to verify if the content is replicated successfully from the Primary Server to the Satellite Server:
/var/opt/novell/zenworks/content-repo/content # ls –lrt
Stop the ZENworks Agent on the Satellite Server by running the following command:
# /etc/init.d/novell-zenworks-xplatzmd stop
Create a user defined content repo under NSS mounted volume. For example:
/media/nss/VOL1/zendata/content-repo/
Copy the content data from the default location to the mounted volume as follows by running the following command:
cp /var/opt/novell/zenworks/content-repo/media/nss/VOL1/zendata
Rename the content-repo directory path to /var/opt/novell/zenworks/content-repo-backup.
Create a soft link by using the following command:
ln -s /media/nss/VOL1/zendata/content-repo/ /var/opt/novell/zenworks/content-repo
Start the ZENworks Agent on the Satellite Server by running the following command:
# /etc/init.d/novell-zenworks-xplatzmd start
Assign the bundle to any managed device.
Check the zmd-message logs to ensure that the content is replicated successfully from the Satellite Server to the managed device. You can find the logs in the following location for a Windows managed device:
C:\Program Files (x86)\Novell\ZENworks\logs\LocalStore