Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, June 18, 2018 8:31 PM
I just installed 2 Windows Server 2016 VM in a pure lab environment based on a third party hypervisor.
I disabled all the firewalls on both VMs, I configured one VM as a DC and the other one as a MS.
I installed Hyper-v on the MS but when I try to manage it from the DC I get an error saying that "An error occurred while attempting to connect to server "<MS server name>". Check that the Virtual Machine Management service is running and that you are authorized to connect to the server".
The Virtual Machine Managememt service is installed and running on the Hyper-v MS and is confngured to work with the Local System Account. Should I install it on the DC as well?
I performed the same installation twice with the same error, so I suspect I missed some relevant step.
How can I solve the issue and go on with my lab?
Regards
marius
All replies (7)
Monday, June 18, 2018 10:51 PM | 2 votes
Hi!
Is the account that you're trying to connect with local administrator on the Hyper-V server? Also run the Hyper-V manager as administrator.
Also make sure that the WinRM is configured, Hyper-V Manager uses WinRM (Windows Remote Management) to establish a connection to Hyper-V running on the remove computer.
You can run the following command to configure WinRM: winrm quickconfig
If it's not configured, you should get something like this:
WinRM is not set up to receive requests on this machine.
The following changes must be made:
Start the WinRM service.
Set the WinRM service type to delayed auto start.
Make these changes [y/n]? y
WinRM has been updated to receive requests.
WinRM service type changed successfully.
WinRM service started.
WinRM is not set up to allow remote access to this machine for management.
The following changes must be made:
Create a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine.
Enable the WinRM firewall exception.
Make these changes [y/n]? y
WinRM has been updated for remote management.
Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine.
WinRM firewall exception enabled.
If it's already configured, you should get the folliwng message:
WinRM service is already running on this machine.
WinRM is already set up for remote management on this computer.
Then this is not the problem and you should continue troubleshooting.
Best regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:
Tuesday, June 19, 2018 10:43 AM | 1 vote
Hi,
Hope your MS server is a member of the domain that is hosted by the DC. if not try to add the same and then try to access it.
secondly, are these machines able to ping each other
thirdly, check the WinRM as mentioned in the post by Leon Laude
With these things, you should definitely be able to connect successfully
Regards,
Bala
Tuesday, June 19, 2018 11:31 AM
Many thanks to everybody.
At the monent I cannot perform any test. However, let me ask for some additional clarification.
I installed the Hyper-v role in the MS while logging on as the domain administrator: is it correct? Should I instead log on as local adminsitrator while installing roles?
> Also run the Hyper-V manager as administrator.
Do you mean I should confngure the service to use the locan "administrator" accouint instead of Local service account? Is so, which other services should I modify?
Regards
marius
Tuesday, June 19, 2018 11:52 AM | 1 vote
The Hyper-V services can run on the default "Local System" user. It won't really matter whether you install the role as local administrator or Domain Administrator.
Blog: https://thesystemcenterblog.com LinkedIn:
Tuesday, June 19, 2018 11:57 AM | 1 vote
Hi,
All that is fine and clears that the MS server is a member of the domain. Domain administrator should be fine
Also I assume when you login to the Domain controller you use Domain administrator credentials only. So it should be fine too
i also assume that you have installed Hyper-V management tools in your DC.
Though you have added the machine to the domain, but still i doubt on the network. Are you able to ping each other?
Regards,
Bala
Tuesday, June 19, 2018 7:26 PM
Many thanks to everybody for the help.
After successfully performing all the suggested checks I discovered the real cause of the problem. While installing the Hyper-v role I used the same network interface for the server end the virtual switch.
After creating a dedicate network interface for the virtual switch the problem disappeared.
I hope this can be useful for other people.
Many thanks again
Marius
Roma - Italy
Tuesday, June 19, 2018 7:43 PM
Glad to hear you solved your problem, and thank you for sharing this!
Best regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn: