Sergey Galushko - Fotolia
Before installing App-V 5.0 SP3, it's important to review the hardware and software prerequisites needed for proper operation of the App-V server and other components. Although there is a lengthy list of software requirements to enable App-V 5.0, such as Microsoft .NET Framework 4.5.1, PowerShell 3.0 or later and many others, almost all prerequisite components are already installed with the required OS versions.
For example, the App-V management server function will require a 64-bit Windows OS, such as Windows Server 2008 R2 SP1 or later, running on almost any server capable of running the OS well. Minimum hardware typically includes a 64-bit 1.4 GHz or faster processor, 1 GB of memory and 200 MB of storage. Essentially, every current enterprise-class server will provide ample computing resources to run App-V components. The App-V management server will also need a database like SQL Server 2008 R2 SP3 or later. App-V publishing and reporting server functions have similar server requirements. App-V is compatible with Windows 7 SP1, Windows 8 and Windows 8.1 client operating systems on any endpoint computer capable of running the OS well.
The move to App-V 5.0 SP3 brings several changes to the App-V platform with numerous improvements to connection groups and management. For example, administrators can now package optional components to application packages -- administrators could package Office for everyone, but include certain plug-ins for different user groups. Options can also be unpackaged or deleted without having to recreate connection groups.
Users can publish packages too, but administrators can limit user publishing capabilities. Administrators can use PowerShell cmdlets like Publish-AppvClientPackage and Unpublish-AppvClientPackage, to publish or unpublish packages for specific users, allowing careful tailoring of application content for user needs. Several new PowerShell cmdlets are available to manage connection groups including Add-AppvServerConnectionGroupPackage, to append a package, Set-AppvServerConnectionGroupPackage, to edit package details, and Remove-AppvServerConnectionGroupPackage, to remove a package.
App-V also generates a variety of logs, which are now consolidated in one location accessible through the Event Viewer application. There are other changes in App-V 5.0 SP3, but these are the most noteworthy points.
Using Microsoft App-V tool
What you need to know about App-V Sequencer
Which is better: App-V versus ThinApp
Dig Deeper on Application virtualization
Related Q&A from Stephen J. Bigelow
Learn how load balancing in the cloud differs from a traditional network traffic distribution, and explore services available from AWS, Google and ... Continue Reading
Access management is critical to securing the cloud. Understand the differences between AWS IAM roles and users to properly restrict access to AWS ... Continue Reading
Containers have rapidly come into focus as a popular option for deploying applications, but they have limitations and are fundamentally different ... Continue Reading