hello guys,

my datastore missing, please help...

it was 2 datastore, but 1 missing after reboot.

but the disk is detected. thx for your help

There is at least one ESXi 6.* build that creates VMFS-volumes that use 128 sectors offset.
See Why does ESXi 6.5 GUI creates VMFS-volumes that are not alligned to 1MB blocks ?
You can check via GUI or
partedUtil getptbl device
or find lines in the vmkernel.log

2018-12-24T12:06:26.924Z INFO     b'gpt\n243201 255 63 3907029168\n1 128 3907029134 AA31E02A400F11DB9590000C2911D1B8 vmfs 0\n'

2018-12-24T12:06:26.924Z DEBUG    Got partGeom: '['1', '128', '3907029134', 'AA31E02A400F11DB9590000C2911D1B8', 'vmfs', '0']'.
Please help to find those build numbers.
I believe we should warn our users not to use those builds.
Or rather to rebuild the affected datastores.
I would also like to see some vmkernel.logs of affected builds.
3 cases with weird behaviour in less than a week is not a large number - it just strikes me as odd and I got interested.
Ulli

新装workstation不能启动虚拟机，提示VMware Workstation 无法连接到虚拟机。请确保您有权运行该程序、访问该程序使用的所有目录以及访问所有临时文件目录。vmx进程提前退出和0x0000007b的错误代码，有哪位大神可以解决

Hello everyone,

i have cluster consist of 4 SuperMicro servers with NVMe drives and i have vCenter 6.7.

when i am trying to configure the VSAN in Create fault domains step i click next but nothing happened and doesn't show me any error.

i tried to reboot the vCenter server multiple time but nothing happened, also i make sure of the disks configuration and VMadapter with vSAN service enable and i have connectivity between the hosts.

also i am working with evaluation license for 60 days.

you can see in the attachment when it's stop.

can anyone help me please with this issue.

thanks

I have a centos 5.x linux server want to migrate to vmware 5.5 , is there way to do the migration , dose vmware have converter for it ?

If I wanted to configure monitoring for Linux based and Windows-based host OS in a hybrid cloud, which of the following services should be confirmed before employing centralized monitoring?

Syslog services,cron services, web services, WMI services or Task Manager services.

This is a question from the exam that I took today?

Thnx

Hello,

I created a virtual machine in virtualbox which I then exported to OVA format using the export.

In VMWare player I then opened the OVA file. The VM opened, I was able to start the virtual machine and test it. All is working correctly.

I now wanted to export the VMWare virtual machine to a OVF format using the ovftool.

I run the ovftool providing the source and target, the ovftool is throwing a "Failed to open file" error no matter which source I provide. It is very frustrating since even in the verbose log there is no indication about which file the program is failing to find.

The verbose log is not very long so I will post it below.

What am I missing??

======= Verbose log

2018-12-27T23:27:15.862-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] [SSL_DB] Using C:\Users\Gordynorth\AppData\Roaming\VMware\ovftool_SSLDB as SSL DB

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Subscribing to signal: 2 (SIGINT)

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Subscribing to signal: 4 (SIGILL)

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Subscribing to signal: 22 (SIGABRT)

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Subscribing to signal: 8 (SIGFPE)

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Subscribing to signal: 15 (SIGTERM)

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Initializing progress

2018-12-27T23:27:15.887-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] OvfTool Version: VMware ovftool 4.3.0 (build-10104578)

2018-12-27T23:27:15.888-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Using home directory: C:\Users\Gordynorth\AppData\Roaming\VMware\ovftool.cfg

2018-12-27T23:27:15.894-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Curl Version: 7.59.0

2018-12-27T23:27:15.894-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Done initializing libs

2018-12-27T23:27:15.894-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Determining source

2018-12-27T23:27:15.895-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Determining target

2018-12-27T23:27:15.895-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Getting source

2018-12-27T23:27:15.896-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Opening source

2018-12-27T23:27:15.896-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] [Context::Context] started. No parameters.

2018-12-27T23:27:15.896-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] [VmxConsumerContext::VmxConsumerContext] started.

