Deny access when managing Hyper-V remote server in Workgroup
Typically, when people use the Hyper-V management tool on Windows Vista or Windows 7 operating systems, then connect to the remote-controlled Windows Server 2008 R2 installation computer with the Hyper-V role activated, and in case both computers are in Workgroup, the system will display the following error ...
TipsMake.com - Normally, when everyone uses the Hyper-V management tool on Windows Vista or Windows 7 operating system, then connect to the remote-controlled Windows Server 2008 R2 installation computer with the Hyper role -V has been activated, and in case both computers are in Workgroup, the system will display the following error:
Bạn không có quyền quyền xác thực để cập nhật này. Liên hệ administrator
For basic information about the installation process and setting up some Hyper-V related tools, please refer here.
Enable Hyper-V's Remote Management feature:
First, you need to use the support tool named Hyper-V Remote Management Configuration Utility, and along with some simple commands, we can enable the Remote Management function of Hyper-V. But if in case your system is managed by System Center Configuration Manager 2008 it should not be applied this way.
Specifically, after downloading the Utility tool on your computer, copy the HVRemote.wsf file to a folder on both computers - server and client (such as C: HVRemote ). Later:
- Open Command Prompt and point to that storage folder (should open under Run as Administrator mode)
- On Hyper-V server : assign 1 more user to directly access Hyper-V with the command:
cscript hvremote.wsf / add: domainuser: if the computer is in the domain
or:
cscript hvremote.wsf / add: user: if the computer is in workgroup
- On the Client machine, if using Windows Vista or 7 (it is not necessary to be Windows Server 2008 or Windows Server 2008 R2): add 1 exception of the Firewall to Microsoft Management Console with the command:
cscript hvremote.wsf / mmc: enable
- On Client machine (in case client and server are in workgroup ): allow DCOM anonymous access by command:
cscript hvremote.wsf / anondcom: grant
- Restart both Hyper-V server and client
Optional on the client system: if you want to display the components set up, customize and check for problems with the command:
cscript hvremote.wsf / show / target: servercomputername
On the server system, if you want to do the same as above, you use the command:
cscript hvremote.wsf / show / target: clientcomputername
From this point on, we were able to control the Hyper-V server to the Windows 7 Hyper-V management system :
Good luck!
You should read it
- Configure Windows Server 2008 to remotely access SSL VPN Server (Part 1)
- Windows Server 2012 released in August 2012
- Install and configure Hyper-V Tools for remote management
- Fix Access Denied in Windows 7
- Activate and configure Remote Desktop for Administration on Windows Server 2003
- Remote management on Windows Server 2012 with Remote Management Service
- Create VPN Server on Windows 8
- How to access Linux server from Android
- 6 ways to access Control Panel on Windows Server 2012
- Build VPN server
- How to install Remote Server Administration Tools (RSAT) in Windows 10
- Instructions for installing Ubuntu Web Server on remote host
Maybe you are interested
How long can SSD hard drive live? 18 'extremely creative' inventions are available only in Japan 8 utopian expectations can harm your life 20 creative inventions are extremely useful in everyday life No one expected the wheel to be made so complicated Watch extremely fierce and fierce sumo fighting robots