Troubleshooting

Understand these common issues and their resolutions, so that you can effectively troubleshoot and resolve problems encountered while managing and monitoring Fixlet Streams, ensuring smooth and efficient deployment processes.

Error Fetching Devices

Issue: When attempting to apply dynamic filters, you may encounter the error message: "Error fetching devices. Please try again."

Causes:

• Incorrectly defined filter conditions.
• Attributes or values that do not exist in the device database.
• Network connectivity issues preventing the system from querying devices.

Resolutions:

• Validate Conditions: Review the conditions you set for the dynamic filters. Ensure that attributes, conditions, and values are correctly specified and applicable to your devices.
• Test with Simplified Filters: Temporarily simplify your conditions to isolate the problematic parameter. Start with broad filters and then narrow down to identify the issue.
• Check Network Connectivity: Ensure that the system has access to the necessary network resources to fetch device information.

Low Fixlet Compliance Percentage

Issue: The Fixlet compliance percentage is lower than expected after a deployment.

Causes:

• Devices may not meet the dynamic filter criteria.
• There may be compatibility issues preventing devices from applying the Fixlet.
• Some devices may be offline or not connected during deployment.

Resolutions:

• Review Filter Conditions: Check if the dynamic filters are too restrictive. Adjust conditions to include more devices if necessary.
• Investigate Compatibility: Ensure that the Fixlet is compatible with the targeted devices (e.g., OS version, hardware requirements).
• Check Device Status: Confirm that all intended devices are online and connected. Consider scheduling the deployment during a time when devices are most likely to be active.

Deployment Progress Stalled

Issue: The deployment progress bar shows little to no movement over an extended period.

Causes:

• High network traffic or bandwidth limitations.
• Issues with the Fixlet itself, such as improper configuration.
• Large numbers of devices being targeted, causing slow processing.

Resolutions:

• Monitor Network Performance: Check network traffic and performance to ensure it can support the deployment. Consider deploying during off-peak hours.
• Verify Fixlet Configuration: Ensure that the Fixlet is configured correctly without any errors that could cause it to stall.
• Segment Deployments: If targeting a large group of devices, consider segmenting the deployment into smaller groups to expedite the process.