Client

Solution

Solved: VDA client unattended install failure.

When you’re solving the same problem after a couple of months it’s probably a good idea to write a post about it so the solution is close at hand. When you perform an unattended install of VDA client from the 7.x XenApp/XenDesktop media the installation may fail, after this first failure all other attempts will fail instantly.

Like every other self respecting IT engineer I always deploy my servers unattended, for this I like to use a product like RES One Automation 2015. When installing the VDA Client for the first time the installation failed, when examining the log file I noticed following lines:

  • XenDesktopSetup:Starting synchronous process ‘C:\Windows\TEMP\wisE4BD.tmp\Support\DotNet451\NDP451-KB2858728-x86-x64-AllOS-ENU.exe’ with args ‘ /norestart /quiet /q:a’

  • XenDesktopSetup:Process completed with error code 3010

  • XenDesktopSetup:Reboot level increased on behalf of ‘Microsoft .NET Framework 4.5.1’ from NoReboot to ImmediateReboot

  • XenDesktopSetup:InstallComponent: Exit (return False)

  • XenDesktopSetup:Install tasks for this session have finished.

  • XenDesktopSetup:Installation partially complete, reboot is required

  • XenDesktopSetup:Installation Manager returned PartialSuccessAndRebootNeeded

So the installation failed because it installed some dependencies from the support folder, and needed a reboot.

After rebooting the machine, I launched the installation again. Surprisingly it fail instantly and each and other try I did the result was the same. when examining the log file again I noticed the following error.

  • XenDesktopSetup:VerifyCDRoot: Failed to find the MediaID file at ‘C:\Windows\TEMP\wisE4BD.tmp\MediaId_F8D0A1D9-128F-4a86-842D-C61294BA0A02_x64’

  • XenDesktopSetup:VerifyCDRoot: Failed to find the MediaID file at ‘C:\Windows\TEMP\wisE4BD.tmp\x64\x64\MediaId_F8D0A1D9-128F-4a86-842D-C61294BA0A02_x64’

  • XenDesktopSetup:OleSafeThread: Install media not found at ‘C:\Windows\TEMP\wisE4BD.tmp\x64’. Exiting.

  • XenDesktopSetup:Installation media cannot be found

I know the wisxxxx.tmp folder is being automatically generated by RES One Automation, and changes each time. So I copied the source files to a fixed location and launched the installation again but still the log file states the same error message, when look up in the logfile I noticed the line

  • CDRoot = C:\Windows\TEMP\wisE4BD.tmp\x64

So the old CDRoot information is saved somewhere and causes the problem, after some search I found out the after the first installation a Citrix folder was created in the %programdata% location. In this location are some files I did not need. So I deleted this folder and tried again. Now the installation succeeded.

 

 

 

 

Solution

Solved: 0x0000007B BSOD after unattended install of PVS Target Device

While building a deployment sequence for a XenApp 6 farm using SCCM, I ran into the problem that the unattended install of the PVS Target Device (5.6 SP1)  succeeds but after after creating a VHD file using “XenConvert P2VHD” and booting the newly created vDisk the Provisioned Server crashes with a BSOD 0x0000007b (inaccessible boot device).

After some investigation on the source machine I noticed the “Citrix Virtual Hard Disk Enumerator PVS”  device did not install correctly and displayed an yellow exclamation mark in Device Manager (devmgmt.msc).  After searching the citrix forums I ran into a thread in which the others experienced the same problem.

Unfortunatly a real solution is not provided in within the thread (other than a manual installation). So digging down the internet I found the solution for this problem. Somehow the drivers files are not transferred to the “%windir%\System32\Driver” folder during unattended (SCCM/Wisdom) installation.  Copy CFsDep2*.* files from “C:\Program Files\Citrix\Provisioning Services\drivers”  to “%windir%\System32\Driver”  afterwards you can install you can install the PVS Target Device client unattended by running “PVS_Device_x64.exe /S /v /qn

After the installation the exclamation mark has disappeared, a newly created vDisk booted successfully.