I'm getting an error for this that states

"Couldn't upload data to the REST endpoint. HTTP status line: 400, Bad Request"

Hi,

I am a fresh-user for VMware. I search a lot on a specific topic, but I could find neither a question nor any answer.

My problem is Copy-Paste. I am able to achieve copy-paste from guest to host, and from guest to guest. However, I somehow cannot make copy paste from host to host (between Mac folders)

I am a Mac-Os user as host. Virtual engine uses Win 10. This question could be a silly one.Please accept my excuses to take your time.

I've had a number of VMs fail to vMotion or straight up crash due to messages similar to these:

Failed to process the set attributes result: Lost previously held disk lock

2018-12-28T15:19:23.749Z| vcpu-0| I125: >>> Error writing log, 89 bytes discarded. Disk full?

2018-12-28T15:19:23.749Z| vcpu-0| I125: Msg_Question:

2018-12-28T15:19:23.749Z| vcpu-0| I125: [msg.hbacommon.locklost] The lock protecting 'vm.vmdk' has been lost, possibly due to underlying storage issues.

2018-12-28T15:19:23.749Z| vcpu-0| I125+ If this virtual machine is configured to be highly available, ensure that the virtual machine is running on some other host before clicking OK.

2018-12-28T15:19:23.749Z| vcpu-0| I125: ----------------------------------------

2018-12-28T15:23:24.379Z| vcpu-0| I125: Timing out dialog 3174

2018-12-28T15:23:24.380Z| vcpu-0| I125: MsgQuestion: msg.hbacommon.locklost reply=0

2018-12-28T15:23:24.380Z| vcpu-0| E105: PANIC: Exiting because of failed disk operation.

2018-12-28T15:23:25.575Z| vcpu-0| W115: A core file is available in "/vmfs/volumes/77955655-79af1105-0000-000000000000/vm_name/vm.zdump.000"

2018-12-28T15:23:25.575Z| mks| W115: Panic in progress... ungrabbing

2018-12-28T15:23:25.575Z| mks| I125: MKS: Release starting (Panic)

2018-12-28T15:23:25.575Z| mks| I125: MKS: Release finished (Panic)

2018-12-28T15:23:25.576Z| vcpu-0| I125: Writing monitor file `vmmcores.gz`

2018-12-28T15:23:25.578Z| vcpu-0| W115: Dumping core for vcpu-0

2018-12-28T15:23:25.578Z| vcpu-0| I125: CoreDump: dumping core with superuser privileges

2018-12-28T15:23:25.578Z| vcpu-0| I125: VMK Stack for vcpu 0 is at 0x439337d13000

2018-12-28T15:23:25.578Z| vcpu-0| I125: Beginning monitor coredump

2018-12-28T15:23:26.171Z| vcpu-0| I125: End monitor coredump

2018-12-28T15:23:26.172Z| vcpu-0| W115: Dumping core for vcpu-1

2018-12-28T15:23:26.172Z| vcpu-0| I125: CoreDump: dumping core with superuser privileges

2018-12-28T15:23:26.172Z| vcpu-0| I125: VMK Stack for vcpu 1 is at 0x439337f13000

2018-12-28T15:23:26.172Z| vcpu-0| I125: Beginning monitor coredump

2018-12-28T15:23:26.577Z| mks| W115: Panic in progress... ungrabbing

2018-12-28T15:23:26.577Z| mks| I125: MKS: Release starting (Panic)

2018-12-28T15:23:26.577Z| mks| I125: MKS: Release finished (Panic)

2018-12-28T15:23:26.759Z| vcpu-0| I125: End monitor coredump

