Bodog (WGS)

Some Lessons Learnt From Setting Up Whs On A Win8 Pc

2 posts in this topic

I hate to think how long since it's been since I last posted - but I've been a constant WHS user since near the beginning


I finally took the plunge and replaced my faithful 5 year old Win7 notebook with a new Win8 unit. I know I'm late to the party but my Win7 was working just fine. Only thing that prompted the move was my old notebook's HDD was making some scary sounds and the keyboard was basically worn out!


Of course that meant setting up the Connector on it to connect to my WHS - relatively easy you would think...


Couple of lessons learnt which I will share here in the hope it helps others, the may well be already well documented but just in case


1. Make sure the location and data and time are correct on the new client - if not you will struggle to get the Connector to find the WHS


2, If you get the Passwords don't match error (and they actually do) - check out this article - this issue had me stumped for a while


I haven't spent anytime on it but has anyone figured out how to use the "Microsoft Account login" as opposed to a local login - when I try that I get the Passwords don't match error (because they actually don't) - is there any work around or do I need to take the plunge and change one of those passwords so they match. I'm guessing I do as it's probably the only way to get access to my personal share on the WHS


Now it's working well and I'm impressed that WHS which is based on Windows Server 2003 is working fine with a client OS from 2012.


I don't think I will ever bother moving to WHS 2011 - by the time I need to move on I guess it will all be held in the "cloud"

Share this post

Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

Good to hear from you. It definitely has been a while!


Enjoying Windows 8? If not, check out Start8 from starDock. :)


And that's some good info.

As for WHS2011... Skip to 2012 Essentials. It's a bit expensive... but I find it works even better than WHS2011. :)


As for the Cloud... I hate that word. It's a marketing term, or buzzword. Somebody is running physical hardware somewhere (in a large data center). And the implication is that anything in the "Cloud" is always safe, always accessible, and always *yours*. None of those may be true. :(

Share this post

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

Upgrade to a WGS Supporter Account to remove this ad.

  • Posts

    • Hopefully I have enough clues below for someone to help me figure out how to troubleshoot this. I am no longer able to log in to my WhS 2011 Server via the Dashboard on either of my two clients. I get this Windows error: Remote Desktop can't connect to the remote computer for one of these reasons:
      1) Remote access to the server is not enabled
      2) The remote computer is turned off
      3) The remote computer is not available on the network However, I can access the Server's shared folders from either client, and I can remote login to the server from either client. When I remote login, I can start the WHS desktop via the Dashboard app there. I just can't login from either of the client Dashboards. Any ideas what could be causing this?  
    • Put a remote/ after the URL to your box and it should work, for some reason it doesn't want to work like 2012r2 did. My issue is I can't find anything to say look at the UPnP stuff as that seems to have been removed on my upgrade ..
    • The Client Backups appear to work and be recognised when I upgraded, however there are various things that don't seem to have worked properly like VPN Access etc. I had to reinstall Essentials and then I ended up copying the Client Computer backups into the right folder as the reinstall decided to put them on a different drive.
    • Yes I had the same issue, add /remote to it no need to map necessarily.  Has UPnP configuration disappeared from anybody else's Anywhere Access configuration?
    • It would appear that they had put the 2012 R2 key on the evaluation site initially, this has now been corrected, key is NCPR7-********************************-3PF6X
  • Popular Contributors

    Nobody has received reputation this week.