To Configure a Host for Registration:

1. Take note of the fully qualified domain name (FQDN) of the Satellite Server or Capsule Server, for example server.example.com.
2. In a terminal, connect to the host as the root user.

3. Install the consumer RPM from the Satellite Server or Capsule Server to which the host is to be registered. The consumer RPM updates the content source location of the host and allows the host to download content from the content source specified in Red Hat Satellite.

   # rpm -Uvh http://server.example.com/pub/katello-ca-consumer-latest.noarch.rpm

   Important

   Any running Docker Daemons will be restarted.

   Note

   The RPM package is not signed, if required, you can add the --nosignature option to install the package. The katello-ca-consumer-hostname-1.0-1.noarch.rpm is an additional katello-ca-consumer RPM available that contains the server’s host name. The katello-ca-consumer-latest.noarch.rpm rpm will always reflect the most recent version. Both serve the same purpose.

To Register Hosts:

1. In a terminal, connect to the host as the root user.

2. Clear any old host data related to Red Hat Subscription Manager (RHSM):

   # subscription-manager clean

3. Register the host using RHSM:

   # subscription-manager register --org=your_org_name \
   --activationkey=your_activation_key

   Example 3.1. Command Output after Registration:

   # subscription-manager register --org=MyOrg --activationkey=TestKey-1
   The system has been registered with id: 62edc0f8-855b-4184-b1b8-72a9dc793b96

To Verify the Red Hat Satellite Tools 6 Repository is Enabled:

1. Open the Satellite web UI, navigate to Content > Red Hat Repositories and click the RPMs tab.
2. Find and expand the Red Hat Enterprise Linux Server item.

3. Find and expand the Red Hat Satellite Tools 6 (for RHEL VERSION Server) (RPMs) item.

   If the Red Hat Satellite Tools 6 items are not visible, it may be because they are not included in the subscription manifest obtained from the Customer Portal. To correct that, log in to the Customer Portal, add these repositories, download the subscription manifest and import it into Satellite.

4. Ensure the Enabled check box beside the repository’s name is selected. If not, select it.

To Install Katello Agent:

1. On the host, verify that the rhel-version-server-satellite-tools-6-rpms repository is enabled. If you registered the host using an activation key with auto-attach enabled, the repository is enabled automatically already.

   # yum repolist enabled | grep -i rhel-version-server-satellite-tools-6-rpms

   If the rhel-version-server-satellite-tools-6-rpms is not enabled, enable it using the following command:

   # subscription-manager repos --enable=rhel-version-server-satellite-tools-6-rpms

2. Install the katello-agent RPM package using the following command:

   # yum install katello-agent

3. Ensure the goferd service is running.

   • On Red Hat Enterprise Linux 6, run the following command:

     # service goferd start

   • On Red Hat Enterprise Linux 7, run the following command:

     # systemctl start goferd

1. On the content host, install the katello-host-tools-tracer RPM package:

   # yum install katello-host-tools-tracer

2. Enter the following command:

   # katello-tracer-upload

3. Verify that Tracer is installed.

   1. In the Satellite web UI, navigate to Hosts > All hosts, and then click on the required host name.
   2. In the Properties tab examine the Properties table, and then find the Traces item. If you cannot find a Traces item in the Properties table, then Tracer is not installed.

1. In the Satellite web UI, navigate to Hosts > Content Hosts, and then click on the required host name.
2. Click on the Traces tab to view any displayed Traces.

To Verify the Red Hat Satellite Tools 6 Repository is Enabled:

1. Open the Satellite web UI, navigate to Content > Red Hat Repositories and click the RPMs tab.
2. Find and expand the Red Hat Enterprise Linux Server item.

3. Find and expand the Red Hat Satellite Tools 6 (for RHEL VERSION Server) (RPMs) item.

   If the Red Hat Satellite Tools 6 items are not visible, it may be because they are not included in the subscription manifest obtained from the Customer Portal. To correct that, log in to the Customer Portal, add these repositories, download the subscription manifest and import it into Satellite.