2018-12-28T15:23:27.220Z| vcpu-0| I125: Printing loaded objects

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9922257000-0x9923324914): /bin/vmx

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x996391E000-0x99639351CC): /lib64/libpthread.so.0

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9963B3B000-0x9963B3CF00): /lib64/libdl.so.2

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9963D3F000-0x9963D47D08): /lib64/librt.so.1

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9963F5A000-0x99641F24E4): /lib64/libcrypto.so.1.0.2

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9964423000-0x996448C4AC): /lib64/libssl.so.1.0.2

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9964697000-0x99647AB37C): /lib64/libX11.so.6

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99649B2000-0x99649C101C): /lib64/libXext.so.6

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9964BC2000-0x9964CA6341): /lib64/libstdc++.so.6

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9964EC5000-0x9964F4521C): /lib64/libm.so.6

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9965148000-0x996515CBC4): /lib64/libgcc_s.so.1

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x996535E000-0x99654BEC74): /lib64/libc.so.6

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99236FD000-0x992371A7D8): /lib64/ld-linux-x86-64.so.2

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99656C9000-0x99656E3634): /lib64/libxcb.so.1

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99658E5000-0x99658E695C): /lib64/libXau.so.6

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9965EB5000-0x9965F4A534): /usr/lib64/vmware/plugin/objLib/upitObjBE.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9966163000-0x99662B9994): /usr/lib64/vmware/plugin/objLib/vsanObjBE.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9966550000-0x9966564F94): /lib64/libz.so.1

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99669AF000-0x99669BA1D0): /lib64/libnss_files.so.2

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9966CC5000-0x9966CC60A4): /usr/lib/vmware/nas_plugins/lib64/libvmfsNasPlugin.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9966EC8000-0x9966EDB44C): /lib64/libvmkfslib.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99670DD000-0x996733A6D4): /lib64/libvmlibs.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x99675E1000-0x99678F91A4): /lib64/libvmsnapshot.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9967B13000-0x9967B20F14): /lib64/libtreestructs.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9967D23000-0x9967D245BC): /usr/lib/vmware/nas_plugins/lib64/libsvaNasPlugin.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: [0x9967F26000-0x9967F4236C): /usr/lib/vmware/nas_plugins/lib64/libnvdkTegileNasPlugin.so

2018-12-28T15:23:27.220Z| vcpu-0| I125: End printing loaded objects

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace:

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[0] 0000009969aa6460 rip=00000099228d75e7 rbx=00000099228d70e0 rbp=0000009969aa6480 r12=0000000000000000 r13=0000000000000001 r14=0000009923ba1460 r15=0000009968371020

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[1] 0000009969aa6490 rip=000000992241766c rbx=0000009969aa64b0 rbp=0000009969aa6990 r12=000000992357c2b0 r13=0000000000000001 r14=0000009923ba1460 r15=0000009968371020

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[2] 0000009969aa69a0 rip=0000009922582d41 rbx=0000009923d68a40 rbp=0000009969aa69c0 r12=0000000000000002 r13=0000009923c9eb48 r14=0000009923ba1460 r15=0000009968371020

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[3] 0000009969aa69d0 rip=000000992257588d rbx=0000009923c9b030 rbp=0000009969aa6b70 r12=00000099233e3550 r13=0000000000000165 r14=0000009923ba1460 r15=0000009968371020

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[4] 0000009969aa6b80 rip=0000009922825431 rbx=00000099236904a8 rbp=0000009969aa6bb0 r12=00000099233e3550 r13=0000000000000165 r14=0000009923ba1460 r15=0000000000000000

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[5] 0000009969aa6bc0 rip=000000992284d176 rbx=000000000000012d rbp=0000009969aa6c00 r12=000000992357c2b0 r13=0000009923687d80 r14=00000099235621a0 r15=0000000000000000

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[6] 0000009969aa6c10 rip=0000009922825518 rbx=0000000000000000 rbp=0000009969aa6c20 r12=0000009969aa6c40 r13=0000009923dbb290 r14=0000009923df18d0 r15=0000000000000003

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[7] 0000009969aa6c30 rip=00000099228c2b05 rbx=0000009923691aa0 rbp=0000009969aa6d80 r12=0000009969aa6c40 r13=0000009923dbb290 r14=0000009923df18d0 r15=0000000000000003

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[8] 0000009969aa6d90 rip=0000009963925cfc rbx=0000000000000000 rbp=0000000000000000 r12=000003805f591a00 r13=0000009969aa79c0 r14=0000009923df18d0 r15=0000000000000003

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[9] 0000009969aa6ea0 rip=000000996542fead rbx=0000000000000000 rbp=0000000000000000 r12=000003805f591a00 r13=0000009969aa79c0 r14=0000009923df18d0 r15=0000000000000003

