I would open the firewall just locally for the requests being made by the agent itself. Advanced Encryption is mandatory for any AIM installed on the agent. The steps you described earlier assure the proper communication between the AIM and the Hyper-V and nothing more.
You can try with your current setup, without making the required changes to see if it works. Most probably it will not. Take one at a time and see if works, but it's a long process. The required changes should not interfere with the functioning of your systems. Again, if firewall is a problem, open the port only for local communication. The command described there enables the predefined firewall rule. You can modify it to allow communication only from local machine.
Most problematic setting here would be the disabling of UAC. That might not be allowed by your local security policies.
------------------------------
Senior Consultant
SolvIT Networks
------------------------------
Original Message:
Sent: 04-13-2021 12:41 PM
From: Jose Gutierrez
Subject: How to configure HyperV(Windows) Pluging for Sysedge 5.9 agent
Hi Catalin,
I read the manual you send. I see that you have to configure something after install the sysedge agent and the AIM Hyper-V.
I have some doubts about the Step number 4 Enable remotw WMI firewall, ¿this command just add a new rule on Windows Firewall? because I have productive virtual machines running on this server and I dont want to made something that can shutdown any Virtual Machines.
And about the step 5, we are using Administrator Account on the Hyper-V but If I looked on the "Distribuited COM Users" group Administrator its not part of it. I have to add Administrator Account?
Thnks for the help and I hope you can answer my questions.
Regards
José