Step-by-step guide for upgrading your App-V 5.0 infrastructure to Service Pack 3

~ Matthew Keyes | Premier Field Engineer

Hi everyone, my name is Matthew Keyes and I’m a Premier Field Engineer here at Microsoft. Lately we have been getting some questions from customers regarding the proper procedure for upgrading App-V 5.0 infrastructure to SP3 so I put together a quick step by step outline that will guide you through the process.

Step 1: Upgrade the database using the SQL scripts

Be sure to update the two scripts as discussed in the following KB article:

3031340 - SQL scripts to install or upgrade the App-V 5.0 SP3 Management Server database fail (https://support.microsoft.com/kb/3031340)

Note that there is no need to upgrade the reporting database because there are no changes in SP3 with regards to reporting.

a. Backup the following registry keys and verify that values exist and are set per the following TechNet article: https://technet.microsoft.com/en-us/library/dn858700.aspx#BKMK_check_reg_key_svr

HKLM\Software\Microsoft\AppV\Server\ManagementDatabase
HKLM\Software\Microsoft\AppV\Server\ManagementService

b. Update the permissions.sql with the correct accounts needed: The App-V_Admins group SID (or whatever the name of the group that has admin rights to the App-V console) for the read rights (PublicAccess) and the SID of the management server’s machine account for the write rights for database access. Also verify that the production database name matches the database name listed in database.sql. See the following for more information:

• How to install the App-V 5.0 Database and Management Server using SQL scripts on the DB
• How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services

You can use the following PowerShell commands to resolve the SID’s:

$Account=”domain\App-V_Admins”
(New-Object system.security.principal.NtAccount($Account)).translate([system.security.principal.securityidentifier]).value
$Account=”domain\machine_account_name$ ”
(New-Object system.security.principal.NtAccount($Account)).translate([system.security.principal.securityidentifier]).value

The bolded text above needs to be updated with the account you will be using in production. Also note that the SIDs need to be pasted into permissions.sql without ‘S’s and ‘-‘s (dashes).

c. Run the management database scripts in SQL Management Studio. Follow the instructions that are listed in the ReadMe.txt file to install or upgrade to the App-V 5.0 SP3 Management Server database. You can find this file in the Management folder in the order indicated by the ReadMe.

d. Verify that the dbo.SchemaVersion table exists.

Step 2: Upgrade the server infrastructure

Be aware that the management and publishing servers should be updated at the same time. More information on this can be found at https://technet.microsoft.com/en-US/library/jj713425.aspx.

a. First, check that all prerequisites have been met (see https://technet.microsoft.com/en-us/library/dn858705.aspx). Be aware that .NET 4.5 is a new prerequisites for Service Pack 3.

b. Run the installer.

c. Verify that the version of the console is 5.0.10107.0 which is the version for App-V 5.0 SP3. You can do this by going to https://localhost:1234/Console.html and then clicking About.

Note that all of the options should be grayed out and the upgrade configuration information will pulled from the registry.

Step 3: Upgrade the clients

More information on this can be found at https://technet.microsoft.com/en-us/library/jj713460.aspx.

a. First, check that all prerequisites have been met (see https://technet.microsoft.com/en-us/library/dn858705.aspx). Be aware that .NET 4.5 is a new prerequisites for Service Pack 3.

b. Execute the installer.

c. Verify that the client version is 5.0.10107.0. This can be viewed by going to Control Panel –> Programs –> Programs and Features.

Step 4: Upgrade the sequencer

More information on this can be found at https://technet.microsoft.com/en-us/library/jj713464.aspx.

a. First, check that all prerequisites have been met (see https://technet.microsoft.com/en-us/library/dn858705.aspx for more information). Be aware that .NET 4.5 is a new prerequisites for Service Pack 3.

b. Execute the installer.

c. Verify that the sequencer version is 5.0.10107.0. This can be viewed by going to Control Panel –> Programs –> Programs and Features.

That should do it - Hope this helps!

Matthew Keyes | Premier Field Engineer| Microsoft

Get the latest System Center news on Facebook and Twitter :

System Center All Up: https://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: https://blogs.technet.com/configurationmgr/ 
Data Protection Manager Team blog: https://blogs.technet.com/dpm/ 
Orchestrator Support Team blog: https://blogs.technet.com/b/orchestrator/ 
Operations Manager Team blog: https://blogs.technet.com/momteam/ 
Service Manager Team blog: https://blogs.technet.com/b/servicemanager 
Virtual Machine Manager Team blog: https://blogs.technet.com/scvmm

Microsoft Intune: https://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: https://blogs.technet.com/sus/
The RMS blog: https://blogs.technet.com/b/rms/
App-V Team blog: https://blogs.technet.com/appv/
MED-V Team blog: https://blogs.technet.com/medv/
Server App-V Team blog: https://blogs.technet.com/b/serverappv
The Surface Team blog: https://blogs.technet.com/b/surface/
The Application Proxy blog: https://blogs.technet.com/b/applicationproxyblog/

The Forefront Endpoint Protection blog : https://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : https://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: https://blogs.technet.com/b/isablog/
The Forefront UAG blog: https://blogs.technet.com/b/edgeaccessblog/

Comments

• Anonymous
  January 01, 2003
  If you are trying to upgrade the RDS client then this article is not relevant. However if you are trying to upgrade the server infrastructure and your databases are local then you will not need to use the SQL scripts as long as the account you are using to do the upgrade has administrative rights to SQL.
• Anonymous
  January 01, 2003
  The comment has been removed
• Anonymous
  January 01, 2003
  In any case, I was able to successfully upgrade to SP3 only by full uninstalling/installing
  http://blog.it-kb.ru/2015/03/26/update-app-v-5-0-sp1-service-pack-1-servers-and-rds-client-with-remote-database-sql-to-sp3-service-pack-3/
• Anonymous
  January 01, 2003
  The comment has been removed
• Anonymous
  January 01, 2003
  There is no need to uninstall any previous update prior to installing the latest update.
• Anonymous
  February 17, 2015
  The comment has been removed
• Anonymous
  March 19, 2015
  Hi There J.C
  
  First of all, thank you for writing this guide. I'm a bit confused though. We haven't used the SQL scripts you refer to in step 1, so i assume i can skip this step. However when i start the RDS setup and i get to the point where i can 'Select App-V Server Features to be Installed', they are all checked and greyed out. But you tell me theres no need to upgrade the reporting server DB?
  
  Everything else in the wizard also seems to be checked and greyed out. I even get to the point where it asks me to create a new reporting database.
• Anonymous
  April 16, 2015
  The comment has been removed
• Anonymous
  August 28, 2015
  Hi, thanks for the step by step description, I found it very usefull ! Is the procedure the same for App-V 5.1? I was reading through the 5.1 documentation, and the SQL part is not very clear...
  Thx,
  Kris
• Anonymous
  September 16, 2015
  Looking for a similar guide for upgrading App-V 5 to App-V 5.1
• Anonymous
  September 29, 2015
  Here is a list of the top Microsoft Support solutions for the most common issues experienced when you
• Anonymous
  November 10, 2015
  The comment has been removed