Natestack's Posts

So having a crack at VHD So far hit and miss, so for some reason current Appvolumes VHD 4.1 templates get assigned for provisioning I can see the CVapps drive but I didn’t get the GUI. So g... See more...
So having a crack at VHD So far hit and miss, so for some reason current Appvolumes VHD 4.1 templates get assigned for provisioning I can see the CVapps drive but I didn’t get the GUI. So got an older 4.0.1 Template now I get the GUI when in provisioning mode Yay. install apps as you do click ok to say I’m done and again to reboot. it seems it cancels my package lol nice machine boots back up. and looking at the server logs I get the following error BaseAdapter method not implemented “volumes_capacity” now I’ve been doing this stuff for a while now never seen this message before has anyone come across if so what was the fix ? might log another job with VMware in this as well when next in the office. maybe 4.2 might have better templates ?
Yeah since 4.1 it’s alright still some bugs to fix. I was just disappointed doing a smaller template and since 4.1 just gave it a drive letter. here is hoping the 4.2 etc fix the template i... See more...
Yeah since 4.1 it’s alright still some bugs to fix. I was just disappointed doing a smaller template and since 4.1 just gave it a drive letter. here is hoping the 4.2 etc fix the template in order to shrink the size as this will be a requirement for my VHD in the future.
Bump. hoping VMware see this if not I will log a job next time I’m in the office. as when you update a package appvol removed the OS I n the update package. anyone else get the same issu... See more...
Bump. hoping VMware see this if not I will log a job next time I’m in the office. as when you update a package appvol removed the OS I n the update package. anyone else get the same issue ?
Awesome seems you and I having very similar problems since Appvolumes 4.1 im hoping this gets sorted but my guess is most users still on the old 2.x
Cleaning out threads. so since this was created we now on windows 10 1809 appvolumes 2.18.4 and 4.1 writable attached and start menu opening as it should happy days.
Cleaning up some old threads ok issue we had was the backend storage could not talk with each other perms. once we did this bam could have a writable on any datastore as the writable could ... See more...
Cleaning up some old threads ok issue we had was the backend storage could not talk with each other perms. once we did this bam could have a writable on any datastore as the writable could talk with the VSAN
Cleaning up some old threads I’ve created. this has been fixed with newer version of Appvol cleaning itself with the database.
Doing a clean up of my old threads a somewhat fix which is documented is doing a shutdown script C:\Windows\System32\net.exe stop /y workstation this seems to make life better.
So having a crack at this. so far hit and miss, so for some reason current Appvolumes VHD 4.1 templates get assigned for provisioning I can see the CVapps drive but I didn’t get the GUI. so... See more...
So having a crack at this. so far hit and miss, so for some reason current Appvolumes VHD 4.1 templates get assigned for provisioning I can see the CVapps drive but I didn’t get the GUI. so got an older 4.0.1 Template now I get the GUI when in provisioning mode. install apps as you do click ok to say I’m done and again to reboot. it seems it cancels my package. and looking at the server logs I get the following error BaseAdapter method not implemented “volumes_capacity” now I’ve been doing this stuff for a while now never seen this message before has anyone come across if so what was the fix ?
Hi all, Appvolumes 4.1 DEM 2006 Windows 10 1809 Ok when packaging multiple packages on Appvolumes 4.1 and deploying to my test users I’m getting a lot of feedback advising the start menu ... See more...
Hi all, Appvolumes 4.1 DEM 2006 Windows 10 1809 Ok when packaging multiple packages on Appvolumes 4.1 and deploying to my test users I’m getting a lot of feedback advising the start menu icons on multiple packages are showing up as dead icons the applications still work just dead icons. mic I assign my self the same package icons work when adding more packages they seem to be dead icons. anyone else experiencIng this same issue ?
Hi All, sorry I’ve been smashing the forums. So before I start this side project thought I would ask the forum. My agency is 90% physical hardware windows 10 1709/1809 So lost the fight... See more...
Hi All, sorry I’ve been smashing the forums. So before I start this side project thought I would ask the forum. My agency is 90% physical hardware windows 10 1709/1809 So lost the fight with VDI which sucks but if you can’t beat them take over them. So as a trial I’m going to look at VHD and do a small test and build my case In terms of delivering applications. So question is, this worth doing or am I just wasting my time ? will be using Appvolumes 4.1 like I said will be Windows 10 1709/1809 whats the pros and cons Any advise on how deploy a VHD to a corporate environment any info on this would be much appreciate. I would love to make this work but would love some opinions on the matter. Thanks in advance.
So we have 2 sites and funny thing is one site the first we upgraded needed that fix. where as my other site I didn’t require it as all. Very random.
Hey Mate, that’s strange I’m on Appvolumes 4.1 windows 10 1809 Did a new package with about 50apps installed including Chrome 85 and all working for us. I found that Group Policy can b... See more...
Hey Mate, that’s strange I’m on Appvolumes 4.1 windows 10 1809 Did a new package with about 50apps installed including Chrome 85 and all working for us. I found that Group Policy can be a pain also the editing of the shortcut we found you couldn’t make Chrome default browser. does it work with a slightly older version of Chrome ?
Hi All, Windows 10 1809 DEM 2006 Appvol 4.1 Got this awesome error with an application once launched application downloads updates to users Appdata once that is done the app asks to rest... See more...
Hi All, Windows 10 1809 DEM 2006 Appvol 4.1 Got this awesome error with an application once launched application downloads updates to users Appdata once that is done the app asks to restart and it can no longer access its folder in Program files becomes unavailable. Could access the folder prior to the application launching.  C:\Program file\Application folder is unavailable. If this location is on this PC, make sure that the device or drive is connected or the disc is inserted, then try again. If the location is on a network, make sure that you're connected to the network or internet, then try again. If the location still can not be found, it might have been moved or deleted. Solution for this that ive found 1. Go to C:\Program files\Application folder. 2. Open the folder name with your user name. 3. Right-click on the Application folder and select Properties. 4. Under the Location tab, click the Restore Default button. 5. Once done, restart your PC. Verify the permissions set on the file. 1. Open File Explorer. 2. Right-click the file folder and select Properties. 3. Go to Security and select Advanced. 4. Check the box for Replace all child object permission entries with permission entries from this object at bottom. 5. Click Apply, then OK. This does nothing. Now the fun part the application does work tho on old version of appvolumes Windows 10 1809 DEM 2006 Appvol 2.18.2 Same application could access the application folder located in C:\Program Files\Appname fine once the application is open and does its thing still could access the folder. So it seems to be Appvol 4.1 any idea any one had this issue ? Thanks, Nathan
So been happy with Appvol 4.1 but one thing choose what OS the packages can be assigned to. So because im packaging all on Windows 10 1809 X64 all been working. Issue today i update an existi... See more...
So been happy with Appvol 4.1 but one thing choose what OS the packages can be assigned to. So because im packaging all on Windows 10 1809 X64 all been working. Issue today i update an existing package to update an application and on completion of the package, it now shows under Operating Systems as There are no Operating Systems for this package. Ive said this back in March VMware please give us the ability to choose what OS this installs on dont lock it down. Ive now had to re create the whole package in order for the package to show Windows 10 X64. I know there is a database hack out in the wild but this should have been fixed on 4.1 i advised of this back on 4.0. Any update on this would be amazing. Thanks,
Hi Ray, thanks for the update never seen this issue before did a bucketload of apps and had to restart again when next back at work will confirm if your link worked or not. maybe with 4.... See more...
Hi Ray, thanks for the update never seen this issue before did a bucketload of apps and had to restart again when next back at work will confirm if your link worked or not. maybe with 4.2 or what not fixes this issue for future. Thanks,
Hi All, So updated to Appvol 4.1 and thought let’s add different size template. following the following instructions which I’ve been doing since 2.11 VMware Knowledge Base so issue I... See more...
Hi All, So updated to Appvol 4.1 and thought let’s add different size template. following the following instructions which I’ve been doing since 2.11 VMware Knowledge Base so issue I have do that with Appvol 4.1 and when you use the template it assigns a drive letter every time thought I would assign 20 packages bam 20 drive letter taken this is not ideal so I’ve gone with the standard template. works as normal all assigned to C:\snapvol im now using 20gb templates for stuff that could be 500mb any ideas? is it just me stuffing it up or this maybe a bug ? thanks in advance
So fixed my issue appvolumes all playing well again NTLM issue persists, disable NTLM authentication in App Volumes Manager: Open Windows Explorer on the App Volumes Manager machine. Righ... See more...
So fixed my issue appvolumes all playing well again NTLM issue persists, disable NTLM authentication in App Volumes Manager: Open Windows Explorer on the App Volumes Manager machine. Right-click My Computer. Click Properties > Advanced System Settings > Environment Variables. In the System Variables panel, click New. Enter AVM_NTLM_DISABLED in the Variable Name text box. Enter 1 in the Variable Value text box. Restart the App Volumes Manager service. Restart all desktops so they check back into App Volumes Manager. just nice I added that bam appvolumes happy. and packaged up Visio and project happy days
Yeah agreed mine displays GUI etc. compete the stack and assign it nothing shows up. but when I had 4.1 agent it gave me error 403 virtualization is disabled so will need to find out what’... See more...
Yeah agreed mine displays GUI etc. compete the stack and assign it nothing shows up. but when I had 4.1 agent it gave me error 403 virtualization is disabled so will need to find out what’s happening and get that sorted.
Can confirm this also Windows 10 1809 Appvol 4.1 Looks like the CVapps is attached but no gui to advise in provisioning mode. Use old client Appvol 4.0.1 all seems to work gui etc.