2018-12-28T15:23:27.220Z| vcpu-0| I125: Backtrace[10] 0000009969aa6ea8 rip=0000000000000000 rbx=0000000000000000 rbp=0000000000000000 r12=000003805f591a00 r13=0000009969aa79c0 r14=0000009923df18d0 r15=0000000000000003

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[0] 0000009969aa6460 rip=00000099228d75e7 in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[1] 0000009969aa6490 rip=000000992241766c in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[2] 0000009969aa69a0 rip=0000009922582d41 in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[3] 0000009969aa69d0 rip=000000992257588d in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[4] 0000009969aa6b80 rip=0000009922825431 in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[5] 0000009969aa6bc0 rip=000000992284d176 in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[6] 0000009969aa6c10 rip=0000009922825518 in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[7] 0000009969aa6c30 rip=00000099228c2b05 in function (null) in object /bin/vmx loaded at 0000009922257000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[8] 0000009969aa6d90 rip=0000009963925cfc in function (null) in object /lib64/libpthread.so.0 loaded at 000000996391e000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[9] 0000009969aa6ea0 rip=000000996542fead in function clone in object /lib64/libc.so.6 loaded at 000000996535e000

2018-12-28T15:23:27.220Z| vcpu-0| I125: SymBacktrace[10] 0000009969aa6ea8 rip=0000000000000000

2018-12-28T15:23:27.220Z| vcpu-0| I125: Exiting

Here is a sample of what's going on in vmkernel.log

2018-12-28T15:19:23.751Z warning hostd[9A81B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/77955655-79af1105-0000-000000000000/vm/vm.vmx] Failed to find activation record, event user unknown.

2018-12-28T15:19:23.752Z verbose hostd[9A81B70] [Originator@6876 sub=PropertyProvider] RecordOp REMOVE: latestPage[33726], session[52610cea-e1e8-e07e-26d6-259c4517645b]52e66a9c-32b6-479e-319f-ca34434ae415. Applied change to temp map.

2018-12-28T15:19:23.752Z verbose hostd[9A81B70] [Originator@6876 sub=PropertyProvider] RecordOp ADD: latestPage[33736], session[52610cea-e1e8-e07e-26d6-259c4517645b]52e66a9c-32b6-479e-319f-ca34434ae415. Applied change to temp map.

2018-12-28T15:19:23.752Z verbose hostd[9A81B70] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: latestEvent, ha-eventmgr. Applied change to temp map.

2018-12-28T15:19:23.752Z info hostd[9A81B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 33736 : Message on vm on esxi in ha-datacenter: The lock protecting 'vm.vmdk' has been lost, possibly due to underlying storage issues.

--> If this virtual machine is configured to be highly available, ensure that the virtual machine is running on some other host before clicking OK.

-->

 

2018-12-28T16:00:05.215Z cpu57:1437367)WARNING: NFS41: NFS41FileOpSetFileAttributes:4540: Failed to process the set attributes result: Lost previously held disk lock

2018-12-28T16:00:05.616Z cpu48:1437367)WARNING: NFS41: NFS41FileOpSetFileAttributes:4540: Failed to process the set attributes result: Lost previously held disk lock

2018-12-28T16:00:06.019Z cpu48:1437367)WARNING: NFS41: NFS41FileOpSetFileAttributes:4540: Failed to process the set attributes result: Lost previously held disk lock

2018-12-28T16:00:06.414Z cpu48:1437367)WARNING: NFS41: NFS41FileOpSetFileAttributes:4540: Failed to process the set attributes result: Lost previously held disk lock

2018-12-28T16:00:06.814Z cpu48:1437367)WARNING: NFS41: NFS41FileOpSetFileAttributes:4540: Failed to process the set attributes result: Lost previously held disk lock

2018-12-28T16:00:10.623Z cpu7:68509)WARNING: NFS41: NFS41_NFSAttrToVolatileFSAttrs:1641: Server FILES_FREE 5779000868 exceeds ESX limit

2018-12-28T16:00:10.623Z cpu7:68509)WARNING: NFS41: NFS41_NFSAttrToVolatileFSAttrs:1654: Server FILES_TOTAL 5779005873 exceeds ESX limit

2018-12-28T16:00:10.629Z cpu7:68509)WARNING: NFS41: NFS41_NFSAttrToVolatileFSAttrs:1641: Server FILES_FREE 5779000868 exceeds ESX limit

2018-12-28T16:00:10.629Z cpu7:68509)WARNING: NFS41: NFS41_NFSAttrToVolatileFSAttrs:1654: Server FILES_TOTAL 5779005873 exceeds ESX limit

