hi

when i try to deploy vm in new server give me blew Error:

A required disk image was missing.

any body can help me to solved this problem ?

Hi,

I've just installed VMWare Workstation 14 on My PC with OS Ubuntu 17.10.

When attempting to run it via the vmware workstation  (Edit > Virtual Network Editor), ask me password and nothing happens.

so I tried to launch the Virtual network editor via cli sudo vmware-netcfg I get prompted for root credential  and then i get this error, anyone seen this that can help?

$vmware-netcfg

Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

- run as super user:

$sudo /usr/lib/vmware/bin/vmware-netcfg

No protocol specified

xcb_connection_has_error() returned true

No protocol specified

xcb_connection_has_error() returned true

No protocol specified

** (vmware-netcfg:14122): WARNING **: Could not open X display

No protocol specified

(vmware-netcfg:14122): Gtk-WARNING **: cannot open display: :0

- run As root:

# /usr/lib/vmware/bin/vmware-netcfg

No protocol specified

xcb_connection_has_error() returned true

XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)

No protocol specified

xcb_connection_has_error() returned true

XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)

No protocol specified

** (vmware-netcfg:14043): WARNING **: Could not open X display

No protocol specified

(vmware-netcfg:14043): Gtk-WARNING **: cannot open display: :0

Hi!

I am facing a problem in recomposing linked clone desktop pool.After I modified the parent virtual machine and took a snapshot of it, I created new recompose task to apply the new snapshot to the desktop pool. It applies on half of them but some virtual machines suffer from the following errors.

View Composer Fault: Could not find VC object of type VirtualMachine, and id (please check the master VM/snapshot or its replica)

Provisioning error occurred for Machine XXX-Agent: Refit operation resync failed

Or on other virtual machines, it shows it has been applied successfully without error, but when I go through virtual machine setting I noticed it doesn't apply.

I changed virtual machine memory from 4 to 3GB memory. I am wondering why did recompose happen to some virtual machines? while

it didn't happen on others !!

Hi folks,

I´m running the Fusion Preview on macOS High Sierra Beta3 (17A315i).

Every time when I try to start a VM I get the following error:

2017-08-06T08:01:17.914+01:00| VMware Fusion| I125: VMHSCmd Command [/vm/#ad41041362aa6272/cmd/##9/op/powerOn/] error: Cannot find a valid peer process to connect to

2017-08-06T08:01:17.924+01:00| VMware Fusion| I125: DUI: Adding new Error dialog 6000001B21A0

2017-08-06T08:01:22.391+01:00| VMware Fusion| I125: SOCKET connect failed, error 2: No such file or directory

Fresh install of Fusion did not work.

I´ve also tried to create a fresh, blank VM but I get the same error. I cannot start anything.

Does anyone see the same behavior?

Thanks and BR/JO!

Hi,

I am using content library items sync. The following codesnippet does not work with line System.Windows.Forms uncommented.. Powershell version is 5.0 and .NET 4.0/4.6.1.

# $groupBoxLog = New-Object System.Windows.Forms.GroupBox

connect-cisserver -server myserver -user user -password password

$contentlibrary = Get-CisService com.vmware.content.local_library

$libraries=$contentlibrary.list()

any idea?

Daniel

Hello,

in a test environment I have 1 ESXi host with some VMs and the VCSA running on it.

As far as I know, the Update Manager of the vCenter is only able to patch the ESXi host, if the ESXi is in maintenance mode. Right?

So in my case, it would be impossible to use Upate Manager for patching the ESXi host? Because if I put the ESXi host to maintenance mode, I would have to shutdown all VMs running on it and therefore also the VCSA. So the Update Manager is unavailable, when the only ESXi host is in maintenance mode.

Or did I understand something wrong?

It's only a very little test environment. But maybe anyone does know a way, how I could use Update Manager with only 1 ESXi host?

Or is it just impossible?

Hi,

I'm trying to install NSX 6.4.0 in our test lab and when I'm trying to deploy the first NSX controller it fails in the vCenter Tasks and Events with the message: Operation timed out.

The log inside Networking & Security states the following:

And by looking at the log inside NSX Manager the first error in a long range of java exceptions is this one:

2018-05-02 16:04:46.479 CEST ERROR pool-45-thread-1 ResourcePoolVcOperationsImpl:196 - - [nsxv@6876 comp="nsx-manager" subcomp="manager"] Error while pushing file '/common/em/components/vdn/controller/ovf/nsx-controller-6.4.0-build7552024-system.vmdk'.
java.net.ConnectException: Connection timed out (Connection timed out)        at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_151]        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_151]

