Hi dotan1234567,

You can also see from the vSphere web client. Just check the VM hardware settings as seen here:

In my example the disk is Thick provisioned do take a look as see what yours says. I'm not aware of anything that would change the format of a VMDK just by attaching and detaching unless something was run inbetween.

As a.p. and continuum have mentioned - it is totally possible that your Thin provisioned disk has expanded to the full allocation.

Anywho - check the above and then revert back

Kind regards.

if any template or VM on temp data store it will give error during pre check.

See my responses here for vMotion discussion and how that's not what you're needing in this case. As far as the disk allocation, no, if these VMs are stored on local storage on individual hosts, while you can *tell* it it can use more than the available space, you can't actually use more than what the datastore has available. And, no, you cannot somehow share the local disk in your second ESXi host with VMs running on the first host.

Hi,

I'm seeing MAC flapping errors on my Cisco switch.  An ESXi host is attached with four interfaces.  No LACP or port-channel is configured.  In any case CDP is a per-physical interface protocol (which should be advertised on physical interfaces and NOT bundles, etc.).

The problem is that the host is sending CDP packets from the same virtual MAC down two interfaces (although the other two interfaces are fine).

Here are the four CDP packets coming from ESX to the Cisco switch (note that the MAC flap error only complains about two of the four ports)

Mar  9 05:13:55.329: CDP-PA: Packet received from esx-01.local on interface GigabitEthernet0/6

Mar  9 05:13:55.329: **Entry NOT found in cache**

Mar  9 05:13:55.329: CDP-EV: Packet Received from esx-01.local with capability = 8 and Platform string = VMware ESX on interface GigabitEthernet0/6

Mar  9 05:13:55.329: CDP-EV: Powernet Event request received on interface GigabitEthernet0/6

Mar  9 05:13:55.329: CDP-EV: New Neighbor discovered, notified registered clients on interface GigabitEthernet0/6

Mar  9 05:13:55.329: CDP-PA: Packet received from esx-01.local on interface GigabitEthernet0/4

Mar  9 05:13:55.329: **Entry NOT found in cache**

Mar  9 05:13:55.329: CDP-EV: Packet Received from esx-01.local with capability = 8 and Platform string = VMware ESX on interface GigabitEthernet0/4

Mar  9 05:13:55.329: CDP-EV: Powernet Event request received on interface GigabitEthernet0/4

Mar  9 05:13:55.329: CDP-EV: New Neighbor discovered, notified registered clients on interface GigabitEthernet0/4

Mar  9 05:13:55.329: CDP-PA: Packet received from esx-01.local on interface GigabitEthernet0/3

Mar  9 05:13:55.329: **Entry NOT found in cache**

Mar  9 05:13:55.329: CDP-EV: Packet Received from esx-01.local with capability = 8 and Platform string = VMware ESX on interface GigabitEthernet0/3

Mar  9 05:13:55.329: CDP-EV: Powernet Event request received on interface GigabitEthernet0/3

Mar  9 05:13:55.329: CDP-EV: New Neighbor discovered, notified registered clients on interface GigabitEthernet0/3

Mar  9 05:13:55.337: CDP-PA: Packet received from esx-01.local on interface GigabitEthernet0/2

Mar  9 05:13:55.337: **Entry NOT found in cache**

Mar  9 05:13:55.337: CDP-EV: Packet Received from esx-01.local with capability = 8 and Platform string = VMware ESX on interface GigabitEthernet0/2

Mar  9 05:13:55.337: CDP-EV: Powernet Event request received on interface GigabitEthernet0/2

Mar  9 05:13:55.337: CDP-EV: New Neighbor discovered, notified registered clients on interface GigabitEthernet0/2

Mar  9 16:13:55.363 AEDST: %SW_MATM-4-MACFLAP_NOTIF: Host 0050.565c.13e7 in vlan 1 is flapping between port Gi0/4 and port Gi0/3

Here is a pcap of the two packets on Gi0/3 and Gi0/4.  Note the identical source MAC (00:50:56:5c:13:e7), however the advertised ports are different.

14:43:55.361048 00:50:56:5c:13:e7 (oui Unknown) > 01:00:0c:cc:cc:cc (oui Unknown), 802.3, length 164: LLC, dsap SNAP (0xaa) Individual, ssap SNAP (0xaa) Command, ctrl 0x03: oui Cisco (0x00000c), pid CDP (0x2000), length 156: CDPv2, ttl: 1

