Hello Experts,

I have installed the VM Workstation Pro 12 on Linux Mint 19. The installation is completed, but the services are not starting up.

I am stuck, Kindly help me to fix the issue.

Attached screenshot for reference.

Hi,

i have a problem with redirecting USB printers with the PCOIP protocol.

The printers are not redirected,

There are two ways to solve this:

Restart the TP AutoConnect and TP VC Gateway Services, after that  the printers will be visible.

Disconnect the session  and connect after a few minutes

i already change the timeout settings on the virtual machine.

HKEY_LOCAL_MACHINE" key="SOFTWARE\ThinPrint\TPAutoConnect" name="TimeOutClient" type="REG_DWORD" value="00124F80"/></Registry>

HKEY_LOCAL_MACHINE" key="SOFTWARE\ThinPrint\TPAutoConnect" name="TimeOutClientExecution" type="REG_DWORD" value="00124F80"/></Registry>

Anyone seen this problem or can help me with a solution?

VMware Horizon Version 7.5 ( I didn\t work in 7.2 as well)

Windows 7 as VDI os

regards

Jan

Hi,

i installed a new VCenter 6.7 Appliance. But if i want to add the a new Storage Provider for my EMC Unity Vcenter tells me he cannot create a new signed Certificate

My first try was to reset all the Certificates for the Vcenter over SSH. But dosent Help.

Bei der Bereitstellung eines signierten Zertifikats der VMware Certificate Authority (VMCA) für den Anbieter ist ein Problem aufgetreten.

Hi everybody,

We have a cluster running 10 HPE Proliant DL380 G9 und VCenter 6.5. Vcenter Appliance is running the latest Version from VMware and also the ESXi Hosts are up to date running Version VMware ESXi, 6.5.0, 8935087.

Cluster is running in EVC Mode in Intel® "Haswell" Generation because 5 of our hosts are running with Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz and the other five are running with Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz.

All of these hosts have applied latest Bios und Microcode Update from HPE (Version 2.60). According to HPE this should fix CVE-2018-3639.

According to VMware Knowledge Base we should find “Capability Found: cpuid.SSBD” in vmware.log of guest VMs after powering down and restarting them. But we don't have this. So it looks like the patch is not correctly applied to all servers in the cluster or something else is missing.

On a Windows Guest VM running Get-SpeculationControlSettings results in:

Speculation control settings for CVE-2017-5715 [branch target injection]

For more information about the output below, please refer to https://support.microsoft.com/en-in/help/4074629

Hardware support for branch target injection mitigation is present: True

Windows OS support for branch target injection mitigation is present: True

Windows OS support for branch target injection mitigation is enabled: False

Windows OS support for branch target injection mitigation is disabled by system policy: True

Windows OS support for branch target injection mitigation is disabled by absence of hardware support: False

Speculation control settings for CVE-2017-5754 [rogue data cache load]

Hardware requires kernel VA shadowing: True

Windows OS support for kernel VA shadow is present: True

Windows OS support for kernel VA shadow is enabled: False

Speculation control settings for CVE-2018-3639 [speculative store bypass]

Hardware is vulnerable to speculative store bypass: True

Hardware support for speculative store bypass mitigation is present: False

Windows OS support for speculative store bypass mitigation is present: True

Windows OS support for speculative store bypass mitigation is enabled system-wide: False

Suggested actions

* Follow the guidance for enabling Windows Server support for speculation control mitigations described in https://supp

ort.microsoft.com/help/4072698

BTIHardwarePresent                  : True

BTIWindowsSupportPresent            : True

BTIWindowsSupportEnabled            : False

BTIDisabledBySystemPolicy           : True

BTIDisabledByNoHardwareSupport      : False

KVAShadowRequired                   : True

KVAShadowWindowsSupportPresent      : True

KVAShadowWindowsSupportEnabled      : False

KVAShadowPcidEnabled                : False

SSBDWindowsSupportPresent           : True

SSBDHardwareVulnerable              : True

SSBDHardwarePresent                 : False

SSBDWindowsSupportEnabledSystemWide : False

Another HPE Proliant DL380 Proliant G9 running Windows native without VMware and with HPE Bios Version 2.60 brings the following result when running Get-SpeculationControlSettings:

Speculation control settings for CVE-2017-5715 [branch target injection]

For more information about the output below, please refer to https://support.microsoft.com/en-in/help/4074629

Hardware support for branch target injection mitigation is present: True

Windows OS support for branch target injection mitigation is present: True

Windows OS support for branch target injection mitigation is enabled: False

Windows OS support for branch target injection mitigation is disabled by system policy: True

