No target system to choose from my machine pool in WHCK / WHLK

Hi All,

I have tried to set the Windows HLK environment twice, but still no success.
I have installed the HLK client on both of my target guest and the support guest machine.
I am also able to create machine pool in the HLK studio configuration page.

However, after creating my HLK project, when I switch to “Selection” tab in HLK studio, I am not seeing any of my guest machines (after selecting my machine pool).

When I am getting instead is a gray message saying “Selected machine pool does not contain any targets of this type”.

Please help as I am not getting any solutions to this problem on the web or MSDN pages.

Thanks in advance.

I have resolved this issue after some more experiments with the setup. Thanks.

Hi,

We have a checklist on how to setup the HCK\HJLK environment here (it is for VMs, but works perfectly for physical machines as well): https://github.com/daynix/VirtHCK/wiki#Checklist_for_a_New_Controller_VM
https://github.com/daynix/VirtHCK/wiki#Checklist_for_a_New_Client_VM

Also we have some scripts to simplify the installation:
https://github.com/daynix/VirtHCK/tree/master/guest_tools/AutoHCK

Best regards,
Yan.

Thanks.

On 03-Apr-2017 1:36 PM, wrote:

> Hi,
>
> We have a checklist on how to setup the HCK\HJLK environment here (it is
> for VMs, but works perfectly for physical machines as well):
> https://github.com/daynix/VirtHCK/wiki#Checklist_for_a_New_Controller_VM
> https://github.com/daynix/VirtHCK/wiki#Checklist_for_a_New_Client_VM
>
> Also we have some scripts to simplify the installation:
> https://github.com/daynix/VirtHCK/tree/master/guest_tools/AutoHCK
>
> Best regards,
> Yan.
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>

getting the same issue, how it was resolved