Jump to content
Welcome to our new Citrix community!
  • 0

VDA Upgrade 7.15 CU3 to 1912 LTSR


Question

Hi -

Was curious if anyone has seen this behaviour before: 

 

VDA 7.15 is deployed with the following parameters: 

VDAServerSetup_7_15_3000.exe /quiet /components vda /exclude "Personal vDisk" /controllers "controller.corpad.net" /enable_hdx_ports /optimize /enable_real_time_transport /enable_remote_assistance /logpath "C:\Windows\Logs" /noreboot

 

and after deployment and one reboot - all citrix related services are up and running

 

VDA 1912 is scripted to upgrade 7.15 via the following command line:

 

VDAServerSetup_1912.exe /controllers "controller.corpad.net" /noreboot /quiet /enable_remote_assistance /disableexperiencemetrics /logpath "C:\Windows\Logs" /enable_real_time_transport /no_mediafoundation_ack /enable_framehawk_port /enable_hdx_ports /enable_hdx_udp_ports /includeadditional "Citrix Universal Print Client","Citrix Supportability Tools","Citrix User Profile Manager","Citrix User Profile Manager WMI Plugin" /exclude "Citrix Telemetry Service","User Personalization layer","AppDisks VDA Plug-in","Citrix Files for Outlook","Citrix Files for Windows","Citrix Personalization for App-V - VDA","Machine Identity Service","Personal vDisk"
 

And after deployment - one reboot - Only the Citrix Desktop service starts. This occurs in all OS's 2008R2 and later. 

Second reboot required to start all Citrix Services.

 

Remediation attempts:

- Use VDA 1912 CU1, reboot - fails (only Citrix Desktop Service starts)

- Execute Uninstall of 7.15 CU3, reboot, install VDA 1912, reboot -  fails (only Citrix Desktop Service starts)

- Execute Uninstall of 7.15 CU3, reboot, VDA Cleanup Utility, reboot, install VDA 1912 - all citrix services start but we have -  partial success (citrix workspace 1911 gets installed)

- VDA Cleanup Utility, reboot, install VDA 1912 - all citrix services start but we have - partial success (citrix workspace 1911 gets installed)

- Execute install of VDA 1912 on a CLEAN system, reboot - all citrix services start but we have partial success (citrix workspace 1911 gets installed)

 

Ideal outcome is to upgrade our worker servers with just the 1912 command line driven install and with one reboot after upgrade - all Citrix services start. 

 

So question to the community:

 

1. even though I specifically omitted /components vda,plugin in the command line for 1912 - why is Citrix workspace 1911 getting installed? (We plan on Citrix Workspace 1912 LTSR to be deployed to worker servers where needed). According to the documentation - omitting /components switch should only deploy vda not plugin. 

 

2. ideas on starting up citrix related services post successful installation of 1912 after ONE reboot could be a workaround. But I fear this may possibly lead to undesirable effects

 

Many thanks in advance

Vic

 

 

Link to comment

6 answers to this question

Recommended Posts

  • 0
On 5/19/2020 at 5:45 AM, Muralidharan Shanmugam said:

@vic delamoya1709161438

I could not repro this issue. When upgrade VDA using same command line as you mentioned, workspace is not installed. please provide more information.

The Citrix services are not started until finish upgrade. Please confirm if the VDA is installed completely.

 

 

 

Hi muralidhar1 

 

Only the Citrix Powershell SDK is installed before the initial installation of multisession VDA 1912. 

 