2018-12-27T23:27:15.897-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] .\ is not a file

2018-12-27T23:27:15.903-05:00 verbose OVFTool[15156] [Originator@6876 sub=Default] Backtrace:

--> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-10104578, tag: OVFTool, cpu: x86_64, os: windows, buildType: release

--> backtrace[00] vmacore.dll[0x001F6D2A]

--> backtrace[01] vmacore.dll[0x00064FD0]

--> backtrace[02] vmacore.dll[0x0006776E]

--> backtrace[03] vmacore.dll[0x0002533C]

--> backtrace[04] ovftool.exe[0x00013FB6]

--> backtrace[05] ovftool.exe[0x0003AF07]

--> backtrace[06] ovftool.exe[0x0023B3CF]

--> backtrace[07] ovftool.exe[0x0023F77B]

--> backtrace[08] ovftool.exe[0x0023EA12]

--> backtrace[09] ovftool.exe[0x00247641]

--> backtrace[10] ovftool.exe[0x000D16E7]

--> backtrace[11] ovftool.exe[0x00159CBF]

--> backtrace[12] ovftool.exe[0x000DAC7C]

--> backtrace[13] ovftool.exe[0x000DB954]

--> backtrace[14] ovftool.exe[0x003846C5]

--> backtrace[15] KERNEL32.DLL[0x00017E94]

--> backtrace[16] ntdll.dll[0x0006A251]

--> [backtrace end]

vSphere Web Client 服务器（虚拟机清单）上生成报告时出错

I am having problems with my ESXi 6.5, it keeps complaining about the raid controller and it disconnects the LUN more often.

The raid controller that is installed is Megaraid SAS 9271-4i and the native controller that was installed 7.703.15.00-1OEM.XXXX. When I researched that version in the internet, it shows that it is meant for LSI Megaraid 12gbps family (which is for 93XX)

https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI65-AVAGO-LSI-MR3-77031500-1OEM&productId=614

While on the manufacturer's website

https://www.broadcom.com/products/storage/raid-controllers/megaraid-sas-9271-4i#downloads

And it's telling me to use this driver "lsi-mr3-7.702.14.00-1OEM"

ESXi 6.5

https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESX65-AVAGO-SAS-LSI-MR3-77021400-1OEM&productId=614

I am not sure if the native driver 7.703.15.00-1OEM.XXXX is compatible with Megaraid SAS 9271-4i and I am thinking that this is the reason why I am having this issue.  

Please help, I am having this issue for months now.

I am seeing in the server that the LSI Megaraid 9271-4i SAS driver that was installed during the vmware installation has the version 7.703.15.00-1OEM.XXXX. When I researched that version in the internet, it shows that it is meant for LSI Megaraid 12gbps family (which is for 93XX)https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI65-AVAGO-LSI-MR3-77031500-1OEM&productId=614 While in the manufacturers websitehttps://www.broadcom.com/products/storage/raid-controllers/megaraid-sas-9271-4i#downloads It's telling me to use this driver ESXi 6.5https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESX65-AVAGO-SAS-LSI-MR3-77021400-1OEM&productId=614

Hello Everyone,

Can we pull the VMware tools version and VM's HW version for the specific lists of VMs into CSV ? E.g. C:\Temp\vmliste.txt

I want to ensure that we are upgrading the VM's having older version of tools & HW

Thanks

vmk

i will instal sql always on vcenter 6.5 . so i will use shared rdm disk for sql always on ( sql 2017 ) . I wonder something. vm vmotion support for these virtual machine? not storage vmotion. because i will use rdm disk for sharing between two windows 2016

Hello VMware community!

So I have been working with vSphere and Veeam for a few years now.  I recently was hired to a new organization which utilizes new technologies that I am not really familiar with - vDS and vSAN (VxRail).  Basically, I have been pretty much used to a more simple environment with embedded VCSA and now working with a physical server running vCenter 6.5 update 2 on top of Windows Server 2008r2 sp1.  The virtual environment is backed up by Veeam VMs.

