HLK : Test in Progress : machine waiting to be assigned

Bindu K 11 Reputation points
2022-01-11T11:19:27.767+00:00

We are trying to setup HLK in our lab. We have installed HLK controller on windows-2016 server and HLK client is installed on win-10 enterprise version.
In the HLK studio, we are able to see the client in the machine pool. The client machine is in ready state with correct platform information. Even on the HLK manager, the client machine is in ready state.

We are trying to test for software drivers. Upon starting the tests, we see the machine to be in waiting state for a very long time (more than a day's time).

We tried to test the standard KMDF driver too using this setup, but still the same issue.

Restallation of the softwares, restarting the machines didnt help.

We tried to reset the client machine from HLK manager, but that also didnt help.

Can somebody please help us with this issue.

Windows for business | Windows Client for IT Pros | Devices and deployment | Other

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Charles Gardiner 0 Reputation points
    2026-08-02T21:28:35.39+00:00

    Didn't notice for a while since the HLK Client PC is running headless which wasted quite a lot of time. The HLK Client PC is at another desk in the lab. Both the HLK controller running Windows 2019 Server Std. and the HLK Client PC running Windows 10 run headless. The operator runs the tests from a work-place PC with access to the same network as the HLK machines.

    None of the suggestions from copilot (pinging the HLK Client PC or HLK controller IP address, restarting services, reinstalling, resetting etc.) worked. Deleting and recreating the project in HLK studio seemed to resolve the problem for a while but this was probably just coincidental. The real solution is in the next paragraph.

    In our case the problem was caused by the HLK user (DTMLLUAdminUser on our machine) not auto-logging on to the HLK Client PC after the HLK Client PC was rebooted remotely from WinDbg running on the work-place PC. Analyzing test failures and installing corrected driver versions was all done from the work-place PC. Multiple (random number of) HLK Client PC reboots from the debugger or simply attaching a monitor and clicking on the sign-in button on the HLK Client PC whenever auto login didn't succeed solved the issue reliably.

    Was this answer helpful?

    0 comments