even hacked a dirty little batch script to fix it -> stick the PS install MSI bits in C:\Temp\PowerShell

set "folderPath=C:\temp\Powershell"

cd /d "%folderPath%"

for %%i in (*.msi) do (
    echo Installing "%%i"...
    msiexec /i "%%i" /qn
    if !errorlevel! neq 0 (
        echo Installation of "%%i" failed with error code !errorlevel!
    ) else (
        echo Installation of "%%i" succeeded.
    )
)

endlocal

And that ctx article where you basically install all the individual posh msis worked in the MDT automation. Just very odd.

you see that as well? Any issues with removing that SDK for the PVS Console, thought there was a different onprem SDK, which is separate from the cloud SDK

used this to uninstall the SDK after the PVS Console gets installed

$GetApp = Get-ItemProperty HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*, HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Sort DisplayName | Where-Object {$_.DisplayName -like "*Daas*"} $GetApp Start-sleep -seconds 5 -Verbose if ($getapp) { Write-host "uninstalling Citrix DaaS Remote Powershell SDK" #Doesn't work when this component is installed with Studio Start-Process $($getapp.BundleCachePath) -wait -ArgumentList "/uninstall /quiet" }

then studio get's installed after

prob should change this to the full name in add/remove programs. Where-Object {$_.DisplayName -like "*Daas*"}