Remote Desktop

You can use Driver Export And then Driver integration as Kyhi noted  See the Driver integration plugin
and yes PENetwork is required for the network connection in win10pese.

The other solution is to enrich "Original NET driver" with missing Drivers from Win10 Driverstore source (Install.wim).
thus, without adding, we have all drivers from the MS Windows Setup: boot.wim + Net drivers from Install.wim + Basic display driver + Audio..
It should be enough for most cases.

As your host is Win10, look in device manager what are the driver files (Properties > Driver> detail) ?

I'm not sure if it's intentional but the RDC.script is still missing from the latest Win10PE SE release.
By the way, there was a mention of a new dependency but I used the script from Win8.1SE and it built and worked okay-ish.
By that I mean, it ran fine but refused to connect throwing an error: 0x80004005

I Google'd that error and hit the answer pretty quick:
1. Open Remote Desktop Client

2. Click "Show Options" and the "Save as"

3. Preferably save it as/replace Default.rdp (empty) profile on Documents folder

4. Close the client and edit in Notepad the profile you saved

5. Find a line that says "authentication level:i:n"
Note: The n placeholder represents the current authentication level.

6. Change the authentication level to 0 so that the line becomes: authentication level:i:0
Note: When you set the authentication level to 0, RDP does not check for server authentication.

7. Add the following line to the end of the file: enablecredsspsupport:i:0
Note: When this line is present, you do not have to provide credentials before you establish a remote desktop connection.

8. Save the profile before closing notepad and try now.

source: https://social.technet.microsoft.com/Forums/exchange/en-US/2416dd59-2410-4fee-bd14-1201fbc73204/remote-desktop-windows-7-laptop-accessing-windows-8-pc-code-0x80004005


Is the script included here the latest recommended? And if so, why not including it by default?

Cheers. 

included here the latest recommended? And if so, why not including it by default?

It is a test plugin,
exograpix did not feedback (although active around),
 so left on topic to whoever like to test and feedback.
   and after 4 months feedback came now.

I am sure ChrisR will follow your feedback and update plugin on servers.
 Again Thanks for the hardwork and detailed guidance.
   Well written, problem solving feedbacks are the ones I like a lot. 

Yes, absolutely, I expected a user feedback. exograpix has not been until the end.
yours returns is very good, clear and detailed 

I'll add Default.rdp with  authentication level:i:0 and enablecredsspsupport:i:0 in %TargetProfilesUserDir%\Documents
and I'll put it on win10se server.

Thanks

Okay, awesome guys.
Just to be clear, I did not test the plugin from this post: http://theoven.org/index.php?topic=1361.msg15702#msg15702
Instead I used the one distributed with Win8.1SE, which I am not sure if both are the same, haven't compared.
If you guys want I can test the plugin before adding it to the distribution, to be sure everything is okay. 

By the way, I didn't quite get the problems mentioned before:

Could not load the remote desktop services activexcontrol
Make sure mstscax.dll in the path

There is a new dependency required for win10: pdh.dll

I did not have any build problems at all and the only issue was the one I mentioned about connection error 0x80004005

Forget the plugin on the previous post, pdh.dll added is already in win8.1se plugin.
I added Default.rdp with your information 

 Rdc.script (34.16 kB - downloaded 160 times.)

It should be good, If you want to do a test before putting it on SE servers.
I have no environment to easily test, my host is Win10 home edition.

I also added an Auto Connect checkBox with a server adress, from an old request.
I'm not sure it is good to put it. It needs the network to be started before (the case in win8.1SE).
And it must probably miss the authentication level and enablecredsspsupport.

Nice, thanks ChrisR! 
I'll test it later today when I get home.
About the auto-connect feature, I think it's a neat addition, I can see it being useful without having the hassle to manually include additional autorun scripts; I'll also have a go at that and see how it does.