80s, checksum: 0x1812 (unverified), length 156

        Device-ID (0x01), value length: 21 bytes: 'esx-01.local'

        Address (0x02), value length: 13 bytes: IPv4 (1) 0.0.0.0

        Port-ID (0x03), value length: 6 bytes: 'vmnic1'

        Capability (0x04), value length: 4 bytes: (0x00000008): L2 Switch

        Version String (0x05), value length: 21 bytes:

          Releasebuild-11675023

        Platform (0x06), value length: 10 bytes: 'VMware ESX'

        VTP Management Domain (0x09), value length: 1 byte: '^@'

        Duplex (0x0b), value length: 1 byte: full

        MTU (0x11), value length: 4 bytes: 9000 bytes

        AVVID untrusted ports CoS (0x13), value length: 1 byte: 0x00

        AVVID trust bitmap (0x12), value length: 1 byte: 0x00

        System Name (0x14), value length: 21 bytes: 'esx-01.local'

14:44:55.360698 00:50:56:5c:13:e7 (oui Unknown) > 01:00:0c:cc:cc:cc (oui Unknown), 802.3, length 164: LLC, dsap SNAP (0xaa) Individual, ssap SNAP (0xaa) Command, ctrl 0x03: oui Cisco (0x00000c), pid CDP (0x2000), length 156: CDPv2, ttl: $

80s, checksum: 0x1811 (unverified), length 156

        Device-ID (0x01), value length: 21 bytes: 'esx-01.local'

        Address (0x02), value length: 13 bytes: IPv4 (1) 0.0.0.0

        Port-ID (0x03), value length: 6 bytes: 'vmnic2'

        Capability (0x04), value length: 4 bytes: (0x00000008): L2 Switch

        Version String (0x05), value length: 21 bytes:

          Releasebuild-11675023

        Platform (0x06), value length: 10 bytes: 'VMware ESX'

        VTP Management Domain (0x09), value length: 1 byte: '^@'

        Duplex (0x0b), value length: 1 byte: full

        MTU (0x11), value length: 4 bytes: 9000 bytes

        AVVID untrusted ports CoS (0x13), value length: 1 byte: 0x00

        AVVID trust bitmap (0x12), value length: 1 byte: 0x00

        System Name (0x14), value length: 21 bytes: 'esx-01.local'

Thoughts?

Thanks,

Scott

I used the esxi-customizer tool, but it gave me an error.The log information is as follows：

[2019/03/14 周四  9:09:02.43] This is ESXi-Customizer v2.7.2 ...

[2019/03/14 周四  9:09:02.44] Called with parameters:

[2019/03/14 周四  9:09:02.44] ... sISO             = "F:\VMware-VMvisor-Installer-6.7.0.update01-10302608.x86_64.iso"

[2019/03/14 周四  9:09:02.44] ... fOEM             = "F:\net55-r8168-8.045a-napi-offline_bundle.zip"

[2019/03/14 周四  9:09:02.44] ... wDir             = "G:"

[2019/03/14 周四  9:09:02.44] ... repackOpt        = "1"

[2019/03/14 周四  9:09:02.44] ... enableUEFI       = "1"

[2019/03/14 周四  9:09:02.46] ... updateCheck      = "0"

[2019/03/14 周四  9:09:02.46] Creating the temp-directory "G:\esxicust.tmp" ...

[2019/03/14 周四  9:09:02.46] Run: mkdir "G:\esxicust.tmp"

[2019/03/14 周四  9:09:02.47] Extracting the source ISO ...

[2019/03/14 周四  9:09:02.47] Run: "F:\ESXi-Customizer-v2.7.2\tools\7zip\7z.exe" x -y -o"G:\esxicust.tmp\iso" "F:\VMware-VMvisor-Installer-6.7.0.update01-10302608.x86_64.iso"

7-Zip 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18

Processing archive: F:\VMware-VMvisor-Installer-6.7.0.update01-10302608.x86_64.iso

Extracting  .DISCINFO

Extracting  ATA_LIBA.V00

Extracting  ATA_PATA.V00

Extracting  ATA_PATA.V01

Extracting  ATA_PATA.V02

Extracting  ATA_PATA.V03

Extracting  ATA_PATA.V04

Extracting  ATA_PATA.V05

Extracting  ATA_PATA.V06

Extracting  ATA_PATA.V07

Extracting  B.B00

Extracting  BLOCK_CC.V00

Extracting  BNXTNET.V00

Extracting  BNXTROCE.V00

Extracting  BOOT.CAT

