Happy New Year! I hope you all had a perfect holiday season, I definitely did but now I think it’s time for my first post of 2013…. Now this is something that I have hardly heard anyone really talk about with App-V 5.0; the fact that we can now target

Wassup App-V heads! I recently published an Introduction to Virtual Application Extensions in App-V 5.0 blog post in which I talked about how virtual applications in App-V 5.0 have a much tighter synergy with the base platform and in some ways are less virtual then in previous versions. Virtual Application Extensions

This is a question I am often being asked as some people are expecting to find this within the MDOP download, in which you will only find the desktop client. To get the App-V RDS client you need to go to the Microsoft Volume Licensing Service Centre.

In App-V 4.6 we used to use the command line Sfttray /exe to open a process inside the virtual environment of an App-V Package, a lot of people referred to this as “breaking into the bubble”. As you would of heard, our trusty sfttray commands have been replaced in v5

Further to our Boston connection, Ryan Cobb’s blog around how to publish individual applications inside a package to different users found here, a few people have been asking me how that data configuration actually works. Let’s take this example whereby we publish Office to an AD group and customise the

Hello People, just a quick reference on how to setup the App-V client and quickly configure it to talk to a Publishing Server First of all the hardware and software requirements: Hardware Requirements Processor— 1 GHz or faster 32-bit (x86) or 64-bit (x64) processor RAM— 1 GB (32-bit) or 2

BIG NEWS! App-V 5.0 has just been made publicly available as part of MDOP 2012 which also includes the release of UE-V! After much speculation about the App-V 5.0 release date its great to have it finally here… Here’s the official announcement Here’s where you can get it Also here are

I think it would be safe to say that Shared Cache in App-V 4.6 was not the most popular solution for reducing the impact of App-V cache on client machines. From VDI to RDS, people didn’t want to duplicate the potentially huge sftfs.fsd cache file across their disks and consume unnecessary

Want to quickly see some of the key differences between 4.6 and 5.0 Beta? Here you go…. App-V 4.6 App-V 5.0 Mount drive (Q:) on sequencer and client No mount drive on sequencer or client RTSPS, RTSP, HTTP, HTTPS and SMB streaming HTTP, HTTPS and SMB streaming .SFT package file

So you may have heard rumours about App-V 5.0 applications being able to have less isolation and more entry points to the base OS. Well, that’s true, and it’s all because of a new feature called Virtual Application Extensions. This new features allows you to be very intentional around certain