Hello People, just a quick reference on how to setup the App-V client and quickly configure it to talk to a Publishing Server
Processor— 1 GHz or faster 32-bit (x86) or 64-bit (x64) processor
RAM— 1 GB (32-bit) or 2 GB (64-bit)
Disk— 100 MB for installation (not including the disk space utilized by virtualized applications)
Microsoft Windows 7 (32-bit and 64-bit versions) or Windows 8
Microsoft .NET 4 Framework (Full)
Windows PowerShell 3.0
The Microsoft Visual C++ 2005 SP1 Redistributable
The Microsoft Visual C++ 2008 Redistributable.
The Microsoft Visual C++ 2010 Redistributable.
The installation itself is very simple and it will not prompt you for any configuration items. After accepting the license terms and choosing whether to join the improvement program, the client will go ahead and install.
Now to register a Publishing Server
Once installed we need to configure the client to get updates from a publishing server for updates, we can do this via PowerShell. Firstly import the App-V Client PowerShell module:
Then to register the publishing server:
Add-AppvPublishingServer -Name displayname -URL http://publishingservername:port
Then we can carry out an initial sync to test connectivity:
Sync-AppvPublishingServer -ServerId 1
This command will check in with the publishing server to check the current entitlements against what has been configured on the management server.
You may notice a few more configurations relating to the publishing server above, these can also be set either at install using the relevant switches against the installer or can be set via PowerShell after install, the ones I want to call out are related to the user refresh:
UserRefreshEnabled Values: (0/1) Enables a publishing refresh for the user
UserRefreshOnLogon Values: (0/1) Specifies whether or not a user refresh should be initiated at user logon
UserRefreshInterval Values: (0-744) Specifies the frequency of the refresh with the publishing server, can be in days or hours as below
UserRefreshIntervalUnit Values: (Hours(0) or Days (1)) Specifies the unit for the UserRefreshInterval setting
Good blog, just what i was looking for. You might want to add that before importing the appvlient module you need to enable running scripts with "Set-ExecutionPolicy RemoteSigned”. SP1 for App-V 5 has been released but the new setup based on SP1 has the same steps as listed above so you can also add that it Applies to App-V 5.0 SP1.
Forgot to sign in, I have added the previous comment.
Good shout Danny and useful info.I tend to avoid adding the remote-signed stuff into the blogs so I don't need to repeat myself in every post that contains PowerShell but definitely worth note for those who aren't familiar with it!
It seems when using a publishing server the applications are not published globally to all users. Can the client obtain that configuration setting from the publishing server or does one need to modify each package at the client level?
You can do this centrally, check out this post: blogs.technet.com/.../enabling-computer-based-targeting-in-app-v-5-0.aspx
Excellent blog, more greese to your elbows
I am really struggling answer for this Question..
1. How can I use the XML files [Deployment Config and User Config] of App-v 5.0 packages, If I install the package only through MSI. Is there any command line options to pass these XML files along with MSI or how it will be handled. Thanks
There isn't a switch. You have to understand the .msi is simply a wrapper for the PowerShell commands that adds your package in via standalone mode. The .msi isn't really designed for mass deployment, rather offers an option for unmanaged end users. If you do need to use the .msi then simply run the relevant PowerShell afterwards to specify the .xml. Does that help?
Really I want to know what is the Command line I have to use for having this XML after installing the MSI.
Thank you for keep blogging on App-V.
I have been using the product since 4.5 version, I like this product.
I have an issue with App-V 5 SP1.
I have 3 virtual machines as the following:
- App-V Management Server (2012 R2) + IIS 8.5
- App-V SQL Server 2012 SP1
- App-V Publishing Server (2012 R2) + IIS 8.5
I deleted the Default Website from the IIS and I am using Port 80 for the management, 81 for reporting and 82 for publishing server.
The Publishing Server is installed on a separate Server.
I can see all my published application in the App-V management Web.
I have registered the App-V Publishing server under Servers TAB in the management Web as well.
I noticed many events errors logged in the Publishing Server, Events ID: 214 & 215
- Event ID214 @ The request URL doesn't contain the query string for the client version.
- Event ID215 @ The request URL doesn't contain the query string for the client OS.
If I browsed the Publishing Server URL, I can see all my published applications:
- <Publishing Protocol="1.0">
<Package PackageId="4711e502-bff3-4e38-a2f3-7c1f164cf2fc" VersionId="9fbd534c-d8ab-47da-b1c2-4540cd947fe0" PackageUrl="\\172.16.20.114\Content$\Computer Lab Apps\ActiveInspire.appv" />
<Package PackageId="51461a66-3949-41ba-afc7-0d47752c9d9c" VersionId="a34dc5b3-bac7-49be-ae66-b255599e8064" PackageUrl="\\172.16.20.114\Content$\Office2010_x86_SP1\Office2010_x86_SP1_3.appv" />
- <Package PackageId="d24c3bdd-8fad-44d3-998c-933f8f053682" VersionId="eb698da1-efa9-4545-beb9-f67cbb959f40" PackageUrl="\\172.16.20.114\Content$\Office365_x86\O365ProPlusRetail_en-us_x86.appv">
<DeploymentConfiguration ConfigurationId="13" Path="policies_67/6/13" Timestamp="2013-11-12T05:46:23.41" />
<Package PackageId="4711e502-bff3-4e38-a2f3-7c1f164cf2fc" />
<Package PackageId="51461a66-3949-41ba-afc7-0d47752c9d9c" />
<Package PackageId="d24c3bdd-8fad-44d3-998c-933f8f053682" />
However, on the client side, the Error Log ID: 19104 is logged
Part or all packages publish failed.
Please check the error events of 'Configure/Publish Package' before this message for the details of the failure.
How can this be solved please?
Your support is highly appreciated.
Hi Arokiyaraj M,
For the deployment configuration xml please use: Add-AppvClientPackage C:\pathto.appv -DynamicDeploymentConfiguration C:\pathtoxml
For the user configuration xml please use: Publish-AppvClientPackage C:\pathto.appv -DynamicUserConfigurationPath C:\pathtoxml
Hope that helps