Blogs from TMurgent
Tim is a Microsoft MVP, and a Citrix CTP Fellow.
He is an expert in App-V and MSIX.
AppV_Manage is a free tool from TMurgent used to test newly sequenced App-V 5 application packages. Versions 3.1 and 3.2 have added integrations to round out this phase of the packaging experience.
Automation When Citrix announced the end of life for Citrix Streaming (See What’s a Citrix Streaming Customer to do now?) there was a need for a tool
Here is my explanation: Someone at Microsoft has been taking lessons on how to name product releases from Citrix. There really can be no other explanation for App-V 5.0 Service Pack 2 Hotfix 4. It is full of features. I mean, why not call it release 5.1 (or 5.3)? Or maybe Service pack 3? Surely they know how to build …
This year marks the 10th Anniversary of BriForums, a rather unique conference that I have had the privilege of speaking at many times. In fact, I’ve lost count of how many I have spoken at since I have spoken at every one and for many of those years there has been both one in Europe and one in the US. …
In writing some apps for some APP-V 5 performance testing, I stumbled on a problem that was at least new to me.
I know that in App-V 5 the client will only run Virtual Services under the Local System account. But I didn’t know that it totally ignored the others, I thought it captured them and just changed the account. …
Microsoft Desktop Optimization Pack (MDOP) is a subscription add-on used by many enterprises with Microsoft Enterprise Agreements (EA) that provides a number of software benefits. The software has recently been released on a twice-a-year basis, making the next version due sometime soon. Microsoft typically does not pre-announce release dates, so we can only guess that, based on the last release …
A small comment by Microsoft’s Thamin Karim at the European AppV User Group event in Amsterdam last week caused me to re-think streaming in App-V 5. It was one of those “duh!” moments that occur when something so obvious hits you and you realize that you hadn’t really thought about it and were operating on wrong assumptions.
The comment, which …
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 …