After this point there's a full range of java related garbage messages that continues for ~5 minutes before it gives up.

It seems that the error message Error while pushing file '/common/em/components/vdn/controller/ovf/nsx-controller-6.4.0-build7552024-system.vmdk'. is quite important here, but I haven't found any solutions yet. So far I've reviewed different kb articles (VMware Knowledge Base, VMware Knowledge Base) that used to be valid for 6.3.x, but it seems that the problem is different on 6.4.0.

DNS is setup correctly (VMware Knowledge Base ) and time is synced on all levels so I'm wondering if anyone has seen anything like this before. This is a totally clean environment that was just recently installed from scratch.

Lars

OS:Linux parrot 4.16.0-parrot12-amd64 #1 SMP Parrot 4.16.12-1parrot12.1 (2018-05-28) x86_64 GNU/Linux

Kernel: Linux version 4.16.0-parrot12-amd64 (team@parrotsec.org) (gcc version 7.3.0 (Debian 7.3.0-11)) #1 SMP Parrot 4.16.12-1parrot12.1 (2018-05-28)

Soft: VMware-Player-14.0.0-6661328

Log Data

 

2018-06-30T06:34:56.710-04:00| vthread-1| I125: Log for VMware Workstation pid=2189 version=14.0.0 build=build-6661328 option=Release 2018-06-30T06:34:56.710-04:00| vthread-1| I125: The process is 64-bit. 2018-06-30T06:34:56.710-04:00| vthread-1| I125: Host codepage=UTF-8 encoding=UTF-8 2018-06-30T06:34:56.710-04:00| vthread-1| I125: Host is Linux 4.16.0-parrot12-amd64 Parrot 4.1 2018-06-30T06:34:56.710-04:00| vthread-1| I125: DictionaryLoad: Cannot open file /usr/lib/vmware/settings: No such file or directory. 2018-06-30T06:34:56.710-04:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file /usr/lib/vmware/settings: No such file or directory. 2018-06-30T06:34:56.710-04:00| vthread-1| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values. 2018-06-30T06:34:56.710-04:00| vthread-1| I125: DictionaryLoad: Cannot open file /home/arito/.vmware/config: No such file or directory. 2018-06-30T06:34:56.710-04:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file /home/arito/.vmware/config: No such file or directory. 2018-06-30T06:34:56.710-04:00| vthread-1| I125: PREF Optional preferences file not found at /home/arito/.vmware/config. Using default values. 2018-06-30T06:34:56.710-04:00| vthread-1| I125: DictionaryLoad: Cannot open file /home/arito/.vmware/preferences: No such file or directory. 2018-06-30T06:34:56.710-04:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file /home/arito/.vmware/preferences: No such file or directory. 2018-06-30T06:34:56.710-04:00| vthread-1| I125: PREF Optional preferences file not found at /home/arito/.vmware/preferences. Using default values. 2018-06-30T06:34:56.768-04:00| vthread-1| W115: Logging to /tmp/vmware-root/vmware-2189.log 2018-06-30T06:34:56.847-04:00| vthread-1| I125: Obtaining info using the running kernel. 2018-06-30T06:34:56.847-04:00| vthread-1| I125: Created new pathsHash. 2018-06-30T06:34:56.847-04:00| vthread-1| I125: Setting header path for 4.16.0-parrot12-amd64 to /lib/modules/4.16.0-parrot12-amd64/build/include. 2018-06-30T06:34:56.847-04:00| vthread-1| I125: Validating path /lib/modules/4.16.0-parrot12-amd64/build/include for kernel release 4.16.0-parrot12-amd64. 2018-06-30T06:34:56.847-04:00| vthread-1| I125: Failed to find /lib/modules/4.16.0-parrot12-amd64/build/include/linux/version.h 2018-06-30T06:34:56.847-04:00| vthread-1| I125: /lib/modules/4.16.0-parrot12-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-06-30T06:34:56.847-04:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check 2018-06-30T06:34:56.855-04:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value 4.16.0-parrot12-amd64. 2018-06-30T06:34:56.855-04:00| vthread-1| I125: The header path /lib/modules/4.16.0-parrot12-amd64/build/include for the kernel 4.16.0-parrot12-amd64 is valid. Whoohoo! 2018-06-30T06:34:57.079-04:00| vthread-1| I125: found symbol version file /lib/modules/4.16.0-parrot12-amd64/build/Module.symvers 2018-06-30T06:34:57.079-04:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.16.0-parrot12-amd64/build/Module.symvers. 2018-06-30T06:34:57.104-04:00| vthread-1| I125: Read 20391 symbol versions 2018-06-30T06:34:57.104-04:00| vthread-1| I125: Reading in info for the vmmon module. 2018-06-30T06:34:57.104-04:00| vthread-1| I125: Reading in info for the vmnet module. 2018-06-30T06:34:57.104-04:00| vthread-1| I125: Reading in info for the vmblock module. 2018-06-30T06:34:57.104-04:00| vthread-1| I125: Reading in info for the vmci module. 2018-06-30T06:34:57.104-04:00| vthread-1| I125: Reading in info for the vsock module. 2018-06-30T06:34:57.104-04:00| vthread-1| I125: Setting vsock to depend on vmci. 2018-06-30T06:34:57.104-04:00| vthread-1| I125: Invoking modinfo on vmmon. 2018-06-30T06:34:57.107-04:00| vthread-1| I125: /sbin/modinfo exited with status 256. 2018-06-30T06:34:57.107-04:00| vthread-1| I125: Invoking modinfo on vmnet. 2018-06-30T06:34:57.111-04:00| vthread-1| I125: /sbin/modinfo exited with status 0. 2018-06-30T06:34:57.111-04:00| vthread-1| I125: Invoking modinfo on vmblock. 2018-06-30T06:34:57.114-04:00| vthread-1| I125: /sbin/modinfo exited with status 256. 2018-06-30T06:34:57.114-04:00| vthread-1| I125: Invoking modinfo on vmci. 2018-06-30T06:34:57.118-04:00| vthread-1| I125: /sbin/modinfo exited with status 256. 2018-06-30T06:34:57.118-04:00| vthread-1| I125: Invoking modinfo on vsock. 2018-06-30T06:34:57.121-04:00| vthread-1| I125: /sbin/modinfo exited with status 0. 2018-06-30T06:34:57.135-04:00| vthread-1| I125: to be installed: vmmon status: 0 2018-06-30T06:34:57.152-04:00| vthread-1| I125: Obtaining info using the running kernel. 2018-06-30T06:34:57.152-04:00| vthread-1| I125: Setting header path for 4.16.0-parrot12-amd64 to /lib/modules/4.16.0-parrot12-amd64/build/include. 2018-06-30T06:34:57.152-04:00| vthread-1| I125: Validating path /lib/modules/4.16.0-parrot12-amd64/build/include for kernel release 4.16.0-parrot12-amd64. 2018-06-30T06:34:57.152-04:00| vthread-1| I125: Failed to find /lib/modules/4.16.0-parrot12-amd64/build/include/linux/version.h 2018-06-30T06:34:57.152-04:00| vthread-1| I125: /lib/modules/4.16.0-parrot12-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-06-30T06:34:57.152-04:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check 2018-06-30T06:34:57.160-04:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value 4.16.0-parrot12-amd64. 2018-06-30T06:34:57.160-04:00| vthread-1| I125: The header path /lib/modules/4.16.0-parrot12-amd64/build/include for the kernel 4.16.0-parrot12-amd64 is valid. Whoohoo! 2018-06-30T06:34:57.388-04:00| vthread-1| I125: found symbol version file /lib/modules/4.16.0-parrot12-amd64/build/Module.symvers 2018-06-30T06:34:57.388-04:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.16.0-parrot12-amd64/build/Module.symvers. 2018-06-30T06:34:57.412-04:00| vthread-1| I125: Read 20391 symbol versions 2018-06-30T06:34:57.412-04:00| vthread-1| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.16.0-parrot12-amd64/build/include 2018-06-30T06:34:57.412-04:00| vthread-1| I125: Update kernel header path to /lib/modules/4.16.0-parrot12-amd64/build/include 2018-06-30T06:34:57.412-04:00| vthread-1| I125: Validating path /lib/modules/4.16.0-parrot12-amd64/build/include for kernel release 4.16.0-parrot12-amd64. 2018-06-30T06:34:57.412-04:00| vthread-1| I125: Failed to find /lib/modules/4.16.0-parrot12-amd64/build/include/linux/version.h 2018-06-30T06:34:57.412-04:00| vthread-1| I125: /lib/modules/4.16.0-parrot12-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-06-30T06:34:57.412-04:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check 2018-06-30T06:34:57.421-04:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value 4.16.0-parrot12-amd64. 2018-06-30T06:34:57.421-04:00| vthread-1| I125: The header path /lib/modules/4.16.0-parrot12-amd64/build/include for the kernel 4.16.0-parrot12-amd64 is valid. Whoohoo! 2018-06-30T06:34:57.423-04:00| vthread-1| I125: Found compiler at /usr/bin/gcc 2018-06-30T06:34:57.427-04:00| vthread-1| I125: Got gcc version 7. 2018-06-30T06:34:57.427-04:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove. 2018-06-30T06:34:57.432-04:00| vthread-1| I125: Got gcc version 7. 2018-06-30T06:34:57.432-04:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove. 2018-06-30T06:34:57.434-04:00| vthread-1| I125: Trying to find a suitable PBM set for kernel 4.16.0-parrot12-amd64. 2018-06-30T06:34:57.434-04:00| vthread-1| I125: No matching PBM set was found for kernel 4.16.0-parrot12-amd64. 2018-06-30T06:34:57.434-04:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove. 2018-06-30T06:34:57.434-04:00| vthread-1| I125: Validating path /lib/modules/4.16.0-parrot12-amd64/build/include for kernel release 4.16.0-parrot12-amd64. 2018-06-30T06:34:57.434-04:00| vthread-1| I125: Failed to find /lib/modules/4.16.0-parrot12-amd64/build/include/linux/version.h 2018-06-30T06:34:57.434-04:00| vthread-1| I125: /lib/modules/4.16.0-parrot12-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-06-30T06:34:57.434-04:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check 2018-06-30T06:34:57.443-04:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value 4.16.0-parrot12-amd64. 2018-06-30T06:34:57.443-04:00| vthread-1| I125: The header path /lib/modules/4.16.0-parrot12-amd64/build/include for the kernel 4.16.0-parrot12-amd64 is valid. Whoohoo! 2018-06-30T06:34:57.448-04:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove. 2018-06-30T06:34:57.448-04:00| vthread-1| I125: Validating path /lib/modules/4.16.0-parrot12-amd64/build/include for kernel release 4.16.0-parrot12-amd64. 2018-06-30T06:34:57.448-04:00| vthread-1| I125: Failed to find /lib/modules/4.16.0-parrot12-amd64/build/include/linux/version.h 2018-06-30T06:34:57.448-04:00| vthread-1| I125: /lib/modules/4.16.0-parrot12-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-06-30T06:34:57.448-04:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check 2018-06-30T06:34:57.456-04:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value 4.16.0-parrot12-amd64. 2018-06-30T06:34:57.456-04:00| vthread-1| I125: The header path /lib/modules/4.16.0-parrot12-amd64/build/include for the kernel 4.16.0-parrot12-amd64 is valid. Whoohoo! 2018-06-30T06:34:57.457-04:00| vthread-1| I125: Using temp dir /tmp. 2018-06-30T06:34:57.459-04:00| vthread-1| I125: Obtaining info using the running kernel. 2018-06-30T06:34:57.459-04:00| vthread-1| I125: Setting header path for 4.16.0-parrot12-amd64 to /lib/modules/4.16.0-parrot12-amd64/build/include. 2018-06-30T06:34:57.459-04:00| vthread-1| I125: Validating path /lib/modules/4.16.0-parrot12-amd64/build/include for kernel release 4.16.0-parrot12-amd64. 2018-06-30T06:34:57.459-04:00| vthread-1| I125: Failed to find /lib/modules/4.16.0-parrot12-amd64/build/include/linux/version.h 2018-06-30T06:34:57.459-04:00| vthread-1| I125: /lib/modules/4.16.0-parrot12-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-06-30T06:34:57.459-04:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check 2018-06-30T06:34:57.467-04:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value 4.16.0-parrot12-amd64. 2018-06-30T06:34:57.467-04:00| vthread-1| I125: The header path /lib/modules/4.16.0-parrot12-amd64/build/include for the kernel 4.16.0-parrot12-amd64 is valid. Whoohoo! 2018-06-30T06:34:57.690-04:00| vthread-1| I125: found symbol version file /lib/modules/4.16.0-parrot12-amd64/build/Module.symvers 2018-06-30T06:34:57.690-04:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.16.0-parrot12-amd64/build/Module.symvers. 2018-06-30T06:34:57.713-04:00| vthread-1| I125: Read 20391 symbol versions 2018-06-30T06:34:57.714-04:00| vthread-1| I125: Invoking modinfo on vmmon. 2018-06-30T06:34:57.718-04:00| vthread-1| I125: /sbin/modinfo exited with status 256. 2018-06-30T06:34:58.468-04:00| vthread-1| I125: Setting destination path for vmmon to /lib/modules/4.16.0-parrot12-amd64/misc/vmmon.ko. 2018-06-30T06:34:58.481-04:00| vthread-1| I125: Extracting the vmmon source from /usr/lib/vmware/modules/source/vmmon.tar. 2018-06-30T06:34:58.526-04:00| vthread-1| I125: Successfully extracted the vmmon source. 2018-06-30T06:34:58.526-04:00| vthread-1| I125: Building module with command /usr/bin/make -j4 -C /tmp/modconfig-1Hpnit/vmmon-only auto-build HEADER_DIR=/lib/modules/4.16.0-parrot12-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no 2018-06-30T06:35:03.465-04:00| vthread-1| W115: Failed to build vmmon. Failed to execute the build command. 

 

 

