With the introduction of RunVirtual as an official feature in App-V 5 SP3, the ability to use it for user targeted packages, and the ability of SP3 to set connection group members as optional, I started wondering whether it would be possible to create a connection group for all your IE (or Office) plugins and automatically launch IE (or any Office Application) inside the connectiongroup by using the RunVirtual Registry key, and still start IE (or any Office application) in a specific Virtual Environment by using the /AppVVE: command line hook switch. What I’m thinking of is a default connection group to start IE in for all standard (non conflicting) IE-plugins and separate packages for a specific Java versions. Similar with Office, one connection group for all standard (non conflicting) Office-plugins and separate packages for special plugins (plugins with conflicting versions, conflicting settings, etc.).
Will this work? What happens when an application is started and set to launch in two different Virtual Environments by a conflict between RunVirtual and the AppVVE parameter? Read More…
When you deploy applications to users that are members of a specific Active Directory Application Group but install them machine based, how do you automatically remove the application when a user is no longer a member of the Application Group? Well, before SCCM 2012 this was not possible. There was no way of knowing from which computer to remove the application if a user was no longer a member of the corresponding Application Group. Another problem was that a user could install de application on any PC he logged on to. Possible causing the company to not adhere to the license agreement.
With SCCM 2012 Microsoft introduced the ability to define Primary Devices for users and only allow installation of an application on the user’s primary device. This gives you better a grip on where applications are installed (and the required licenses).
This for me raised the question “Can I automatically remove an application from the primary PC for a user that is not (or no longer) the member of the Application Group for that application?”. Read More…
Hotfix 4 is actually more than just a hotfix. It is quite a major update. Most importantly it fixes the following:
- Hotfix 4 finally solved the issue with having to grant the local system access to a network share from which you wanted to launch an executable inside an App-V 5 environment. The workarounds described in my earlier post(s) are no longer required.
- It also finally allows us to write inside the Virtual Environment again, although with some limitations tot the types of files that can be written.
- We can now again save packages as new packages, like we were used to in App-V 4.6. This makes it much easier to create a (slight) variation of the same package.
- Performance issues have been addressed.
More Information and the rest of the fixes in HF4 can be found here.
Hotfix 5 adds the ability to create user based connection groups that contain both user published applications as well as globally published applications. This allows you to for instance publish Office globally and Office Add-ins on a per user basis.
This feature is however not supported in a full infrastructure scenario as there is no fix for the server available (yet) to enable this feature. But it should work with SCCM managed connection groups, although I haven’t been able to test it yet.
More Information and the rest of the fixes in HF5 can be found here.
*As of App-V 5 SP2 HF4 this article is no longer applicable*
About a year ago I wrote an article about launching a network executable inside an App-V 5 Virtual Environment (VE). This article unfortunately contained an error with regards to the required rights. So here’s the a revised version of that article with also some extra info.
The problem is that when running an executable that is on a networkshare inside a VE using the /appvve parameter you may get the following error. ‘The application was unable to start correctly (0xc0000142). Click OK to close the appliction.’ Read More…
Recently I had to sequence Autodesk TrueView 2014 using App-V 5 Sp1. At first this seemed pretty straightforward as I found some recipies on the Internet. But these all turned out to be incomplete or for App-V 4.6. I found that for the best result I had to move (at least the client) to SP2. So here’s my recipe for sequecing Autodesk TrueView 2014.
Visited the Packaging Event 2013 yesterday and today. The event will be renamed to Appmangevent for next year to be more inline with the broadened scope of the event. As it is no longer solely focused on packaging, but also on the other aspects of application management, although application (re)packaging was still the main focus this year.
My highlights were the Key Notes by Chris Jackson (the app compat guy from Microsoft) about the future of application packaging and of course application compatibility and by Ruben Spruijt and Jeroen van de Kamp about their perspective on tomorrow’s workspace. Trends such as Enterprise Mobility and Consumerization of IT and the developments in Desktop Virtualization, Application Delivery and Mobility Management were adressed and placed to show their importance to IT workspace design on both short and long term.
Other interesting sessions I found were Darwin Sanoy’s (CSIwindows.com) about Powershell Tips voor packagers (got some handy tips from there) and about SCCM 2007 to 2012 migration. His sessions are always interesting allthough the pace is very high (due to his enthousiasm to give you as much info and tips as possible) so they take some effort to follow, especially for non-native English speakers.
Sessions will be available for download allthough I don’t know whether they will be publicly available. If so I will post a link on this blog.
Of course meeting other people from the industry and renewing some old contacts was anoher great benifit of this event.
Hope to see you at APPMANAGEVENT 2014.
In this article I will try to explain how SCCM 2012 can be used to manage App-V 5 Connection Groups, and what the differences are between managing them with SCCM and managing them from a App-V 5 Full Infrastructure management server.
App-V 5 Connection Groups are managed from SCCM through what are called Virtual Environments. Virtual Environments define how the Connection Groups are created on the clients. Read More…