My issue is the lack of patch management for the current severs here...vCenter being one of them.  I purchased a physical host license from Veeam to backup the server and my question is not regarding this.  My question is the availability of vSAN and the vDS during the potential vCenter outages that may happen during the patching of this server.  I have done some research on this I wanted to post this to get some input on this.  Even links to KBs would be appreciated.

I am no stranger to fixing things I break but proprietary equipment (VxRail) with technology I haven't worked with to much (vSAN, vDS) scares me a little.

Thanks

Does someone remember what to append to vcenter ip address to retrieve some vm folder information?

Thanks!

I use two Supermicro servers in a homelab. I have had an issue with one of them where if you put it under heavy load it hard resets.

So far there has been nothing in the logs either on the host or within IPMI.

I have two identical hosts and I swapped memory and replaced both HDDs but the issue persisted with the bad host. So I have suspected motherboard, CPU or other hardware issue.

This morning I went to boot it up and I got the following PSOD.

It looks to be an issue with one of the SSDs which forms part of the vSAN disk group. Both SSDs in the host have been replaced and the issue was present on the old ones.

This leads me to believe it is a hardware issue on the box itself, such as the CPU, motherboard, hard drive controller etc.

Is there anything I can check to back up my thoughts?

I just made a fresh install of VMWare 6.7 and it seemed like an automated install. After the installation was done I tried to login but it is asking for a root password. During installation, the install program did not prompt for a root password. In fact all I did was insert the cd and reboot the machine and the installation did the rest to finish without my input. Now I am stuck I have tried loging in without a password but failed. I even tried a lot of suggested passwords such as vmware, password, changeme etc with no luck. please help

I'm trialing ESXI, but when i select "Product version 6.0" from drop-down list, and on the next page "Download trial" it takes me straight to 6.7 download...

Is older versions not available for trial users?

Hello,

I just did a fresh install of ESXI 6.7 on my home lab server. (i7 2600 on intel motherboard)
The VMs are running fine, all stored on SSD.

I wanted to make a backup of the VMs from the SSD on a WD 1TB drive and the transfer is extremely slow.
For example, a Windows 10 VM thin provisioned that use actually about 30 GB took more than 2 hours.
I did the copy with the datastore management.

Is that any normal?

I remember on ESXI 5.5 the transfer was way more quicker.

Exact setup is:
- intel i7 2600
- motherboard intel DZ77GA-70K

- Samsung 860 EVO SSD and WD Blue 1To (both VMFS 6)
- Both drives connected to the same sata controller (intel one)

Thanks a lot for the help, and have a nice day!

Hola Buenas tardes.

Quisiera saber si alguien me puede ayudar con el siguiente tema. En licencias en fecha de caducidad dice nunca.

En los host dice su licencia de EXSI dice licencia caduco.

Trato de bajar una nueva licencia y no he podido. La versión del EXSI es la 6.7. No he podido quitar este menaje o de registrar nuevamente.

Dear all,

I'm struggling with one remote host (6.5 U1) and my vCenter (6.7 U1 appliance) updates.

The remote host is rented in a data center and serves as a "backup plan" for ore services (DCs, Exchange DAG)

It is available through a IP in Internet.

When I had no problem connecting that host to my vCenter, I have difficulties making update manager to work.

Looking at logs a little bit further, I've seen that the host tries to reach the vCenter by looking at DNS name.

Nothing strange there, but as the host is not really on the network, it won't find it.

Some more info :

* All VMs are on a isolated vSwitch, except the firewall that have 2 NICs.

* The FW VM makes a VPN tunnel connection back to the data center, using a second IP on Internet.

I though about putting a manual entry in host file and authorize the host IP to connect back to the vCenter through my firewall with NAT, but maybe there is a cleaner solution.

How would you solve that to get that host patched (and not transforming patching in a nightmare !) ?

Thanks in advance and best regards

ESXi host logs (esxupdate) :

