Hyper-v Converged network


Im setting up a new 2016 failover cluster. I just want to clarify that im understanding the concept and design of this converged network. On my physical server i only have two 10Gb Nics which i need to team. The switchports in which the NICs are connected
as an etherchannel LACP and the etherchannel is an Access port.

So traditionally, i’d fire the LbfoAdmin console and configure NIC teaming on the management OS. In a Hyper-v Converged network, im not going to do this. Instead, Im going to team the NICs on the vSwitch itself. So id run a powershell that looks something
like this: New-VMSwitch -Name vSwitch -AllowManagementOS $True -NetAdapterName NIC1,NIC2 -EnableEmbeddedTeaming $True.
I will then configure vNICs and assign to appropriate vlan. When the packets from a VM with a vNiC configured for vlan 20 will leave the physical NIC and onto the switch, it will be tagged with vlan 20, likewise for ingress and Hyper-v will understand
where to deliver the packet. 

Is the above correct? I have two questions:

  1. In order for this work, i need to configure the switchport as a trunk port. However, would i need to remove the etherchannel LACP considering that EmbeddedTeaming is must likely not going to perform an LACP negotiation, or will it?
  2. Part of the traffic is obviously storage, ISCSI. I would like to configure MPIO between two NICs, or is it unnecessary because the EmbeddedTeaming takes care of aggregating and failing over? If not, then can i still configure MPIO?

Read full post . . . .

Free Webinar – Proactive Support with VMware Skyline

Read full post . . . or


Have you been anxiously awaiting your invitation to receive proactive support from VMware?  Or have you received your invitation but haven’t installed the Skyline Collector yet?  Learn more about proactive support with VMware Skyline by joining us for a free 30-minute webinar.

We’re hosting two webinars.  Please register for the webinar that works best for you.

  • Wednesday, July 25th, 9pm Eastern Daylight Time / 6pm Pacific Daylight Time - Register
  • Thursday, July 26th, 10am Eastern Daylight Time / 7am Pacific Daylight Time - Register

First, we’ll provide an overview of VMware Skyline.  Next, We’ll walk through the steps needed to install the Skyline Collector, which is required to receive proactive support.  We’ll also share a sample of the proactive findings and recommendations delivered today with the Operational Summary Report (OSR).  Finally, we’ll answer some of the most common questions about VMware Skyline.  A live Q&A chat session will also be available during the duration of the webinar.

This is your chance to learn more about how proactive support with VMware Skyline is transforming the customer support experience.

The post Free Webinar - Proactive Support with VMware Skyline appeared first on Support Insider.

Auto-Upgrade with Skyline Collector 1.3

Read full post . . . or


We are excited to announce the release of Skyline Collector 1.3. New within version 1.3 is an improved User Interface and the ability to enable automatic upgrades the Skyline Collector for future updates.

The Skyline Collector enables VMware Global Support Services (GSS) to deliver proactive support.  With proactive support, GSS can notify you of potential issues and areas of risk within your vSphere and NSX environments.  Most noteworthy, proactive support is available at no additional cost to customers with an active Production Support or Premier Services contract.

Please sign up for the Managed Access Program if interested in learning more about proactive support.  Premier Services customers should contact their Support Account Manager/Support Account Engineer for information how they can begin receiving proactive support from VMware today.

Improved User Interface

The Skyline Collector administrative interface has been improved to allow for easier navigation and management of the Skyline Collector.  An overview, along with Skyline Collector management capabilities now reside on the System Status page.  Furthermore, you can see the status of each product endpoint.

The new Skyline Collector 1.3 System Status page provides you with more information, allowing you to view the overall health of the appliance in a single-place.

The Configuration page includes the following options:  Add vCenter Server, Add NSX Manager, Proxy, Collector Name, Active Directory and the newly-added Auto-Upgrade.  Next, we’ll share how auto-upgrade works and why you should enable it.

The Skyline Collector 1.3 Configuration Menu


We continue to work towards making Skyline Collector management as effortless as possible.  New within Skyline Collector 1.3 is the option to enable Auto-Upgrade.  The first step is to enable Auto-Upgrade by toggling the Enable Collector Auto-Upgrade switch to Yes.  Next, you can choose every day or specific day of the week along with time of day for the Collector to automatically upgrade, if any upgrade is available.

