I would like to ask if someone can try this script to check ILO information's I just need to know if is valid, I got these info when I run:

So, I suppose 2.20, 2.40 are ILO version...thanks

Get-View -ViewType HostSystem -Property Name, Runtime.HealthSystemRuntime.SystemHealthInfo.NumericSensorInfo -SearchRoot (Get-View -ViewType ClusterComputeResource -Property Name -Filter @{"Name" = "^$([RegEx]::escape($strHostsClusterName))$"}).MoRef | %{    $arrNumericSensorInfo = @($_.Runtime.HealthSystemRuntime.SystemHealthInfo.NumericSensorInfo)    # HostNumericSensorInfo for BIOS, iLO, array controller    $nsiBIOS = $arrNumericSensorInfo | ? {$_.Name -like "*System BIOS*"}    $nsiArrayCtrlr = $arrNumericSensorInfo | ? {$_.Name -like "HP Smart Array Controller*"}    $nsiILO = $arrNumericSensorInfo | ? {$_.Name -like "Hewlett-Packard BMC Firmware*"}    New-Object PSObject -Property @{        VMHost = $_.Name        "SystemBIOS" = $nsiBIOS.name        "HPSmartArray" = $nsiArrayCtrlr.Name        "iLOFirmware" = $nsiILO.Name        }} | Export-Csv -Path C:\Users\gemela\ILO_info.csv -NoTypeInformation -UseCulture

Hi,

We are going to migrate our existing VMware infrastructure from DELL Servers with EMC SAN (vSphere 6.0) to HP Servers with HP SAN (vSphere 6.5).

Consultant suggests the migration of VMs to make use of VMware Convertor as it costs the least money.

Is there any free tools for migration ?  Besides downtime, is there any other pitfall for using VMware Convertor ?

Thanks

Hi,

We are going to migrate our vSphere infrastructure to a new platform.  We intend to make use of this opportunity to upgrade vSphere 6.0 to vSphere 6.5.

Consultant suggests us to make use of VMware Convertor to migrate VM from the old Data Centre to the new one.

Just wonder whether there is any change we need to work on the VM after migrated via VMware Convertor ?  What will be the bottle neck for conversion (Network / CPU of the machine running VMware Converter or CPU of the destination ESXi Host) ?  How many VM we can convert at the same time (It seems to be 4) ?

Thanks

A common question I get from customers and partners that are beginning their dive into the VMware Validated Designs is around the placement of the edge components.  This is often because these individuals have been doing some fantastic due diligence by reading not only the VMware Validated Designs, but also the NSX for vSphere documentation and the NSX Design Guide.

After reading these, a general concern is that the documentation and guide reference a “Management and Edge” cluster construct whereas the VMware Validated Designs reference an initial “Shared Edge and Compute Pod.”

So, why the difference?

First off,  the documentation and design guide for NSX is a starting point and seeks to address specific use cases. In turn, the VMware Validated Designs, such as, the VVD for Software-Defined Data Center and the VVD for Remote Office/Branch Office address their own use cases. That said, these designs have absolute synergies with and are fully supported by VMware’s Network and Security Business Unit.

The biggest thing to understand is that the VMware Validated Designs use NSX for both the management and compute workloads. When we crafted the designs, we made some key design decisions on how to construct edge services for the management domain and the workload domains. We could have combined the edge into either one of the two; however, we specifically decided to place edge services for workloads alongside the compute clusters for a couple reasons:

1. From a security and scale perspective, the design seeks to isolate the north/south traffic of the management pod for the SDDC from the tenant compute pods.
   
   
2. As compute clusters scale out, so can the NSX deployment. With on-demand network and security services for the tenant workloads automated by vRealize Automation, the design would have needed to scale the management pod to meet the potential NSX requirements for these components. Instead, we made a key decision to have the management pod isolated and sized to run the SDDC stack optimally.

Since an NSX Manager can be associated with one, and only one, vCenter Server the NSX Controllers and any ESGs must be deployed into a cluster that the associated vCenter Server instance manages.

As such, we created a management domain and tenant workload domain, each with their own instance of NSX Manager, NSX Controllers, etc.

The result is:

1. A management pod with its own vCenter Server associated with its own NSX Manager instance. These are instantiated within the management pod’s cluster itself.
   
   
2. A shared edge and compute pod with its own vCenter Server associated with it own NSX Manager instance. The NSX Manager is instantiated within the management domain cluster whereas, due to the one-to-one relationship, the NSX Controllers and any ESGs must for this pod are deployed into an initial shared edge and compute cluster that the associated vCenter Server instance manages.  Now, as organization grows beyond the capacity of initial shared cluster, any new compute only clusters for workloads will be deployed under the same vCenter Server instance and consume network and security services that are isolated from management.

Now,  if you step back for a moment, and look at it at it a little differently, you’ll notice that we technically implement a “Management and Edge” pod and a shared “Edge and Compute” pod.

Whoa, how so?

Management (and Edge) Pod - In the management cluster, we utilize NSX to provide network and security services to the management stack - think distributed logical routing, distributed firewall, north/south routing, and policies for the management stack solutions like vRealize Operations and vRealize Automation. Here, we have an NSX Manager - associated with the management vCenter Server instance - which deploys two NSX Edge Services Gateways (ESGs) for north/south routing, two highly-available pairs of ESGs to provide load balancing services for the Platform Services Controllers and the vRealize Operations and Automation components. Now, we don’t explicitly call it a “Management and Edge” pod since these ESGs are only service the management components, and don’t provide edge services to tenant workloads. We simple call it the "Management" pod.

Shared Edge and Compute Pod - In the initial shared edge and compute pod we also use NSX to provide network and security services to the tenant workloads. That is, of course, distributed logical routing, distribute firewall, north/south routing, policies, and on-demand network services for the tenant workloads in the stack. Since an NSX Manager can be associated with one, and only one vCenter Server instance the NSX Controllers and any ESGs must be deployed into a cluster that the associated vCenter Server instance manages. So, here we have an NSX Manager associated with a separate vCenter Server instance that serves the tenant compute workloads only. Therefore, the only option is for ESGs to be here in the hence named Shared Edge and Compute Pod.

And, there you have it, this is why there may appear to be a difference between the NSX documentation and design guide and what’s documented in the VMware Validated Designs. But, rest assured, it’s completely validated, tested, and supported architecture base on key design decisions for our use cases.

Got comments on this topic? Simply reply to this thread.

Got more questions,? Post your questions in the communities. We’re here to help.

Hello.

There are two patterns of "DHCP" and "IP Pool" in the IP address assignment method of VTEP,

Which one is recommended?

As far as I looked

I think both automatic and manual IP address assignment to VTEP is possible.

If there is no difference, IP Pool that does not need to build a DHCP server thinks it is the best.

Reference materials

https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.4/com.vmware.nsx.install.doc/GUID-2FA9D4DE-56C0-40A4-A085-2FCE502A87B9.html

https://communities.vmware.com/docs/DOC-27683

→ There is no description about IP Pool

testing

I could not create the virtual machine from my local machine. I dont know what to do now. I found a similar problem here but i cant make sense out of it.

Can anybody help? I have the logs if required

Markus

xecution time:00:03.039

[UTC:2018-06-23 04:30:17 Local:2018-06-22 21:30:17] Failed to retrieve the status of infrastructure Website server. A retry will follow. Error details: System.AggregateException: One or more errors occurred. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.

   --- End of inner exception stack trace ---

   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)

   at VMware.IaaS.Installation.Common.WebInstaller.PerformWapiHealthCheck(String wapiHost, NotifyUserEventHandler notifyUserEvent, NotifyDebuggerEventHandler notifyDebuggerEvent, X509Certificate2 expectedCertificate)

