RDP client in WIN10XPE?

hi,
First, i'm not sure to understand very well. So, If you think I don't understand, i beg your pardon.

a - From a windows10 to winpe :
On the picture mstscToWinpe.png, you can see my two physical screens side by side ( print screen ).
On the right side, i make a RDP connection to "pc-p702" computer ( windows 10, only to have a remote computer).
In this "pc-p702" computer, i launch a VM hyperV : winpeFlat1803EN.
This VM starts on the "system" session and its IP is 192.168.0.11
On the left side, i launch "Mstsc" and i connect to 192.168.0.11 with "administrator" and the password i created when VM boots.
And YES, i can use the two sessions ( system and administrator) from two computers ( mine and pc-pc702) at the same time !
RDP to Winpe use "TermialService" which is a little more complexe to get.

b - from winpe to a windows 10
Please see picture "MstscNLA5.png"
Using RDP from Winpe use NLA and there is a change in keys registry since V1703 ( as i note in my pdf ).
i try today for a verification. And in my winpe it is the console logon screen that is displayed. I enter my password, hit the "tab" touch and use cursor to "OK". So, I can connect but i prefere the GUI screen. I search 5 minutes and find that i forgot today "the key minint". After rename it, i can see the GUI and connect to my computer under windows 10.
NLA in winpe seems to me not too complex. I play last year with a connection using the "RD gateway Server" parameters from winpe to a vm in the cloud.

I'm too lazy to translate my script to a pluggin. It's true i don't like the "language" of pluggin.
But if someone want to do...i can help a bit.

PS : I don't remember if i update my microWinpeBuilder with V1803 on this site

hi,
@teik: I atached a script that is based on the first version, that corrected the Shortcut problem (tested), so that should work for you.
RDP Script is ment for client only, server is not implemented for SPE by that.

@noelBöanc: Sorry, but I think I don't understand your post completely. What is your intention?
For NLA, I plan to work on this topic, but not at the very moment.
I need a solution for many problems with my PE and at the moment, I use "wFreeRDP.exe" for NLA connection.
I think I understand you have NLA working on yout build with native "mstsc.exe".
If you want, you can share the interesting parts of your changes.

Regards

Test Plugin with ONLY "Network" selected on Build Core
To help find dependences

Hi,
I checked out a fresh copy of 10xpe, tested "RDP_XPEv3.script", with 10, 1809, amd64, deselected many default plugins (7Zip,....), see attached image.

Regards

 

Hi,
I checked out a fresh copy of 10xpe, tested "RDP_XPEv3.script", with 10, 1809, amd64, deselected many default plugins (7Zip,....), see attached image.

Regards

 

I just tried it too and now it works the direct access in the menu and the connection without problems.

- Regarding how to connect as a server, that is, that you can connect from another computer to this, is it possible?

Greetings and thanks for the changes and your work.

@ teik and @ Someone

I have sent you both via PM a Test "RemoteDesktopConnectionSecure_XPE.script with Date 2018.11.11

Teik has tested and reported as working with just "Network" and "PENetwork" - as only options..
he also stated he tested again with all his default plugins...

Teik asked that the option to Save or use a custom Default.rdp (I assume his custom Configuration File)
Which is Feasible and can be done with plugin

Also the Auto Connect feature has the have Network started first.
Which may not be the case with teik's testing report
Starting the Auto connect at a later time to allow network to start first is also feasible..

I am just trying to expand upon the work in progress here...

I do not use RDC - so your testing is helpful...

Also I do not want to get Chastised for Trying to Help or for uploading "TEST" plugins to the forum topic

I am glad that development can be followed among all. There are certain topics that my help is little, but I am always there to help in what I know. In the end you end up learning a lot from the bigger ones and especially when analyzing the code of the script.

Thank you both for making this Win10XPE project more and more versatile and big.

well, good I'll sent you another TEST for auto connect

in my winpe it is the console logon screen that is displayed. I enter my password, hit the "tab" touch and use cursor to "OK". So, I can connect but i prefere the GUI screen. I search 5 minutes and find that i forgot today "the key minint". After rename it, i can see the GUI and connect to my computer under windows 10.