2018-12-28T16:00:10.633Z cpu7:68509)WARNING: NFS41: NFS41_NFSAttrToVolatileFSAttrs:1641: Server FILES_FREE 5779000868 exceeds ESX limit

2018-12-28T16:00:20.596Z cpu20:67009)SunRPC: 1116: Destroying world 0x1a0157

2018-12-28T16:00:20.598Z cpu20:67009)SunRPC: 1116: Destroying world 0x1a018e

2018-12-28T16:00:20.628Z cpu44:66542)WARNING: NFS: 221: Got error 13 from mount call

2018-12-28T16:00:20.628Z cpu20:67009)SunRPC: 1116: Destroying world 0x1a018f

2018-12-28T16:00:20.630Z cpu20:67009)SunRPC: 1116: Destroying world 0x1a0190

2018-12-28T16:00:20.649Z cpu44:66542)WARNING: NFS: 221: Got error 13 from mount call

2018-12-28T16:00:20.649Z cpu20:67009)SunRPC: 1116: Destroying world 0x1a0191

vobd shows the VM crash happening

It shows an APD on the NFS storage well before the crash itself, maybe about an hour before:

2018-12-28T11:17:56.077Z: [APDCorrelator] 2034244476342us: [vob.storage.apd.start] Device or filesystem with identifier [77955655-79af1105-0000-000000000000] has entered the All Paths Down state.

I would like to know how to get vmware tools version from a Linux VM that can be found in a file.  I am trying to output the vmware tools version into IBM BigFix without the need to run the "vmware-toolbox-cmd -v" command.  Is the vmtools version listed somewhere in a file in a Linux VM?

I have a windows 10 template, installed the Guest Agent and have a cert.pem.  The guest agent service is running and all the logs look fine, comparing it to another working template and it looks similar.

When I request this Windows 10 template from vRA, the allocation succeeds but the provisioning was taking a while. I went to the vCenter and could see the new windows 10 machine. When opening the console I notices an 'Install Windows' box, with "Windows could not finish configuring the system. To attempt to resume configuration, restart the computer".

On vRA, when the machine eventually fails, it says Timeout Customizing Machine

Am I missing something, why would this be happening?

Any help greatly appreciated, Thanks

I am trying to add/move vmnic0 from a standard switch to an already existing vDS that has vmnic1 attached.  Everything is good until it tries to add vmnic0 (see attached code screenshot).  I believe it has something do with the highlighted section.  It is creating an array, but for some reason the second pnicSpec is not defined and throws the error below.  I am able to do one vmnic at a time so it seems like I have to define that array for 2 pnicSpec's and I'm unsure how to go about it.  @iiliev any ideas?

TypeError: Cannot set property "pnicDevice" of undefined to "vmnic0"

Using Postman.... is it possible to pass multiple vm's when making an API call to:

                     -find the resourceID's and only return the resourceID

                     -pass in the resourceID's to show the property "summary|parentvcenter" for each vm

Use case: We need to know the parent vcenter for 100 vm's located across multiple vcenters and multiple vROps instances via the API.... I know powershell will work, but what about Postman?  Thanks.

E.g.,

https://vrops/suite-api/api/resources?resourceKind=virtualmachine&name=server1,server2,server3=resourceID

Then

https://vrops/suite-api/api/resources/resourceID1,resourceID2,resourceID3/properties=summary-parentvcenter

We are running Horizon 7.x with windows 7 VMs.   On these, there is office 365 proplus 2016 64 bit.   Our biggest complaint we get is that excel is very laggy /crashes all the time. The SAN these are on is SSD, and there is plenty of RAM / CPU for each VM.   I am at my wits end.   Does anyone have any tips or tricks to get excel functioning in a usable state for end users?  Any help is appreciated

-Paul

Mac bookpro (Mid 2015) Mac OS version is 10.14.2,VMware version 11.0.2，When I was going to create a new mac os vm, I made a mistake as shown in the diagram

With Fusion 11.0.2 (macOS 10.13.6) on a MacBook Pro 2017, I have the Touch Bar set to display function keys (F1, F2, etc.).

This is a problem because it is hard to use the top row of regular keys without accidentally brushing a function key on the Touch Bar, thus activating an unwanted function.

How can I set it so I have to press the Function key (Fn) to show the function keys instead?

Thank you,

David

Hola.

Estoy intentando mediante RCP conectar un UBS Model a una VM. 