---> (Inner Exception #0) System.Threading.Tasks.TaskCanceledException: A task was canceled.<---

Starting registration of catalog types.

Executing:C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe RegisterCatalogTypes -v

Catalog registration starting.

[21:30:46.298] VMware.Cafe: [sub-thread-Id="1"  context=""  token=""] Setting from config CafeClientCacheDuration: 05:00:00

[21:30:46.355] VMware.Cafe: [sub-thread-Id="1"  context=""  token=""] (1) GET endpoints/types/sso

[21:30:57.173] VMware.Cafe: [sub-thread-Id="9"  context=""  token=""] (1) Response: OK 0:12.035

[21:30:57.693] VMware.Cafe: [sub-thread-Id="5"  context=""  token=""] (2) POST SAAS/t/vsphere.local/auth/oauthtoken?grant_type=client_credentials

[21:30:57.749] VMware.Cafe: [sub-thread-Id="9"  context=""  token=""] (2) Response: OK 0:00.081

[21:30:57.806] VMware.Cafe: [sub-thread-Id="5"  context=""  token=""] (3) GET endpoints/types/com.vmware.csp.component.iaas.proxy.provider.api/default

[21:30:57.834] VMware.Cafe: [sub-thread-Id="8"  context=""  token=""] (3) Response: OK 0:00.034

[21:30:57.946] VMware.Cafe: [sub-thread-Id="1"  context=""  token=""] (4) POST services/667dde45-3553-40ee-a0db-957bf628b80c

[21:31:11.078] VMware.Cafe: [sub-thread-Id="9"  context=""  token=""] (4) Response: InternalServerError 0:14.597

[21:31:11.112] VMware.Cafe: [sub-thread-Id="6"  context=""  token=""] Json Error: (System exception.)

VMware.Cafe.JsonResponseException: System exception.

   at VMware.Cafe.JsonRestClient.d__2`1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at DynamicOps.Common.Client.RestClient.d__a7`1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()

   at DynamicOps.Common.Client.RestClient.d__c1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at DynamicOps.Common.Client.RestClient.d__8c.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at VMware.Cafe.Client.Registration.d__3.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at VMware.VcacConfig.ServiceCatalogCommands.RegisterCatalogTypes.Execute(CommandLineParser parser)

Warning: Non-zero return code. Command failed.

VRA 7.4 , IAAS(Windows 2012) . All the validations are clean . Any thoughts ?

We are preparing to implement our first VCF solution and VMware have suggested the best approach would be to run the via VM on an ESXi management host rather than use a laptop for stand up.

Looking at the VCF documentation the requirements for this type of deployment seem very specific in terms of having an ESXi host configured with a vmk0 address of 10.1.0.200 and also a private physical switch connected from this ESXi host to the management switch for VCF.

My question is could an existing ESXi host be used to run the VIA VM rather than a dedicated one to avoid this overhead? If so, is there a way to change the need for this specific IP address requirement on vmk0?

The other point I’m looking for clarification on is the need for the dedicated private switch. If i choose to deploy the solution using a laptop i connect directly to my management switch and run the deployment but when i use an ESXi host to run via it adds this additional physical switch to the solution.

Please can someone help me understand the above.

many thanks

Hello,

On a Win 7, 32-bit guest, VM Workstation 12, after some Windows updates and a re-install of VMWare Tools, the guest seems to be running at 100% CPU continuously.

Saw that vmtoolsd.exe was running and would go up to 30% CPU.

Went to system32 and ran the following:

> lodctr /R

the above did run successfully

But issue persisted.

Opened Process Explorer and it seems that VMWare tools vmtoolsd.exe has a related process - WmiPrvSe.exe that keeps getting upto 60% of  CPU. As soon as I stop VMTools service under 'Services', WmiPrvSe.exe goes away and guest runs nicely.

Any suggestion on how to fix this issue?

Thanks,

I recently bought a Gemalto CT1100 bluetooth smart card reader which I intend to use with my Windows 10 under VMWare Fusion 10.1.2. I have a 2016 macbook pro with only USB-C which makes me want to use bluetooth stuff to get rid o adapters. My OS is High Sierra.

I installed the Gemalto Bluetooth Device Manager (GBDM) )on both the Mac OS and in my Windows 10 virtual machine. It se to work fine on the host OS but not in my virtual machine. GDBM software instantly claim "bluetooth is not supported" and I can't seem to find the reader in the bluetooth list in Windows 10.

