Same issue within my environment. Seems to be tied to the following error in the client service logs:
The OS handle's position is not what FileStream expected. Do not use a handle simultaneously in one FileStream and in Win32 code or another FileStream. This may cause data loss.
Don't really have any leads on this.
We have the same exact issue. 53 computers Waiting for Device. Uninstall/reinstall of the client allows it to connect and it gets most of the way done uploading, then goes back to Waiting for Service. We have been upgrading everyone to Windows 10 and installing all updates, and all of the updated computers have been affected. Has anyone heard any word on this issue?
any news???? how can we leave clients without solutions !
150 euros per licences..I have more than 400 computers......and i got stucked becaused of an update to 1803...
what are our choices ? what are the solutions which could provide us with another solution ? i loved mirage but if it's over, it's over
Hallo, we have same problem and we would like to know what VMware will do about Mirage
Customers buy licenses by spending a lot of money but they can not use mirage with Windows 10 clients systems updated!
We have open a ticket and VMware response is: "We have a limited support for Windows 10 1709 and as Windows 10 update 1803 has released recently, we don 't have an update if this will be included in Mirage 5.9.1 ", there is not even a roadmap for any updates. "Currently we don't have an ETA on it, if there will be any updates on the product that will be mentioned in the public release notes".
Whoever has invested a lot of money wants to have an official and exhaustive answer from VMware about Mirage's future.
Hi, did you found a workaround? or still stucked?
I think support for Mirage is over. They announced that it is end-of-life and I doubt they are allocating many resources to it.
I have the same issue.. Hits 80% upload and service stops.. Hope they offer a fix soon..
Pour moi, la réponse du support est : reformatez votre parc en Windows 10 - 1709 puis remonter les données utilisateurs de Mirage et bloquer les Mises à jours.
La je teste un nouveau produit et bye bye Mirage.
Courage à tous.
the official communication has arrived Mirage and FLEX are over. VMware recommends switching to VMware AirWatch® UEM but this product does a lot of things I do not need and not what we need like for example endpoint backup and it does not do anything FLEX does.
At this point the investment we made on VMware Mirage was bad!
Does anyone know really alternative products to Mirage and FLEX?
Alors pourquoi Vmware a encaissé l'argent de mon renouvellement de maintenance de mon parc ce 30 juin 2018 pour un an en sachant qu'ils ne vont rien faire.
Si c'est cela, Vmware prend l'argent et nous nous devons nous débrouiller.
Donc, il ne compte pas honorer leur contrat ?
Et je pense que tous les autres utilisateurs ont fait de même et ce retrouve dans la M.....
Dans ce cas si Vmware ne veut pas faire le développement adéquate, il nous rembourse et on change de produit.
Je suis d'accord avec toi
It seems VMware may have relented on their position that 5.9.x for 1803 would not be patched/supported:
Update July 24th 2018
Mirage 5.9.1 currently does not support Windows 10 v1803 for any operations. Due to changes in the underlying OS, Mirage client 5.x is unable to run on Windows 10 v1803. VMware is working on resolving this issue