Am I allowed to add RDC to a WinPE boot Image?

Question

Possible Duplicate:
Can you help me with my software licensing question?

I am trying to emulate what a user has suggested here:

Use WDS to provide a WinPE image (that contains a RDC client) over PXE.

While I have a working PXE WDS Server with a WinPE Image I am not sure if this is actually allowed. I have tried to find if this is possible but so far I think it may be against the WinPE EULA to use WinPE as a RDC client. Can this be used, or would I be better adding something like a VNC client to the WinPE Image?

Solution 1

Yes and No. Yes it's possible to copy the binaries to WinPE and run the RDP Client. But WinPE is licensed only for administrative purposes. If you're using it as a thin client OS, you're in clear violation of the license.

See my answer to this related question for the list of files: Boot to Remote Desktop

Solution 2

While not directly answering your question (because I'm not sure you can make mstsc.exe work in PE), why not try to work around the problem? Like you mentioned, try VNC. I've packaged other executables in PE environments and had them work just fine. As long as you have network drivers and capability it could do the trick.

Edit: According to Microsoft, as long as the workstation/hardware you are using has its own Windows Pro license, it's ok by them. This isn't my interpretation of their EULA, this was their rep telling me this over the phone.

Solution 3

You can use free implementation of RDP client (like FreeRDP or rdesktop).

Comments

[John Gardeniers]

Your title indicates you want the PE image to be the host but the question indicates you want it to be the client. Please clarify.

[tombull89]

I wish the PE Image to contain the client, that is, Remote Desktop Connection, or mstsc.exe.

[tombull89]

@JohnGardeniers ...really? "Am I allowed to add RDC to a WinPE..." make perfect sense to me. I'm not asking "can I RDC to the WinPE enviroment", that's why I put "add" in there. You can't add it from the WinPE image, it was never there in the first place. </nitpick>

[John Gardeniers]

You're right. I've rolled it back.

[MDMarra]

Sorry to cast the last vote on this, pal. :)

[tombull89]

Oh, it's certainly possible as I've managed to get it working. I'd prefer RDC over VNC, but I may as well include both. It'll be an interesting exercise anyway.

[Ben Campbell]

Care to share how? It's not something I've ever tried... although I can come up with a few scenarios. I'm thinking what might be against the EULA is the terminal services piece. I seem to remember dealing with Microsoft and their terminal services license agreements in years past. One specific case involved thin clients and how the terminal service license cost, when added to the price of the thin client, made it harder to justify thin clients in that solution.

[Ben Campbell]

I updated my answer to include some license info from Microsoft.

[tombull89]

Thanks, Chris, I've seen there's a 24-hour-uptime period in the WinPE enviroment before it force reboots to prevent you using it as a Thin Client. In the linked question you say it can be done but I take it using WinPE for a client OS, even one WAIK-customised, is not allowed?

[Philip]

Correct, WinPE is only licensed for administrative tasks. MS wants you to buy Win Embedded or Win Thin PC if you want to create a thin client.

[tombull89]

Out of interest, do you know if Windows ThinPC can be booted purely from PXE in live format?

[Philip]

Any of the 6.1 kernels can be booted from PXE; the problem is that it all has to load into a RAM disk, which for WinTPC is a minimum of ~3.8GB