Problem/Question
You would like to deploy Microsoft Virtualised applications (AppV) via LANDesk Management Suite/LANDesk Security Suite (LDMS) and have full control over them.
You would like to test the concept of using virtualised applications with LDMS and the use of them in my environment.
Background
If you do not know anything about AppV or how it is used; it is highly recommended that you read and explore the following Microsoft TechNet webpages on this product
http://technet.microsoft.com/en-us/appvirtualization/bb508934.aspx
Here is also a good article from Microsoft on setting up a test environment to test the product (Trial Guide) This will also give you some background information on how the product works
http://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V%20%205.0%20Trial%20Guide.docx
Solution/Resolution
In this article I am going to provide two ways in which you can use the Microsoft Application virtualisation software with LDMS. The AppV product I will using is version 5 and the LDMS version 9.5 .
I will describe two methods in which you can publish an application via the software distribution component of the LDMS suite.
Here is a simplified diagram of each method and how they can be used:
Quick Reference:
Method 1
Method 2
Reconfiguration of Standalone client
The first method will be to deploy the AppV client using command switches to point it towards the AppV publishing server so that clients can receive Applications from the server which they have the rights to access.
N.B. This method(1) requires the AppV infrastructure in place to work correctly, i.e the AppV publishing server
Here is an article on the command switches for the executable for AppV Client.
http://technet.microsoft.com/en-us/library/jj713460.aspx
This scenario works best for computers that always are connected to the company WAN/LAN and can access the publishing server on a constant basis.
]
The second method is to deploy a standalone AppV client, no command switches are required as this client is not connected to any publishing server. This method needs Virtual Apps deployed to it via LDMS to receive the applications themselves and any updates that you make to the virtualised application.
The Virtualised application will come in the form of an Offline deployment MSI, which is created by the AppV Sequencer, which negates the need to configure the client and have a constant connection to the Publishing server.
This automatically caches the shortcuts and application into the client ready for use.
This scenario would be ideal for users (Laptops) who need this Virtualised application at home or away from the main WAN/company network in which they cannot connect to the publishing server for authentication for the use of the product.
Each scenario has its advantages and disadvantages e.g the advantage for the first method is that any application you publish on the AppV server will be available to your chosen clients almost immediately, but they will need to be connected to the company network to do this.
With this method all AppV deployments and updates will be handled by the publishing server
Where as the second method will allow you deploy the virtualised applications offline, so users , such as laptop users or home users will able to use these applications without having to be connected to the company network. With this method all AppV deployments will be handled by the LDMS software distribution component.
Pre-Requisites
The AppV client requires some pre-requisites before it can be installed.
The pre-requisites are Microsoft .Net 4.0 Extended and PowerShell 3.0.
Download Locations:
Microsoft .Net 4.0 Extended
http://www.microsoft.com/en-gb/download/details.aspx?id=17718
PowerShell 3.0
http://www.microsoft.com/en-gb/download/details.aspx?id=34595
Please note that PowerShell 3.0 requires a reboot to complete its installation
The best way with the files above is to use the software distribution component of LDMS, using this method you can also set dependencies for the AppV client packages which I will show you how to create later in the document
Using the software distribution component deploy the above Microsoft .Net 4.0 Extended download as a executable with the following switches for a silent and no restart install:
/q /norestart
The executable contains both installers for 32 and 64 bit machines
To deploy the PowerShell msu package via software distribution a batch file is the best method, here is an example script which you can use:
@ECHO OFF
REM Set the commands to run from the current directory
cd %0\..\
REM Processor type so the right update is installed
IF EXIST PROCESSOR_ARCHITECTURE=AMD64
GOTO AMD64
IF EXIST PROCESSOR_ARCHITECTURE=x86
GOTO x86
:x86
START /WAIT WUSA Windows6.1-KB2506143-x86.msu /QUIET /NORESTART
EXIT
:AMD64
START /WAIT WUSA Windows6.1-KB2506143-x64.msu /QUIET /NORESTART
EXIT
Along with this script add the above PowerShell Microsoft update files as well to the distribution package as additional files
Deployment of AppV Client and Virtualised Applications
For both scenario's you will have to set up a AppV sequencer to create the virtualised application ready for deployment, here is a TechNet article on how to do it
http://technet.microsoft.com/en-us/library/jj713464.aspx
From here you can create a virtualised application of your choice.
Here is a TechNet article describing the process:
http://technet.microsoft.com/en-us/library/jj713468.aspx
QR:Method1
Once you have created the virtualised application that you want to use , this is where the two different methods come into play, for the first method, create a virtualised application as normal and publish it onto the AppV server via the publishing server console. Assign the appropriate rights ,publish and your application will be available for you on the client once the client has been refreshed.
In this example I used Firefox as my Virtualised Application.
Now this application is published you are now ready to deploy the AppV client ready for the published Virtual App.
Firstly copy the AppV client packages from the installation ISO into your packages folder,
In the software distribution component of LDMS, create a new executable package, selecting the AppV client package.
Now add the additional files that are required for the installation of the product
Now enter the command switches that will point the AppV client to the publishing server
Here is the example of the command line switches that I used to point this towards my publishing server
/NORESTART /ACCEPTEULA /q /S1PUBLISHINGSERVERNAME=APPV2008R264
/S1PUBLISHINGSERVERURL=http://APPV2008R264:889
/S1GLOBALREFRESHENABLED=1 /S1GLOBALREFRESHONLOGON=1 /Log C:\LOGS\LOG.LOG
More information on the switches can be found here:
http://technet.microsoft.com/en-us/library/jj713460.aspx
From here you can set up some dependencies for the installation of the AppV client package either in the form of a Prerequisites query or Dependant Package.
More information for using dependant packages can be found here :
http://community.landesk.com/support/docs/DOC-7753
Now deploy the package to client and it is now ready to use with the AppV Publishing server
QR:Method2
For the second method, instead of publishing the virtualised application on the publishing server you will deploy the virtualised application's .msi file which is created as part of the sequencing process outline above., along with all over of the files created for the virtualised application
Create the AppV client as outline above , with the added difference of setting the command line to only this :
/NORESTART /ACCEPTEULA /q
Once this package has been deployed it will be empty of any Applications.
To fill it with Virtualised Applications we will deploy the .msi file created earlier as part of the Sequencing process along with the other files that were created.
Open up the software distribution window and create a new msi deployment.
Point the to the main Virtualised Msi package in your packages store
Now add the additional files that are needed for this Virtual Application
As this is a msi distribution the silent and norestart switches will already be in place as default
As with the package before you can set up a dependency for this installation to only install if the AppV client is installed:
Once you have finished, deploy the standalone AppV package and the Virtualised Application .
Once this has finished deploying you now have the virtual app installed and available offline
QR:Reconfigure
Adding the standalone AppV client to the publishing server
At some point you might want to connect to the AppV standalone client to the publishing server so that you can push updates and applications to it via the publishing server as opposed to the LDMS core.
You can either redeploy the executable with the switches as described above or send a PowerShell script to redirect the client towards the publishing server.
Here is an example one I used to redirect my standalone AppV client to my publishing server:
Import-Module AAppVClient
Add-AppvPublishingServer -Name APPV2008R264 -URL http:\\APPV2208R264:889
Set-AppVPublishingServer -ServerID 1 -GlobalRefreshEnabled 1 -GlobalRefreshOnLogon 1
After you have successfully deployed this , restart the client machine for the changes to take effect.
Here is a TechNet article on the different PowerShell Commands that you can send to the AppV client to configure it remotely:
http://technet.microsoft.com/en-us/library/jj713419.aspx
And here is an article on sending the settings to AppV clients via the GPO:
http://technet.microsoft.com/en-us/library/jj684299.aspx