Extracting  BOOT.CFG

Extracting  BRCMFCOE.V00

Extracting  BTLDR.T00

Extracting  CHARDEVS.B00

Extracting  CHAR_RAN.V00

Extracting  EFI

Extracting  EFI\BOOT

Extracting  EFI\BOOT\BOOT.CFG

Extracting  EFI\BOOT\BOOTIA32.EFI

Extracting  EFI\BOOT\BOOTX64.EFI

Extracting  EFIBOOT.IMG

Extracting  EHCI_EHC.V00

Extracting  ELXISCSI.V00

Extracting  ELXNET.V00

Extracting  ELX_ESX_.V00

Extracting  ESXUPDT.V00

Extracting  ESX_DVFI.V00

Extracting  ESX_UI.V00

Extracting  FEATURES.GZ

Extracting  HID_HID.V00

Extracting  I40EN.V00

Extracting  IAVMD.V00

Extracting  IGBN.V00

Extracting  IMA_QLA4.V00

Extracting  IMGDB.TGZ

Extracting  IMGPAYLD.TGZ

Extracting  IPMI_IPM.V00

Extracting  IPMI_IPM.V01

Extracting  IPMI_IPM.V02

Extracting  ISER.V00

Extracting  ISOLINUX.BIN

Extracting  ISOLINUX.CFG

Extracting  IXGBEN.V00

Extracting  JUMPSTRT.GZ

Extracting  K.B00

Extracting  LPFC.V00

Extracting  LPNIC.V00

Extracting  LSI_MR3.V00

Extracting  LSI_MSGP.V00

Extracting  LSI_MSGP.V01

Extracting  LSI_MSGP.V02

Extracting  LSU_HP_H.V00

Extracting  LSU_INTE.V00

Extracting  LSU_LSI_.V00

Extracting  LSU_LSI_.V01

Extracting  LSU_LSI_.V02

Extracting  LSU_LSI_.V03

Extracting  LSU_SMAR.V00

Extracting  MBOOT.C32

Extracting  MENU.C32

Extracting  MISC_CNI.V00

Extracting  MISC_DRI.V00

Extracting  MTIP32XX.V00

Extracting  NATIVE_M.V00

Extracting  NE1000.V00

Extracting  NENIC.V00

Extracting  NET_BNX2.V00

Extracting  NET_BNX2.V01

Extracting  NET_CDC_.V00

Extracting  NET_CNIC.V00

Extracting  NET_E100.V00

Extracting  NET_E100.V01

Extracting  NET_ENIC.V00

Extracting  NET_FCOE.V00

Extracting  NET_FORC.V00

Extracting  NET_IGB.V00

Extracting  NET_IXGB.V00

Extracting  NET_LIBF.V00

Extracting  NET_MLX4.V00

Extracting  NET_MLX4.V01

Extracting  NET_NX_N.V00

Extracting  NET_TG3.V00

Extracting  NET_USBN.V00

Extracting  NET_VMXN.V00

Extracting  NFNIC.V00

Extracting  NHPSA.V00

Extracting  NMLX4_CO.V00

Extracting  NMLX4_EN.V00

Extracting  NMLX4_RD.V00

Extracting  NMLX5_CO.V00

Extracting  NMLX5_RD.V00

Extracting  NTG3.V00

Extracting  NVME.V00

Extracting  NVMXNET3.V00

Extracting  NVMXNET3.V01

Extracting  OHCI_USB.V00

Extracting  PROCFS.B00

Extracting  PVSCSI.V00

Extracting  QCNIC.V00

Extracting  QEDENTV.V00

Extracting  QFLE3.V00

Extracting  QFLE3F.V00

Extracting  QFLE3I.V00

Extracting  QFLGE.V00

Extracting  QLNATIVE.V00

Extracting  RSTE.V00

Extracting  S.V00

Extracting  SAFEBOOT.C32

Extracting  SATA_AHC.V00

Extracting  SATA_ATA.V00

Extracting  SATA_SAT.V00

Extracting  SATA_SAT.V01

Extracting  SATA_SAT.V02

Extracting  SATA_SAT.V03

Extracting  SATA_SAT.V04

Extracting  SB.V00

Extracting  SCSI_AAC.V00

Extracting  SCSI_ADP.V00

Extracting  SCSI_AIC.V00

Extracting  SCSI_BNX.V00

Extracting  SCSI_BNX.V01

Extracting  SCSI_FNI.V00

Extracting  SCSI_HPS.V00

