Seeing "Evaluated to False" in your SCCM (System Center Configuration Manager) deployments can be frustrating. This message indicates that a condition within your deployment hasn't been met, preventing the software from installing. This comprehensive guide provides simple troubleshooting steps to identify and resolve the issue, getting your deployments back on track.
Understanding "Evaluated to False" in SCCM
Before diving into troubleshooting, let's understand what this message means. SCCM uses various criteria to determine if a device is eligible for a particular application or software deployment. These criteria can include things like:
- Operating System: Is the target device running a compatible OS version?
- Hardware Inventory: Does the device meet specific hardware requirements (e.g., sufficient RAM, disk space)?
- Software Inventory: Is prerequisite software already installed?
- Custom Queries: Are there any custom rules defined that must be true for the deployment to proceed?
If any of these conditions evaluate to "False," the deployment will not proceed, and you'll see the "Evaluated to False" message in the SCCM console.
Common Causes and Troubleshooting Steps
Let's address some of the most frequent causes of "Evaluated to False" and provide step-by-step troubleshooting:
1. Incorrect Operating System Targeting
Problem: The deployment might be targeting an operating system that doesn't match the client's actual OS version.
Troubleshooting:
- Verify Target OS: In the SCCM console, double-check the deployment's properties, specifically the "Operating System" targeting section. Ensure it accurately reflects the OS versions of the affected devices.
- Check Client OS: Use SCCM's reporting features or remote tools to confirm the actual operating system versions on the devices reporting "Evaluated to False." Discrepancies need to be resolved.
- Adjust Targeting: If inconsistencies exist, refine the deployment's OS targeting to match the clients accurately.
2. Missing Prerequisite Software
Problem: The deployment might require prerequisite software that's missing on the target devices.
Troubleshooting:
- Identify Prerequisites: Review the deployment's properties to identify any required prerequisites.
- Check for Prerequisites: Verify if these prerequisites are installed on the affected devices using SCCM's software inventory or other inventory management tools.
- Deploy Prerequisites: If prerequisites are missing, create and deploy them separately before deploying the main application.
3. Hardware Requirements Not Met
Problem: The target device might lack the necessary hardware resources (RAM, disk space, etc.) specified in the deployment.
Troubleshooting:
- Review Hardware Requirements: Examine the deployment's properties for specified hardware requirements.
- Check Device Specifications: Use SCCM's hardware inventory or other tools to check the hardware specifications of the affected devices.
- Adjust Requirements or Reimage: If hardware requirements aren't met, you'll need to either adjust the deployment's requirements or replace the hardware on affected devices.
4. Incorrect or Conflicting Custom Queries
Problem: Custom queries used in deployment targeting might contain errors or conflicts.
Troubleshooting:
- Review Custom Queries: Carefully examine the SQL query used for custom targeting. Look for syntax errors, incorrect field names, or conflicting conditions.
- Test the Query: Test your custom query separately to ensure it returns the expected results.
- Simplify the Query (If Complex): Break down complex queries into smaller, simpler ones for easier troubleshooting.
5. Client Communication Issues
Problem: The SCCM client on the target device might be having trouble communicating with the management point.
Troubleshooting:
- Check Client Status: Review the client's status in the SCCM console. Look for errors related to communication or policy retrieval.
- Check Network Connectivity: Ensure the client has proper network connectivity to the management point, including DNS resolution and firewall settings.
- Restart the SCCM Client: Try restarting the SCCM client service on the affected devices.
6. Policy Conflicts
Problem: Conflicting policies might be interfering with the deployment.
Troubleshooting:
- Review All Applicable Policies: Check for any other policies that might be affecting the deployment. This could involve reviewing device settings, software settings, or other policies relevant to the deployment process.
- Prioritize Policies: If there are conflicts, prioritize the necessary policies to ensure the desired deployment occurs.
By systematically checking these common causes and following the troubleshooting steps, you'll significantly improve your chances of resolving the "Evaluated to False" issue and successfully deploying your applications via SCCM. Remember to always document your findings and changes for future reference and to improve your SCCM management processes.
