4.4.1.2. Deployment Steps

To ensure that the use case that we are deploying works correctly, it is necessary to carefully follow the steps we indicate. These may change depending on the requirements and needs in our case.

The mandatory and optional steps are detailed below. Remember it will depend on your specific case.

Architecture

  • Architecture: The first step is the deployment of the nodes needed for this use case. Here we will find the necessary information related to the architecture of the use case. A detailed explanation of the deployment of each one of the nodes can be found in Deployment and basic configuration

Administration

  • Define the UD Tag Policies: Through the use of UD Tag Policies, we can determine the compliance status of a device based on the tags that have been assigned to it. This will allow us to create custom tags for each level of compliance based on their characteristics.

Optional:

  • Define the UD Tag Application Requirements: With the use of the ON Agent, we can obtain information related to the applications and updates installed on the equipment. The UD Tag Application Requirements allow us to verify the compliance of a device based on the installed applications and the minimum version of these.

  • Define the Profiling: Improving the profiling process can be important for this use case since it can allow us to perform one compliance or another based on the type of device, as well as increase the information available to improve compliance rules.

Operation

  • Operation : In this step we will start operating the use case and checking that all the functionalities are working as expected. If we find some unexpected behavior we can go to the troubleshooting step in order to find and fix the issue.

Monitoring

  • Monitoring : At this point we will see how the data is being ingested and saved in ON Analytics. To check this, we can open the different visualizations available for this use case.

Troubleshooting