Extracting  SCSI_IPS.V00

Extracting  SCSI_ISC.V00

Extracting  SCSI_LIB.V00

Extracting  SCSI_MEG.V00

Extracting  SCSI_MEG.V01

Extracting  SCSI_MEG.V02

Extracting  SCSI_MPT.V00

Extracting  SCSI_MPT.V01

Extracting  SCSI_MPT.V02

Extracting  SCSI_QLA.V00

Extracting  SHIM_ISC.V00

Extracting  SHIM_ISC.V01

Extracting  SHIM_LIB.V00

Extracting  SHIM_LIB.V01

Extracting  SHIM_LIB.V02

Extracting  SHIM_LIB.V03

Extracting  SHIM_LIB.V04

Extracting  SHIM_LIB.V05

Extracting  SHIM_VMK.V00

Extracting  SHIM_VMK.V01

Extracting  SHIM_VMK.V02

Extracting  SMARTPQI.V00

Extracting  TOOLS.T00

Extracting  UC_AMD.B00

Extracting  UC_HYGON.B00

Extracting  UC_INTEL.B00

Extracting  UHCI_USB.V00

Extracting  UPGRADE

Extracting  UPGRADE\ESXIMAGE.ZIP

Extracting  UPGRADE\EXTLINUX

Extracting  UPGRADE\ISOINFO

Extracting  UPGRADE\MBR.BIN

Extracting  UPGRADE\MCOPY

Extracting  UPGRADE\METADATA.XML

Extracting  UPGRADE\METADATA.ZIP

Extracting  UPGRADE\PRECHECK.PY

Extracting  UPGRADE\PREP.PY

Extracting  UPGRADE\PROFILE.XML

Extracting  USBCORE_.V00

Extracting  USB_STOR.V00

Extracting  USER.B00

Extracting  USEROPTS.GZ

Extracting  VIM.V00

Extracting  VMKATA.V00

Extracting  VMKFCOE.V00

Extracting  VMKPLEXE.V00

Extracting  VMKUSB.V00

Extracting  VMWARE-ESX-BASE-OSL.TXT

Extracting  VMWARE-ESX-BASE-README

Extracting  VMWARE_E.V00

Extracting  VMW_AHCI.V00

Extracting  VMX.V00

Extracting  VSAN.V00

Extracting  VSANHEAL.V00

Extracting  VSANMGMT.V00

Extracting  WEASELIN.T00

Extracting  XHCI_XHC.V00

Extracting  XORG.V00

Extracting  [BOOT]\Bootable_NoEmulation.img

Everything is Ok

Folders: 3

Files: 184

Size:       329346510

Compressed: 329611264

[2019/03/14 周四  9:09:09.35] Checking media type ...

[2019/03/14 周四  9:09:09.35] --- INFO: This looks like an ESXi 5.x installation media.

[2019/03/14 周四  9:09:09.37] ---       No admin rights needed to customize ESXi 5.x. Continuing ...

[2019/03/14 周四  9:09:09.37] Removing old boot.cat from ISO directory. It will be created by mksiofs ...

[2019/03/14 周四  9:09:09.38] Run: del /f /q "G:\esxicust.tmp\iso\boot.cat"

[2019/03/14 周四  9:09:09.38] Removing [BOOT] directory from ISO directory ...

[2019/03/14 周四  9:09:09.38] Run: rmdir /s /q "G:\esxicust.tmp\iso\[BOOT]"

[2019/03/14 周四  9:09:09.40] Selected customization type is .zip.

[2019/03/14 周四  9:09:09.40] Unpacking the IMGDB.TGZ file ...

[2019/03/14 周四  9:09:09.40] Run: "F:\ESXi-Customizer-v2.7.2\tools\7zip\7z.exe" x -y -o"G:\esxicust.tmp" "G:\esxicust.tmp\iso\IMGDB.TGZ"

7-Zip 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18

Processing archive: G:\esxicust.tmp\iso\IMGDB.TGZ

Extracting  <fdopen>

Everything is Ok

Size:       1792000

Compressed: 227919

[2019/03/14 周四  9:09:09.45] Run: "F:\ESXi-Customizer-v2.7.2\tools\7zip\7z.exe" x -y -o"G:\esxicust.tmp\imgdb" "G:\esxicust.tmp\IMGDB.tar"

7-Zip 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18

Error:

cannot find archive

[2019/03/14 周四  9:09:09.46] !-----------------------------------------------------------------------------------