The SC reader is found as seen in the picture below.

The following picture is from the event log in my virtual machine.

Anyone who have had similar issues or got an idea on what this could be?

I have VMware Workstation 12 Pro.  I've been using it for weeks without a problem.  Suddenly the mouse will stop working in VM.  This happens while the guest is booted and running.  I click to another window and click back, and the mouse will not work in the guest.  This happens in all guests regardless of operating system.  The only way to resolve this is to reboot the host.  Then I can use the guests again for about 15-20 minutes before the problem happens again.

We currently have a problem which has been experienced on VMWare Workstation 7 and VMWare Player 3.1.6 build-744570 and VMWare Workstation 7.1.6 build-744570.

The problem causes mouse clicks to be ignored within the guest OS, and seems to occur after a sound is played within the guest OS.  The issue can be reproduced by opening Windows explorer and navigating through folders by double clicking on the folder.  After opening a folder and then attempting to open another folder or selecting a file within the folder, any further mouse clicks are ignored for a period of time (around 3-5 seconds).  The same thing occurs if a Windows application displays an error message.  The only workaround we have found so far is to disconnect the sound between the host and guest OS:  VMWare menu > Removable Devices > Sound > Disconnect.

The issue was first experienced after a laptop upgrade for the Host OS (upgrade from Windows 7 to Windows 8.1, and a new model of Lenovo Thinkpad).  The issue occurs in VMs that we working fine with the old laptops using the same versions of VMWare.  We are speculating the issue must be related to either Windows 8.1 or the sound driver installed in the Host OS (or a combination).

The driver being used in the Host OS is:
Realtek High Definition Audio
Driver Date: 18/02/2014
Driver Version: 6.0.1.7179

Laptop being used is Lenovo Thinkpad W540 (although this has been seen with other versions of Lenovo laptop)

Host OS version is : Windows 8.1 64-Bit.

Has anyone else experienced these symptoms?

Товарищи, подскажите в чем может быть проблема:

Имеем vCenter 5.5 и vSpehere Data Protection 5.5. При подключении ошибка:

The most recent request has been rejected by the VDP Appliance. 

