MCS-provisioned VDA dropped out of the domain after OS upgrade

MCS-provisioned VDA dropped out of the domain after OS upgrade

book

Article ID: CTX324207

calendar_today

Updated On:

Description

Following an OS upgrade, MCS-provisioned VDAs leave their domain on reboot. 

You may also observe computer account password resets at that time.

Environment

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Resolution

  1. On the VDA, open the Services console and check dependencies of the Citrix Pvs for VMs agent, Netlogon, and Workstation services (under Properties > Dependencies). Verify that the dependencies are set up as expected. 

The expected dependencies:

  1. If you observe that these services lost any of their dependencies, re-assign them manually via the Registry Editor (Option 1) or Command Line (Option 2).
    • Option 1: in the Registry Editor, create the below regkeys.

Registry Path : HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation
Name : DependOnService
Type: REG_MULTI_SZ
Data : PvsVmAgent

Registry Path : HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer
Name : DependOnService
Type: REG_MULTI_SZ
Data : PvsVmAgent

    • Option 2: execute the following two commands via the Command Line.
reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation /v DependOnService /t REG_MULTI_SZ /d "PvsVmAgent\0Bowser\0MRxSmb20\0NSI" /f

reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer /v DependOnService /t REG_MULTI_SZ /d "PvsVmAgent\0SamSS\0Srv2" /f

Problem Cause

Citrix recommends that you uninstall the VDA Agent component from a VDA machine prior to upgrading its OS. If you decide to carry out the OS upgrade without uninstalling the VDA, you will notice the dependencies for PvsVmAgent missing from "HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation" and "HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer". That happens because Microsoft overwrites the LanmanWorkstation and LanmanServer settings with default values during OS upgrades. There is no way to avoid this behaviour as it occurs at the OS level. 

Powered by Wolken Software