I have been told if you are booting WINPE 64-bit or UEFI that remote control does not work.
I have tested this using a dell 5470, HP X2 tablet, and a Microsoft Surface.
If I have the Dell 5470 and X2 in full UEFI mode, no legacy, you can not remote control the device in the WINPE environment.
If you set the 5470 and X2 where legacy options are enabled and boot BIOS mode, you can remote control in WINPE.
The Microsoft Surface devices are UEFI only, no legacy options, I have yet to be able to remote into the WINPE environment on them.
I have tested this using both PXE boot from the network and booting from USB Media. If you have a Fat32 (GPT) UEFI boot media, no remote control. If you create a NTFS (MBR) BIOS boot media, remote control works.
Maybe this will get fixed in a future update.
We are running 2016.3 with the latest SU patch installed.
I did, see that Kenyon, but am unable to locate the ldvpe1.img file anywhere (even in the installation media).
It appears the biggest obstacle I'm facing now, even in Legacy WinPE (32bit) is that issuser.exe won't start as a service. Issuser.exe is located in the cba8 folder (got it from the original boot.wim). Are there any registry keys I need to add other than what's in the All.Reg that pertains to issuser.exe?
Did you copy the whole CBA8 and LDCLient directories from the boot.wim into your own WinPE? And start the service than with Net Start ISSUSER?
frank.wils, I have copied the directories from the original boot.wim into our own boot.wim (created in MDT 2013). I used the startnet.cmd file from the boot.wim and still I get the error "The service name is invalid. More help is available by typing NET HELPMSG 2185."
At this point, I may just try UVNC as we need a single solution that works across both architectures (x32 and x64). Based on my research and the article Eric provided (thanks by the way EXiang, it doesn't appear LD Remote Control works in x64 (UEFI). WinPE 64bit Remote Control Agent