Enabling Auto-Upgrade will keep your Skyline Collector virtual appliance up-to-date with all the latest features and capabilities.

In order for Auto-Upgrade to work properly, ensure that the Skyline Collector can reach over port 443.  If Auto-Upgrade is enabled, the Skyline Collector automatically retrieves updates from this address.  If you choose not to enable Auto-Upgrade, the Skyline Collector still needs to be able to reach this address to apply updates.  You can apply updates to the Skyline Collector manually using the Check and Install Updates option within the VAMI.

After each successful auto-upgrade, an email will be sent to the email address that was used to register the Skyline Collector.  This is the My VMware account you entered during the installation and configuration of the Skyline Collector.

Enabling Auto-Upgrade will ensure that your Skyline Collector is always up-to-date, including bug fixes and improvements, such as new VMware product support in the future.  Additionally, this removes the manual task today of logging into the VAMI, checking for updates and if an update is available, installing the update.


You can take advantage of the new features available within the Skyline Collector by upgrading to 1.3.  After upgrading your Skyline Collector to 1.3, you can enable Auto-Upgrade so that all future updates are automatically applied as they become available.

VMware Skyline enables the delivery of proactive support by VMware Global Support Services (GSS).  Today, customers who have adopted proactive support with VMware Skyline receive an Operational Summary Report (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.

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.


The post Auto-Upgrade with Skyline Collector 1.3 appeared first on Support Insider.

Server Service


Does hyperV Host server need the server service to operate?

I want to lock down smb and file share access to the server from network clients. 

Read full post . . . .

Kerberos error when attempting to connect to Hyper-V Server from Hyper-V manager

When I am attempting to connect to the Hyper-V Server from the Hyper-V manager i get this error:

Hyper-V between Windows 10 & Windows 8.1 in a workgroup

I got my notebook and server connected to the switch which are not having internet. I configured the IP-addresses and subnets and they can ping to each other.
I can also start a remote session on the server from my notebook. They both are also in the same workgroup.

I already configured the Windows Hyper-V 2016 Server as TrustedHost on my notebook and TrustedHost on the server of my notebook also both with
CredSSP. I followed this video:

Anyone knows if I need to activate or code something more? I have read that there were new updates that caused this error. The ISO file of the server is an evaluation file which I downloaded today. My notebook is running Windows 10 Pro with the newest updates
and build 1803. It is a HP Probook notebook.

Don’t mind my English language, I am a Dutch student and I still need to learn some better English 🙂

Thanks in advance.

Read full post . . . .

Hyper-V in Windows Server 2012 R2 Essentials – Newbie information gathering question


I am new to virtualization in general.  I am trying to figure out what I can do to install management software that uses SQL Server 2017.  As you know, SQL Server does not like to be installed on a domain controller which is the Windows Server
2012 R2 Essentials operating system. Rather than buy another server just to run SQL Server 2017 and buy another operating system, I was wondering if its possible to install the Hyper-V role and use the Hyper-V to create a virtual machine just for SQL
Server 2017, the management software and the remote access into the management software thru an IIS website that has an SSL Certificate.  Would I be able to leave the existing operating system the way it is if I am able to use Hyper-V? I am interpreting
some web sites as saying I could have 2 copies of my operating system then. One being virtual.. then other websites I interpret it as it becomes 2 virtual machines.. one basic, one with all roles and features.  I am not sure what to do, if its possible
or if I should be looking another direction. Again, I am totally green to this whole area so need some direction.  I don’t want to affect what the server is doing right now.. I don’t want to cause it issues by installing SQL Server 2017 on it.. possibly…

if this is possible at all in hyper-v… could someone point me in the right direction to learn more as a newbie and figure out how to configure it and access it etc…

Read full post . . . .

New KB articles published for week ending 15th July 2018

Read full post . . . or


VMware NSX for vSphere

NSX manager stuck as no timeout present in SSO client library
Date Published: 07-09-2018

Support for McAfee MOVE AntiVirus [Agentless] 4.7 with NSX Manager 6.3.0, 6.4.0 and 6.4.1
Date Published: 07-11-2018

NSX Edge Unable to Resolve Hostnames
Date Published: 07-11-2018

NSX Load Balancer Crashes Due to High Memory Usage
Date Published: 07-12-2018

VMware SDDC Manager

How to reconfigure the vCenter Server Appliance and Platform Service Controllers in VMware Cloud Foundation to use syslog forwarding in place of the Log Insight agent
Date Published: 07-09-2018

The SDDC Manager UI displays a 404 error when attempting to log in.
Date Published: 07-09-2018

VMware Integrated OpenStack

VIO Opening a console to an instance generates Error “Failed to Connect to server code 1006” is shown
Date Published: 07-10-2018

VMware NSX-T

Upgrading NSX-T manager from to reports “General Error has occurred” on Firewall’s General UI section.
Date Published: 07-10-2018

VMware Cloud on AWS VMware Cloud on AWS

HCX Virtual Machines are using 2.0x storage space when 1.5x storage space is expected.
Date Published: 07-10-2018

Reserved subnets for SDDC creation in VMware Cloud on AWS
Date Published: 07-12-2018

HCX replication are in Syncing state with 0% progress and 0 bytes with status Error
Date Published: 07-13-2018

VMware vCloud Availability for Cloud-to-Cloud DR

VM details are displayed incorrectly in the vCloud Availability for Cloud-to-Cloud DR 1.0 Portal
Date Published: 07-11-2018

VMware vRealize Operations Manager

Reclaimable Metrics do not immediately reflect changes in vRealize Operations Manager 6.x
Date Published: 07-11-2018

VMware Horizon

Timeout settings and F5 persistence for VMware Horizon 6.x and 7.x
Date Published: 07-12-2018

VMware vCloud Availability for vCloud Director

How to reset the vCloud Availability Installer appliance’s root password
Date Published: 07-12-2018

VMware vRealize Log Insight

vRealize Operations Manager unable to write to the liagent.ini file after li-agent deletion and re-installation
Date Published: 07-12-2018

Missing ESXi events in vRealize Log Insight 3.x and Later
Date Published: 07-13-2018

VMware vSphere ESXi

The Oracle Unbreakable Enterprise Kernel (UEK) is not supported with VMware Tools Operating System Specific Packages (OSPs) for vSphere 5.x
Date Published: 07-13-2018

VMware vCenter Server

While installing vCenter Server 6.7, an error displays “Failed to validate sso.(‘PSC_FQDN’ doesn’t match with hostname in Platform Services Controller certificate)”
Date Published: 07-13-2018

VMware vRealize Suite Lifecycle Manager

Sometimes data is not loaded in to vRealize Suite Lifecycle Manager UI after upgrading from vRCLM 1.2 to 1.3
Date Published: 07-13-2018

VMware vCenter Server Appliance

Configuring proxy settings for Update Manager returns “An internal error has occurred - Error #1009”
Date Published: 07-13-2018

The post New KB articles published for week ending 15th July 2018 appeared first on Support Insider.

auto revert to a snapshot after each vm reboot


I like to config a VM will be revert to specific snapshot every reboot. Seen like Hyper-v not support that, so do we have any tool or script support that?


Read full post . . . .

auto revert to a snapshot after each vm reboot


I like to config a VM will be revert to specific snapshot every reboot. Seen like Hyper-v not support that, so do we have any tool or script support that?


Read full post . . . .

Cannot delete Checkpoint after manually merging avhdx-files


we had a problem with our backup-software. There have been created checkpoints every day but haven’t deleted after the backup.
I merged the avhdx files until only a vhdx-disk has been left with the following powershell command:

merge-vhd -Path FS1_F6BECDB6-FE79-4A43-A550-7F5FD563A062.avhdx -DestinationPath FS1_FFA1D4D5-033F-4E3C-ACB4-222CBFBCE14D.avhdx

This works all find. Then I chanced the disks at the fail-over-manager from the avhdx-files to the vhdx.files. The server now runs without any problems.

BUT!! in the Hyper-V-manager the old checkpoint are still visble and I’m not able to delete them with the following message:
The operation failed because the file was not found.
That message is write - all the avhdx-files have been deleted.

How do I manage to delete these old - no longer existing - checkpoints? As long as they exist the backup-software will not create new ones and we don’t have a backup 🙁

I hope someone can help me to solve this problem.

Thank you in advance


Read full post . . . .

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 580974 bytes) in /home/content/36/8658336/html/goquecom/wp-content/themes/WPGoqueV52/library/misc.php on line 25