Name                                                       Version   Caption                                                   
----                                                       -------   -------                                                   
Citrix Configuration Logging Service PowerShell snap-in    7.19.0.8  Citrix Configuration Logging Service PowerShell snap-in   
Citrix Delegated Administration Service PowerShell snap-in 7.19.0.8  Citrix Delegated Administration Service PowerShell snap-in
Citrix Machine Creation Service PowerShell snap-in         7.19.0.8  Citrix Machine Creation Service PowerShell snap-in        
Citrix Storefront Service PowerShell snap-in               7.19.0.8  Citrix Storefront Service PowerShell snap-in              
Citrix Workspace Environment Management Agent Host         4.07.0000 Citrix Workspace Environment Management Agent Host        
Citrix Host Service PowerShell snap-in                     7.19.0.8  Citrix Host Service PowerShell snap-in                    
Citrix PoSH SDK Proxy PowerShell Snap-In                   7.19.0.8  Citrix PoSH SDK Proxy PowerShell Snap-In                  
Citrix Broker PowerShell Snap-In                           7.19.0.19 Citrix Broker PowerShell Snap-In                          
Citrix Configuration Service PowerShell snap-in            7.19.0.8  Citrix Configuration Service PowerShell snap-in           
Citrix AD Identity Service PowerShell snap-in              7.19.0.8  Citrix AD Identity Service PowerShell snap-in             
Citrix Analytics PowerShell snap-in                        7.19.0.8  Citrix Analytics PowerShell snap-in                       

 

 

Attached is the installation log for a fresh install of multisession VDA 1912 install onto the same system. 

 

Please note that /components switch is missing from the commandline parameters and yet it still deploys Workspace 1911.

 

This behaviour does not occur when you upgrade from 7.15 CU3 to 1912 using the exact same parameters.

 

 

XenDesktop Installation.log

Link to comment
  • 0
On 5/22/2020 at 4:06 PM, vic delamoya1709161438 said:

 

 

Hi muralidhar1 

 

Only the Citrix Powershell SDK is installed before the initial installation of multisession VDA 1912. 

 

Name                                                       Version   Caption                                                   
----                                                       -------   -------                                                   
Citrix Configuration Logging Service PowerShell snap-in    7.19.0.8  Citrix Configuration Logging Service PowerShell snap-in   
Citrix Delegated Administration Service PowerShell snap-in 7.19.0.8  Citrix Delegated Administration Service PowerShell snap-in
Citrix Machine Creation Service PowerShell snap-in         7.19.0.8  Citrix Machine Creation Service PowerShell snap-in        
Citrix Storefront Service PowerShell snap-in               7.19.0.8  Citrix Storefront Service PowerShell snap-in              
Citrix Workspace Environment Management Agent Host         4.07.0000 Citrix Workspace Environment Management Agent Host        
Citrix Host Service PowerShell snap-in                     7.19.0.8  Citrix Host Service PowerShell snap-in                    
Citrix PoSH SDK Proxy PowerShell Snap-In                   7.19.0.8  Citrix PoSH SDK Proxy PowerShell Snap-In                  
Citrix Broker PowerShell Snap-In                           7.19.0.19 Citrix Broker PowerShell Snap-In                          
Citrix Configuration Service PowerShell snap-in            7.19.0.8  Citrix Configuration Service PowerShell snap-in           
Citrix AD Identity Service PowerShell snap-in              7.19.0.8  Citrix AD Identity Service PowerShell snap-in             
Citrix Analytics PowerShell snap-in                        7.19.0.8  Citrix Analytics PowerShell snap-in                       

 

 

Attached is the installation log for a fresh install of multisession VDA 1912 install onto the same system. 

 

Please note that /components switch is missing from the commandline parameters and yet it still deploys Workspace 1911.

 

This behaviour does not occur when you upgrade from 7.15 CU3 to 1912 using the exact same parameters.

 

 

XenDesktop Installation.log 100.21 kB · 1 download

 

 

Hi guys - 

 

Just wanted to give an update:

 

For the scenario where we deploy multisession VDA 1912 to a clean system

- The "/components vda" must be explicitly declared in order to omit the deployment of Citrix Workspace 1911

 

Upgrading to multisession VDA 1912 from 7.15CU3 is still under investigation (Still requires two reboots before Citrix Services are fully started)

Link to comment
  • 0

@vic delamoya1709161438

 

