Natestack's Accepted Solutions

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.
Ok fixed this issue due to adobe CS6 having the same error. fix is package the application like normal and add the license fix from adobe in the start menu. running this fixes the error and... See more...
Ok fixed this issue due to adobe CS6 having the same error. fix is package the application like normal and add the license fix from adobe in the start menu. running this fixes the error and users can run adobe like normal. now I need UEM to play and automatically run the license fix when user logs on.
Got this sorted. so the appv packages that gets installed copy the contents from the first guid. create a folder direct in C:\ or in C:\program files or C:\program files (x86) while doin... See more...
Got this sorted. so the appv packages that gets installed copy the contents from the first guid. create a folder direct in C:\ or in C:\program files or C:\program files (x86) while doing a capture and this methord seems to work. Remember to change the shortcuts from the current appv file path to the new location and all works well.
This was fixed using UEM to untick the protected view boxes for the applications
Hey Guys, Sorry for the late reply. issue resolved bad SQL database
Ok got this working with just thinapp. closing task as UEM was not the correct way to get this issue sorted.