How to remove an orphaned virtual machine under vsphere 6.5 U1.  The vm was deleted under a esxi session but vSphere sees it as "orphaned".  How to remove the orphan?

Dear all,

I recently upgraded my lab server to ESXi 6.7. Everything worked fine until I tried to access my virtual machines using VMRC (Remote Console)

If I open VMRC trough Chrome or Firefox, It shows an authentication screen and it doesn't matter what I enter on it. never authenticates.

With browser console, it fails to connect to virtual machine console

And with new window browser console, it shows only the vmware logo page

I do not have this issue with Microsoft Edge or with Opera browsers.

Do you have any idea what it is happening?

Thank you for your attention.

how to shared VMDK's between virtual machines on one physical host?

Hello Everyone,

If someone can provide some guidance on how to proceed I will appreciate it.

I need advise on what exact training and material I should be using to pursue VMware certifications. So far I found some information on the following site -> VMware Certification Guide: Overview and Career Paths

The site provides the following categories for certification. So I guess I should do them in this order -> VCA -> VCP -> VCAP -> VCDX

• VMware Certified Associate (VCA)
• VMware Certified Professional (VCP)
• VMware Certified Advanced Professional (VCAP)
• VMware Certified Design Expert (VCDX)

Currently I have access to the following VMware training from CBT Nuggets but by looking at the release dates is seems to be outdated.

