Hi,

I do not understand the new Pulseway policy about Hyper-V module or role. For years I was just installing PW engine on servers, configure it to enable all needed/hosted roles, and Hyper-V and ESX were among them. Now there aren't anymore:

To add to confusion, in WEB portal I can see under DEVICES --> ROLES that 9 of my devices have Hyper-V role.

But I remember, that for the last one I had to mangle something under DEVICES --> ACTIVE CONNECTORS, but there I can only see 2 Hyper-V hosts, which host 11 VMs together:

QUESTIONS:

1. What am I missing there to not have Hyper-V and ESX roles anymore in client?

2. How can I add Hyper-V now using those CONNECTORS? I spent half an hour researching, but I am still confused.

3. What are those 9 Hyper-V ROLES?

4. Is not the only way to add Hyper-V and ESX via CONNECTOR?

Thank you all!

I had a conversation with Pulseway support a bit more than a year ago(because I couldn't get my hyper v cluster machines to appear through the same setup you are trying) and after a back and forth they told me how to re-enable the functionality at the local manager app level but I can't find that email... I'll keep poking around to see if I can find it, in the meantime you should open a ticket with support and ask them directly how to re-enable that functionality.

EDIT:Found this discussion.

Edited 2 hours ago2 hr by DarienAL