4. Ensure the Enabled check box beside the repository’s name is selected. If not, select it.

To Install and Enable the Puppet Agent:

1. On the host, open a terminal console and log in as the root user.

2. Verify that the rhel-version-server-satellite-tools-6-rpms repository is enabled, using the following command:

   # yum repolist enabled | grep -i rhel-version-server-satellite-tools-6-rpms

   If the rhel-version-server-satellite-tools-6-rpms is not enabled, enable it using the following command:

   # subscription-manager repos --enable=rhel-version-server-satellite-tools-6-rpms

3. Install the Puppet agent RPM package using the following command:

   # yum install puppet

4. Configure the puppet agent to start at boot:

   1. On Red Hat Enterprise Linux 6:

      # chkconfig puppet on

   2. On Red Hat Enterprise Linux 7:

      # systemctl enable puppet

To Configure the Puppet Agent:

1. Configure the Puppet agent by specifying the server and environment settings in the /etc/puppet/puppet.conf file:

   # vi /etc/puppet/puppet.conf

   [main]
       # The Puppet log directory.
       # The default value is '$vardir/log'.
       logdir = /var/log/puppet
   
       # Where Puppet PID files are kept.
       # The default value is '$vardir/run'.
       rundir = /var/run/puppet
   
       # Where SSL certificates are kept.
       # The default value is '$confdir/ssl'.
       ssldir = /var/lib/puppet/ssl
   
   ...
   
   [agent]
       # The file in which puppetd stores a list of the classes
       # associated with the retrieved configuratiion.  Can be loaded in
       # the separate ``puppet`` executable using the ``--loadclasses``
       # option.
       # The default value is '$confdir/classes.txt'.
       classfile = $vardir/classes.txt
       pluginsync = true
       report = true
       ignoreschedules = true
       daemon = false
       ca_server = satellite.example.com
       server = satellite.example.com
       environment = KT_Example_Org_Library_RHEL6Server_3
   
       # Where puppetd caches the local configuration.  An
       # extension indicating the cache format is added automatically.
       # The default value is '$confdir/localconfig'.
       localconfig = $vardir/localconfig
   
   ...

   Important

   Set the environment parameter to the name of the Puppet environment to which the host belongs. A Puppet environment is a collection of Puppet modules that can be associated with a host or a host group.

   • To find the host’s Puppet environment, navigate to Hosts > All Hosts and inspect the Environment column in the host table.
   • To assign a Puppet environment to a host, navigate to Hosts > All Hosts and click Edit next to the selected host.
   • To list Puppet environments enabled on the Satellite Server, navigate to Configure > Environments. You can also inspect the /etc/puppet/environments/ directory on the Satellite Server to find what Puppet modules and manifests are associated with Puppet environments.

   For more information see the Red Hat Satellite Puppet Guide.

2. Run the Puppet agent on the host:

   # puppet agent -t --server satellite.example.com

3. Sign the SSL certificate for the Puppet client through the Satellite Server web UI:

   1. Log in to the Satellite Server through the web UI.
   2. Select Infrastructure > Capsules.
   3. Select Certificates from the drop-down menu to the right of the required Capsule.
   4. Click Sign to the right of the required host.

   5. Enter the puppet agent command again:

      # puppet agent -t --server satellite.example.com

1. Ensure you are in the correct directory. For example, to change to /root:

   # cd

2. Download the script:

   # curl -O http://satellite6.example.com/pub/bootstrap.py

   This installs the script in the current directory.

3. Make the script executable:

   # chmod +x bootstrap.py

4. To confirm that the script can now be run, view the usage statement as follows:

   # ./bootstrap.py -h

5. Optionally, when the transition process is complete, remove the script:

   # cd
   # rm bootstrap.py

Using the web UI to set permissions for the bootstrap script:

1. Navigate to Administer > Users.
2. Select an existing user or create a new user especially for the purpose of running this script. Users are located under the Username field. A new pane will open with tabs to modify information about the selected user.
3. Click the Roles tab.