VMware Horizon 6 (with View)             Release date 2/4/2015

VMware VCA-DCV                               Released date 10/2/2014

VMware vSphere 5.5 VCP5-DCV        Released date 8/25/2014

VMware vSphere 6 (VCP6-DCV)         Released date 8/31/2015

VMware vSphere 6.5 (VCP6.5-DCV)   Released date 7/27/2017

Thanks in advanced.

Hi to all,

we have this problem with our vmware solution.

We have 2 host dell ( vmware vs. 6.5 ) in cluster, connected to a vcenter appliance at the same version 6.5

we want to uograde the vcenter to 6.7 version.

After the first step, when we insert the network information and than wait with the "pre-upgrade checks" we receive this error:

"

Error

Resolution

Author : mimartin

URL : http:////docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-206CF841-F34E-4F54-855F-DA403311CB66.html

Topic Name : Adjust Latency Sensitivity

Publication Name : vSphere Resource Management

Product/Version : VMware vSphere/6.5

Question :

Can I configure this setting at any time after deploying the VM? i.e. can the vm be running? Does the change take effect immediately with no other user interaction required?

c:\scripts\plink.exe : Errors:

At line:1 char:1

+ c:\scripts\plink.exe -pw xxxxx root@esx "/sbin ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (Errors: :String) [], RemoteException

    + FullyQualifiedErrorId : NativeCommandError

