App Orchestration 2.6. Upgradability Guide for App Orchestration 2.6

Transcription

1 App Orchestration 2.6 Upgradability Guide for App Orchestration 2.6 Last Updated: July 11, 2015

2 Contents Introduction... 3 Before You Begin... 3 Supported Upgrades... 3 Prerequisites... 3 Credentials... 3 User impact... 4 Upgrade order... 4 Upgrade progress... 4 Web console connectivity... 5 Known Issues... 5 Download App Orchestration 2.6 and related software... 5 Backup the database... 5 Option 1: App Orchestration 2.6 with bundle... 5 Option 2: App Orchestration StoreFront XenApp XenApp 7.6 and XenDesktop Upgrade the App Orchestration 2.5 Configuration Servers...10 Upgrade the XenDesktop and XenApp 7.5 Delivery Controllers and App Orchestration Agent.12 Upgrade the XenApp 6.5 App Orchestration Agent...12 Upgrade StoreFront 2.5 and App Orchestration Agent...13 Upgrade the Virtual Delivery Agents...13 Page 2

3 Introduction This document contains information on upgrading your existing App Orchestration 2.5 deployment to App Orchestration 2.6. You can manage the upgrade of complex environments, including those with multiple App Orchestration configuration servers, by upgrading each server and the database schema that hosts the information for App Orchestration. During the upgrade process, the App Orchestration console provides information on the upgrade status of various components of your deployment, including the App Orchestration configuration servers, XenDesktop or XenApp Delivery Controllers, and StoreFront servers. Upgrades to the Virtual Delivery Agent are handled by creating a new version of the Session Machine Catalog, as explained in the document Upgrading Session Machine Catalogs in App Orchestration 2.6. Before You Begin Supported Upgrades The procedures in this document apply only to the following component versions: Upgrade from this version: Table 1 Component Upgrades To this version: App Orchestration 2.5 App Orchestration 2.6 XenDesktop and XenApp 7.5 XenDesktop and XenApp 7.6 XenApp 6.5 HRP04 XenApp 6.5 HRP05 StoreFront 2.5 StoreFront 3.0 Prerequisites Before you begin the upgrade process, make sure you have the following: PowerShell 4.0.NET Framework Credentials Perform the upgrade using your orchestration service account, with local administrative rights (App Orchestration Administrator group). Page 3

4 User impact User sessions are not impacted during the upgrade process. Upgrade order If your deployment has multiple App Orchestration configuration servers, Citrix recommends upgrading half of the configuration servers to App Orchestration 2.6, then upgrading the database schema and environment configuration, and finally upgrading the remaining configuration servers. Citrix recommends waiting for any workflows to complete before you begin the upgrade process. However, if you decide to begin the upgrade while workflows are still processing, you can upgrade all but one of your configuration servers. After the workflows finish, upgrade the database schema and environment configuration, and then upgrade the last configuration server. Citrix doesn t recommend upgrading all of the configuration servers before upgrading the database schema and environment configuration. After the last configuration server is upgraded, you would temporarily have no way to connect to the web console until after the database schema and environment configuration upgrade finish. Upgrade App Orchestration (including all of your configuration servers, plus the database schema and environment configuration) before you upgrade XenDesktop, XenApp, and StoreFront. Otherwise, the App Orchestration 2.6 agents on those upgraded products will be unable to communicate with your App Orchestration 2.5 deployment. Upgrade progress For App Orchestration 2.6, upgrading related software is done via PowerShell scripts. Do not attempt to use the Citrix App Orchestration Install Center to perform an upgrade. Once you have begun the upgrade process, you can monitor the status of your deployment upgrade using the App Orchestration web console. The Dashboard reports the database schema version status of each configuration server in your deployment. For example: Page 4

5 Web console connectivity The App Orchestration web console loses connectivity to the configuration server while that server is being upgraded. To make changes to your deployment, either wait until the upgrade completes, or connect to a different configuration server. After you install App Orchestration 2.6 on a configuration server, that server cannot connect to the App Orchestration web console until you upgrade the deployment s database schema and environment configuration to App Orchestration 2.6. If you try to connect from a configuration server with newer software, a dialog box asks whether you want to Manage the deployment (which reroutes you to a different configuration server that s still running App Orchestration 2.5), or Upgrade the deployment (which runs an assessment to determine the components that need upgrading). Known Issues Refer to the Known Issues for App Orchestration 2.6 document for the complete list of issues for this release. Download App Orchestration 2.6 and related software Backup the database 1) Backup your deployment databases: For App Orchestration - AppOrchestration and AppOrchestrationLogging For XenDesktop - xdsite, xdlogging, xdmonitoring For XenApp xasite Option 1: App Orchestration 2.6 with bundle 1) Navigate to the download page for the Citrix Cloud Provider Pack. 2) Log on to your Citrix account and download App Orchestration 2.6 with Bundle. Page 5

