A Satellite is a managed device that can perform some of the roles that a ZENworks Primary Server normally performs, including authentication, information collection, content distribution, and imaging. A Satellite can be any managed Windows or Linux device (server or workstation), but not a Primary Server. For more information, see Managed Device Requirements” in the ZENworks System Requirements and Deploying the ZENworks Agent
in the ZENworks Discovery, Deployment, and Retirement Reference.
NOTE:ZENworks no longer allows you to promote a 32-bit device to the Satellite Server role or add a new role to an existing 32-bit Satellite Server. However, ZENworks will continue to support the existing 32-bit Satellite Servers.
When you configure a Satellite, you specify which roles it performs (Authentication, Collection, Content, or Imaging). A Satellite can also perform roles that might be added by third-party products that are snap-ins to the ZENworks framework.
You might, for example, create a Satellite in a location across a slow WAN link and create Closest Server rules to offload one or more roles from the Primary Server to the newly created Satellite to improve the performance of your ZENworks system.
NOTE:For information about Satellites from the perspective of an end user using the ZENworks Agent, see Satellite Roles
in the ZENworks Agent Guide.
The following sections contain more information:
Section 22.0, Manually Replicating Content from a Primary Server to Satellite Devices
Section 23.0, Moving a Satellite from One Primary Server to Another Primary Server
Section 24.0, Specifying a Different Repository for the Content Role Satellite (Windows Only)
Section 25.0, Specifying a Different Repository for Content Role Satellite (Linux Only)
Section 26.0, Promoting an RHEL 6 device as a Content or Collection Role Satellite
Section 27.0, Promoting a Macintosh Device to Be a Content Role Satellite Server
Section 28.0, Promoting a Macintosh Device to Be a Collection Role Satellite Server