The most common cause for this error is that the time on the VDP Appliance and the SSO Server are not synchronized. See NTP Configuration in the vSphere Data Protection Administration Guide for more information.

Ок, читаем статью из KB. выясняем что не работает синхрогизация между VDP и vCenter. Вопрос: почему?

Если я вручную пишу команду синхронизировать время - ошибка пропадает и сессия работает пару минут. Время спешит на 3 минуты, дата и часовой пояс соотвествуют.

vCenter работает в одном домене, VDP введен в другой домен, для бэкапа которого он и нужен.

Время в доменах не совпадает, но штука в том, что VDP, не синхронизируется ни с vCenter ни с контроллером второго домена. Вообще живет своей жизнью:

Может кто сталкивался....

Hello All,

I am dealing with two scenarios here.

     1. Migration of vRA/vRO 6.2 to 7.3

     2. Upgradation of vRA/vRO 6.2 to 7.3

I am working for an environment which is running two isolated stacks of vRA 6.2. There needs to be a change in the version of existing vRAs, they need to be of 7.3 version as the support of vRA 6.2 is about to expire in next few months.

Now one instance needs to be migrated to vRA 7.3 as it has already been installed. The other instance needs to be upgraded to vRA 7.3.

I seek help to perform both of the above activities gracefully and want to make it a success in the first attempt. These needs to be done for both the applications vRA and vRO.

Could anyone please let me know all the necessary steps that I ought to take to make it a go through for both of the scenarios? I have been reading various documents related to this, but not able to consolidate all the checks and steps.

If someone could share their experience and knowledge regarding this, that would be great help to me.

Looking forward for the replies.

Hi All,

i need your guys help.

i am trying to add new host   esxi 5.5.0 to my NSX version 6.4.0  Cluster although I read in support information and it mentioned this version of ESX(5.5.0.3568722) is compatible with my NSX (6.4.0 ) but enconter with the error below:

" host X : agent is not deployed due to incompatible host . The host with ESX version 5.5.0 is not compatible with current NSX manager version .please upgrade the ESX version "

what can i do in order to solve this issue.

Thanks!

Ehsan@

Hello Expert ,

I am unable add  Vcenter endpoint in Vra 7.3.1 using cloud client 4.5. I need your help to resolve this problem .

CloudClient>vra endpoint import --filename Vcneter-endpoint.json

Error: Cannot deserialize instance of `java.util.ArrayList` out of START_OBJECT token

at [Source: (String)"{

      "CredentialName": "test",

      "CredentialId": "59518425-7a04-4abb-8914-60877e99c5c4",

      "Description": "",

      "Id": "b3c55e78-3d21-4a0c-9d7d-c300c19365da",

      "Name": "proxy-agent-vsphere-01",

      "PlatformType": 15

}

Hi all,

In the  "Setting up virtual desktops in Horizon 7" PDF on page 23 it says to change Window Firewall Service settings to restart after a failure. All of the settings in the Windows Defender Firewall service are greyed out. I tried shutting off User Account Control and rebooting, I tried shutting off real time protection for Windows Defender... no luck. I am logged in as the local administrator and this master image is not joined to the domain so I know it is not an Active Directory group policy over writing it.

When I try changing the service settings using the SC command I get....

[SC] OpenService FAILED 5:

Access is Denied

Any thoughts?

Thanks!

I often get offline alerts for a ESXi guest. When I login to vSphere, I see the VM is on and can open the console. After opening the console, I'll find the VM not not responding to any commands such as ping or RDP. This time, I happened to see desktop instead of the lock screen. The desktop shows the timestamp of when the machine went "offline". Has anyone else seen this issue. I don't see anything in vmkernel logs or the event viewer for the guest.

ESXi Server 6.0.0,3568940

Vm Guest Version 8

I manage ESXi 6.5.0 Update 1 (Build 7967591) under free license.

I would like to upgrade it to 6.7 (because better macOS client support). There is no .zip file patch yet.

Hypervisor is in restricted network where all HTTP comunication must go through proxy 10.1.2.3:3128.

First I disable firewall to be able to connect to port 3128. I verify this by running nc -vz 10.1.2.3 3128.

When I run either of these commands:

esxcli software sources profile list --depot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-d
epot-index.xml --proxy=http://10.1.2.3:3128

esxcli software sources profile list --depot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-d
epot-index.xml --proxy=https://10.1.2.3:3128

esxcli software sources profile list --depot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-d
epot-index.xml --proxy=10.1.2.3:3128

I get:

 [MetadataDownloadError]
 Could not download from depot at https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml, skipping (('https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml', '', 'file not found'))        url = https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
 Please refer to the log file for more details.

I am able to use http_proxy enviroment varible to use `wget` to download files from the internet.

Is there something wrong with my command or is --proxy switch broken in 6.5.0?