I tested the new RDC script but unfortunately could not try the auto-connect feature. The RDC worked as expected since the new settings for Default.rdp were added, everything good on that end.
As for the auto-connect, my problem was related to getting network connection before the shell which was a total failure. I changed PENetwork autostart setting to start before the shell but then it never reached the desktop, just showed a black screen after initiating the network device, I just see the black screen and can move the mouse cursor, CTRL+ALT+DEL does nothing either. I checked my router and it attributed an IP address correctly through DHCP so it doesn't look like it's waiting for connectivity, I don't have a clue what else it could be. I also tried enabling PENetwork "Alternate autostart network method" setting, but just behaved the same way (and worse).
I'm not sure if I'm missing something to get the network starting before the shell and actually having the shell starting also afterwards, so far the shell never starts.

Hi nor0,

Good to hear rdp works fine 


shell related things are a bit complex and differ project to project.......

for years only general solution, it seems to be starting an application (so far nearly always rdp similar ones)
after network ready is using a .cmd with waiting some seconds (ex: 20 seconds)
 I guess Chris can implement such thing to rdp plugin if required.

ps: @Chris, check \Downloads\AppYGS\Network\Remote Connect\UltraVNC and VNC Real

other special ways:
 using Penetwork "after boot" setting (see PeNetwork_After.cmd on penetwork plugin)
 using .cmd with ping, google will give you a set of alternatives.


Well there can be a better, more general way, to check "network ready" so after ready wait 5 seconds and process... maybe one day...

A while I have not used Autostart PENetwork Before Shell.
It has worked before in Win7PESE. I do not know if it is always the case.

I just try, indeed, it does not work in Win10PESE.
By changing hidewait|PENetwork|xxxxx by nowait|PENetwork|xxxxx in Win10PE.cfg,
Win10SE works but PENetwork waits for explorer shell to really start the network. So, it is also After Shell.

Develop someting to wait for the network could be done.
the Network can be started aslo with Pecmd and with something like this.

Code: [Select]

_SUB INIT_NETWORK

     IFEX %WinDir%\system32\schema.dat, !EXEC =!netcfg.exe -v -winpe
     EXEC =!netcfg.exe -c s -i MS_Server
     EXEC =!netcfg.exe -c p -i MS_NDISWAN
     EXEC =!netcfg.exe -c s -i MS_RASMAN
     EXEC =!netcfg.exe -c p -i MS_PPPOE
     EXEC =!netcfg.exe -c p -i MS_NDISUIO
     EXEC =!netcfg.exe -c s -i ms_nativewifip
     //Link Layer Discovery Protocal
     EXEC =!netcfg.exe -c p -i ms_lltdio
     EXEC =!netcfg.exe -c p -i ms_rspndr
     EXEC =!netcfg.exe -c p -i ms_lldp
     SERV dhcp
     
     IFEX %WinDir%\system32\schema.dat, !EXEC =!startnet.exe -wg WORKGROUP
_END

But, except very specific case, I do not think that AutoStart RDC is really useful.
It is easier for now not to use, by hiding "Auto Connect" (disabled) and "Server Adress" on interface.

Yes, I agree.
For now the auto-connect in RDC should be commented out.
In any case, if I wanted to do it anyway I would maybe use an autorun script like this:

Code: [Select]

@echo off

set ip_address=192.168.0.2
set port=3389

:loop
ping -n 1 8.8.8.8 | find "TTL=" && (
mstsc.exe /v:%ip_address%:%port% /f
goto :eof
)
goto :loop

Use PC Packed ner0, point your .cmd file

Demonstration:
Utils\PC Packed
-> click "CMD" button at right bottom
--> click "Goooo"

you will have
AppsMy\1Prepare\"Test - Me" plugin,
with "startup" option
with "Edit" button --> you can copy paste your above cmd codes...

Yes, I agree.
For now the auto-connect in RDC should be commented out.

RDC plugin is on server now.
Thanks for Default.rdp and for your testing

PC Packed "CMD" or PENetwork_After.cmd may be used to Autostart Remote Desktop Connection, if someone needs.