6 3) Extract the downloaded zip file (App_Orchestration_2.6_Bundle.zip) into a folder of your choice (for example, AO), with the following layout, you do not need to do anything more to prepare the product media folder: Note: The image folder can be local to all machines (recommended), or on a portable drive, a network share of any kind, or any other location that is visible to all of your machines. Citrix recommends that you protect this folder with appropriate access controls, to prevent unauthorized access that might result in file corruption or the introduction of malware. Option 2: App Orchestration 2.6 1) Navigate to the download page for the Citrix Cloud Provider Pack. 2) Log on to your Citrix account and download App Orchestration ) Extract the downloaded zip file (App_Orchestration_2.6.zip) into a folder of your choice, for example, AO, with the following layout. Page 6

7 4) Build out the product media folder. The product media folder hosts the media for App Orchestration and any related products that you copy into the folder. The product media folder serves a similar purpose to the Product Depot in App Orchestration 2.5, while providing greater flexibility in its location. a) Expand the Setup folder to show the contents of the folder ProductMedia: Setup ProductMedia CloudAppManagement Page 7

8 b) Create additional folders in ProductMedia so that the folder structure looks like this: Note: Create the XenDesktop folder if your deployment will use XenDesktop 7.5 or XenApp 7.5. Create the XenApp folder and its subfolders if your deployment will use XenApp ) Download the related software into the appropriate locations within the ProductMedia folder structure, as explained below. StoreFront 3.0 1) Navigate to the StoreFront download page and download StoreFront ) Copy the StoreFront software to the CitrixStoreFront folder in the ProductMedia folder. XenApp 6.5 1) Navigate to the XenApp 6.5 download page to download XenApp ) Navigate to the Hotfix Rollup Pack5 for XenApp 6.5 to down XenApp 6.5 HRP 05. Page 8 From the download media, copy the XenApp software to the XenApp folder in the ProductMedia folder. Then copy the entire contents of the Hotfix Rollup Pack 5 to Xenpp\XenAppHRP in the ProductMedia folder. Lastly copy the entire Setup\ProductMedia\CloudAppManagement\Support\SQLServer2012 folder to XenApp\Support folder

9 XenApp 7.6 and XenDesktop 7.6 1) Navigate to the XenDesktop download page and download the version 7.6 Platinum Edition. 2) From the download media, copy the XenApp 7.6 or XenDesktop 7.6 software to the XenDesktop folder in the ProductMedia folder. 3) Download Hotfix for Citrix Studio 7.6 from x64 version download page or x86 version download page. 4) Rename the downloaded.msi files and copy to XenDesktop folder: For x64 version Rename DStudio760WX64002.msi to DesktopStudio_x64.msi and copy to XenDesktop\x64\DesktopStudio For x86 version Rename DStudio760WX86002.msi to DesktopStudio_x86.msi and copy to XenDesktop\x86\DesktopStudio 5) Download Hotfixes Update 2 for Delivery Controller 7.6 from x64 version download page or x86 version download page. 6) Rename the downloaded.msi files as follows: For x64 version Rename BrokerSrvc760WX64002.msi to Broker_Service_x64.msi and copy to XenDesktop\x64\Citrix Desktop Delivery Controller Rename ConfigMgrWOL760WX64002.msi to ConfigMgr_WOL_Plugin_x64.msi and copy to XenDesktop\x64\Citrix Desktop Delivery Controller Rename HostSrvc760WX64002.msi to Host_Service_x64.msi and copy to XenDesktop\x64\Citrix Desktop Delivery Controller Rename MCSrvc760WX64002.msi to MachineCreation_Service_x64.msi and copy to XenDesktop\x64\Citrix Desktop Delivery Controller Rename MonitorPSSI760WX64002.msi to Monitor_PowerShellSnapIn_x64.msi and copy to XenDesktop\x64\Citrix Desktop Delivery Controller Rename MonitorSrvc760WX64002.msi to Monitor_Service_x64.msi and copy to XenDesktop\x64\Citrix Desktop Delivery Controller For x86 version Rename BrokerSrvc760WX86002.msi to Broker_Service_x86.msi and copy to XenDesktop\x86\Citrix Desktop Delivery Controller Rename ConfigMgrWOL760WX86002.msi to ConfigMgr_WOL_Plugin_x86.msi and copy to XenDesktop\x86\Citrix Desktop Delivery Controller Rename HostSrvc760WX86002.msi to Host_Service_x86.msi and copy to XenDesktop\x86\Citrix Desktop Delivery Controller Rename MCSrvc760WX86002.msi to MachineCreation_Service_x86.msi and copy to XenDesktop\x86\Citrix Desktop Delivery Controller Rename MonitorPSSI760WX86002.msi to Monitor_PowerShellSnapIn_x86.msi and copy to XenDesktop\x86\Citrix Desktop Delivery Controller Rename MonitorSrvc760WX86002.msi to Monitor_Service_x86.msi and copy to XenDesktop\x86\Citrix Desktop Delivery Controller Page 9