4. Select Viewer and Edit hosts from the Roles list. The selected roles should appear on the Selected Items list confirming that they have been selected.

   Warning

   Be aware that the following role Edit hosts allows the user to edit and delete hosts as well as being able to add hosts. If this is not acceptable to your security policy, create a new role with the minimal permissions required by the bootstrap script. Create the bootstrap role using the Hammer command line tool, see Using Hammer to set permissions for the bootstrap script:, then assign this role alone, to the user who will be running the bootstrap script. Alternatively, create an appropriate role using the web UI, navigate to Administer > Roles. Subsequently, use the web UI to create a role and set up the appropriate filters.

5. Click Submit. The permissions required for the bootstrap script to run will now be set for the user you have specified.

Using Hammer to set permissions for the bootstrap script:

1. Create a role with the minimum permissions required by the bootstrap script. This example creates a role with the name Bootstrap. Modify this to provide a more specific name if you wish.

   $ ROLE='Bootstrap'
   $ hammer role create --name "$ROLE"
   $ hammer filter create --role "$ROLE" --permissions view_organizations
   $ hammer filter create --role "$ROLE" --permissions view_locations
   $ hammer filter create --role "$ROLE" --permissions view_domains
   $ hammer filter create --role "$ROLE" --permissions view_hostgroups
   $ hammer filter create --role "$ROLE" --permissions view_hosts
   $ hammer filter create --role "$ROLE" --permissions view_architectures
   $ hammer filter create --role "$ROLE" --permissions view_ptables
   $ hammer filter create --role "$ROLE" --permissions view_operatingsystems
   $ hammer filter create --role "$ROLE" --permissions create_hosts

2. Assign the new role to an existing user.

   $ hammer user add-role --id user_id --role Bootstrap

   There is also the option to create a new user and assign this new role to them. For more information on how to create users through Hammer see Creating Users in the Red Hat Satellite Hammer CLI Guide.

To Add a Physical Interface:

1. Navigate to Hosts > All hosts to view available hosts.
2. Click Edit next to the host you want to edit.
3. On the Interfaces tab, click Add Interface.
4. Keep the Interface option selected in the Type menu.
5. Specify a MAC address of the additional interface. This setting is required.
6. Specify the device Identifier, for example eth0 or eth1.1. Identifier is used for bonded interfaces (in the Attached devices field, see ]), VLANs and aliases (in the Attached to field, see xref:proc-Red_Hat_Satellite-Managing_Hosts-Adding_a_Virtual_Interface-To_Add_a_Virtual_Interface[).
7. Specify the DNS name associated with the host’s IP address. Satellite saves this name in the Capsule Server associated with the selected domain (the "DNS A" field) and the Capsule Server associated with the selected subnet (the "DNS PTR" field). A single host can therefore have several DNS entries.
8. Select a domain from the Domain drop-down menu. To create and manage domains, navigate to Infrastructure > Domains.
9. Select a subnet from the Subnet drop-down menu. To create and manage subnets, navigate to Infrastructure > Subnets.
10. Specify the interface IP address. Managed interfaces with assigned DHCP Capsule Server require this setting for creating a DHCP lease. DHCP-enabled managed interfaces provide an automatic suggestion of IP address.
11. Decide if the interface will be managed. If the Managed check box is selected, the interface configuration is pulled from the associated Capsule Server during provisioning, and DNS and DHCP entries are created. If using kickstart provisioning, a configuration file is automatically created for the interface.
12. Select the Virtual NIC check box to create a virtual interface. See Section 3.11.2, “Adding a Virtual Interface” for details.
13. Click OK to save the interface configuration, and then click Submit to apply the changes to the host.

To Add a Virtual Interface:

1. Navigate to Hosts > All hosts to view available hosts.
2. Click Edit next to the host you want to edit.
3. On the Interfaces tab, click Add Interface.
4. Keep the Interface option selected in the Type menu.

5. Specify the general interface settings. The applicable configuration options are the same as for the physical interfaces described in Section 3.11.1, “Adding a Physical Interface”.

   Specify MAC address for managed virtual interfaces so that the configuration files for provisioning are generated correctly. However, MAC address is not required for virtual interfaces that are not managed.

   If creating a VLAN, specify ID in the form of eth1.10 in the Identifier field. If creating an alias, use ID in the form of eth1:10.

6. Select the Virtual NIC check box. Additional configuration options specific to virtual interfaces are appended to the form:

   • Tag: You can specify tags per interface to provide a higher-level segmentation of the network. If left blank, managed interfaces inherit the tag form the VLAN ID of the associated subnet, given that this subnet has the VLAN ID specified. User-specified entries from this field are not applied on alias interfaces.
   • Attached to: Specify the identifier of the physical interface to which the virtual interface belongs, for example eth1. This setting is required.
7. Click OK to save the interface configuration. Then click Submit to apply the changes to the host.

To Add a Bonded Interface:

1. Navigate to Hosts > All hosts to view available hosts.
2. Click Edit next to the host you want to edit.
3. On the Interfaces tab, click Add Interface.
4. Select Bond from the Type menu. Additional type-specific configuration options are appended to the form.
5. Specify the general interface settings. The applicable configuration options are the same as for the physical interfaces described in Section 3.11.1, “Adding a Physical Interface”. Bonded interfaces use IDs in the form of bond0 in the Identifier field. It is sufficient if you specify a single MAC address in the MAC address field.

6. Specify the configuration options specific to bonded interfaces:

   • Mode: Select the bonding mode that defines a policy for fault tolerance and load balancing. See Table 3.2, “Bonding Modes Available in Red Hat Satellite” for a brief description of individual bonding modes.
   • Attached devices: Specify a comma separated list of identifiers of attached devices. These can be physical interfaces or VLANs.
   • Bond options: Specify a space separated list of configuration options, for example miimon=100. There are several configuration options you can specify for the bonded interface, see Red Hat Enterprise Linux 7 Networking Guide for details.
7. Click OK to save the interface configuration. Then click Submit to apply the changes to the host.

To Enable BMC Power Management on an Existing Capsule Server:

1. Use the satellite-installer routine to configure BMC power management on the Capsule Server by running the following command with the following options:

   # satellite-installer --foreman-proxy-bmc=true \ --foreman-proxy-bmc-default-provider=ipmitool

2. Refresh the features for the Capsule Server.

   1. Log in to the Satellite web UI, and navigate to Infrastructure > Capsules.
   2. Identify the Capsule Server whose features you need to refresh. In the drop-down list on the right, click Refresh. The list of features in the Features column should now include BMC.

To Add a BMC Interface:

1. Navigate to Hosts > All hosts to view available hosts.
2. Click Edit next to the host you want to edit.
3. On the Interfaces tab, click Add Interface.
4. Select BMC from the Type menu. Type-specific configuration options are appended to the form.
5. Specify the general interface settings. The applicable configuration options are the same as for the physical interfaces described in Section 3.11.1, “Adding a Physical Interface”.

6. Specify the configuration options specific to BMC interfaces:

   • Username, Password: Specify any authentication credentials required by BMC.
   • Provider: Specify the BMC provider.
7. Click OK to save the interface configuration, and then click Submit to apply the changes to the host.

To Add Packages to Host Collections:

1. Click Hosts > Host Collections.
2. Click the host collection where the package should be added.
3. On the Collection Actions tab, click Package Installation, Removal, and Update.
4. To update all packages, click the Update All Packages button to use the default method. Alternatively, select the drop-down icon to the right of the button to select a method to use. Selecting the via remote execution - customize first menu entry will take you to the Job invocation page where you can customize the action.
5. Select the Package or Package Group radio button as required.

6. In the field provided, specify the package or package group name. Then click:

   • Install — to install a new package using the default method. Alternatively, select the drop-down icon to the right of the button and select a method to use. Selecting the via remote execution - customize first menu entry will take you to the Job invocation page where you can customize the action.
   • Update — to update an existing package in the host collection using the default method. Alternatively, select the drop-down icon to the right of the button and select a method to use. Selecting the via remote execution - customize first menu entry will take you to the Job invocation page where you can customize the action.

To Add Errata to a Host Collection:

1. Click Hosts > Host Collections.
2. Select the host collection where the errata should be added.
3. On the Collection Actions tab, click Errata Installation.
4. Select the errata you want to add to the host collection and click the Install Selected button to use the default method. Alternatively, select the drop-down icon to the right of the button to select a method to use. Selecting the via remote execution - customize first menu entry will take you to the Job invocation page where you can customize the action.

To Create a Job Template:

1. Navigate to Hosts > Job templates.
2. Click New Job Template. As an alternative, you can modify an existing template – in the Actions column, select Clone from the drop-down menu.

3. Configure the job template:

   1. On the Template tab, enter a unique name for your job template. Select Default to make the template available for all organizations and locations. You can insert the template manually using Template editor or upload it from a text file by clicking Browse. Templates use Embedded Ruby (ERB) template syntax, see ] for more information. An advanced template is required, for example, for executing jobs that perform power actions; see xref:exam-Managing_Hosts-Including_Power_Actions_in_Templates[ for information on how to include the Power Action - SSH Default template in a custom template.
   2. On the Job tab, you can define the job category (define your own or select from the default categories listed in ]) as well as the effective user; these settings can be configured also when invoking the job (see xref:proc-Managing_Hosts-Executing_a_Remote_Job[). You can also define input parameters for template commands. These parameters are then requested when executing the job.
   3. Remaining tabs enable setting the template type, organizations and locations as well as viewing the template history.
4. Click Submit. When the page refreshes, your new template should appear in the list of job templates.

To Execute a Remote Job:

1. Navigate to Hosts > All hosts and select the target hosts for your job. You can use the search field to narrow down the host list.
2. From the Select Action menu at the upper right of the screen select Schedule Remote Job. This will take you to the Job invocation page. Alternatively, if you target just one host, click its name and click Schedule Remote Job on the host information page. Note that you can invoke jobs also from the Job Templates page by using the Run button.

3. On the Job invocation page, define the main job settings:

   1. Select the Job category and the Job template you want to use. These settings are required.
   2. Optionally, select a stored search string in the Bookmark list to specify the target hosts.
   3. Optionally, further limit the targeted hosts by inserting a Search query. The Resolves to line displays the number of hosts affected by your query. Use the refresh button to recalculate the number after changing the query. The preview icon will list the targeted hosts.
   4. The remaining settings depend on the selected job template. See To Create a Job Template: for information on adding custom parameters to a template.

4. Clicking Display advanced fields will show advanced setting for the job. Some of the advanced settings depend on the job template, the following settings are general:

   • Effective user defines the user for executing the job, by default it is the SSH user.
   • Concurrency level defines maximum number of jobs executed at once, which can prevent overload of systems' resources in a case of executing the job on a large number of hosts.
   • Time span defines time interval in seconds after which the job should be killed, if it is not finished already. A task which could not be started during the defined interval, for example, if the previous task took too long to finish, is canceled.

   • Type of query defines when the search query is evaluated. This helps to keep the query up to date for scheduled tasks.

     Concurrency level and Time span settings enable you to tailor job execution to fit your infrastructure hardware and needs.

5. If you want to execute the job immediately, ensure that Schedule is set to Execute now. You can also define a one-time future job, or set up a recurring job. For recurring tasks, you can define start and end dates, number and frequency of runs. You can also use cron syntax to define repetition. For more information about cron, see the Automating System Tasks section of the Red Hat Enterprise Linux 7 System Administrator’s Guide.
6. Click Submit. This displays the Job Overview page, and when the job completes, also displays the status of the job.

To Monitor a Job:

1. Navigate to the Job page. This page is automatically displayed if you triggered the job with the Execute now setting. To monitor scheduled jobs, navigate to Monitor > Jobs and select the job run you wish to inspect.
2. On the Job page, click the Hosts tab. This displays the list of hosts on which the job is running.
3. In the Host column, click the name of the host that you want to inspect. This displays the Detail of Commands page where you can monitor the job execution in real time.
4. Click Back to Job at any time to return to the Job Details page.

To Configure PXE-booting for host discovery:

1. In the Satellite web UI, navigate to Hosts > Provisioning Templates.
2. In the upper-right of the Provisioning Templates page, click Build PXE Default, and click OK.

To Manually Provision a Discovered Host:

1. Navigate to Hosts > Discovered Hosts.
2. Select the host you want to provision and click Provision.
3. On the host’s Edit page, complete the necessary details, and then click Save.

To Decommission a Discovered Host:

1. Shut down the host.
2. Navigate to Hosts > Discovered Hosts.
3. In the Name column find the host you want to decommission and then select Delete from the corresponding Edit drop-down menu.

To Create a Provisioning Rule:

1. Navigate to Configure > Discovery rules.

2. Click New Rule. Specify the following parameters of the provisioning rule:

   • Name is the name of the rule displayed in the list of rules. This name must not contain spaces or non-alphanumeric characters.
   • Search is the search statement used to match discovered hosts for the particular rule. You can use scoped search syntax to define it. See Section 6.4.4, “Scoped Search Syntax” for examples of using scoped search.
   • Host Group is the host group to be assigned to a matching host before starting the provisioning process. Make sure that the selected host group has all the required parameters set; required parameters are marked with an asterisk (*).
   • Hostname defines a pattern for assigning human-readable host names to the matching hosts. When left blank, the host name is assigned in the format "macMACADDRESS" by default. The same syntax used for provisioning templates is used in this instance. See Section 6.4.5, “Host Name Patterns” for more information and examples.
   • Hosts limit is the maximum number of provisioned hosts per rule. If the limit is reached, the rule will not take effect until one or more hosts are deleted. Typical use cases are rules per server rack or row when it is necessary to change provisioning parameters such as host name or host group per entry. You can set this value to zero (0) to specify no limit.
   • Priority specifies the order of execution of rules. The value must be greater than or equal to zero. A lower value indicates a higher priority. If two rules have the same priority, the first rule encountered is applied.
   • Enabled provides the option to temporarily enable or disable rules.
3. Click Submit to save the rule.

To Enable Automatic Provisioning:

1. Navigate to Administer > Settings > Discovered in the Satellite web UI.
2. Locate Auto provisioning in the Name column, and set its value to true.
3. Click Save.

To Create a Host:

1. Click Hosts > Create Host.

2. On the Host tab, enter the required details:

   1. In the Name field, enter the host name, for example host1.example.com.
   2. In the Organization field, enter the organization name, for example MyOrg.
   3. In the Location field, enter the location name, for example MyLoc.
3. Optionally, on the Puppet Classes tab, select the Puppet classes you want to include.

4. On the Interfaces tab, edit the primary interface:

   1. Click the Edit button in the Actions column.
   2. Select a type from the Type drop-down menu, for example Interface.
   3. In the MAC address field, enter the MAC address of your host.
   4. In the Device Identifier field, specify the device identifier for this interface, for example eth0.
   5. In the DNS name field, specify the DNS name of your host. For the primary interface, this host name is used with the domain name to form the FQDN.
   6. Select a domain from the Domain drop-down menu, for example satellite.example.com. This automatically updates the IPv4 Subnet and IPv6 Subnet lists with a selection of available subnets. Optionally, select the subnets.
   7. In the IPv4 address field, specify the IPv4 address of your host.
   8. Click Ok.

5. On the Operating System tab, enter the required details:

   1. Select an architecture from the Architecture drop-down menu, for example x86_64.
   2. Select an operating system from the Operating system drop-down menu, for example RHEL Server 7.4.
   3. Select a partition table from the Partition table drop-down menu, for example Kickstart default.
   4. In the Root password field, enter the root password for your host.
6. Optionally, on the Parameters tab, select the parameters you want to supply to the Puppet master to override the default values.
7. Optionally, on the Additional Information tab, enter additional information about the host.
8. Click Submit.

To Register the Host:

1. In a terminal, connect to the host as the root user.

2. Ensure that a time synchronization tool is enabled and running on the host:

   # systemctl start chronyd; systemctl enable chronyd

3. Install the consumer RPM from the Satellite Server or Capsule Server to which the host is to be registered. The consumer RPM updates the content source location of the host and allows the host to download content from the content source specified in Red Hat Satellite.

   # rpm -Uvh http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm

4. Ensure that an activation key associated with the appropriate Content View and environment exists for the host. If not, see Managing Activation Keys in the Content Management Guide for more information.

5. Clear any old host data related to Red Hat Subscription Manager (RHSM):

   # subscription-manager clean

6. Register the host using RHSM:

   # subscription-manager register --org=MyOrg \
   --activationkey=my_activation_key

   Command output after registration:

   # subscription-manager register --org=MyOrg --activationkey=my_activation_key
   The system has been registered with id: 62edc0f8-855b-4184-b1b8-72a9dc793b96

7. Enable the Red Hat Satellite Tools 6 repository:

   # subscription-manager repos --enable=rhel-version-server-satellite-tools-6-rpms

8. Install the katello-agent:

   # yum install katello-agent

9. Ensure the goferd service is running:

   # systemctl start goferd

10. Install and configure the Puppet agent:

    1. Install the Puppet agent:

       # yum install puppet

    2. Configure the Puppet agent to start at boot:

       # systemctl enable puppet

    3. Configure the Puppet agent by specifying the server and environment settings in the /etc/puppet/puppet.conf file:

       # vi /etc/puppet/puppet.conf

       [main]
           # The Puppet log directory.
           # The default value is '$vardir/log'.
           logdir = /var/log/puppet
       
           # Where Puppet PID files are kept.
           # The default value is '$vardir/run'.
           rundir = /var/run/puppet
       
           # Where SSL certificates are kept.
           # The default value is '$confdir/ssl'.
           ssldir = /var/lib/puppet/ssl
       
       ...
       
       [agent]
           # The file in which puppetd stores a list of the classes
           # associated with the retrieved configuratiion.  Can be loaded in
           # the separate ``puppet`` executable using the ``--loadclasses``
           # option.
           # The default value is '$confdir/classes.txt'.
           classfile = $vardir/classes.txt
           pluginsync = true
           report = true
           ignoreschedules = true
           daemon = false
           ca_server = satellite.example.com
           server = satellite.example.com
           environment = KT_Example_Org_Library_RHEL7Server
       
           # Where puppetd caches the local configuration.  An
           # extension indicating the cache format is added automatically.
           # The default value is '$confdir/localconfig'.
           localconfig = $vardir/localconfig
       
       ...

    4. Run the Puppet agent on the host:

       # puppet agent -t --waitforcert 10 --server satellite.example.com

    5. Sign the SSL certificate for the Puppet client through the Satellite Server web UI:

       1. Log in to the Satellite Server through the web UI.
       2. Select Infrastructure > Capsules.
       3. Select Certificates from the drop-down menu to the right of the required Capsule.
       4. Click Sign to the right of the required host.

       5. Enter the puppet agent command again:

          # puppet agent -t --server satellite.example.com

To Execute a Remote Job:

1. Navigate to Hosts > All hosts and select the target host, in our example host1.example.com.
2. From the Select Action menu at the upper right of the screen select Schedule Remote Job.

3. On the Job invocation page, define the main job settings:

   1. Select a job category from the Job category drop-down menu, for example Commands.
   2. Select a job template from the Job template drop-down menu, for example Run Command - SSH Default.
   3. In the command field, enter the command you want to run on the host. For example, timedatectl set-timezone Europe/Prague will set the time zone to Prague in Europe.
4. Click Submit.