Remove RDP Client (mstsc)

[bseklecki_ge]

Is there not a graceful mechanism (disable optional feature, etc.) to remove mstsc.{exe,dll}?

(Pragmatically, I suppose Application Whitelisting is the best approach here.)

Thanks ~BAS

 

[garlin]

Doesn't removing Remote Desktop Client work for you?

<c>rdpclient 'Remote Desktop Client'</c>
<c>rdpclient32 'Remote Desktop Client - 32 bit'</c>
<c>rdpserver 'Remote Desktop Server'</c>
<c>rdpserverlic 'Remote Desktop Licensing'</c>

 

[bseklecki_ge]

I must be not sleeping again; not sure how I missed that. Thanks. ~BAS

 

[bseklecki_ge]

Without disclosing any of the secret sauce recipes inside NTLite: There isn't a native Microsoft framework/function to accomplish this, correct? This hook is simply removing files and registries?

 

[garlin]

There's tools for unhiding components in the registry, then you use DISM. The secret sauce is fixing all the glitches.

 

[bseklecki_ge]

I'll experiment with this tweak now. Of course, I'll be keen to learn if there is any way to easily re-add the client back in for a select number of hosts >:}

 

[garlin]

The normal answer is to use DISM /RestoreHealth against a source folder IDENTICAL to your installed image, but having the missing features not removed. This is the same idea as running sfc /scannow for repairs, but using a different WinSxS source.

A real danger is when you don't exactly match the same components, DISM will unintentionally add/change other files during the "repair".
Normal users don't have this problem because they always use the factory ISO.

I would clone a target machine, and first experiment on a non-production host.

 

[bseklecki_ge]

Follow-up question:

For component removal tweak:
<c>rdpserver 'Remote Desktop Server'</c>

...To hotfix repair this on an image (without reinstall) that was accidentally built with this (windows 10 EntIOT LTSC 2021 / 21H2), is that simply a matter of placing [ termsrv.dll ] from a generic/unmodified OEM image into place on the machine in question?

 

[garlin]

Lol no. Then we wouldn't need those hack scripts to install RDP on Home Edition. There's a ton of missing reg keys.

For a live environment, repair install with a non-stripped image is the best answer. The problem is creating a new image which duplicates the production install version, so you don't introduce random side effects because the updated files don't match.

DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim

PS - As always test on a non-production box first.

 

[bseklecki_ge]

FYI just for the record of the forum archives; as far as restoring RDP Server, it was more than just <c>rdpserver</c>

-----------------------------------------------------------

It was more than just:

<c>rdpserver 'Remote Desktop Server'</c>

It was one of the additional associated sub-entries:

<c>driver_termkbd.inf</c>
<c>driver_termmou.inf</c>
<c>driver_ts_generic.inf</c>
<c>driver_tsgenericusbdriver.inf</c>
<c>driver_tsprint.inf</c>
<c>driver_tsusbhubfilter.inf</c>
<c>driver_rdpbus.inf</c>
<c>remoteportredirector 'Remote Desktop Services Port Redirector'</c>
<c>rdpserverlic 'Remote Desktop Licensing'</c>
<c>remotefx</c>
<c>driver_wsynth3dvsc.inf</c>
<c>driver_rdvgwddmdx11.inf</c>


I'm not certain which; I'm checking now.

But for sure, air gapped environments like OT/ICS can remote:

<c>remoteassistance 'Remote Assistance'</c>