Do your App-V 5 Publishing MSIs just roll back, so that you can’t deploy applications to your stand-alone or test machines?
Sebastian Gernert tells you why on his blog (in German)
Apparently the App-V 5 SP1 x 64 Sequencer creates MSIs that just roll back.
Sebastian’s recommendation (and due to his job this is almost an official MS recommendation) you should apply a work around and set the following Registry keys (note that it ain’t values):
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\StrongName\Verification\*,31bf3856ad364e35] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\StrongName\Verification\*,31bf3856ad364e35]
(simply copy/paste into a .reg file and apply it)
Another option of course would be to use the add/publish/mount Powershell cmdlets (as we did in the training I was conducting this week in Austria)
(This is a fast publish article)
RollupPack for Citrix XenApp 6.0 may ‘break’ your App-V deployment.
It converts the command line for a published application into all lowercase characters – and if you use the SFTTRAY command and specify the App-V application’s name here, SFTTRAY requires case sensitive spelling of the vApp name.
In that case, App-V throws an error 04-00000A09
Luckywise there’s a Hotfix by Citrix at CTX136159.
This issue does not occur if you only use published desktops. It also does not occur if your XenApp publication ‘command line’ points to OSD files instead of SFTMIME
Recommendation: Apply HF03 for XA60R02 right away (… or migrate to XenApp 6.5)
(Fast publish article)
While previous versions of App-V targeted a single instance implementation, the new infrastructure servers for an App-V 5 native deployment are designed to be scaled out and to be diverged across separate machines. The services for Management, Publishing and Reporting are based on IIS, also Streaming can be done from a web site. App-V’s Services uses different ports for all these services – but what if you only want to use a single port, like 80?
The App-V Visio Stencil has been updated to reflect the new components that were introduced with App-V 5.
It contains dedicated symbols for the Publishing, Management, Reporting and Streaming Service as well as symbols for Clients running in shared-content mode. Symbols are genric enough to be used with App-V 4.x as well.
According to http://blogs.msdn.com/b/sgern/archive/2012/10/12/10359028.aspx (a very trustworthy source), Service Pack 2 for Microsoft Application Virtualization 4.6 will be deployed via Microsoft Update “at the end of this month” (which is November). A thing to consider…
“Hi there” ? This – for me – quite exuberant blog introduction may indicate to you that I am really excited about the book announcement that Nicke, Kalle, Ment and I published just yesterday
A while ago I wrote an article about what to do if you want to implement a Full App-V 5 Infrastructure – and you’re not the SQL Admin. Now, with App-V 5 going RTM, there are some updates – including additions for the Reporting Database and a little Powershell helper for you.
Do you want to launch ‘cmd.exe’ within an App-V 5 (Beta) Virtual Environment? ‘OSD Scripting’ can’t help you here… OSDs are gone. Read about a quite neat method that was discussed during the German User Group – and that was streamlined by Volker Kleiner (@vkleinerde)…
All right, you do have your new App-V Beta system installed according to the Beta Documentation – but your Apps just don’t appear on the Client Desktop! Where do you start? Let’s try to figure out some basic steps that can be the foundation of a troubleshooting guideline
We are currently in the preparation of our fifth German App-V User Group Meeting (“App-V Day”) for June 22nd close to Erfurt (Sömmerda).
Not only it is the fifth German App-V Day. This year we also have an Organizer Team of five people. And yes, for sure we will talk mostly about App-V 5 (but we have more than 5 topics to cover).
UPDATE: Agenda and Registraion online at http://bit.ly/IHYhW7