2018-12-27T09:33:54Z esxupdate: 10819274: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetTimeout']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2018-12-27T09:33:54Z esxupdate: 10819274: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetRetries']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2018-12-27T09:33:54Z esxupdate: 10819274: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetRateLimit']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2018-12-27T09:33:54Z esxupdate: 10819274: esxupdate: INFO: --- Command: scan Args: ['scan'] Options: {'cleancache': None, 'viburls': None, 'retry': 5, 'loglevel': None, 'hamode': True, 'timeout': 30.0, 'meta': ['http://vcenter.domain.local:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.5.0-metadata.zip'], 'cachesize': None, 'nosigcheck': None, 'maintenancemode': None, 'proxyurl': None}

2018-12-27T09:33:54Z esxupdate: 10819274: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2018-12-27T09:33:54Z esxupdate: 10819274: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2018-12-27T09:33:54Z esxupdate: 10819274: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2018-12-27T09:33:54Z esxupdate: 10819274: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2018-12-27T09:33:55Z esxupdate: 10819274: HostImage: INFO: Installers initiated are {'boot': <vmware.esximage.Installer.BootBankInstaller.BootBankInstaller object at 0xb9b4c0dd8>, 'live': <vmware.esximage.Installer.LiveImageInstaller.LiveImageInstaller object at 0xb9b32b4a8>, 'locker': <vmware.esximage.Installer.LockerInstaller.LockerInstaller object at 0xb9b32b780>}

2018-12-27T09:33:55Z esxupdate: 10819274: downloader: DEBUG: Downloading http://vcenter.domain.local:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.5.0-metadata.zip to /tmp/tmpj3_uj5ss...

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR: An esxupdate error exception was caught:

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR: Traceback (most recent call last):

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1495, in _do_perform

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR: pycurl.error: (6, "Couldn't resolve host 'vcenter.domain.local'")

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR: During handling of the above exception, another exception occurred:

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR: Traceback (most recent call last):

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esximage/Downloader.py", line 199, in _getfromurl

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1182, in urlgrab

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1036, in _run_callback

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1030, in _do_raise

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1178, in urlgrab

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1097, in _retry

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1070, in _retry

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1163, in retryfunc

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1265, in __init__

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1602, in _do_open

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1740, in _do_grab

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1736, in _do_grab

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/urlgrabber/grabber.py", line 1588, in _do_perform

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR: urlgrabber.grabber.URLGrabError: [Errno 14] curl#6 - "Couldn't resolve host 'vcenter.domain.local'"

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR: During handling of the above exception, another exception occurred:

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR: Traceback (most recent call last):

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esximage/Transaction.py", line 83, in DownloadMetadatas

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esximage/Downloader.py", line 289, in Get

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esximage/Downloader.py", line 202, in _getfromurl

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR: vmware.esximage.Downloader.DownloaderError: ('http://vcenter.domain.local:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.5.0-metadata.zip', '/tmp/tmpj3_uj5ss', '[Errno 14] curl#6 - "Couldn\'t resolve host \'vcenter.domain.local\'"')

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR: During handling of the above exception, another exception occurred:

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR: Traceback (most recent call last):

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/usr/sbin/esxupdate", line 239, in main

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:     cmd.Run()

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esx5update/Cmdline.py", line 105, in Run

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esximage/Transaction.py", line 85, in DownloadMetadatas

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: ERROR: vmware.esximage.Errors.MetadataDownloadError: ('http://vcenter.domain.local:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.5.0-metadata.zip', None, '(\'http://vcenter.domain.local:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.5.0-metadata.zip\', \'/tmp/tmpj3_uj5ss\', \'[Errno 14] curl#6 - "Couldn\\\'t resolve host \\\'vcenter.domain.local\\\'"\')')

2018-12-27T09:33:55Z esxupdate: 10819274: esxupdate: DEBUG: <<<

Hi there,

I was creating a simple script to Clone VM from .csv list. It was working well on certain vCenter, however, when tried on different vCenter, the task was created multiple time resulting in an error saying that the vm already exist, I'm not sure why this happens on this server specifically.

Attached is the script used. And some additional details.

The vCenter version that works is:

• Version 6.5.0
• Build 8024368

The vCenter that doesn't work (task created multiple times):

• Version 6.5.0
• Build 5973321