He configurado los parametros de local device and resourcesde la maquina fisica

He configurado gpo tanto de la maquina fisica

Remote Desktop Connection Client \ RemoteFX USB Device Redirection \ All RDP Redirection (Enable)

Remote Desktop Session Host \ Remote Session Environment \ RemoteFX for Windows Server 2008 R2 \ Configure RemoteFX (Enable)

Remote Desktop Session Host \ Connections \ Allow users to connect remotely using Remote Desktop Services (Enable)

Remote Desktop Session Host \ Device and Resource Redirection\ Do not allow supported Plug and Play device redirection (Disable)

gpupdate /force in elevated CMD Prompt and reboot

Pero nada de nada.

Solo ejecutando la VM mediante Workstation o VMware Remote Console , conectando el dispositivo manualmente a la VM, he podido activar el Host usb Device para el model.

Mi pregunta seria,

Se podria configurar el RCP o la VM para que al conectar el Model automáticamente se puede activar el Host usb Device sin utilizar aplicaciones de terceros o agregando el dispositivo USB apor ejemplo usb redirector?

Ha se me olvidaba indicar. Tambien realize la prueba modificando el fichero .vmx, colocando los parametros del USB manualmente, pero nada de nada.

Gracias de antemano y felices Fiestas

One out of 25 clients have the error in Horizon connector "View Connection Server communication error".  I have set this one up with a static ip and dhcp. It states that it is connected and provides the screen of which IP to log into. When I do this, that is when the error arrives. To show error on the client it has Firmware of 5.4.1 installed.  Currently I put in a static ip and tried to use the ping utility that keeps sending to different IP's but the response stays at 0. The machine can be pinged from other machines with no errors.  I have also placed this in other network jacks that have working WYSE boxes attached and the same messages appear. Anyone have suggestions on fixing ?

Thanks

Hi all.  Quick question.  We're upgrading from 6.0 U2 ESXi hosts to 6.7 U1.

Just wanted to confirm that this is a POST 6.7U1 patch (given 6.7U1 went GA in mid October and this patch was released Nov 9).

VMware ESXi 6.7, Patch Release ESXi670-201811001

So... upgrade 6.0 U2 hosts >>> 6.7 U1 >>> then apply ESXi670-201811001 as final step for hosts.  All caught up?  Thanks!

To start out, thank you for taking the time to read this post.

I'm using vRA 7.4 and attempting to allow a user provision a VM and allowing them to select a network via a dropdown on a blueprint. I have several networks defined in vRA, which have pools of IPs associated with them. These networks are tied to specific business groups.

All of the network configuration in vRA seems to be working as expected. I've created a custom property VirtualMachine.Network0.Name which populates a dropdown using the vRO action com.vmware.vra.networks\getApplicableNetworks.

This appears to work, in at least its populating the dropdown with the appropriate networks. (there are a few extra networks shown in the image below. This is expected as image capture was with an admin user)

The issue I'm seeing is that when the VM is provisioned it does receive the appropriate network (as shown below) but the client does not get configured with the IP address allocated from the pool. instead, it just clones the address from the template.

Is there another step I'm missing to actually assign the allocated IP information the VM itself?

I want to buy a NAS box for a home lab. Either QNAP or Synology or any of the other low end brands. I'll connect it to an ESXi server using iSCSI.

What is the one  spec I should be looking for, so I would have adequate speed when running the VMs on the NAS?

So far I was looking for "iSCSI write to target" speeds here

Is this the spec I should be looking for? I won't have many VMs. Maybe 10 or 15, and they won't be really writing all the time.

So what's important when running VMs on a NAS? What's the most important spec I should be looking for?

Having a weird problem with the Remote Desktop Connection client.  If I delete the users writable profile then the RDP client works like normal and allows you to enter your credentials to connect.  The next time the users logs in and opens the RDP client you are not able to enter any credentials.  I attached the screenshot.  I tried to exclude the MSTSC.exe process from the snapvol.cfg file but no luck.

Any other ideas?

When I check for updates on the appliance it just fails. Is there a way to upgrade via ISO/CDROM?

I am unable to find a solution to connect my VDI using VM Horizon client in mac  or windows 10. It is working fine with windows 7.

The script：

Installing is OK. But I  want after installing has been completed auto eject CD.

What should I do?

When will this be available?