10 7) Download Hotfixes For Machine Identity Service Agent 7.6 from x64 version download page or x86 version download page. 8) Rename the downloaded.msi file and replace the same files under XenDesktop folder: For x64 version Rename MISA760WX64001.msi to MachineIdentityServiceAgent_x64.msi and copy to XenDesktop\x64\Virtual Desktop Components For x86 version Rename MISA760WX86001.msi to MachineIdentityServiceAgent_x86.msi and copy to XenDesktop\x86\Virtual Desktop Components folder 9) Download Feature Pack 2 for XenDesktop 7.6 from XenDesktop FP2 download page and Extract the download.zip package 10) Rename the downloaded.msi files and replace the same.msi files under XenDesktop folder: Copy DesktopDirector_x64.msi and replace DesktopDirector.msi XenDesktop\x64\DesktopDirector\DesktopDirector.msi Copy DesktopDirector and replace XenDesktop\x86\DesktopDirector\DesktopDirector.msi Rename GPMx240WX64002.msi to CitrixGroupPolicyManagement_x64.msi and copy to XenDesktop\x64\Citrix Policy Rename GPMx240WX86002.msi to CitrixGroupPolicyManagement_x86.msi and copy to XenDesktop\x86\Citrix Policy Rename HDXWMIPROV220WX64001.msi to CitrixHDXWMIProvider-x64.msi and copy to XenDesktop\x64\Virtual Desktop Components\TS copy WMIProxy_x64.msi to XenDesktop\x64\Virtual Desktop Components copy WMIProxy_x86.msi to XenDesktop\x86\Virtual Desktop Components Rename XDPoshModule760WX64002.msi to XDPoshSnapin_x64.msi and copy to XenDesktop\x64\Citrix Desktop Delivery Controller Rename XDPoshModule760WX86002.msi to XDPoshSnapin_x86.msi and copy to XenDesktop\x86\Citrix Desktop Delivery Controller 11) Copy the downloaded.msp files to XenDesktop\MspHotfixes folder: copy ICATS760WX64022.msp to XenDesktop\MspHotfixes\x64\Virtual Desktop Components\Server copy ICAWS760WX64022.msp to XenDesktop\MspHotfixes\x64\Virtual Desktop Components\WorkStation copy ICAWS760WX86022.msp to XenDesktop\MspHotfixes\x86\Virtual Desktop Components\WorkStation Upgrade the App Orchestration 2.5 Configuration Servers Note: After you upgrade an App Orchestration configuration server to version 2.6, you cannot join additional App Orchestration 2.5 configuration servers to that deployment. However, you can Page 10

