When publishing App-V 5.x applications it is interesting to know how long it takes to publish all applications. I needed this information during a large scale test to get a better understanding of the impact on the user experience. I also wanted to know if the publishing time increases when more users are active. This information can be used to optimize the publishing time and eventually the user experience.
In this blog post I will share a powershell function that can get the App-V publishing time on a remote specific machine.
Login VSI supports application virtualization, but how do you integrate App-V within a workload? Depending which applications are virtualized it is possible to run the medium workload without any modifications. When every application is virtualized some modifications are required. Because Login VSI v4 has a simple workload language, App-V can be easily integrated. In this blog post I will explain the App-V 4.x & 5.x integration with Login VSI.
Please note: Workload customization/modification requires a Login VSI PRO license. More information can be found here.
On my corporate laptop I use a virtual Mozilla Firefox sequenced with Microsoft App-V. I created the package with all the plugins and settings that I prefer. One day I discovered strange behavior when I applied a desktop background from the virtual package.
During sequencing of an application I received an error about the services (App-V Sequencer 4.6). The installer of the application installs a service that is required for the application. Normally the installer starts the service and continues the installation but this time the following error message occurred.
With the SCCM 2007 R2 release Microsoft delivers a VBScript to import and manage App-V applications. Because the limitations I wrote the import part in Powershell. The following script is only to import an App-V application and does not create a Collection or Advertisement.
To import an App-V application the following parameters are required.
$App = The App-V sequence name based on the directory name.
$Site = SCCM Site
$smsShare = The share of the SCCM server to copy the application to.
$AppShare = The share where the application is located.
$SCCMServer = SCCM Server Name.
Param($App, $Build, $Site, $smsShare, $AppShare, $SCCMServer)
The following function is to add the icon in SCCM.
$Obj = New-Object -ComObject ADODB.Stream
$Obj.Type = 1
Set-Variable -Name IconData -Value $Obj.Read() -Scope 2