[2019/03/14 周四  9:09:09.46] !-- FATAL ERROR: Error un-taring IMGDB.tar!

[2019/03/14 周四  9:09:09.48] !-----------------------------------------------------------------------------------

[2019/03/14 周四  9:09:09.48] Run: "F:\ESXi-Customizer-v2.7.2\tools\MsgBox.exe" 266260 "FATAL ERROR:&n   Error un-taring IMGDB.tar!&n&nSee log file 'G:\ESXi-Customizer.log' for details! Do you want to open the log file in notepad now?"

[2019/03/14 周四  9:09:18.60] Cleaning up ...

[2019/03/14 周四  9:09:18.62] Run: rmdir /s /q "G:\esxicust.tmp"

[2019/03/14 周四  9:09:18.70] This is the end.

Hope the name of that VM does not mean what it looks like ....
Anyway - we need to see a vmware.log from a start with the current config to check your vmx-file parameters.

I not permit use close source SetUserFTA.exe.  too got EricNichols script work using settings here Windows 10 – How to configure file associations for IT Pros? – C:>Windows Internals – L'équipe Française de Support Wind…

> STORAGE IS FULL
That is an easy fix:
Plan A: free up some space by deleting stuff you  no longer need
Plan B: get more storage
> AND ITS MAKING A BEEP SOUND.
What does that sound like ?
Option A: some app uses this as a warning signal and this alarm may go away after you are done with Plan A oder B
Option B: it sounds like the device is kaputt - you can probably ignore this after you are done with plan B
> I would like to clear the messages and the get ride of the deep sound.
Bad approach: you want to solve your "dont have enough free space to work" problem - cureing the symptoms will not help you.

I have to tell you the same as you have already been told.
More details >>> better answers

Do not use "auto-bridgeing" when you create a bridged network.
Do not use "Custom" for vmnet0 - instead assign vmnet0 to a physical network card.
If you think you need to violate one of the 2 rules above you may need to create your vmx-files manually - see sanbarrow.com

The problem could very well be the following.  I would bet 99% this is it.  So pay attention.

Your linux machines are using SMB1.  In the recent updates, Microsoft has disabled that due to very dangerous virus / ransom attacks through SMB1.

However if you need it you can go to control panel and select apps.  There on the right side of a fully opened screen, Programs and Features.  Click that and then on the left side click Turn Windows Features on and Off.   Go down to SMB1 and click it and you get two more check circles.  Client or Server.  I think you just need client.  Exit, reboot and go.

Remember to close you virtual machines before you do this so you can reboot.

If this works you can try the following too...

In you smb.conf file you can add the following for VMware

interface eth0 vmnet0

and in the global section add a security item

nt pipe support = no

Good luck

Hello,

I created an RDM disk and copied / moved it to another folder.

But when I try to add an existing disk and locate the pointer, it does not show as a physical lun. Shows a common disk (Thick).

If I try to add the existing disk that is still in the VM folder, it shows as physical lun.

What did I do wrong?

Thank you.

Just a thought.  I don't suppose https://kb.vmware.com/s/article/56614

would apply?

Carl L.

Create a new RDM descriptor instead.

How do I do that?

Facing similar issue, tried with all the suggested recommendations, same error everytim

It always creates in the VM folder.

I want to create in another folder.

I want the RDM pointers to be in another folder.

Having the same problem here. ESXi: 6.7.0 Update 1 (Build 10302608). It seams is dependent on the hardware. I have the same build installed on 5 different machines and this issue occurs only on one of them : ASRock E3C226D2I mother board with Intel Haswell Core i3-4170 3.7 GHz CPU and 16GB RAM.

We have currently running on version 17.2 and will be upgrading to 18.3 Horizon Cloud Hosted to be done by VMware.

We need to install HAI unified agent 18.2.2 which replaces DaaS agent and Horizon Agent on our RDSH master image.

Do we need to update the ADMX files which is included in the download link for 18.3?

File: Horizon 7.5.0 View GPO Bundle (VMware-Horizon-Extras-Bundle-4.8.0-8519436.zip)

Hi,

Thanks for the reply. Actually, these are the correct settings that I currently have and I believe it is the same as what you mentioned. If there is any mistake kindly let me know. There is still no internet access, unfortunately.

Thank you

Sincerely

Chathuka     

Hi,

After I enabled the FlexEngine logoff command, it will sign me out immediately after entering my username and password. Did I miss anything? Thank you.

User Configuration > Windows Settings > Scripts> logoff

C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe –s

Yazid-