Jump to content
2 minutes ago, wkdpaul said:

do you mean "enable" instead of hack???

my understanding is home edition has the RDP client software but does not have the actual RDP server software. Im guessing the hack would be to install RDP server on home edition by copying it from win pro or server. I wouldn't be bothered coz there are free alternatives. If I'm wrong and the home edition does have the server software and it only needs to be enabled; I do know for sure the home edition license does not have the "bits" required to use server components. You're a staffer so its up to you how far we can go into this discussion in breaking MS license terms.

             ☼

ψ ︿_____︿_ψ_   

Link to post
Share on other sites

1 minute ago, SCHISCHKA said:

my understanding is home edition has the RDP client software but does not have the actual RDP server software. Im guessing the hack would be to install RDP server on home edition by copying it from win pro or server. I wouldn't be bothered coz there are free alternatives. If I'm wrong and the home edition does have the server software and it only needs to be enabled; I do know for sure the home edition license does not have the "bits" required to use server components. You're a staffer so its up to you how far we can go into this discussion in breaking MS license terms.

That's why I asked if he meant "enable", since doing that isn't hacking the RDP the Home version has but rather "extends" the fonctionalities.

 

There's the RDP wrapper project that does just that, and since it doesn't touch the Home RDP dlls it's not really a hack :P

 

If you need help with your forum account, please use the Forum Support form !

Link to post
Share on other sites

14 minutes ago, wkdpaul said:

That's why I asked if he meant "enable", since doing that isn't hacking the RDP the Home version has but rather "extends" the fonctionalities.

 

There's the RDP wrapper project that does just that, and since it doesn't touch the Home RDP dlls it's not really a hack :P

 

the RDP wrapper is working around windows firewall and is using terminal services components. I'm telling you this is against home edition licensing. Because I'm not charging you for this advice this is as far as I will go:

https://www.microsoft.com/en-us/Useterms/Retail/Windows/10/UseTerms_Retail_Windows_10_English.htm

 

Quote

c.      Restrictions. The manufacturer or installer and Microsoft reserve all rights (such as rights under intellectual property laws) not expressly granted in this agreement. For example, this license does not give you any right to, and you may not:

(i)      use or virtualize features of the software separately;

(ii)     publish, copy (other than the permitted backup copy), rent, lease, or lend the software;

(iii)    transfer the software (except as permitted by this agreement);

(iv)    work around any technical restrictions or limitations in the software;

(v)     use the software as server software, for commercial hosting, make the software available for simultaneous use by multiple users over a network, install the software on a server and allow users to access it remotely, or install the software on a device for use only by remote users;

(vi)    reverse engineer, decompile, or disassemble the software, or attempt to do so, except and only to the extent that the foregoing restriction is permitted by applicable law or by licensing terms governing the use of open-source components that may be included with the software; and

(vii)   when using Internet-based features you may not use those features in any way that could interfere with anyone else’s use of them, or to try to gain access to or use any service, data, account, or network, in an unauthorized manner.

Windows 10 home edition has RDP server hosting disabled and if you want to run a remote session you need to use VNC or team viewer, and only a single user (you) can access the machine remotely unless it is for maintenance or technical assistance.

             ☼

ψ ︿_____︿_ψ_   

Link to post
Share on other sites

So looks like a bigger can of worms than I would like but essentially, I have heard of software like TighVNS, Team Viewer etc... I like the security protocols form Windows native RDP and wanted to see if there was a way to either 1. enable RDP or 2. run a work around so that I can RDP into the machine without having to log in first and get the service started. In normal RDP, I an send a remote signal through the LAN, then RDP in. 

 

And are these services like TightVNC trusted. Not sure what is happening in the background. I want to RDP in and wanted something trusted and will run Win 10 instead of Pro.

 

Any ideas?

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×