11 continue using existing App Orchestration 2.5 configuration servers until you have upgraded the database schema to version 2.6. After you upgrade to App Orchestration 2.6, you cannot join additional XenDesktop and XenApp 7.5 Delivery Controllers or StoreFront 2.5 servers to your deployment. However, you can continue to use, but not modify, existing ones. 1) From the first App Orchestration configuration server, browse to CloudAppManagement in the ProductMedia folder and run Setup. Follow the prompts to install App Orchestration 2.6 on the first server. The installer detects that App Orchestration 2.5 is currently installed and prompts you to start the upgrade to App Orchestration 2.6. This step should take about 5 minutes. 2) Close the Setup dialog box. When prompted, click Yes to restart the machine. Note: If the upgrade fails, check the log files in %temp%\citrixlogs\apporchestrationserverconfiguration. A new log file is generated each time you run the application. The format of the log filename is: AppOrchestrationServerConfiguration_YYYYMMDDHHMMSS.log 3) Install the App Orchestration 2.6 software on half of your configuration servers. 4) From one of the upgraded configuration servers, run Citrix App Orchestration Server Configuration to upgrade the database schema and environment configuration. Upgrading the database schema and the environment configuration for all of the servers takes about minutes for the schema and about 3 minutes per configuration server. Note: When upgrade App Orchestration 2.5 to 2.6 in a multiple configure server environment, the administrator might encounter the following error during App Orchestration Configure Server upgrade wizard process: Cannot find any service with service name 'CitrixCamAgent' and the upgrade process will halt. The reason behind the failure is that Windows Firewall blocks the Microsoft built-in command get-service against the remote computer. To work around this issue, please enable the Remote Service Management (NP-In) and Remote Service Management (RPC) firewall in-bound rule on App Orchestration Configure Servers and re-run the App Orchestration Configure Server upgrade wizard. 5) Now install the App Orchestration 2.6 software on the remaining half of your configuration servers. 6) Run Citrix App Orchestration Server Configuration again to upgrade the configuration on the remaining servers. 7) Click the Close button to launch the web console. In the Dashboard Notifications section, orange alerts indicate that XenDesktop and StoreFront are still at older version levels. While you can continue to use the older versions, we recommend updating to the latest versions to take advantage of the new features. Page 11

12 Upgrade the XenDesktop and XenApp 7.5 Delivery Controllers and App Orchestration Agent To take advantage of all of the features of App Orchestration 2.6, upgrade the XenDesktop and XenApp 7.5 Delivery Controllers to 7.6 and the App Orchestration agent to 2.6. Note: Upgrade one Delivery Controller at a time. Upgrading multiple machines concurrently could cause the upgrade process to fail and render the Delivery Site unusable. 1) Log on to one of the XenDesktop and XenApp 7.5 Delivery Controller machines in the App Orchestration 2.5 deployment. 2) Open a PowerShell window and set the location to the ProductMedia folder, then run the script.\upgrade-xendesktopcontroller.ps1. 3) If prompted, enter Yes to restart the controller. Important: After the machine reboots, re-run the script to finish the installation. 4) After the first Delivery Controller has successfully been upgraded, repeat for all remaining controller machines. Note: This procedure only upgrades the controllers; the Session Machines are still using XenDesktop and XenApp 7.5 and will continue to function. However, the remaining unallocated session machines in the existing session machine catalogs might not be allocated anymore. To take advantage of the XenDesktop 7.6 and XenApp 7.6 features, upgrade your Session Machines Catalogs as described in the document How to Upgrade App Orchestration Session Machine Catalogs, Offerings, and Subscriptions in Place Upgrade the XenApp 6.5 App Orchestration Agent You can continue using your existing XenApp 6.5 controllers after you upgrade to App Orchestration 2.6; however, you should install the new App Orchestration agent for XenApp servers. 1) Log on to one of the XenApp 6.5 Controller machines in the App Orchestration 2.5 deployment. 2) Open a PowerShell window and set the location to the ProductMedia folder, then run the script.\upgrade-xenappcontroller.ps1. 3) If prompted, enter Yes to restart the controller. Important: After the machine reboots, re-run the script to finish the installation. 4) Repeat for all remaining controller machines. Page 12

13 Upgrade StoreFront 2.5 and App Orchestration Agent To take advantage of all of the features of App Orchestration 2.6, upgrade the StoreFront servers to StoreFront 3.0, and the App Orchestration agent to App Orchestration ) Log on to one of the StoreFront server 2.5 machines in the App Orchestration 2.5 deployment. 2) Open a PowerShell window and set the location to the ProductMedia folder, then run the script.\upgrade-storefrontserver.ps1. The script: Enables maintenance mode for the StoreFront Server Group until all servers have been upgraded. Upgrades the StoreFront server to version 3.0 and the App Orchestration agent to 2.6. Checks whether any StoreFront servers in the group still need to be upgraded. If so, the script notifies the administrator. If not, the script disables maintenance mode. 3) If prompted, enter Yes to restart the controller. Important: After the machine reboots, re-run the script to finish the installation. 4) Repeat for all remaining StoreFront server machines. Upgrade the Virtual Delivery Agents Refer to the document How to Upgrade App Orchestration Session Machine Catalogs, Offerings, and Subscriptions in Place. Page 13