• Announcements

    • Terry (WGS)

      WGS Forums Will Close on January 31st 2017   01/18/17

      Hi everyone, We're coming up to We Got Served's ten year anniversary and I've been taking a good look at the site to work through some plans for the future. I wanted to give you all a couple of weeks notice that I'll be closing WGS Forums at the end of this month.  As you'll be aware, the forums were opened to support Windows Home Server users and have done so brilliantly, thanks to everyone's participation. However, with each day that passes, there are fewer and fewer WHS deployments out there, meaning that forum registrations and traffic has now dwindled. I've tried a few times over the years to test some forums on related or adjacent topics, however, they simply haven't caught on. It's clear that these were always going to be predominately Windows Home Server forums and, with the passing of that platform, they've served their purpose well. So, please take some time to archive anything you need over the next two weeks. Access to the forums will end on Jan 31st 2017. Many, many thanks once again for your participation and support here. It's been a great community! Very best wishes Terry
Sign in to follow this  
Followers 0
mncasper78

Remote Access To Home Premium Hack

1 post in this topic

I thought I was upto the challenge of configuring things so I can remote access my Win7 Home Premium from WHS. Yes I know that Home does not have RDP, but that is easily resolved with this http://thegreenbutto...ms/t/79427.aspx. I am able to remote into my PC without issue from Win7 and XP PC's once I ran that. So that is working.

Next step is to trick WHS (SP2) to thinking that the PC is capable of RDP. Through some troubleshooting I was able to figure out that if I change the registry entry below WHS thinks it is capable. Granted this gets refreshed often a simple scheduled batch file will keep that setting.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Transport\Clients\the client entry----->from there I edit the TerminalServicesSupport key to "DS" versus "OS"

So now WHS shows that my PC is capable, but is states "Connection disabled"

One thing that I researched was if my RDP was configured correctly in the Home Premium PC. With this article, http://www.technize....-and-windows-7/ I confirmed my settings are correct. Additionally considering I am remote into it from both XP and Win7 this should be set correctly.

So this is where I am stuck and since I have commited myself to this hack I have to finish it. By all mean the time I have invested will far outway the $100 upgrade to Pro, but that is not why we do stuff like this.

Any suggestions?

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

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
Sign in to follow this  
Followers 0



Upgrade to a WGS Supporter Account to remove this ad.



  • Posts

    • Hi - I'm now on Lights-Out 2, but the problem persists. Today 3 client computers suddenly shut down after a Lights-Out backup, whilst they were in use (but the users were away from the keyboard so never saw the warning message). All 3 computers had missed their previous backup (scheduled during Friday night). The 3 computers were automatically backed up during the day today, Monday (their next scheduled backup was set for Monday night). At the end of the backup they shut down & the users lost work. I'm trying to create a situation where... Each evening, the client computers are put to Sleep. During the night, the server wakes up the clients in turn, runs a Lights-Out backup, then shuts down the clients. When all the backups are done, Lights-Out puts the server to Sleep. In the morning the clients are re-started, the server wakes up, and the day begins as normal (I like the idea of the clients being restarted regularly). If one of the client computers can't be woken up during the night (the user had accidentally shut it down at the end of the day, or took it home with them), I don't mind what happens next: either a 'normal' Windows server backup during the day; or nothing happens until the next scheduled night-time backup. But these unexpected daytime shutdowns are making me increasingly unpopular - is there any way to avoid them during the daytime when everyone is trying to work normally? many thanks, Simon
    • Please contact support@green-it-software.com and I can send you a copy.
    • Hi, I am looking for these drivers HpMssServiceSetup_v1.0.6 but the dowmload link is dead. Does anyone have a working link please. Thank you.
    • That guide is for installing Exchange on a Server Essentials network, not necessarily installing both services on the same server, which isn't a good idea at all to do (as SBS with Exchange 2007/2010 was a good example of how poorly both AD and Exchange run when both are on the same server), nor is it supported by Microsoft.  Exchange 2016 initially had compatibility issues when installed on Server 2016 until Microsoft's server team came up with KB3206632 and the Exchange team released December 2016's quarterly update (CU3 or 4). Your IIS Reverse proxy will only (currently) be supported on Windows Server 2012/R2, as you've no doubt discovered, the Application Request Routing version and update only support 2012/R2. I know it works for 2012 R2 because I'm running Exchange 2016 CU4 on Server 2012 R2 on my domain that also includes a Server Standard with Essentials Role installed (5 VMs:  2 Domain Controllers, Exchange 2016 CU4, Server Essentials and a Reverse Proxy server all running 2012 R2 using ARR 2.5 -- the ARR Reverse Proxy allows me to share Exchange, Essentials RWA and my QNAP on 443), but thus far, I haven't seen anything for Windows Server 2016.  ARR 3.0 might work with Server 2016, or your other alternative is to deploy another server running 2012/R2 and use ARR 2.5.
  • Popular Contributors