yes, windows
"Which is the problem of creating the disk, set to physical and then, "multi-writer"?" (done, scsi controller set to virtual share and the disk to multi-writer)
And I don't mind to see it on GUI (windows file system browser) I just want to receive all the files at their newest state.dbalcaraz
Well, in that case you it will be okay.
If the vmdk is shared like that, you will have acces from both VMs without problem. If you notice a missed state from one VM, just refresh the explorer Window for example, or check it in CMD.
Thank you LucD.
Sorry, i missed to say. Apologies. I need to check the bulk VM's from the lists ( C:\temp\liste.txt ) then how will be the script work for this. Not for single VM
Hi,
First, to answer your question - yes you can delete and re-deploy a single controller when it encounters catastrophic, unrecoverable errors or when one of the controller VMs become inaccessible and cannot be fixed - you must first delete the broken controller before deploying a new one.
Second, The controllers lies in the control plane and even if all three controller instances are down, it does not impact your data plane (i.e. your ESXi Hosts running your VMs) network communication. The Impact is when "new" VMs are provisioned, new logical switches are created or any amendments you make to existing objects that require updates to be reported to the controllers and for the controllers to propagate the newly learnt information, down to the VTEPS e.g. routes, MAC addresses, new VTEPS (in case of adding new ESXi Hosts), etc.
If you would like to learn more about the controller nodes and its architecture, please see the link below:
Understanding the Controller Cluster Architecture
The control plane is completely segregated from the data plane to stand its failures, with the caveat I mentioned above, so don't be reluctant to delete and re-deploy all three controllers.
I don't know exactly what happened in your environment and why a single controller node got disconnected, but troubleshooting and resolving an issue with the controllers can sometimes be very quick, but at times can be very cumbersome. The issue may or may not be related to the vCenter memory alarms you mentioned, but I am sure VMware support may have spent time on the issue after which they reached a conclusion to suggest a re-deploy of all three instances. It is also the easiest and quickest way to get a clean and healthy state as the re-deployment and its cluster formation, takes minutes compare to the hours of time spent on troubleshooting. Having said that, it would be ideal to troubleshoot and find the root cause if the issue is re-occurring.
Hope this helps.
Regards,
Varun
Knowledge increases by sharing it...
I am having this issue with Workstation Pro 15. When I drag to an external monitor, mouse works perfectly, when I drag back to my monitor on my laptop, mouse doesn't work. When I open the VM with Player 15 mouse works. I have spent several hours now researching this. I didn't have this issue with version 12, upgraded the other day to Workstation Pro 15 introduced this issue. Any other ideas.....
I'm afraid that nobody except your provider will be able to help in this case.
From a technical point of view, it should be possible to import a previously exported VM, assuming that the export worked correctly.
André
Thanks for the response, that was my first thought, but unfortunately metadataEntry.type returns:
application/vnd.vmware.vcloud.metadata.value+xml
For any metadata type - which while being accurate is not that helpful.
Although I assume that the command line that you've posted is the result of a copy&paste issue, please try the following:
Just to clarify, is the source .vmdk a monolithic virtual disk (a single, large .vmdk file), or is is split into multiple .vmdk files. In case of a split virtual disk, please verify that none of the files is missing.
André
I'm afraid that this won't work.
What you can do, is to enable Shared VMs in VMware Workstation (usually enabled by default), and then configure Autostart for the VM, which will allow you to start the VM with the host.
André
Thanks.
Now I am getting a Windows error message: This app can't run on your PC
And cmd returns this error: Access is denied.
This is the sequence, in an elevated command prompt:
C:\Users\ME\Virtual Machines\Win10>"C:\Program Files (x86)\VMware\VMware Workstation\vmware-vdiskmanager.exe" -r Win10-disk1.vmdk -t 2 Win10-pre-allocated-disk1.vmdk
Access is denied.
I have just performed a P2V conversion using vCenter Converter Standalone 6.2.0.1 with a legacy Dell PowerEdge R2950 running Windows Server 2003 R2 with SP2. The conversion completed 100% successfully and I'm able to boot the converted VM on my ESXI 6.7 U1 host. However, I'm unable to install the VMware Tools to the VM to complete the driver setup for the NIC. I'm running the latest build of VMware Tools of 10338. I'm getting the following pop-up error in vCenter when I attempt to install VMware Tools:
"The required VMware Tools ISO image does not exist or is inaccessible."
I presume the issue is due to running such an old version of Windows Server 2003 on the converted VM. Is there a way to manually install this version of VMware tools or possibly an older version of VMware tools so that I can get the NIC drivers to complete? The original server is using a motherboard NIC by Broadcom.
Thanks for any input.
Ken
Ok, let's see what may be causing this:
André
Windows 10 x64 1809
Workstation 15.0.2 build-10952284
output from dir:
C:\Program Files (x86)\VMware\VMware Workstation>dir
Volume in drive C has no label.
Volume Serial Number is E019-DDBD
Directory of C:\Program Files (x86)\VMware\VMware Workstation
12/12/18 10:02 AM <DIR> .
12/12/18 10:02 AM <DIR> ..
11/21/18 01:22 AM 1,160,112 7za.exe
11/21/18 01:22 AM 94,128 adjperm.dll
11/21/18 01:28 AM 49,072 basichttp.dll
10/20/16 05:11 PM 395,456 DIFXAPI.dll
11/21/18 01:29 AM 997,296 diskLibWrapper.dll
11/21/18 01:29 AM 1,236 dispatcher.xml
11/21/18 01:22 AM 513,968 drvInst64.exe
11/21/18 01:28 AM 210,352 elevated.dll
12/12/18 10:02 AM <DIR> env
12/12/18 10:02 AM 3,117 environments.xml
11/21/18 01:03 AM 112,851 EULA.jp.rtf
11/21/18 01:03 AM 34,900 EULA.rtf
11/21/18 01:03 AM 73,590 EULA.zh_CN.rtf
11/21/18 01:29 AM 141,744 expat.dll
11/21/18 01:24 AM 1,028,528 glib-2.0.dll
11/21/18 01:24 AM 446,896 glibmm-2.4.dll
11/21/18 01:24 AM 31,664 gmodule-2.0.dll
11/21/18 01:24 AM 248,752 gobject-2.0.dll
11/21/18 01:24 AM 25,520 gthread-2.0.dll
11/21/18 01:28 AM 5,412,272 gvmomi.dll
12/12/18 10:02 AM <DIR> hostd
12/12/18 10:02 AM <DIR> ico
11/21/18 01:29 AM 940,464 iconv.dll
11/21/18 01:21 AM 9,609,648 icudt44l.dat
11/21/18 01:24 AM 79,280 intl.dll
11/21/18 01:21 AM 5,175 isoimages_manifest.txt
11/21/18 01:21 AM 165,816 libcds.dll
11/21/18 01:24 AM 402,352 libcurl.dll
11/21/18 01:29 AM 1,364,912 libeay32.dll
11/21/18 01:29 AM 2,035,120 libxml2.dll
11/21/18 01:00 AM 57,602,048 linux.iso
11/21/18 01:00 AM 54,939,648 linuxPreGlibc25.iso
12/12/18 10:02 AM <DIR> messages
11/21/18 01:21 AM 440,848 mkisofs.exe
11/21/18 01:27 AM 28,685 netadapter.inf
11/21/18 01:27 AM 4,408 netbridge.inf
11/21/18 01:27 AM 3,420 netuserif.inf
11/21/18 01:01 AM 540,672 netware.iso
11/21/18 01:29 AM 186,288 nfc-types.dll
11/21/18 01:29 AM 470,960 openssl.exe
11/21/18 01:03 AM 726,629 open_source_licenses.txt
12/12/18 10:02 AM <DIR> OVFTool
11/21/18 01:01 AM 213,443 ovftool_open_source_licenses.txt
11/21/18 01:16 AM 368,056 pcre.dll
11/21/18 01:03 AM 136 readme.txt
12/12/18 10:02 AM <DIR> Resources
11/21/18 01:24 AM 46,000 sigc-2.0.dll
11/21/18 01:01 AM 16,832,512 solaris.iso
11/21/18 01:29 AM 309,168 ssleay32.dll
11/21/18 01:29 AM 472,496 ssoclient.dll
11/21/18 01:28 AM 1,420,957 swagger.zip
11/21/18 01:16 AM 1,471,320 sysimgbase.dll
11/21/18 01:29 AM 1,689 tagExtractor.xml
11/21/18 01:21 AM 451 tools-key.pub
12/12/18 10:02 AM <DIR> tools-upgraders
01/05/18 08:56 PM 944,880 TPClnRDP.dll
11/13/17 02:47 PM 5,966,576 TPClnt.dll
11/13/17 02:47 PM 138,480 TPClntdeu.dll
11/13/17 02:47 PM 129,784 TPClntjpn.dll
11/13/17 02:47 PM 135,408 TPClntloc.dll
01/05/18 08:59 PM 268,024 TPClnVM.dll
10/18/17 03:05 PM 228,592 tppcoipw32.dll
10/18/17 03:05 PM 227,576 tprdpw32.dll
11/21/18 01:29 AM 19,385,776 vim-types.dll
11/21/18 01:29 AM 1,548,288 VirtualPrinter-Linux.iso
11/21/18 01:29 AM 27,820,032 VirtualPrinter-Windows.iso
11/21/18 01:29 AM 5,345,712 vix.dll
11/21/18 01:16 AM 985,600 vixDiskMountApi.dll
11/21/18 01:21 AM 465,016 vixDiskMountServer.exe
11/21/18 01:21 AM 1,232 vixwrapper-product-config.txt
11/21/18 01:21 AM 38,366 vm-support.vbs
11/21/18 01:29 AM 4,158,384 vmacore.dll
11/21/18 01:28 AM 711,088 vmappcfg.dll
11/21/18 01:28 AM 443,824 vmappsdk.dll
11/21/18 01:28 AM 3,276,208 vmapputil.dll
11/21/18 01:16 AM 89,520 vmauthd.dll
11/21/18 01:24 AM 163,248 vmclientcore.dll
11/21/18 01:24 AM 265,648 vmdbCOM.dll
11/21/18 01:24 AM 78,256 vmdkShellExt.dll
11/21/18 01:22 AM 129,968 vmeventmsg.dll
11/21/18 01:27 AM 396,208 vmnat.exe
11/21/18 01:27 AM 46,040 vmnet.sys
11/21/18 01:27 AM 10,659 vmnetadapter.cat
11/21/18 01:27 AM 46,040 vmnetAdapter.sys
11/21/18 01:27 AM 9,504 vmnetbridge.cat
11/21/18 01:27 AM 103,432 vmnetBridge.dll
11/21/18 01:27 AM 66,600 vmnetBridge.sys
11/21/18 01:29 AM 3,732,912 vmnetcfg.exe
11/21/18 01:27 AM 374,192 VMnetDHCP.exe
11/21/18 01:27 AM 9,293 vmnetuserif.cat
11/21/18 01:27 AM 43,992 vmnetUserif.sys
11/21/18 01:29 AM 2,282,416 vmomi.dll
11/21/18 01:16 AM 463,280 vmPerfmon.dll
11/21/18 01:15 AM 789 vmPerfmon.h
11/21/18 01:15 AM 2,962 vmPerfmon.ini
11/21/18 01:28 AM 1,817,008 vmplayer.exe
11/21/18 01:31 AM 5,243,824 vmrest.exe
11/21/18 01:29 AM 469,936 vmrun.exe
11/21/18 01:29 AM 669,616 vmss2core.exe
11/21/18 01:21 AM 53,688 vmUpdateLauncher.exe
11/21/18 01:16 AM 100,784 vmware-authd.exe
11/21/18 01:29 AM 15,446,960 vmware-hostd.exe
11/21/18 01:28 AM 709,552 vmware-kvm.exe
11/21/18 01:28 AM 4,515,248 vmware-remotemks.exe
11/21/18 01:24 AM 97,712 vmware-shell-ext-thunker.exe
11/21/18 01:29 AM 53,680 vmware-tray-helper.dll
11/21/18 01:29 AM 125,872 vmware-tray.exe
11/21/18 01:28 AM 214,448 vmware-unity-helper.exe
12/16/18 12:22 AM 0 vmware-vdiskmanager.exe
11/21/18 01:29 AM 2,402,224 vmware.exe
11/21/18 01:16 AM 6,790,064 vmwarebase.dll
11/21/18 01:24 AM 13,634,992 vmwarecui.dll
11/21/18 01:24 AM 63,920 vmwarestring.dll
11/21/18 01:24 AM 5,827,504 vmwarewui.dll
11/21/18 01:27 AM 134,104 vnetinst.dll
11/21/18 01:29 AM 1,067,440 vnetlib.dll
11/21/18 01:29 AM 1,043,888 vnetlib.exe
11/21/18 01:29 AM 1,266,096 vnetlib64.dll
11/21/18 01:29 AM 1,238,448 vnetlib64.exe
11/21/18 01:27 AM 278,448 vnetsniffer.exe
11/21/18 01:27 AM 273,328 vnetstats.exe
11/21/18 01:22 AM 29,616 vprintproxy.exe
11/21/18 01:01 AM 121,536,512 windows.iso
11/21/18 01:00 AM 14,090,240 winPre2k.iso
11/21/18 01:00 AM 87,752,704 winPreVista.iso
12/12/18 10:02 AM <DIR> x64
11/21/18 01:22 AM 306,608 zip.exe
11/21/18 01:24 AM 91,568 zlib1.dll
120 File(s) 529,543,892 bytes
10 Dir(s) 157,810,233,344 bytes free
If it's a W2k3 it should work no matter the version or edition.
Aren't you able to mount the VMware tools?
If not, the usual ways I think that they use VMware tools.
A thing you can do is, to create a new vmdk, attach it to another server, put the VMware tools package there, then attach it to your server.
And try to install it from that hd.
This, it should work.
The file list I'd like to see is the one from the VM's folder, i.e. "C:\Users\ME\Virtual Machines\Win10".
André
C:\Users\ME\Virtual Machines\Win10>dir
Volume in drive C has no label.
Volume Serial Number is E019-DDBD
Directory of C:\Users\ME\Virtual Machines\Win10
12/16/18 09:08 PM <DIR> .
12/16/18 09:08 PM <DIR> ..
12/12/18 10:16 AM <DIR> caches
12/16/18 03:48 PM 8,684 nvram
12/16/18 10:49 AM 253,130 vmware-0.log
12/16/18 08:59 AM 340,882 vmware-1.log
12/16/18 07:43 AM 250,205 vmware-2.log
12/16/18 03:48 PM 421,045 vmware.log
12/16/18 10:49 AM 2,271 vprintproxy-0.log
12/16/18 08:59 AM 2,271 vprintproxy-1.log
12/16/18 07:43 AM 2,273 vprintproxy-2.log
12/16/18 03:48 PM 2,276 vprintproxy.log
12/16/18 05:46 PM 26,838,958,080 Win10-disk1.vmdk
12/15/18 06:44 PM 95 Win10.vmsd
12/16/18 03:48 PM 3,912 Win10.vmx
12/06/18 12:48 PM 3,592 Win10.vmxf
13 File(s) 26,840,248,716 bytes
3 Dir(s) 156,951,977,984 bytes free
OK.
Could you show your code using instanceof which you said is not working?
Another thing to check (a bit stupid, but there is a chance for it to work). As there is only a handful of possible metadata entry types, for each entry you can try to retrieve its value for each possible type. there is a chance that these calls will return null or throw an error if the entry actual type doesn't match the type you pass to it. Something like the following:
for each (var metadataEntry in metadataEntries) { var val = null; var stringValue = metadataEntry.typedValue.getValue(new VclMetadataStringValue); if (val == null && stringValue != null) { val = stringValue; } var booleanValue = metadataEntry.typedValue.getValue(new VclMetadataBooleanValue); if (val == null && booleanValue != null) { val = booleanValue; } var numberValue = metadataEntry.typedValue.getValue(new VclMetadataNumberValue); if (val == null && numberValue != null) { val = numberValue; } var datetimeValue = metadataEntry.typedValue.getValue(new VclMetadataDateTimeValue); if (val == null && datetimeValue != null) { val = datetimeValue; } if (val != null) { System.log("Metadata key: " + metadataEntry.key + " value: " + val.value); }
} Hello.
What is the VMware community opinions about Xen, Citrix XenServer and XCP-ng? Why you choice VMware? Please tell me clear.
Thank you.
I can't see any thing unusual.
Just to have that checked, please run the two following commands from the VM's folder (C:\Users\ME\Virtual Machines\Win10):
and post the output.
Does your A/V do on-access scanning for .vmdk files? Which A/V application do you use?
Can you please run the vmware-vdiskmanager command again in the way I mentioned earlier, but this time from a "normal" command prompt (i.e. not elevated), to see whether this also returns an error.
André
I am able to mount the VMware tools ISO to the Windows 2003 VM. However, when I attempt to install VMware tools manually by browsing the CD and going to D:\Setup.exe, I am getting "D:\Setup.exe is not a valid Win32 application." The VM is a 32bit version of Windows Server 2003 R2.
Thanks for your suggestions.
Ken