Thanks Noel, works well to get the Credentials GUI
I implemented it with a batch:
It rename the MiniNT key before calling mstsc.exe.
The MiniNT key is then restored when Remote Desktop Connexion is closed 

Code: [Select]

@Echo OFF
Title Launch Remote Desktop
mode con: cols=60 lines=15
Color 30
 
Echo Launch Remote Desktop With Credential Window
Echo       (Instead of the Console Mode)
Echo.
Echo The MiniNT Control Key is Renamed for this.
Echo.
Echo This Window will be Closed and the MiniNT Key Restored 
Echo Once the Remote Desktop Connection is Closed.
Echo.

Reg Copy HKLM\SYSTEM\CurrentControlSet\Control\MiniNT HKLM\SYSTEM\CurrentControlSet\Control\MiniNT_Sav /f >nul
Reg Delete HKLM\SYSTEM\CurrentControlSet\Control\MiniNT /f >nul
Start /WAIT %WinDir%\System32\mstsc.exe
Reg Copy HKLM\SYSTEM\CurrentControlSet\Control\MiniNT_Sav HKLM\SYSTEM\CurrentControlSet\Control\MiniNT /f >nul
Reg Delete HKLM\SYSTEM\CurrentControlSet\Control\MiniNT_Sav /f >nul
Exit

Here is the result in a screenshot (Multiple layers assembled)



In addition to mstsc.cmd launcher, I reviewed a bit the dependencies
 RemoteDesktop_XPE.script (39.77 kB - downloaded 84 times.)

I don't really use Remote Desktop. I'm just trying it here
So it would be nice to have other feedbacks, failure or success.

I prefer patch the Windows.UI.CredDialogController.dll directly on building.   
Using Credentials GUI not only for the RemoteDesktop, but access share folders.

That's why I stop develop WinXShell.exe's UI_Credentials.

Remote Desktop\main.bat:
rem ==========update filesystem==========
call AddFiles %0 :end_files
goto :end_files

@\Windows\System32\
+mui
cngcredui.dll,CredentialUIBroker.exe,credssp.dll,credui.dll,cryptui.dll
d2d1.dll,d3d10warp.dll,d3d11.dll,dcomp.dll,DWrite.dll,dxgi.dll
msacm32.dll,msacm32.drv,mstsc.exe,mstscax.dll
ncryptprov.dll,ncryptsslp.dll,pdh.dll,TSpkg.dll
Windows.Globalization.dll,Windows.Graphics.dll
Windows.Internal.UI.Logon.ProxyStub.dll
Windows.UI.Cred.dll,Windows.UI.CredDialogController.dll
Windows.UI.Xaml.Resources.Common.dll
wuceffects.dll
\Windows\SystemResources\Windows.UI.Cred
bdeunlock.exe,fvenotify.exe

;SystemPropertiesRemote
racpldlg.dll,remotepg.dll,srrstr.dll,SystemPropertiesRemote.exe

:end_files

rem ==========update registry==========

if not "x%opt[build.registry.software]%"=="xfull" (
  call RegCopy "HKLM\Software\Microsoft\Terminal Server Client"
  call RegCopy HKLM\System\ControlSet001\Control\Lsa
  call RegCopy HKLM\System\ControlSet001\Control\SecurityProviders
)

reg add HKLM\Tmp_System\ControlSet001\Control\Lsa /v LimitBlankPasswordUse /t REG_DWORD /d 0 /f
reg add HKLM\Tmp_System\ControlSet001\Control\Lsa /v LmCompatibilityLevel /t REG_DWORD /d 2 /f
reg add HKLM\Tmp_System\ControlSet001\Control\Lsa /v "Security Packages" /t REG_MULTI_SZ /d tspkg /f

reg add HKLM\Tmp_System\ControlSet001\Control\Lsa\OSConfig /v "Security Packages" /t REG_MULTI_SZ /d kerberos\0msv1_0\0tspkg\0pku2u\0livessp\0wdigest\0schannel /f
reg add "HKLM\Tmp_System\ControlSet001\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f