Windows OS support for branch target injection mitigation is disabled by absence of hardware support: False

Speculation control settings for CVE-2017-5754 [rogue data cache load]

Hardware requires kernel VA shadowing: True

Windows OS support for kernel VA shadow is present: True

Windows OS support for kernel VA shadow is enabled: False

Speculation control settings for CVE-2018-3639 [speculative store bypass]

Hardware is vulnerable to speculative store bypass: True

Hardware support for speculative store bypass mitigation is present: True

Windows OS support for speculative store bypass mitigation is present: True

Windows OS support for speculative store bypass mitigation is enabled system-wide: False

Suggested actions

* Follow the guidance for enabling Windows Server support for speculation control mitigations described in https://supp

ort.microsoft.com/help/4072698

BTIHardwarePresent                  : True

BTIWindowsSupportPresent            : True

BTIWindowsSupportEnabled            : False

BTIDisabledBySystemPolicy           : True

BTIDisabledByNoHardwareSupport      : False

KVAShadowRequired                   : True

KVAShadowWindowsSupportPresent      : True

KVAShadowWindowsSupportEnabled      : False

KVAShadowPcidEnabled                : False

SSBDWindowsSupportPresent           : True

SSBDHardwareVulnerable              : True

SSBDHardwarePresent                 : True

SSBDWindowsSupportEnabledSystemWide : False

So according to this one. The HPE Bios have the problem fixed but only VMware have something missing.

does somebody have such issues? what can we do to get this fixed?

Thank you for help,

Virtual Machine disk descriptor file is missing:

We performed vmotion of a virtual machine (VM1) and had a strange incident (errors) faced.

Relocate virtual machine

Status: The VM failed to resume on the destination during early power on.

Error stack:

The source detected that the destination failed to resume.

The VM failed to resume on the destination during early power on.

Power On virtual machine

Status: File /vmfs/volumes/<datastore>/VM1/VM1.vmdk was not found

Error stack:

An error was received from the ESX host while powering on VM VM1

Failed to start the virtual machine.

Module 'Disk' power on failed.

Cannot open the disk '/vmfs/volumes/<datastore id>/VM1/VM1.vmdk' or one of the snapshot disks it depends on.

The system cannot find the file specified

File system specific implementation of Lookup[file] failed