When upgrading VDA from 7.15 CU3 to 1912,  VDA needs to restart 4 times: the first reboot after .Net 4.7.1 installed, the second reboot after VC++ installed, the third reboot during VDA installation, the fourth reboot after component initialization. The Citrix services are not started until the finished upgrade. Please try and confirm if the VDA is installed successfully.

Link to comment
  • 0
On 5/28/2020 at 6:41 AM, Muralidharan Shanmugam said:

@vic delamoya1709161438

 

When upgrading VDA from 7.15 CU3 to 1912,  VDA needs to restart 4 times: the first reboot after .Net 4.7.1 installed, the second reboot after VC++ installed, the third reboot during VDA installation, the fourth reboot after component initialization. The Citrix services are not started until the finished upgrade. Please try and confirm if the VDA is installed successfully.

 

Thanks, that's super helpful to know. We are having issues doing scripted in-place upgrades from 7.15 CU3 to 1912 as well, and I'm thinking the issue is that with those prerequisites making it difficult for the upgrade to run unattended. Can you confirm what versions of VC++ get installed in this process? We will try installing those ahead of time to see if we have better luck.

Link to comment
  • 0

I had to modify my install script to make it loop enough times through the reboots and check if the install completed. This is part of a much larger script, but maybe will give you some ideas how to modify your scripted install. 
 

    4{
    If(GetRegValue $global:ScriptStateInfoKey $global:ScriptStateNewInstallName) {
        $Message = "Sleeping for waiting for setup to continue"; LogMessage $Message
        $timerouter = 0
		
        while ( ( (get-process | where { $_.Name -like "*Setup*" }).Count ) -eq 0 -and $timerouter -lt 5) {
            Start-Sleep -Seconds 15
            $timerouter++  
        }
		
		$status = GetRegValue $global:ScriptStateInfoKey $global:ScriptStateLastExecutionStep4
		If($status -eq "INITIAL" -or $status -eq "FIRSTPASS") 
		{
			if((Get-Service "BrokerAgent" -ErrorAction SilentlyContinue) -eq $null) {
				$Message = "Install did not complete...rebooting and trying again."; LogMessage $Message
				$Message = "Rebooting machine in 15 seconds..."; LogMessage $Message
				Start-Sleep -Seconds 15
				
				If($status -like "*INITIAL*")
                {
				    $a = SetExecutionStatus -step 4 -PassFail "FIRSTPASS"		
				}
                else
                {
                    $a = SetExecutionStatus -step 4 -PassFail "SECONDPASS"
                }
				Restart-Computer -force
				Exit
			}
		}
		else
		{
			$myvalue = 3
			SetRegValue $global:ScriptStateInfoKey $global:ScriptStateInfoName $myvalue "DWORD"
		}

        while ( ( (get-process | where { $_.Name -like "*Setup*" }).Count ) -gt 0 -and (Get-Service "BrokerAgent" -ErrorAction SilentlyContinue) -eq $null ) {
			$Message = "Install running. Sleeping 15 seconds..."; LogMessage $Message
            Start-Sleep -Seconds 15
        }

        If ( (Get-Service "BrokerAgent" -ErrorAction SilentlyContinue) -eq $null) 
        {
			$myvalue = 3
			SetRegValue $global:ScriptStateInfoKey $global:ScriptStateInfoName $myvalue "DWORD"

            $Message = "Install did not complete...rebooting and trying again."; LogMessage $Message
            $Message = "Rebooting machine in 15 seconds..."; LogMessage $Message
            Start-Sleep -Seconds 15
            Restart-Computer -force
            Exit
        }
        Else 
        { 
            $Message = "Installation complete..."; LogMessage $Message
            SetRegValue $global:ScriptStateInfoKey $global:ScriptStateNewInstallName 0 "DWORD"

            RestoreAutoLogon

			$myvalue = 4
			SetRegValue $global:ScriptStateInfoKey $global:ScriptStateInfoName $myvalue "DWORD"

            $Message = "Rebooting machine in 60 seconds..."; LogMessage $Message
            Start-Sleep -Seconds 60
            Restart-Computer -force
            Exit
        }
    }

 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...