Install program through RDP vs install program through Hyper-V console

Viktor Backan 6 Reputation points

Is there a difference installation wise? We have a sub contractor refusing support for a program installed through RDP with local admin account since they say all registry keys are not applied and we should have had installed the programs directly through the Hyper-V console on the host machine or through TeamViewer etc.

We've never had a problem with installations through RDP before and it would be great to get some documentation or a statement from Microsoft stating there are is a registry difference between the two install methods.

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
3,227 questions
No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Leon Laude 85,136 Reputation points

    Hi @Viktor Backan ,

    Aside from security there's no difference really, RDP can cause higher security risks instead of being locally logged on, but logging on via the Hyper-V console also does have its risks, unless the infrastructure is well designed and has its security very tighten.


    If the reply was helpful please don't forget to upvote and/or accept as answer, thank you!

    Best regards,

  2. Jenny Yan-MSFT 9,216 Reputation points


    Some considerations should be paid attention to when installing the app on an RD Session Host server like: application compatibility and dependencies, capacity and Licensing related requirements and so on.

    Basically when trying to install the app on the remote session host server, we shall use change user /install command to allow each user has a unique copy of the .ini files for an application.
    This prevents instances where different users might have incompatible application configurations. The installation related the registry key files will be shadowed to Terminal server path as explained below and copied to users' home directory.

    When the system is running change user /install, several things occur. All registry entries that are created are shadowed under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Currentversion\Terminal Server\Install, in either the \SOFTWARE subkey or the \MACHINE subkey. Subkeys added to HKEY_CURRENT_USER are copied under the \SOFTWARE subkey, and subkeys added to HKEY_LOCAL_MACHINE are copied under the \MACHINE subkey. If the application queries the Windows directory by using system calls, such as GetWindowsdirectory, the rd Session Host server returns the systemroot directory. If any .ini file entries are added by using system calls, such as WritePrivateProfileString, they are added to the .ini files under the systemroot directory.

    When the system returns to change user /execute, and the application tries to read a registry entry under HKEY_CURRENT_USER that does not exist, Remote Desktop Services checks to see whether a copy of the key exists under the \Terminal Server\Install subkey. If it does, the subkeys are copied to the appropriate location under HKEY_CURRENT_USER. If the application tries to read from an .ini file that does not exist, Remote Desktop Services searches for that .ini file under the system root. If the .ini file is in the system root, it is copied to the \Windows subdirectory of the user's home directory. If the application queries the Windows directory, the rd Session Host server returns the \Windows subdirectory of the user's home directory.

    The "change user /install" procedure, still matters?


    Hope this helps and please help to accept as Answer if the response is useful.