Blogs from TMurgent
VDI is often categorized as either Non-Persistent or Persistent.
Non-persistent VDI is where you use a shared common image. Only one image to maintain. When the user logs off, the image is destroyed and the next time the user logs on they get the original image.
Persistent VDi is where the complete image is retained upon logout and the next …
OK. So a simple solution for every connection group situation isn’t going to happen any time soon. See recent posts in this series “Who Are You”? and App-V 5 Script Error 534 and A collection (so far) of #APPV 5 Client file visibility and blocking information. But here is one situation that I solved, and maybe that might help …
While I continue to try to get a better grip on connection groups, let’s continue documenting some of the side issues I have come across. Today, I’ll focus on a single package and either want to block visibility of a potential local installation or need to allow visibility of something local, like a license file.
In attempting to work solutions …
One of the frustrations that I have in working with App-V 5 virtual apps is remembering to forget everything that I know about how application virtualization worked before version 5. Quite often, the same concept is implemented just so slightly differently that I make assumptions about an app problem that is incorrect, simply because I “know” more than I should. …
Maybe there is something to AppV_Manage you’ll find useful. This free tool from the App-V 5 Tools section of the TMurgent website was recently covered as a great source for troubleshooting App-V in a Microsoft support blogpost on TechNet by Microsoft’s own John Behneman!
Check it out here: https://blogs.technet.com/b/appv/archive/2014/01/30/how-to-troubleshoot-app-v-5-0-deploymentconfig-amp-userconfig-script-deployment-failures-using-appv-manage.aspx …
In our training class on App-V 5 SP2 two weeks ago (yes, I did do the class using the Service pack less than a week after the release), we had a problem in one of the labs and saw a new client error 0x8AD. I won’t name names, but the student causing all the chaos is visible in the photo …
Yesterday, Microsoft released App-V 5.0 SP2 as part of MDOP 2013 R2. (The photo on the left is from the MVP summit two weeks ago with myself, Nicke Kallen, Aaron Parker, and Adam Kiu of the App-V Dev team. He couldn’t tell us when the release would come down, but clearly his work had been completed and he was one …
I have written a new “white paper” on App-V 5. This one looks at package “pellucidity” (the layering effect caused by the settings “override local” or “merge with local”), and package deletion objects and how these are implemented at the client when you use Connection Groups.
As it was in 4.6 with DSC, all is not as simple as you …