Invalid operation requested: This ruleset is required and connot be disabled

any idea why i am getting this error? The putty session restarts the services.sh fine but got error

Write-Output "yes" | plink $plink $vmhost root 'xxxxx' '/sbin/services.sh restart'

Hey everyone I am at last resort, I am running 12.5.9 build-7535481 VMWare Workstation

A VM with Windows Server 2012 R2 is provided to us for installation of a Hyper-V Role.

I can install the Hyper-V role fine and restart but upon restarting it hangs on the loading screen for some time before loading up a BSOD Watchdog Violation Error.

I do not know where to start looking as I have already googled my heart out and tried other forums but I cannot figure it out, some students have had the similar problem and mentioned it was a BIOS issue.

I am using a HP Notebook Windows 10 updated and everything, SSD Samsung fully updated as well.

Thank you for the support and I hope I can find an answer!

Cheers!

I just upgraded my environment to 6.4.1, and am trying to update the certificate being used by an Edge that's providing SSL VPN Plus services. Unfortunately, every time I go to the edge and select Manage->Settings->Certificates, I get the 'greyed out' Flash/Flex "refresh" and the client locks up. This happens with every browser I've tried (that will run a version of Flash, that is) and several different systems, even after flushing cache, etc.

First, I'd like to know if I've got an isolated environment that's to blame (please: someone reproduce this!)

