Hi! does anyone has any ıssue about App Volumes 2.10 with Horizon 7 Windows 10 desktops? My linked clone desktops with persistent disk attached, are getting in "repair" state after user installed application then reboot.
I have tried writable volumes instead of persistent disks. But I got the same situation. Users install something to their LC Win10 desktops and the restart them. Then windows 10' s are in repair state.
I decided to set up app volumes 3.0. But with this version I cannot see my captured apps in AV manager. I captured filezilla and put the .vmdk and .json file in a shared folder. Creating "FileShare Location" is successful. I have synced it many times bur "AppCapture" state is "incomplete"
screenshot is attached. thanks in advance for your helps
Don't use 3.0 in production, just stay wit 2.10.
That being said. I know there is an issue with W10 and Appvolumes 2.10 with the start menu but what you are stating is more of an issue with VMWare.
What happens with Appvolumes is that, after the machine is refreshed (or recomposed or deleted, whatever you set it to) the machine is being cleaned up. Just before the refresh or delete the Appstacks and writable volume is being detached from the VDI machine, thus not having any impact on the VDI itself.
Have you created linked clones in a floating pool? This is what you need to do for Appvolumes. Also make sure to either refresh or delete the machines directly after use.
Don't use 3.0 in production, just stay wit 2.10.
That being said. I know there is an issue with W10 and Appvolumes 2.10 with the start menu but what you are stating is more of an issue with VMWare.
What happens with Appvolumes is that, after the machine is refreshed (or recomposed or deleted, whatever you set it to) the machine is being cleaned up. Just before the refresh or delete the Appstacks and writable volume is being detached from the VDI machine, thus not having any impact on the VDI itself.
Have you created linked clones in a floating pool? This is what you need to do for Appvolumes. Also make sure to either refresh or delete the machines directly after use.
Thanks Ray
I tried to make appstacks work with linked clone-dedicated-with persistent and disposable disk pool work. I think appstacks cannot work with persistent and disposable disks. Yesterday I created linked clone-dedicated pool without persistent and disposable disks and attached users writable volumes. Users installed their own apps and restarted their desktops. No issues so far. I will go with floating pools. if persistent or disposable disks aren' t used there is no need for dedicated pools.
Have you ever tried this with win7 or 8? Did you get the same issue?
Hey, do you mean Windows 7 or 8 with persistent machines? Nopes.
I know that documentation isn't all that
. Thing is that Appvolumes only works with linked clone pools and preferably floating. It's this that makes the product as good as it is as we have some 20000 users that in no way all need their own personal machine but we do like to give some users some personalisation with the ability to install applications for themselves.
Does 2.10 support Horizon 7, Windows 10 and ESXi 6.0 U2 ?? I don't see that in the release notes.
We have all of those installed and yes it works.
U2 even has the slow reconfigure bug hotfix build in.
I'm aiming at having a floating pool with Win 10 and using App volumes för application delivery and a writeable volume because some of the applications are writing user data locally on the C drive.
Hello,
there apre some pröblems with writables + w10. Mainly search in the start menu is not working unless the user has admin rights
Cristiano
OK, so how should I go about implementing it not using wr volumes?
I also got an error when I login to a VM.. NTLM Auth Invalid. Error 401 from the manager. I'm using a floating pool using Instant Clones. Any caveats there?
Instant clone is not supported in App Volumes 2.10.
:smileycry: Ok, so then it's useless to even try using 2.9. Back to square one and 3.0 then. I just think that the capturing process and update of appstacks in 3.0 is "crap".. ![]()
... or using Composer and Linked Clones maybe is better?
Yes please. It works pretty good with Linked clones and Full clones.
I would say use composer and linked clones, going for 3.0 might disappoint you quite a bit. My feeling is that it is buggy as hell (to say the least).
2.10 also has a known issue with the NTLM error and I believe both this and the instant clone support will be in 2.11. I am eagerly anticipating that one
We never went to 2.10 in our production enviornment due to the 2.10 NTLM error.
