Hi all,

I have a task to clear one storage completely.

For this, I need to do storage vmotion of around 200 + vms  from one datastore to another.

I can write script for this purpose to automate the activity.

If executed in async mode, so that multiple vms can get svmotion simultaneously, I believe there will be a large queue of svmotion to be executed.

To avoid this, i would like to introduce sleep if live storage vmotion on that vcenter is more than 4.

Is there a possibility to find the number of live storage vmotion in progress? If yes, how to do it.

Please help.

Thanks in advance.

We are trying out to qualify our web client plugin on vCenter 6.5 RC. The registration fails saying that the "Underlying connection was closed". An exactly similar setup with 6.5 beta works absolutely fine.

Both the setups use same vertical stack below. i.e till windows server 2008 R2. The 6.5 RC was also tried on windows server 2012. But to get the same error suring plugin registration.

The services listed in the host w.r.t VMWare are exactly same and are started. Is there anything that is changed between beta and RC for plugin developers to check out for?

Anticipating your help here. We are blocked with the qualification as of now.

Hi All,

I'm having trouble setting the Advanced Option DisallowSnapshotLUN in Powershell for vSphere 6

I don't know the correct syntax.

Who can help

Thanks

Jean

Is it supported to upgrade directly from vRA 6.2 to vRA 7.1?

Hi,

I am trying to access a VXLAN network that I created in VIO from vSphere environment.

I am just adding an interface to the VM in vSphere and adding the VIO network. After adding the VIO network I am modifying the IP details like IP address, gateway and subnet.

When I am trying to ping to the gateway from the vSphere VM, I am unable to get any response to the ICMP request.

Question - How can I access a VIO network in vSphere environment?

Question - Is it possible to add an external network as a subnet to a router ?  I am only able to set an external network's gateway (that I created as a portgroup in vSphere) to the VIO router. Any information on the above will be very helpful

Thanks

Ratnajit

After some time running, the console UI crashes with the following messages:-

(the virtual machines stay running though)

MXUserAllocSerialNumber: too many locks!

VMware Workstation Error:

VMware Workstation unrecoverable error: (vix)

MXUserAllocSerialNumber: too many locks!

A log file is available in "/tmp/vmware-devnull/vmware-vix-6115.log". 

You can request support. 

To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.

You can also run the "vm-support" script in the Workstation folder directly.

We will respond on the basis of your support entitlement.

MXUserAllocSerialNumber: too many locks!

VMware Workstation Error:

VMware Workstation unrecoverable error: (vmui)

MXUserAllocSerialNumber: too many locks!

A log file is available in "/tmp/vmware-devnull/vmware-ui-28658.log". 

You can request support. 

To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.

You can also run the "vm-support" script in the Workstation folder directly.

We will respond on the basis of your support entitlement.

Hey all,

I posted a discussion yesterday that included this question as well. But as i was able to figure out all other parts and this is the one that I can't figure out I posted a new discussion.

Hope thats ok

every single time I call cloud client with parameters from UI (even in same session) it keeps logging in (even though it says persistent). example:

(the parts in RED are messing up my output (can't parse the result after it) and it's unnecessary. are there any switches or any ways I get the results without cloudclient loggin in every time and desplaying java.version?

cloudclient.bat vra catalog list --format JSON

java.version

CloudClient is logging in vRealize Automation with persisted session

vRA 7.0 login: [ACTIVE], session: [ACTIVE], sessionKey=[default], user=[me], server=[https://myserver], tenant=[vsphere.local]

CloudClient is logging in IaaS with persisted session

IaaS Model Manager login: [ACTIVE], session: [ACTIVE], sessionKey=[default], user=[me], server=[myserver]

CloudClient is logging in vRealize Orchestrator with persisted session

VCO login: [ACTIVE], session: [ACTIVE], sessionKey=[default], user=[administrator@vsphere.local], server=[myserver]

[ {

  "callbacks" : null,

invoke the same command again: Any way to skip the whole red output???

cloudclient.bat vra catalog list --format JSON

java.version

CloudClient is logging in vRealize Automation with persisted session

vRA 7.0 login: [ACTIVE], session: [ACTIVE], sessionKey=[default], user=[me], server=[https://myserver], tenant=[vsphere.local]

CloudClient is logging in IaaS with persisted session

IaaS Model Manager login: [ACTIVE], session: [ACTIVE], sessionKey=[default], user=[me], server=[myserver]

CloudClient is logging in vRealize Orchestrator with persisted session

VCO login: [ACTIVE], session: [ACTIVE], sessionKey=[default], user=[administrator@vsphere.local], server=[myserver]

[ {

  "callbacks" : null,

Thanks for any help!

kalli

Hi VMware Gurus,

I ran into a problem installing with custom kickstart script.  I began by following William Lam's virtually ghetto blog site on how to create and ESXi ISO with a custom kickstart added into it.

I've modified the boot.cfg.

Before: kernelopt=runweasel

After: kernelopt=ks=file://etc/VMware/weasel/custks.cfg and at the end of the modules I put the tar file into the ranks adding in --- /custks.tgz

I also added the custks.tgz into the main directory of this ISO.

I got two errors when I tried installing.

When booting in EFI mode:

It says "Modules relocation error".

When running in Legacy mode, I get a different error:

It says "Error loading /s.v00 Fatal error: 10 (Out of resources)"

I've digged through this forum but haven't seen anyone run into my first error, but a few with my second error, but their solutions didn't work.

Any suggestions?  Thanks for reading.

glad to see scale out/in made it back into vRA 7 :-)

if I use the action scale-out/in on a deployment it automatically adds/removes machines in the deployment (works fine). But how can I provide this information (scale direction, which machine will be added etc) to my orchestrator workflow, so I can configure my load balancer (i use my own workflows for netscaler/Restful as there are no plugins available). Currently I don't have NSX.

See the graphic here (F5, Apache!!!!)

from: vRealize Automation 7.1 - What's New - VMware Cloud Management

Will the newly announced VMware Workstation 12.5 support Ubuntu 16.04 (Xenial) as a host? There are many reports that Workstation 12.1 does not. Thank you.

Ciao,

vi scrivo perchè avrei bisogno di qualche consiglio su come meglio gestire i miei ambienti virtuali. Sono autodidatta dunque...temo che qualcosa mi sia sfuggito.

Illustro lo stato in essere.

una macchina con esx 5.0. licenza essential. sopra ho circa 15vm. veeam per il backup.

la macchina sul quale risiede veeam è messa su una lun esterna.

a causa di un restore , una vm è finita, come files, sulla lun (e non sul datastorage di server).

come faccio a riportarla sullo storage originario?

inoltre, da qualche giorno, ho associato una nuova macchina, sempre con esx 5.0 e che vorrei "andasse in aiuto" della precendente macchine.

per questo vorrei che venissero condivise le risorse, tanto ram, che disco che cpu.

ho quindi installato vcenter, creato un datacenter, inserito gli host sotto l'unico datacenter creato...e ora?

:-)

posso spostare le macchine da una parte all'altra? anche spente, non devo per forza farlo a caldo.

e le risorse si bilanciano da sole?

perdonate le domande che immagino siano basiche.

grazie a chiunque abbia la voglia e la pazienza di darmi una mano.

V.

hello

can we have some news on a possible new version of vdp ?

thanks,

Can we integrate VDP with VRA where in users can able to select backup from VRA. Looking forward to hear from you all soon .

I couldn't find a specific section for VDP so posting here.  The latest VDP 6.1 admin guide doesn't list Exchange 2016, does anyone know the timeline for it to be updated?

Hi,

Five months ago I was halfway through migrating from my vCSA 5.5 to 6.0. I'd completed the move to the 6.0 appliance, upgraded one of my three hosts and moved some (less important) VMs onto the upgraded host to see how they went and called it a night.

That night we got hit by a cryptovirus and had to restore some files from backup (VEEAM).

Of course, I'd neglected to update VEEAM to point to the new vCSA and the backups hadn't run. Luckily the data from the previous backup run was only 28hrs old so I switched off the 6.0 vCSA, powered up the old one and added back the 5.5 hosts. The v6 host was left on its own because the vCSA on 5.5 couldn't manage it.

After some mayhem, VMWare earnt my eternal respect by sorting the whole lot out pretty much automatically and within a couple of hours all the VMs were running on the two remaining hosts.

Now I've just managed to pull myself together and repeat the upgrade!

I'm running with the original two hosts under a new vCSA on 6.0u2. The third host is still disconnected and showing powered-off copies of some of the VMs which have been running happily on my other two hosts for five months.

Now I can re-add the third host, do I have to worry about those out of date copies of the VMs? There seems to be a lot of options, ranging from just re-connecting it and letting VMware sort it out again (seems risky) to nuking the third host from orbit and installing it from scratch again.

Can anyone recommend a course of action?

In the meantime, I'm off to update my VEEAM config

Hello everyone,

I just upgraded my desktop to ubuntu LTS 16.04.01 with kerner 4.4.0-34-generic. I have vmware workstation 10 and now it is not loading with the attached errors and log, can anyone assist me please?

Here is the error log, appreciate any help, many thanks in advance!!!!!

cat vmware-modconfig-16439.log

2016-08-22T16:25:44.119+02:00| vthread-3| I120: Log for VMware Workstation pid=16439 version=10.0.4 build=build-2249910 option=Release

2016-08-22T16:25:44.119+02:00| vthread-3| I120: The process is 64-bit.

2016-08-22T16:25:44.119+02:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8

2016-08-22T16:25:44.119+02:00| vthread-3| I120: Host is Linux 4.4.0-34-generic Ubuntu 16.04.1 LTS

2016-08-22T16:25:44.118+02:00| vthread-3| I120: Msg_Reset:

2016-08-22T16:25:44.118+02:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2016-08-22T16:25:44.118+02:00| vthread-3| I120: ----------------------------------------

2016-08-22T16:25:44.118+02:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2016-08-22T16:25:44.119+02:00| vthread-3| I120: Msg_Reset:

2016-08-22T16:25:44.119+02:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.

2016-08-22T16:25:44.119+02:00| vthread-3| I120: ----------------------------------------

2016-08-22T16:25:44.119+02:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2016-08-22T16:25:44.119+02:00| vthread-3| I120: PREF Unable to check permissions for preferences file.

2016-08-22T16:25:44.119+02:00| vthread-3| I120: Msg_Reset:

2016-08-22T16:25:44.119+02:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.

2016-08-22T16:25:44.119+02:00| vthread-3| I120: ----------------------------------------

2016-08-22T16:25:44.119+02:00| vthread-3| I120: PREF Failed to load user preferences.

2016-08-22T16:25:44.119+02:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-16439.log

2016-08-22T16:25:44.125+02:00| vthread-3| I120: Obtaining info using the running kernel.

2016-08-22T16:25:44.125+02:00| vthread-3| I120: Created new pathsHash.

2016-08-22T16:25:44.125+02:00| vthread-3| I120: Setting header path for 4.4.0-34-generic to "/lib/modules/4.4.0-34-generic/build/include".

2016-08-22T16:25:44.125+02:00| vthread-3| I120: Validating path "/lib/modules/4.4.0-34-generic/build/include" for kernel release "4.4.0-34-generic".

2016-08-22T16:25:44.125+02:00| vthread-3| I120: Failed to find /lib/modules/4.4.0-34-generic/build/include/linux/version.h

2016-08-22T16:25:44.125+02:00| vthread-3| I120: /lib/modules/4.4.0-34-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2016-08-22T16:25:44.125+02:00| vthread-3| I120: using /usr/bin/gcc for preprocess check

2016-08-22T16:25:44.129+02:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "4.4.0-34-generic".

2016-08-22T16:25:44.129+02:00| vthread-3| I120: The header path "/lib/modules/4.4.0-34-generic/build/include" for the kernel "4.4.0-34-generic" is valid.  Whoohoo!

2016-08-22T16:25:44.244+02:00| vthread-3| I120: Reading in info for the vmmon module.

2016-08-22T16:25:44.244+02:00| vthread-3| I120: Reading in info for the vmnet module.

2016-08-22T16:25:44.244+02:00| vthread-3| I120: Reading in info for the vmblock module.

2016-08-22T16:25:44.244+02:00| vthread-3| I120: Reading in info for the vmci module.

2016-08-22T16:25:44.244+02:00| vthread-3| I120: Reading in info for the vsock module.

2016-08-22T16:25:44.244+02:00| vthread-3| I120: Setting vsock to depend on vmci.

2016-08-22T16:25:44.244+02:00| vthread-3| I120: Invoking modinfo on "vmmon".

2016-08-22T16:25:44.245+02:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2016-08-22T16:25:44.245+02:00| vthread-3| I120: Invoking modinfo on "vmnet".

2016-08-22T16:25:44.246+02:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2016-08-22T16:25:44.246+02:00| vthread-3| I120: Invoking modinfo on "vmblock".

2016-08-22T16:25:44.247+02:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2016-08-22T16:25:44.247+02:00| vthread-3| I120: Invoking modinfo on "vmci".

2016-08-22T16:25:44.248+02:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2016-08-22T16:25:44.248+02:00| vthread-3| I120: Invoking modinfo on "vsock".

2016-08-22T16:25:44.249+02:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.

2016-08-22T16:25:44.259+02:00| vthread-3| I120: to be installed: vmmon status: 0

2016-08-22T16:25:44.259+02:00| vthread-3| I120: to be installed: vmnet status: 0

2016-08-22T16:25:44.275+02:00| vthread-3| I120: Obtaining info using the running kernel.

2016-08-22T16:25:44.275+02:00| vthread-3| I120: Setting header path for 4.4.0-34-generic to "/lib/modules/4.4.0-34-generic/build/include".

2016-08-22T16:25:44.275+02:00| vthread-3| I120: Validating path "/lib/modules/4.4.0-34-generic/build/include" for kernel release "4.4.0-34-generic".

2016-08-22T16:25:44.275+02:00| vthread-3| I120: Failed to find /lib/modules/4.4.0-34-generic/build/include/linux/version.h

2016-08-22T16:25:44.275+02:00| vthread-3| I120: /lib/modules/4.4.0-34-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2016-08-22T16:25:44.275+02:00| vthread-3| I120: using /usr/bin/gcc for preprocess check

2016-08-22T16:25:44.279+02:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "4.4.0-34-generic".

2016-08-22T16:25:44.279+02:00| vthread-3| I120: The header path "/lib/modules/4.4.0-34-generic/build/include" for the kernel "4.4.0-34-generic" is valid.  Whoohoo!

2016-08-22T16:25:44.391+02:00| vthread-3| I120: Kernel header path retrieved from FileEntry: /lib/modules/4.4.0-34-generic/build/include

2016-08-22T16:25:44.391+02:00| vthread-3| I120: Update kernel header path to /lib/modules/4.4.0-34-generic/build/include

2016-08-22T16:25:44.391+02:00| vthread-3| I120: Validating path "/lib/modules/4.4.0-34-generic/build/include" for kernel release "4.4.0-34-generic".

2016-08-22T16:25:44.391+02:00| vthread-3| I120: Failed to find /lib/modules/4.4.0-34-generic/build/include/linux/version.h

2016-08-22T16:25:44.391+02:00| vthread-3| I120: /lib/modules/4.4.0-34-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2016-08-22T16:25:44.391+02:00| vthread-3| I120: using /usr/bin/gcc for preprocess check

2016-08-22T16:25:44.397+02:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "4.4.0-34-generic".

2016-08-22T16:25:44.397+02:00| vthread-3| I120: The header path "/lib/modules/4.4.0-34-generic/build/include" for the kernel "4.4.0-34-generic" is valid.  Whoohoo!

2016-08-22T16:25:44.397+02:00| vthread-3| I120: Found compiler at "/usr/bin/gcc"

2016-08-22T16:25:44.400+02:00| vthread-3| I120: Got gcc version "5.4.0".

2016-08-22T16:25:44.400+02:00| vthread-3| I120: GCC minor version 5 does not match Kernel GCC minor version 5.  But that is ok.

2016-08-22T16:25:44.400+02:00| vthread-3| I120: Using user supplied compiler "/usr/bin/gcc".

2016-08-22T16:25:44.402+02:00| vthread-3| I120: Got gcc version "5.4.0".

2016-08-22T16:25:44.402+02:00| vthread-3| I120: GCC minor version 5 does not match Kernel GCC minor version 5.  But that is ok.

2016-08-22T16:25:44.405+02:00| vthread-3| I120: Trying to find a suitable PBM set for kernel "4.4.0-34-generic".

2016-08-22T16:25:44.405+02:00| vthread-3| I120: No matching PBM set was found for kernel "4.4.0-34-generic".

2016-08-22T16:25:44.405+02:00| vthread-3| I120: GCC minor version 5 does not match Kernel GCC minor version 5.  But that is ok.

2016-08-22T16:25:44.405+02:00| vthread-3| I120: Validating path "/lib/modules/4.4.0-34-generic/build/include" for kernel release "4.4.0-34-generic".

2016-08-22T16:25:44.405+02:00| vthread-3| I120: Failed to find /lib/modules/4.4.0-34-generic/build/include/linux/version.h

2016-08-22T16:25:44.405+02:00| vthread-3| I120: /lib/modules/4.4.0-34-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2016-08-22T16:25:44.405+02:00| vthread-3| I120: using /usr/bin/gcc for preprocess check

2016-08-22T16:25:44.411+02:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "4.4.0-34-generic".

2016-08-22T16:25:44.411+02:00| vthread-3| I120: The header path "/lib/modules/4.4.0-34-generic/build/include" for the kernel "4.4.0-34-generic" is valid.  Whoohoo!

2016-08-22T16:25:44.412+02:00| vthread-3| I120: GCC minor version 5 does not match Kernel GCC minor version 5.  But that is ok.

2016-08-22T16:25:44.412+02:00| vthread-3| I120: Validating path "/lib/modules/4.4.0-34-generic/build/include" for kernel release "4.4.0-34-generic".

2016-08-22T16:25:44.412+02:00| vthread-3| I120: Failed to find /lib/modules/4.4.0-34-generic/build/include/linux/version.h

2016-08-22T16:25:44.412+02:00| vthread-3| I120: /lib/modules/4.4.0-34-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2016-08-22T16:25:44.412+02:00| vthread-3| I120: using /usr/bin/gcc for preprocess check

2016-08-22T16:25:44.418+02:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "4.4.0-34-generic".

2016-08-22T16:25:44.418+02:00| vthread-3| I120: The header path "/lib/modules/4.4.0-34-generic/build/include" for the kernel "4.4.0-34-generic" is valid.  Whoohoo!

2016-08-22T16:25:44.418+02:00| vthread-3| I120: Using temp dir "/tmp".

2016-08-22T16:25:44.419+02:00| vthread-3| I120: Obtaining info using the running kernel.

2016-08-22T16:25:44.419+02:00| vthread-3| I120: Setting header path for 4.4.0-34-generic to "/lib/modules/4.4.0-34-generic/build/include".

2016-08-22T16:25:44.419+02:00| vthread-3| I120: Validating path "/lib/modules/4.4.0-34-generic/build/include" for kernel release "4.4.0-34-generic".

2016-08-22T16:25:44.420+02:00| vthread-3| I120: Failed to find /lib/modules/4.4.0-34-generic/build/include/linux/version.h

2016-08-22T16:25:44.420+02:00| vthread-3| I120: /lib/modules/4.4.0-34-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2016-08-22T16:25:44.420+02:00| vthread-3| I120: using /usr/bin/gcc for preprocess check

2016-08-22T16:25:44.426+02:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "4.4.0-34-generic".

2016-08-22T16:25:44.426+02:00| vthread-3| I120: The header path "/lib/modules/4.4.0-34-generic/build/include" for the kernel "4.4.0-34-generic" is valid.  Whoohoo!

2016-08-22T16:25:44.564+02:00| vthread-3| I120: Invoking modinfo on "vmmon".

2016-08-22T16:25:44.565+02:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2016-08-22T16:25:44.565+02:00| vthread-3| I120: Invoking modinfo on "vmnet".

2016-08-22T16:25:44.567+02:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2016-08-22T16:25:44.701+02:00| vthread-3| I120: Setting destination path for vmmon to "/lib/modules/4.4.0-34-generic/misc/vmmon.ko".

2016-08-22T16:25:44.701+02:00| vthread-3| I120: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2016-08-22T16:25:44.706+02:00| vthread-3| I120: Successfully extracted the vmmon source.

2016-08-22T16:25:44.706+02:00| vthread-3| I120: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-Tafbm9/vmmon-only auto-build HEADER_DIR=/lib/modules/4.4.0-34-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2016-08-22T16:25:45.601+02:00| vthread-3| W110: Failed to build vmmon.  Failed to execute the build command.

2016-08-22T16:25:45.603+02:00| vthread-3| I120: Setting destination path for vmnet to "/lib/modules/4.4.0-34-generic/misc/vmnet.ko".

2016-08-22T16:25:45.603+02:00| vthread-3| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2016-08-22T16:25:45.606+02:00| vthread-3| I120: Successfully extracted the vmnet source.

2016-08-22T16:25:45.606+02:00| vthread-3| I120: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-Tafbm9/vmnet-only auto-build HEADER_DIR=/lib/modules/4.4.0-34-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2016-08-22T16:25:56.845+02:00| vthread-3| W110: Failed to build vmnet.  Failed to execute the build command.

qatesting12

Hi Folks,

if 1 VM failed which is part of a job with multiple VMs, How do i just rerun this VM backup in VDP?

Will "Backup>Backup job name> Backup now" run only failed VM?

regards,

Max

Hi - I hope someone will be able to point me in the right direction to resolve this.

I am trying to deploy the standard 2GB VDP 5.8.4 into a 5.5 environment.

The .ova deploys without issue and powers on.

I log into the suggested web page and am able to confirm the network details and run through the rest of the set up wizard, linking to my chosen VC and adding storage. The wizard completes works for a few mins to add the storage and then reboots the appliance and then the appliance comes up and steps through the configuration until it returns to the standard blue logon screen. Subsequent reboots are just reboots.

I believe the next step is to go into the VDP Node in the webclient, select the appliance from the drop down and click 'Connect' - when I do this the interface 'grey's out and the clock timer symbol appears... and that's it... no failure message, nothing until the client times out or I manually refresh.

All the DNS entries are in place and resolve in both directions, the account I used to join the appliance to VC has full permissions.

I have trawled the KBs looing for something similar but the articles I have found do not appear to apply to these symptoms - I will raise a case if necessary but I'm hoping someone has seen this before and can help me out.

Hi community,

I transferred a Windows 2012 R2 VM from one ESXi 5.5 to another ESXi 6.0 via scp.

The source works fine after this on 5.5 but the same thing on 6.0 is corrupt. The machine

starts with the selection of the keyboard-layout and will not find a valid operating system.

Any suggestions?

Thanks in advance

Torsten