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.
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.
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
App-V 5 Beta allows to connect to a Database that is installed on a remote machine. However, it has shown that using a remote SQL Database is not that trivial. This article will highlight how to prepare the remote SQL Database to be used by App-V 5.
Reading through the documentation there is no hint that connecting an App-V 5 Publishing Server to an SQL database that is running on a different machine might be sort of ‘special’. Instead, it states something like “just enter the name of your Database Server’ and that’s it. Well, if you read some forum articles, posts and tweets it appears that this implementation does not exactly provide an ‘out-of-the-box’ experience. Let’s see…
So, you followed one of the posts orthe Admin Guide that have told you how to publish a new application with the App-V 5 Beta Management/Publishing Server(s) – but your Client doesn’t seem to refresh changes?
The potential reason for this is an interval that is defined on the Publishing Server feature. By default, it only refreshes its information every ten minutes. If this appears to slow for you, there is a simple switch to shorten that period…
The installation of the App-V Management Server 4.5.x on a Windows Server 2008/2008R2 occasionally fails with an “The installation programm was unable to create the required IIS virtual directory: Error 25120″
The most likely cause for this is that the “IIS Management Scripts and Tools” and/or the “IIS 6 Management Compatibility” role features are not installed. This has been discussed and confirmed several times, like at BallBlog, SystemCenterCentral, the App-V forum on Technet, Miito’s Blog and other sources (like here).
Another potential cause, that obviously is not so common, is a missing “Default Web Site” in IIS…