Hyper-V Server 2016 – HNV 1.0 – configuration lost after a while
Hi Expert,
Background and issue:
- Hypervisor: Hyper-V Server 2016 (note that it’s not Windows Server 2016)
- Deployment Model:Standalone
- Host Network: NIC teaming is used, and 2 physical NICs
- Hyper-V Network Virtualization: 1.0 (just consider it’s supported by Hyper-V Server 2016 since both HNV1 & HNV2 are supported by Windows Server 2016)
- Want to implement network isolation by using HNV 1.0
- run the following PowerShell command:
New-NetVirtualizationLookupRecord -VirtualSubnetID "5001" -CustomerAddress "10.156.1.1" -ProviderAddress "172.31.153.101" -MACAddress "00155D971F27" -Rule "TranslationMethodEncap"
7. after that, I can view the lookup record by running get-NetVirtualizationLookupRecord, but almost 3-5 minutes later, run get-NetVirtualizationLookupRecord again, no any output, seems that the configuration is totally lost.
Thanks in advance!
amoschb
New KB articles published for week ending 24th June 2018
VMware Horizon
Horizon 7.5 JMP server installation may write SQL username and password to a log file
Published Date:6/20/2018
VMware SDDC Manager
Network port requirements for VMware Cloud Foundation for Service Providers
Date Published:6/19/2018
How to manually repopulate the /backup partition of the sddc-manager-utility VM with NSX and node/host backup data on VMware Cloud Foundation
Date Published:6/18/2018
VMware Site Recovery Manager
Unable to modify/repair/uninstall SRM service 6.1
Date Published:6/19/2018
VMware vCenter Lifecycle Manager
vRealize Operations Manager UI access from vIDM app catalogue displays a 404 error
Date Published:6/20/2018
Unable to perform snapshot/upgrade of imported environment when the VM imported has a hostname
Date Published:6/20/2018
Creating a snapshot of a vRealize Suite product from vRealize Suite Lifecycle Manager might fail
Date Published:6/20/2018
VMware vCenter Server Appliance
VPXD stops responding and reports error: “Double register of key: ‘vm-XXX’ and name: ”
Date Published:6/19/2018
VMware vCloud Availability for vCloud Director
Date Published:6/18/2018
VMware vCloud Director for Service Provider
Cannot connect to virtual machine console on vCloud Director 8.x
Date Published:6/17/2018
VMware View
Display autofit does not work properly with blast and HTML access when connecting to VDI installed View Agent 6.2.6.
Date Published:6/22/2018
VMware vRealize Suite Lifecycle Manager
Cannot enter details for User DN if LCM is upgraded from 1.0/1.1 with pre-integrated VMware Identity Manager (vIDM)
Date Published:6/18/2018
vRealize Operations Manager deployment fails when connecting to vIDM
Date Published:6/20/2018
Pre-check succeeds but vRealize Operations Manager deployment fails due to insufficient disk space
Date Published:6/20/2018
Resume request fails to load vRealize Automation 7.3 product details
Date Published:6/20/2018
VMware vSphere Replication
VAMI page not accessible after upgrading to vSphere Replication 6.5.1.3
Date Published:6/19/2018
The post New KB articles published for week ending 24th June 2018 appeared first on Support Insider.
connecting to virtual machine management service hangs
Re-posting from this thread:
https://answers.microsoft.com/en-us/windows/forum/windows_other-performance/connecting-to-virtual-machine-management-service/f1c6c189-7937-4bac-b800-0400292ada7c
ORIGINAL POST from itr88:
Overview of environment
Hyper-V host 1 - Server 2016 - not domain bound - static IP - 4 nics (1 mgmt 2 guests and 1 spare)
- software additional to OS (webroot / labtech / veeam backup & replication)
- Runs two guests
-guest1 = DC / FS / DNS / DHCP / Backup server
-guest2 = WEBSERVER
Situation
This morning at 4am, the host reboot because of monthly patches (was not suppose to but a different story altogether), issue since then.
Can connect to host, but cannot connect to hyper-v manager, stuck on this: "connecting to hyper v management service"
We have done the following in troubleshooting
-Setup DHCP and DNS (as this is running on the DC that is not running atm)
-Run MOFCOMP %SYSTEMROOT%System32WindowsVirtualization.V2.mof
-Uninstall webroot and labtech and patches.
-Ran DCOM fixes and various other attempts to fix this
We have then booted from OS disc, reinstalled OS, after reinstall could access Hyper-V manager, imported VM’s, one failed, one succeeded, rebooted server and back to square one, unable to connect to hyper-v manager service.
Hyper-V still runs as we have the webserver running, and we can do some management via powershell, but that’s it.
Anyone encounter this or a similar issue, we’ve searched the internet and we can’t find anything closely related to this issue.
RESPONSE:
Did you end-up figuring out what happened, or find a fix?
We experienced the exact same issue on June 17th (the day after your post).
We have two VM host servers. After scheduled Windows patches in the middle-of-the-night, both rebooted. One came up normal. But when the other
host rebooted, it came up, but none of the VMs were online.
Same thing - It was stuck on "connecting to hyper v management service".
We tried the following, but had no luck
- Reviewed Error logs - (nothing useful, other than the service was not able to change the states of the VMs)
- Tried running MOFCOMP %SYSTEMROOT%System32WindowsVirtualization.V2.mof
- Uninstalled the recent Windows patches, rebooted
We’re running a Lenovo System X server. We initially thought perhaps it was a firmware issue / incompatibility issue with the latest patch, but uninstalling
the patch didn’t help.
We ended up re-installing Window Server 2016, after updating all system firmware. Ran all Windows Updates, then reinstalled Hyper-V role.
With no VMs added, we started Hyper-V manager and it came up.
We did not restore any of the prior VMs. Instead we created a new one. Started it. Rebooted the host, it all came up.
We added two more VMs, rebooted the host, all came up.
Since then, we added the rest of our VMs but have not rebooted the server. We are definitely concerned about not having yet determined the root cause
of this issue, troubleshooting (besides reinstalling everything from scratch) or a fix. Nothing we did brought the service back, so this is still of great concern.
Any new information you may have on this issue would be highly appreciated.
Event 21502 when I Linv Migration a Virtual Machine
I have 3 node in Failover Cluster,when i use live Migration function ,it accuse an error:ID21502,detail was that “the virtual machine management service failed to establish a connection for virtual machine migration with host S1;No connection could
be made because the target machine actively refused it (0x8007274D)”
ps: I can move VM between S2 and S3 by live migration
OS Win2016 std
Invoke command in powershell is not working with Hyper-V to run a script in VM
Hi,
I am trying to run a command with "invoke-command" cmdlet in Hyper-V host to run a script in VM and i am getting the error "An error has occured which windows powershell cannot handle.
A rewmote session might have ended"
+categoryinfo : openerror: (win2012:String) [], PSRemotingDatastructureException
+FullyQualifiedfieldErrorId : PSsessionstateBroken
Please provide the solution to resolve it.
New KB articles published for week ending 17th June 2018
Read full post . . . or http://feedproxy.google.com/~r/VmwareKnowledgebaseBlog/~3/NxOuegK2Eac/new-kb-articles-published-for-week-ending-17th-june-2018.html
Datacenter Products
VMware response to CVE-2018-3665 (LazyFP)
Date Published:6/15/2018
VMware App Volumes
Unable to view the status of Trend Micro Deep Security Notification when writable volumes are attached to the machine
Date Published:6/12/2018
VMware Horizon
Unmatched Base Image is shown in View Composer Settings in Machines in View Administrator
Date Published:6/13/2018
VMware NSX for vSphere
Viewing logical switches in the vSphere Web Client displays the error: “Internal server error has occurred”
Date Published:6/12/2018
VMware SDDC Manager
Workload domain creation fails on the vCenter: Configure LACP on VDS task in VMware Cloud Foundation 2.3.2 environments
Date Published:6/11/2018
VMware Validated Design
TCS Agile SDI on VMware Validated Design 4.2
Date Published:6/12/2018
VMware vCenter Server
Upgrading vCenter Server 6.x fails with the error “A problem occurred while getting data from the source vCenter Server”
Date Published:6/16/2018
VMware vCloud Availability for vCloud Director
Replicated VMs have no network after configuring a to-the-cloud replication with vCloud Availability for vCloud Director
Date Published:6/13/2018
Stale vRCS node records are visible when querying vRCS node information from the vCloud Availability for vCloud Director API
Date Published:6/12/2018
VMware vRealize Business for Cloud Standard
vRBC support for vRealize Operations Manager 6.7
Date Published:6/12/2018
Unregistering vRBC services from vRA
Date Published:6/13/2018
VMware vSphere Storage Appliance
vMSC Solutions with Inspur MCS InMetro
Date Published:6/14/2018
The post New KB articles published for week ending 17th June 2018 appeared first on Support Insider.
Hyper-V Manager – CredSSP Issue
Hello,
I hope this is the right place to post this question. I have roughly 60 servers running Hyper-v Server Core 2012 r2. From time to time I have to use Hyper-V Manager to connect to one of the machines. Such as when the server loses power and shuts down. Sometimes
the RODC VM will come to the boot recovery options screen, after such a shutdown, and I have no choice but to use Hyper-V Manager to connect to it.
Recently our workstations were patched against the CredSSP vulernability, and as work around until we can get the servers patched, we’ve deployed a GPO disabling network level authentication. So, I can RDP into the Hyper-V core host using mstsc.exe, but I cannot
"connect" to the VM using Hyper-V Manager.
Has anyone seen this? The only way I can "connect" to the VMs on the the Hyper-V host using Hyper-V Manager is to uninstall the CredSSP patch on my Windows 10, 1803 PC.
I also don’t see a way to patch the Hyper-V Core server. I tried to install the patch slated for Server 2012 R2 core and it fails to install stating that the server doesn’t need this patch.
Anyway, I could use some help, if anyone has any to offer. If not, I will open a ticket with MS.
Proactively Identifying Potential Risk with VMware Skyline
Read full post . . . or http://feedproxy.google.com/~r/VmwareKnowledgebaseBlog/~3/et3Oo4l0iU0/proactively-identifying-potential-risk-with-vmware-skyline.html
As part of our goal to continuously improve the customer support experience, Technical Support Engineers (TSEs) can now interactively view the proactive findings and recommendations delivered to customers today within the Skyline Operational Summary Report (OSR). Additionally, within the findings and recommendations, TSEs can view customer environment inventory information along with all Support Requests (SRs) for the particular customer they are assisting. All of this together enables Global Support Services (GSS) to better help our customers. These new capabilities are only available to those customers who have adopted VMware Skyline.
VMware Skyline is available globally to Premier Services customers along with a select number of Production Support customers. If you are interested in receiving proactive support from VMware, show your interest by signing-up for the Managed Access Program. We will continue to invite customers from the Managed Access Program as we scale proactive support services. Additionally, you can ask your VMware Account Team for information about how we’re radically transforming the customer support experience.
Going Beyond Break/Fix
When the circumstances exist that a SR is needed to troubleshoot an issue, TSEs will help the customer resolve the issue. Additionally, they can now review the customer’s proactive findings and recommendations as part of the SR process.
Perhaps the customer experienced an issue that was discovered by Skyline. In that instance, the TSE can immediately assist the customer with determining how many additional objects could be impacted by the same issue. TSEs can now help answer the question, how many more objects could be impacted by the same issue. Furthermore, the recommendation to resolve the issue has already been found, helping expedite the resolution of the issue across all impacted and potentially impacted objects.
Or, if a customer experiences an issue that requires a patch or update, the TSE can review the proactive findings and recommendations to determine if the patch or update required to resolve the original issue, could also resolve additional potential issues. This is not always the case, however, with more information available to TSEs, the better enabled they are to help customers.
Finding Potential Issues
TSEs can now view customer proactive findings and recommendations within a SaaS-based web application. This allows for better search and filter capabilities of findings and recommendations. TSEs can sort by issue severity, quickly looking at all critical findings within a customer’s environment. Or, a TSE can filter for only network-related findings if assisting a customer with a network-related SR. All of this together better enables our TSEs to better serve our customers and assist them beyond just problem resolution.
Conclusion
Today, customers who have adopted proactive support with VMware Skyline receive an OSR. Within the OSR, customers are proactively notified of potential risks within their environment. Additionally, recommendations are provided for how to remediate those potential risks. Now, TSEs have this same information at their fingertips and can help customers with understanding potential risk within their VMware environment.
These new enhanced support capabilities are only available to customers who are receiving proactive support with VMware Skyline. This is just one of many steps VMware is taking is radically transform the customer support experience. Additional information about VMware Skyline is below.
Additional Resources
- VMware Skyline
- Managed Access Program (Sign-Up for VMware Skyline)
- Frequently-Asked Questions
- VMware Skyline Community
The post Proactively Identifying Potential Risk with VMware Skyline appeared first on Support Insider.
New KB articles published for week ending 10th June 2018
Read full post . . . or http://feedproxy.google.com/~r/VmwareKnowledgebaseBlog/~3/Fk3dp7CS_gY/new-kb-articles-published-for-week-ending-10th-june-2018.html
VMware Cloud on AWS
Failed to add groups to the “CloudAdminGroup” during HLM
Date Published: 6/5/2018
Authenticity of the host’s ssl certificate is not verified
Date Published: 6/5/2018
VMware Horizon
Unable to login to Horizon Console or View Administrator using IP address
Date Published: 6/6/2018
Unable to enable/disable Connection Server when backup frequency is set to “Never”
Date Published: 6/8/2018
VMware Integrated OpenStack
VIO After upgrade from 3.1 to 4.x unable to manage volumes
Date Published: 6/5/2018
VIO Error in method invocation The requested availability zone is not available when importing VM
Date Published: 6/5/2018
VIO Bulk deleting of nova datastores
Date Published: 6/6/2018
VMware NSX for vSphere
Trend Micro Deep Security v 10.0 for NSX 6.2, 6.3 and 6.4
Date Published: 6/8/2018
VMware NSX-T Data Center
While upgrading the NSX Agents in the CSM, some of the instances may show a “Failed” status
Date Published: 6/4/2018
Host preparation fails in NSX-T with the error: “Invalid host thumbprint”
Date Published: 6/5/2018
UI trace flow debug issue with Centralized Service Port backed VM in NSX-T
Date Published: 6/6/2018
VMware SDDC Manager
VMware Cloud Foundation Workload Domain expansion fails at the Task “Configure new vCenters and ESXi hosts from workload domains in vRLI”
Date Published: 6/6/2018
VMware vCenter Site Recovery Manager
Running Reprotect or Recovery on PURE storage reports error “Failed to sync data on replica devices. A storage operation requested on unknown storage device ‘peer-xxxxxxxxxxxxxx’”
Date Published: 6/4/2018
VMware vRealize Network Insight
VRNI 3.X unable to see the physical Dell switches
Date Published: 6/4/2018
vRealize Operations Manager
Modifying DNS of vRealize Operations Manager vAPP using vami_config_net, will not generate correct resolve.conf
Date Published: 6/7/2018
VMware vSAN
vSAN Controller health check warning for Intel VMD controllers
Date Published: 6/4/2018
Ensure data accessibility is always used before vSAN host entering maintenance mode when using Host Client
Date Published: 6/7/2018
VMware vSphere ESXi
Hostd process crashes repeatedly on ESXi host with a virtual distributed switch
Date Published: 6/5/2018
The post New KB articles published for week ending 10th June 2018 appeared first on Support Insider.
importing and starting VMs in Hyper-V Server 2016 core using Powershell. All Virtual Machines are located on a diffierent partition
Background:
I’ve upgraded my infrastructure hastily and I done this before the correct way but as I sold my original server I had move the VM’s quickly but with consequences.
The correct way would have been to build the server, add to domain whilst it was live on a different Hyper-V host, assign static IP, change server name, installed windows feature e.g. Hyper-V,
etc.
I done this before and all worked fine as the DC is a VM which is was always online to authenticate against without issues e.g. AD, DNS, DHCP. however as mentioned I rushed it and now I’m stuck
in a workgroup environment on the Hyper-V server 2016 core install.
current Setup:
x1 HP ProLiant ML350 G6, 3 partitions with partition 1 is OS running Hyper-V server 2016 (Core OS), Partition 2 is VMS Datastore (I store all my Virtual machines here) and Partition 3 is ISO and
general software and files.
all other Hyper-V servers are offline and unavailable which would not help as DC VM is offline
Currently the Hyper-V server 2016 core is in a workgroup environment
IP address for the server are statically assigned, and I can ping them from w10 workstation
All workstations are on the domain there are no workgroups and I cannot connect to the domain as
the VM is offline
Firewall has been disabled on server and workstations to allow connectivity for ping, etc
routers been configured for DHCP, DG to allow connectively
Dilemma:
How do I import the DC VM into Hyper-V via PowerShell, so I can turn it on, then I can connect the server to the domain after configuring the server IP statically, so the IP & DNS point to
the DC VM and all will be good in the world again as I can use Hyper-V manager to connect and import the other VM via Hyper-V manager?
Question:
I have a Hyper-V server 2016 core install and I’m not sure how to import the virtual machine to get them started using PowerShell with VM’s located on a different partition, does anyone know how
to do this?
Thank you, God speed
- Top 20 articles for vSAN, November 2019 December 12, 2019
- Enabling replication failed December 11, 2019
- Guest Slow Network Connection with Jumbo Packets December 11, 2019
- New KB articles published for the week ending 8th December,2019 December 10, 2019
- a virtual machine resource was not found in clustered virtual machine December 10, 2019