-
Subscribe
Subscribed
Already have a WordPress.com account? Log in now.
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
“Alles bleibt anders” (Everything remains different) might be a good short description for App-V 5 (Beta). While most of the components keep their names and follow existing general concepts, quite a lot changed under the hood. This post gives you a short overview about Aoo-V 5’s main components and the communication flow between them.
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…
A colleague of mine, Volker Kleiner (owner of App-V.info) , posted a German article on Softgrider.de about how to install the App-V 4.5 Management Server onto Windows Server 8 Beta. Why… well, because it just doesn’t work out-of-the-box. During installation, you’d get an Error 25100 or Error 25122. For Windows 2008, a solution is described at MS KB2212140, but that doesn’t work on Win8: To prepare the machine, you need to “convert” it into a “GUI less” server instance and convert it back afterwards. This is the (loose) English translation of that article…
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…
Kirx' Blog - kirxblog.wordpress.com 