Second, if anyone has a work-around to get this working, it would be appreciated.

vSphere previously implemented Enhanced vMotion Compatibility (EVC) as a cluster-wide attribute because, at the cluster-wide level,  you can make certain assumptions about migrating a VM (for example, even if the processor is not the same across all ESXi hosts, EVC still works). However, this policy can cause problems when you try to migrate across vCenter hosts or vSphere clusters. By implementing per-VM EVC, the EVC mode becomes an attribute of the VM rather than the specific processor generation it happens to be booted on in the cluster.

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,

Hello,

I have VCSA 6.7.0.  I see there is 6.7.0a - so I downloaded the ISO for this (VMware-vCenter-Server-Appliance-6.7.0.11000-8546234-patch-FP.iso).  I connect this to the cdrom, and I try via command line:

Command> software-packages stage --iso
 [2018-06-28T17:54:56.179] : ISO mounted successfully
 [2018-06-28T17:54:56.179] : ISO unmounted successfully
 [2018-06-28T17:54:56.179] : Target patch version is not supported.
 

I've also noticed that in Updates (i.e. VUM) - I have no icon for Updates.  All other functions (Administration, Policies, etc.) have a small icon.  Updates is blank (but I can click on it).

Once I'm in updates, the only "available" updates are from 2015 and version 6.0.0 ?!  I choose Download, and the task fires that claims it's downloading updates.  Nothing changes though.

One other data point - I initially installed this on eval licenses, and I just today bough Essentials and applied the licenses.  I rebooted VCSA clean after applying the licenses.  No change.

TL;DR: VCSA with updates completely stuck.