Connector Software Server Not Found When Using Vista

When installing the Windows Home Server connector software the server may not be found. This may be because you are running as a restricted Vista user and if this is the case you will need to install the connector software as “Administrator”. The step by step instructions are on Tranquil PC’s Weblog.

connect-run-admin

69.png

AddThis Social Bookmark Button

Virtual Windows Home Server

If you are like me and enjoy testing the different features of Windows Home Server and all the different add-ins available for it then it is a good idea to set up another copy of WHS in a testing environment.

One way of doing this is within a virtual machine that allows you to install a complete copy plus applications into a virtual (emulated) computer, complete with BIOS and hardware configuration options.

This way you can create a custom test environment that can be rebuilt at any time, and can easily be restored to previous states without going through a full installation of Home Server.

For full details on how to accomplice this the website I Hate Linux has the walk through using the free Microsoft Virtual PC software.

69.png

AddThis Social Bookmark Button

November Update – Your Network Health Icon Will Turn Red.

After installing the new November update for Windows Home Server you will notice that your network health icon will turn red. With this update, you can now get a trusted SSL certificate for your <your_name>.HomeServer.com domain name.  If you have already set up remote access via the console, settings screen, you will need to quickly unconfigure your existing sub-domain name and re-run Setup to acquire an SSL certificate for your HomeServer.com domain name.

For more details on how to accomplish this, see the following post at the official Windows Home Server Blog.

69.png

AddThis Social Bookmark Button

Microsoft’s Troubleshooting Tips

We have the following troubleshooting tips for help during setup of Windows Home Server, courtesy of the Windows Home Server sub-pages over at Microsoft.

Troubleshooting tips

Having problems setting up Windows Home Server? Ensure that you’ve taken these simple steps:

  • Plug in and power on your home server.

  • Connect your home server with a wired network connection to your broadband router or to a switch that is connected to your broadband router.

If you’ve encountered issues while setting up your home computers with the Windows Home Server Connector software, run through this quick checklist:

  • Connect your home computer to your home network (using either a wired or a wireless connection), and make sure the home computer is on the same logical network as Windows Home Server.

  • Make sure firewall software on your home computer is not blocking access to Windows Home Server.

  • If your computer has been joined to a corporate network (such as a corporate laptop), check with the corporate network administrator about the IPsec policy. This may block access from the corporate computer to Windows Home Server.

69.png

AddThis Social Bookmark Button

Installing the Connector Software on Vista x64

Microsoft are currently internally testing an x64 Connector for Windows Vista Machines, which should be available between December 07 – March 08. Unfortunately a Connector for XP x64 will not be available, but what can you do in the meantime if you want to install the Connector software on your Vista x64 machine. Well, good news, we have a solution for you.

You can easily install the Windows Home Server Connector software on Vista x64 by running the following in an elevated command prompt (Start > All Programs > Accessories and then right-click on “Command Prompt” and select “Run as administrator”) in Windows Vista.

msiexec /i "\\SERVER\Software\Home Server Connector Software\whsconnector.msi" WHSMSI="RUNSETUP"

It will then install the connector software fine on that Vista x64 machine without running the SETUP.EXE bootstrap. Backups won’t work, but everything else will on that machine, so just disable backups for that machine in the console once it’s installed.

Thanks to Jerry Zeisler for bringing our coding mistake to our attention, which has now been corrected.

69.png

AddThis Social Bookmark Button

Stop False Password Nags from the WHS Client

If you have installed Windows Home Server and previously had RC1 installed, or another machine on your network had the same name you are now using for WHS, chances are you might run into the situation where the WHS connector software on the client machine is always telling you that you need to “Update Your Password”.  Well, you will soon find out that no matter how many times you update it, the message never goes away.  It’s frustrating to say the least, and even when WHS says your password is out of sync with the server, you’ll find you can still access your shares and take backups.

The problem stems from the fact that on at least XP and Vista, Windows will store your credentials.  So if before you installed WHS you had another server on your network called “SERVER” then WHS gets confused about the old credentials being stored and no amount of updating your password seems to work.
If you run into this problem, on the client machine giving you problems go to your Start > Run window and type in:

rundll32.exe keymgr.dll, KRShowKeyMgr

Stored_Passwords

This will bring up the stored credentials dialog.  Find your WHS name, highlight it and hit remove.  Logout of the client machine and then log back in.  WHS may ask you to update your password one last time.  Go head and do it and now you should notice that the WHS connector client stops falsely informing you that your passwords don’t match.

Guest Writer
Robert Stinnett
www.robertstinnett.com

UPDATE by Philip Churchill – The above did not work for me until I done the following:

————————————————————————————————–
To finish, update your user password one final time through the WHS client:

Log on to the Windows Home Server Console
Click User Accounts
Right click the user and click change password
Type your password twice, even if its the same one!
Click ok

————————————————————————————————–

Some have also had success with the following as well, but only use as a last resort.
On the Client computer go to:
XP: C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys
Vista: C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys AND C:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys
and see that the FOLDER AND ALL FILES in it have Full permissions for the Administrators GROUP and SYSTEM account.

AddThis Social Bookmark Button

WHS Version Information 1500.0 or 1500.6 – We have the Answer

I posed a question to you readers a couple of days ago regarding the version information displayed on the Resources tab within the console.

My clean OEM install after Windows Update showed the following:

myversion

Whilst my friends server and others from the WHS forums were showing:

othersversion

As you can see my “Windows Home Server Backup & Restore” was the only item which was updated to version 6.0.1500.6 whilst the bottom screen shot shows all components updated to the latest version.

Why? Well, I have the answer for you. I had an anonymous email from a reader stating that my version number of 1500.6 on only the backup component is the correct behavior for an RTM system upgraded via Windows Update. And systems that have all versions showing as 1500.6 are installs built from a “second edition” of WHS that has incorporated the update 941913 from Microsoft.

So all new RTM media from the last few weeks have the Windows Update download incorporated into the CD/DVD media. Tom from Ramblings Of a Home Server User also confirmed this, explaining that a newer version of Windows Home Server was released, known as a Media Refresh.

So, rest assured, in both instances both system are upgraded as expected.

69.png

AddThis Social Bookmark Button