rem COPY from EXPLORER\main.bat
rem Patch Windows.UI.CredDialogController.dll to use the Credentials Window than Credentials  Console
rem M.i.n.i.N.T => N.i.n.i.N.T
ren %X_SYS%\Windows.UI.CredDialogController.dll Windows.UI.CredDialogController_org.dll
binmay.exe -i "%X_SYS%\Windows.UI.CredDialogController_org.dll" -o "%X_SYS%\Windows.UI.CredDialogController.dll" -s "5C004D0069006E0069004E0054000000" -r "5C004E0069006E0069004E0054000000"
fc /b "%X_SYS%\Windows.UI.CredDialogController_org.dll" "%X_SYS%\Windows.UI.CredDialogController.dll"

I was actually getting ready to ask either you or noel once I saw what needed to be done in Chris's post...

thanks slore, chris, and noel   

Good Things Come when we all work together...

  almost forgot, thanks to you too james.. 

Yes, amazing things are possible when we all work together.. and I am so very grateful that we all are..

This time slore makes the rest of us all look tiny with his fix   

RDC plugin updated on SE project servers with slores fix.  As stated, this also works for mapping network drives.

These are the lines I used if you want to adapt them to XPE instead of downloading SE for them or rewriting it all..  Attach binmay.exe from slores post above in Folder

Code: [Select]

If,%TC_Win10_v1709%,Equal,Bigger,Begin
  ExtractFile,%ScriptFile%,Folder,binmay.exe,%Tools%
  FileRename,%Target_Sys%\Windows.UI.CredDialogController.dll,%Target_Sys%\Windows.UI.CredDialogController_org.dll
  ShellExecute,Hide,%Tools%\binmay.exe,"-i #$q%Target_Sys%\Windows.UI.CredDialogController_org.dll#$q -o #$q%Target_Sys%\Windows.UI.CredDialogController.dll#$q -s #$q5C004D0069006E0069004E0054000000#$q -r #$q5C004E0069006E0069004E0054000000#$q"
  FileDelete,%Tools%,binmay.exe
  FileDelete,%Target_Sys%\Windows.UI.CredDialogController_org.dll
End

I will defer to Chris's choice of the process to use in XPE project..

bob.omb
I think it should be a standalone optional plugin like "Use  Credentials GUI(by patch Windows.UI.CredDialogController.dll)" in tweak or build core option.

It is out of RDP box.
people should have right to choose which way they want like Chris's cmd option.

2 comment for it:
keep org.dll for in case bad effect. it is small.
binmay is x86 command, cant work in pure x64 PE for building, need other tools for publish plugin.

james
MiniNT key is global, be checked by many exes, dlls.
Chris's cmd may cause unexpected result for other features when you using mstsc.exe.
Choice is free, and it is on your hands.

I would like it in build core, but the changed file is only provided in SE in the RDC plugin.  It is not present otherwise.  Maybe I will move the option to the Finals>Optimizations section, and as an optional checkbox (enabled by default) using If,ExistFile if the file is present it will edit.

No issues here for x64 but I am using Wow64 plugin..  All changes made in System32..  (I think you mean if I am using a pure x64 host to build it will not work)

well, here is a matter you guys should consider.

Network Level Authentication of RDP works by SYSTEM account with Credentials Console, not the notice as WIN10XPE's RDP plugin said requires Administrator Account .

Access share folders or mstsc.exe work by Credentials Console in SYSTEM account.
rename MiniNT key or use patched.dll make it force to use Credentials GUI, got error with missing files.

Enable "Switch to Admin" option, the Credentials GUI will work for both SYSTEM/Administrator account.

So, the "Credentials GUI" plugin/option needs go with "Switch to Admin" plugin, or add the required files/registy items(which included in Swith To Admin plugin).

james
MiniNT key is global, be checked by many exes, dlls.
Chris's cmd may cause unexpected result for other features when you using mstsc.exe.
Choice is free, and it is on your hands.

@Slore
On this topic
I'll Take the backseat and Let You Drive..
Others will have to take Shotgun..
As I am just along for the ride..

On my personal builds I use SwitchtoAdmin and use RunAsSystem context entries for nsudo...  As system, there are things you cannot do... As admin you can do everything because you can "RunAsSystem" either with a right click or by creating a shortcut... including for cmd.exe and anything else..

No need whatsoever to boot into system... but every once in a while there is a need for admin.  I dont understand why people still use system.. They are only limiting themselves..

Admin = Admin+System both possible
System = System possible only