Fix for 'Selected machine pool does not contain any targets of this type' (Windows HLK)

It seems like the issue you are encountering, where the selected machine pool does not contain any targets of the type you are testing, can be related to several factors. Here are some troubleshooting steps you can take:

1. Ensure Proper Installation: Verify that the HLK Client is correctly installed on the Test Client server. If the installation was not successful, it may lead to no targets being detected.
2. Check Compatibility: Make sure that the drivers or software you are trying to test are compatible with the version of Windows Server you are using on the Test Client. If they are not compatible, they may not appear as targets.
3. Machine Pool Configuration: Double-check the configuration of your machine pool in HLK Studio. Ensure that the Test Client is correctly added to the pool and that it is set to "Ready".
4. Target Visibility: In HLK Studio, navigate to the Selection tab and ensure that you are looking at the correct view (e.g., systems, device and printers, device manager, or software device). Sometimes, targets may not appear if the wrong view is selected.
5. Refresh Data: Try refreshing the data in HLK Studio. You can do this by restarting the HLK Client on the Test Client server or by reinstalling the HLK Client if necessary.
6. Check for Heartbeats: Since you mentioned that the Controller receives heartbeats from the Client, ensure that the communication between them is stable and there are no network issues.

If after trying these steps you still do not see any targets, consider reviewing the installation logs for any errors during the HLK Client setup or checking the Microsoft documentation for any additional troubleshooting steps specific to your setup.

References:

• Troubleshooting Windows HLK Client
• Step 5: Select target to test

Hello,

Thank you for reaching out to the Microsoft Q&A community. 

This error typically occurs when the compute cluster in your Azure Machine Learning workspace is not ready to execute the job. This can be due to the cluster being in the process of scaling up from zero nodes or being in an updating or failed state.

Here are the steps you can take:

1. Check the status of your compute cluster:

• Navigate to your Azure Machine Learning Studio.
• In the left-hand menu, go to the Compute section.
• Find your compute cluster and check its state. Ensure it is in the "Succeeded" state and that the number of nodes is greater than zero. If the cluster is in a "Resizing" state, please wait for the process to complete before resubmitting your job.

2. Verify the cluster's node count:

• If your compute cluster is configured to scale down to a minimum of zero nodes, it may take a few minutes for new nodes to be provisioned when a new job is submitted. This can sometimes lead to the error you're seeing.
• Consider setting the Minimum number of nodes to 1 or more to keep at least one node active and ready to accept jobs.

3. Recreate the compute cluster:

• If the compute cluster is in a failed state or the issue persists, recreating the cluster can often resolve underlying problems.
• Delete the existing compute cluster and create a new one with the same or updated configuration.

If these this information helps you, please "Accept" the answer to help other members of the community.

Please let me know if you have any further questions or if the issue persists. I'm here to assist you.