Do you want to update all your old SoftGrid / App-V Packages to the newest Sequencer / Client version? Do you need to create Publishing MSIs for a bunch of packages because in the past you didn’t need them but want to use them now? Here is a simple Powershell Script that converts all existing packages within a folder structure recursively.
I was given they chance to attend this year’s European HP Discover event in Vienna. Because there were some quite surprising aspects for me, there might be some news for you as well.
Apparently, I am not that Server Hardware, Network Equipment nor Storage guy, so I was quite sceptic about the value HP Discover could give to me.
So I was seeking for at least ‘sort of’ interesting stuff amongst the 650 breakout sessions and technical demos. Of course there were tons of Storage and Server related sessions, but also a lot of ‘cloud’ stuff I actually started with.
After some German only events, I’m glad to announce the first Euopean App-V User Group Meeting on Nov. 18th in the Netherlands.
There will be about half of all world wide App-V MVPs on site (most of them even presenting), so this is probably a unique oppurtunity to meet with them and other community leader.
While the day is fully packed with awesome presentations, time is planned for questions and answers. And as Community events should be: it’s free!
You can register at www.appvug.com.
If you’d like to tweet about it: #AppVUG is the tag of choice.
Hope to see you there!
Falko
Citrix’ policy for the release of Provisioning Services is – let’s say it
that way – not quite clear. mal. Some Hotfixes simply disappear from the public
site, some hotfixes that appear there are replaced by others. Also, the
individual CTX articles for the hotfixes don’t always tell clearly, if a hotfix
has replaced others or if it was superseded itself.
Forced to by some projects I tried to collect all the Citrix Hotfixes that
are:
Please refer to the PDF for more details on the hotfixes: Citrix-PVS-Hotfixes_2011-09-06
[Update 2011-09-12] Hotfix clarification by Citrix Support about E028 and E006 applied: E006 replaces E028. The updated PDF is Citrix-PVS-Hotfixes_2011-09-12.
Do you want to get a comprehensive overview of all your App-V applications and packages, no matter if you use a Management Server, SCCM, another deployment solution or even manual deplyoments?
Do you want to verify quickly, if Naming Conflicts between virtual packages, 8+3 folders and other items occur?
Then, get Login Consultant’s “App-V Analyzer” to get all the infos usefully presented!
Sebastian Gernert posted in German at http://blogs.msdn.com/b/sgern/archive/2011/07/19/10187771.aspx that Hotfix 3 for App-V 4.6 SP1 is available on request.
According to Sebastian, this patch addresses the following issues:
Treat the topics with caution: they are a “free translation” from German!
Some of the topics have been addressed with HF1 and HF2 already.
If you encounter any of the issues described above, you may contact Microsoft Support to request the Hotfix.
The KB article ID will be 2571168.
It has been a question “ever since”:
Now, Project Virtual Reality Check (http://www.projectvrc.com) has released a Whitepaper that provides an idea of that. ProjectVRC compared Microsoft App-V, VMware ThinApp and Citrix XenApp Streaming running in Virtual Windows 7 machines.
While the impact is significant, there are some things to note…
The new App-V Sequencer 4.6 SP1 introduces – besides new features – a set of new wizards. While in the „old“ Sequencers, basically there were three different
wizards (New; Open; Open for Upgrade), there are 7 wizards available within 4.6 SP1. To increase confusion, most of these wizards contain choices that influence the Sequencing process. Depending on those process choices, some wizard steps will be skipped.
After working with the new Sequencer for a while now I tried to figure out which wizard allows (or prevents) certain activities.
… at least that is one question that often is discussed in an App-V environment.
While monitoring an application setup with the App-V Sequencer, you will have to decide if you install the application to the C: drive (the installer’s default location) or to the Q: drive. Microsoft strongly recommends to always install to the Q: drive (an “MNT install”). However, many
applications proved to work fine after they were installed to C: (a “VFS install”).
This article discusses some of the myths and facts around that “C: vs. Q:” or “VFS vs. MNT” installations.
Note: To limit the size of that post, there is an “Extended Version” availabe as PDF at http://bit.ly/mam6oO. This PDF contains more detailed information, esp. the details to reason the table’s content.
[Update 2011-05-23: Tim Mangan blogged about an issue when Sequencing to Q: in the App-V 4.6 SP1 Sequencer. http://www.tmurgent.com/TmBlog/?p=402]
This is a loose translation of Sebastian Gernert’s blog articel “4.6 SP1 Sequencer registriert Dateien nicht richtig…” (German).
Sebastian namely thanks Jan Pfisterer and Marius Gawenda, who pointed him to that issue.
Because the new Sequencer does not require a separate hard disk partion for the Q: drive (but uses a Symbolic Link), some components (like OCX controls) may not register correctly. In their registration, they may point to the Symbolic Link’s target (on the C: drive) instead.