File system specific implementation of Lookup[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of Lookup[file] failed

VMware ESX cannot find the virtual disk "/vmfs/volumes//<datastore>/VM1/VM1.vmdk ". Verify the path is valid and try again.

When we browse to check the files in datastore>VM folder, there was no VM1.vmdk of the virtual machine and we can see VM1-flat.vmdk and VM1-ctk.vmdk files?????

We have re-created the VM1.vmdk file and brought VM live in production (as mentioned in the link),

My Question is:

What could be the reason for vmdk descriptor file is missing???

How all these days it was working fine without any issue??

Hello.

Do you know if vCloudDirector 8.20 and vSphere 6.5 products support the OVF2.0 specification to deploy a new vApp?

If this is the case, if a vApp was deployed with an OVF1.0 descriptor file, can it be upgraded to ovf2.0 some way?

We'd need to add the "Support for Network Ports" feature to a running vApp deployed with OVF1.0 by adding the <ovf:EthernetPortItem > under the VirtualHardwareSection.

Good morning guys,

I'm in the process of moving my Domain Controller VM from my main datastore to a second due to damage on the first datastore.

Unfortunatelly the VM wasn't made by me so it' essentially a 1.08TB VM to move... I started the move and it's saying that it's gonna take upwards of 2 DAYS to move it...

is it possible?????

Hello !

Can anyone provide me with tips to study for the VCAP-DCV 6.5 deploy Exam

Thank you in advance

what will happens after 60 days of evaluation of VSphere esxi 6.7

Hi

Im trying to migrate a VM using Converter 5.1 but I get the "Permission to perform this operation was denied" error message when i select the source machine (which is powered off) or when i click on the "view source details..."

I see the following error in the Convertor Standalone client log file "[05496 error 'wizardController'] Must be administrator to access physical computer"

The domain account I am using is a member of the Local Users group on the Convertor server and has Converter permissions on the source vCenter where the VM is.

Any ideas as to why I get this error?

VM Hardware version 9

2013-10-30T12:40:53.106+01:00 [05496 verbose 'wizardController'] Trying connection to VC server 'vcserver.domain.local' with user 'domain\domadminac'

2013-10-30T12:40:53.106+01:00 [05496 verbose 'wizardController'] Getting VIM connection to vcserver.domain.local...

2013-10-30T12:40:53.106+01:00 [05496 info 'wizardController'] Reusing existing VIM connection to vcserver.domain.local

2013-10-30T12:40:53.106+01:00 [05496 verbose 'ManagedMachineDataConnectionLogger'] Getting VIM connection to vcserver.domain.local...

2013-10-30T12:40:53.106+01:00 [05496 info 'ManagedMachineDataConnectionLogger'] Connecting to host vcserver.domain.local on port 443

2013-10-30T12:40:53.106+01:00 [05496 info 'ManagedMachineDataConnectionLogger'] localVersion is: vim.version.version8

2013-10-30T12:40:53.107+01:00 [05496 info 'ManagedMachineDataConnectionLogger'] Remote version is: vim.version.version8

2013-10-30T12:40:53.107+01:00 [05496 verbose 'ManagedMachineDataConnectionLogger'] [VimApi] Local and Remote Version are the same. Talking with version vim.version.version8

2013-10-30T12:40:53.107+01:00 [05496 info 'ManagedMachineDataConnectionLogger'] Authenticating user domain\domadminac

2013-10-30T12:40:53.107+01:00 [05496 verbose 'HttpConnectionPool-000006'] HttpConnectionPoolImpl created. maxPoolConnections = 1; idleTimeout = 900000000; maxOpenConnections = 1; maxConnectionAge = 0

2013-10-30T12:40:53.322+01:00 [05496 error 'wizardController'] Must be administrator to access physical computer

2013-10-30T12:41:29.461+01:00 [05496 verbose 'HttpConnectionPool-000005'] [RemoveConnection] Connection removed; cnx: <SSL(<io_obj p:0x0555e980, h:-1, <TCP '0.0.0.0:0'>, <TCP '10.XXX.XXX.XXX:443'>>)>; pooled: 0

2013-10-30T12:41:29.461+01:00 [06592 verbose 'HttpConnectionPool-000003'] [RemoveConnection] Connection removed; cnx: <SSL(<io_obj p:0x051c30c0, h:-1, <TCP '0.0.0.0:0'>, <TCP '10.XXX.XXX.XXX:443'>>)>; pooled: 0

2013-10-30T12:41:39.477+01:00 [04588 verbose 'HttpConnectionPool-000006'] [RemoveConnection] Connection removed; cnx: <SSL(<io_obj p:0x0555eba8, h:-1, <TCP '0.0.0.0:0'>, <TCP '10.XXX.XXX.XXX:443'>>)>; pooled: 0

Message was edited by: GuyTC changed "target vCenter" to read "source vCenter"

Message was edited by: GuyTC : corrected errors in original question. It turns out my domain account was NOT a member of the Local Administrators group on the Converter server. Adding my domain account to the Local Admins group on the Converter server fixed the error.

Dear All,

Last week, I found one of my VM cannot work properly and found the VM host is full of disk. I would like to delete one of my snaphot to free the disk. There are totally 4 snapshots (001,002,003,004). I power down the VM and deleted the 003 snapshot. After deleting the snapshot, It can free up over 100G.

However, when I tried to power up the VM, I found it can't start the VM and prompted "The system cannot find the file specified VMware ESX cannot find the virtual disk ".....FMC-0003.vmdk.". Even I want to consolidate the disk and it also promoted the error.

Actually, I didn't backup the 0003.vmdk file and at this moment, I am worried the VM can't start forever as there is some important information stored.

I would like to ask whether any method or suggestion at this moment ? Thanks all.

Hi,

I am trying to add a step to my server build workflow that moves the server object to a different OU after its joined the domain, it works fine with a single VM but when i add the variable input by the user into the worflow it fails. basically fails as soon as i try to do a foreach and i think that is because the data input variable is a string but the AD element required the input to be an array. I have tried adding code like these 2 to convert the code but neither work. The code is a bit further down,

var str = vm;

//var computer = str.split();var =

var computer = Array.from(str);

var newOu = XXXXX

var newSQLOu = XXXX

for (var vm in vmName) {

var temp = ActiveDirectory.getComputerAD(vm);

if (vm.name = GBRDCTST) {

ActiveDirectory.rename(temp.distinguishedName,"CN="+vm,newOu);

}

else {ActiveDirectory.rename(temp.distinguishedName,"CN="+vm,newSQLOu);

}

}

Hello Everyone,

Use case : “Promoting existing VMs or Cloud VMs to vRA for management”.

I am able to generate a CSV file using VRO Javascript Workflow and files gets saved in local machine.

Now I am stuck at the next step , i.e. to import machines from that CSV file to vRA, for management. I explored Rest API for this process, though it did not provide much information. Any suggestions, how to do this achieve this process VRO Javascript Workflow ?

Hi,

We migrate our VMs from a 7.3 environment to a new 7.4 environment.

We encounter this error :

Error occurred while retrieving blueprint and component information. Message: 'One or more errors occurred.'

We have try to :

- Recreate a New IaaS blueprint.

- IaaS BP are present in the BG entitlement

- We have exported the virtual machines with the option "Include custom properties"

- We have modified the CSV file like this :

Has anyone come across this problem before ?

Thx for your feedback.

Hello,

Is there a way to return a list of all applications in Horizonview.

I can create an application with VMware.Hv.ApplicationService but how do i retrieve all the applications?

Best regards,

vSphere HAが有効な環境でメンテナンスモード後にESXi1台で障害が発生して起動不可となった場合、

対象ESXi上の仮想マシンを別ESXiで起動させるにはどうすると良いでしょうか。

例えばデータストアから対象の仮想マシンを別名で登録するといった方法になりますでしょうか。

またこのとき、vCenter Serverが起動できていた場合、起動できていない場合で対処方法はかわりますでしょうか。

以下の設定になっている環境とします

・vSphere 6.x

・vSphere HAは有効

・アドミッションコントロールは無効

以下の処理は正常に出来ているとします

・仮想マシンは全て停止

・ホストは全てメンテナンスモード(※仮想マシンの移動はなし)

・ホストを全てシャットダウン

添付図のように"esx-02"は起動できず、"esxi-03"は起動できた状態で、

"切断状態"となっている仮想マシンを起動させたいような状況です。

Hi

i have exactly the same issue. Do we have any solution for this or workaround.

Regards,

Aravind.g.k.

Is it possible to determine just be connecting to a VCSA and examining it by Web Client or PowerCLI how it was deployed? By which I mean : when it was deployed what Deployment Size and Storage Size options were chosen?

I am using RegisterVM_Task API to register Virtual Machines on VCenter 6.5 (managed ESXs are also 6.5).

However, at times, the RegisterVM_Task fails with SystemError and the message is: "A general system error occurred: internal error"

Following is a log snippet from vpxd log for one such failure:

2018-07-26T08:23:16.173Z error vpxd[7FDDBBA66700] [Originator@6876 sub=VmProv opID=14f2e116-01] Get exception while executing action vpx.vmprov.RegisterDestinationVm: N5Vmomi5Fault11SystemError9ExceptionE(vmodl.fault.SystemError)

--> [context]zKq7AVECAAAAAAHCfgAddnB4ZAAAJGcrbGlidm1hY29yZS5zbwAA9B4bAD5vGAHI5VR2cHhkAAHd51QBYRzLAR4C0AFza9EBqqTOATDHzgF9zM4BFdBzAYrFcwFB6nMBoLJzAQVQygH7UMoBiNl4ggZeBgFsaWJ2aW0tdHlwZXMuc28AAfzYdAEV0HMBisVzAUHqcwGCPXQAo7QjAIq3IwDbvysDRHQA

2018-07-26T08:23:16.233Z info vpxd[7FDDBBA66700] [Originator@6876 sub=Default opID=14f2e116-01] [VpxLRO] -- ERROR lro-549516 --  -- VmprovWorkflow: vmodl.fault.SystemError:

--> Result:

--> (vmodl.fault.SystemError) {

-->    faultCause = (vmodl.MethodFault) null,

-->    faultMessage = <unset>,

-->    reason = "internal error"

-->    msg = ""

--> }

--> Args:

-->

2018-07-26T08:23:16.233Z info vpxd[7FDDBBA66700] [Originator@6876 sub=vpxLro opID=14f2e116] [VpxLRO] -- FINISH task-2654

2018-07-26T08:23:16.233Z info vpxd[7FDDBBA66700] [Originator@6876 sub=Default opID=14f2e116] [VpxLRO] -- ERROR task-2654 -- group-v3 -- vim.Folder.registerVm: vmodl.fault.SystemError:

--> Result:

--> (vmodl.fault.SystemError) {

-->    faultCause = (vmodl.MethodFault) null,

-->    faultMessage = <unset>,

-->    reason = "internal error"

-->    msg = ""

--> }

--> Args:

-->

--> Arg path:

--> "[vsanDatastore] vsan-scale-vm9/vsan-scale-vm9.vmx"

--> Arg name:

--> "vsan-scale-vm9"

--> Arg asTemplate:

--> false

--> Arg pool:

--> 'vim.ResourcePool:resgroup-23'

--> Arg host:

-->

Please let me know if anybody else has seen this behavior and if there was any resolution.

Also let me know if looking at some other logs might help.

When I connect my esxi host by remote location give no peer certificate found