Hi there
Trying to install programs while connected via RDP (the normal way of accessing your HYPER-V VM remotely).
Cannot install programs.
This seems a bit daft - I can't always be at the console of the HOST machine - I usually access VM's remotely anyway.
cheers
jimbo
The fact that there's an error message displayed saying it's not permitted says this was done on purpose as opposed to it being simply a bug. I wonder what the reasoning would be to prevent installing via RDP?
Hi there
Got round the problem
Mapped the tsclient and then connected that as a Network drive --then it worked.
(Testing with a small install before I try Office / photoshop etc). I certainly don't want to COPY all to local drives so I'm glad the tsclient trick worked).
Cheers
jimbo
Last edited by jimbo45; 08 Oct 2014 at 08:06.
EDIT: Seems you solved it while I was composing this post.
Jimbo, reading that screenshot "between the lines" (if that's possible when we talk about an image :)), it looks like you are trying to install a program on your Guest (RDP host) using installer on your host (RDP client). If that's true, have you tried to copy the installer to RDP host and install from there?
Kari
Hi there
Yes - as above -- map the TSCLIENT drive as a network drive. Obviously I didn't want to copy programs to local drives before install -- that would make it horrible (and wasteful) if I have several machines.
I don't think the RDP error though is a specific W10 error - I remember something like that on earlier releases.
Cheers
jimbo.
It has to do with elevation / UAC. This article does not describe your now solved issue per se but points to right direction: A Black Screen Appears During a Remote Assistance Session in Windows 7
I think that error message is poorly worded. I think what it means is "cannot install from a remote desktop connection *folder*" RDP's tsclient file redirection is a bit goofy and doesn't fully support all filesystem functions (basically, it has to copy the file to a local temp folder first then do operations locally).
You have to copy the installer file to the machine you want to install it with. Then delete the installer after. It happens mostly when the installer file has to be decompressed first before the installation itself.
Quote