Windows Home Server Update Announcement!
Todd Headrick just posted a new blog post explaining details about a new update for Windows Home Server!
Answers
Rupio
If you want to upgrade to RTM you have two options:
1 - find a retailer with the RTM code in stock and buy it
2 - very soon you will be able to order a 120 eval copy from the MS WHS website
Andrew
All Replies
i know no one can answer this as it is all just rumors and speculation but for the interest of conversation:
since WHS was originally RTMed on 7/16 and HP was "scheduled" - unofficially that is - to ship on 9/15, could that mean that they (HP) will now ship within a time frame of 2 months? or maybe even sooner since they have just been waiting for this update, which is just that, an update, and not a whole new version that they would have to familiarize themselves with and tweak from scratch....just some ideas for thought
jpearl
Will these updates get installed on all versions of WHS (or RTM only)?
- OEMs will be able to slipstream these updates into their initial distributions. System builder purchasers, who are enthusiasts installing on their own hardware for the most part, will not be able to do this (and usually won't want to, since we're normally doing a "one off" installation). Instead, you'll receive this update as part of the initial installation updates, which means that the updates (and install) will take a bit longer, and you won't see the benenfit of the changes to that initial update process.
Still no sign of the 64 Bit connector though
I wish that it was online I really could have used it around about now to sort out a problem that I may have just caused on my Vista 64.
Ken Warren wrote: OEMs will be able to slipstream these updates into their initial distributions. System builder purchasers, who are enthusiasts installing on their own hardware for the most part, will not be able to do this (and usually won't want to, since we're normally doing a "one off" installation). Instead, you'll receive this update as part of the initial installation updates, which means that the updates (and install) will take a bit longer, and you won't see the benenfit of the changes to that initial update process. I guess I didn't word that question correctly.
What I meant is will it be available for earlier versions of WHS (Beta 2, CTP, RC1)?
- Of course not.
kariya21 wrote: What I meant is will it be available for earlier versions of WHS (Beta 2, CTP, RC1)? 
Beta 2 is expiring for most users still running it; CTP will be doing so in the near future. RC1 will expire by the end of the year for most. Why would Microsoft supply usability updates for old beta software that's about to expire? Ken Warren wrote: Of course not.
Beta 2 is expiring for most users still running it; CTP will be doing so in the near future. RC1 will expire by the end of the year for most. Why would Microsoft supply usability updates for old beta software that's about to expire?Because I don't think RTM will ever be available here in the US...
I've updated my server running the RTM tonight with this 'update'.
However: the server update was fine, at the end, it said it had to reboot, which I so did. After some time, I noticed that the Console icon on the client I was using, was still showing red; I remoted into the server and it was running just fine, so I selected the red Console icon on the client.
A window appeared, saying that this version of Connector is not compatable and needs to be updated and 'click OK' to upgrade.
This then again showed a licence agreement window, where I agreed and pressed OK, the pop-up then proceeded to uninstall the 'old' version of Connector software, but DIDN'T install any new version!
The only way, was to navigate to the copy in the server shared folders and run it from there.
I understand that there aren't too many people yet with a working setup of the RTM, but if this isn't just a one-off, there are going to be some very confused people.
I'm off now to see if the same thing happens on the other clients.
Colin
Colin
Im getting something slightly different to you by the looks of it.
I ran the updates on my RTM box, the server updated fine and rebooted - now showing as 6.0.1500.6. The connector told me that there was a newer version available and did I want to upgrade. I selected upgrade but got "an error" message so did the upgrade manually. When I go into the console it is still showing as the console version of 6.0.1500.0 so it hasnt changed a version number but I did notice a different "passwords do not match" warning :-)
Andrew
I too have run the upgrade, and I got yet another variation of upgrade messages.
WHS updated fine, then rebooted. My main PC then showed the red icon (same as everyone else at this point). However then when it started to upgrade it failed to read my CD-drive. Strange as I had not put a CD in and it should be using the install on WHS. Selected 'Continue' and it ran through fine. My other two PCs upgraded without an issue.
Also on a slightly separate note.
Installed the OEM WHS on Friday (yes I live in the UK) and Microsoft Update is already showing 25 updates. I realise that most of these are part of the initial install, but 25 in four days!
Another thing was that Microsoft Update showed IE7 as a priorty update, this suprised me as a) it's been out a while; b) WHS is a headless system so should only need a basic web viewer.
Anyway these were my observations of the upgrade. Still a great product though.
Simon
Further:
One installation gone fine. Next installation had to install from Software share, as wouldn't complete via it's own upgrade.
Also, it now gets 'Passwords do not match' message, when nothing has changed and am unable to clear it.
Not a very good start to a new product, I din't have this many problems with the Release Candidate!
On to the next ones.
Colin
Interesting - all is cool here. I installed the update via RDP-ing into the server (wanted to grab a screenshot for WGS), rebooted, like everyone else, received a red icon on my home computer. Double clicked, the WHS Connector program re-ran its installation, re-found the home server, password entered and WHS Console ran no problem.
Terry
I have installed earlier this evening and have been experiencing problems ever since. After the update the Connector software on the PCs says that it needs to be updated, displaying a red icon in the system tray. When choosing to update it uninstalls, then reinstalls the connector software from the software folder of the WHS.
So far so good but when trying to then add the PC to the WHS and set up backups it hits an error and declares that I need to install the latest version of the connector software (which is what I was doing), continuing completes the process unsuccessfully and closes the connector software. Re-opening the WHS connector software to the system tray kicks starts the whole process over again.
I have tried resetting both the PCs and the WHS box, removing the PCs from the WHS Computers & Backups tab, and all manner of other things, none of which seem to be helping.
So at the moment I have no backups and no connector software, however the folder sharing and Remote Access to the WHS is working.
Especially frustrating as i only had my RTM copy delivered yesterday and did a clean install (upgrading from the RC) to start a fresh, so haven’t even had time to play before it has hit this complication.
It looks to me like the problem is with the Connector software that has updated in the WHS software folder.
Hope someone can help or MS come up with a fix or a solution soon.I think I am getting something different again.
I only have the Windows Home Server Backup and Restore updated to 6.0.1500.6. The console and all other items are still at 6.0.1500.0
All of my PC's are displaying critical red colour in the taskbar, but the server itself is yellow due to backups failing. In the Console Computers and Backup tab, all the PC's are listed as off (icon greyed).
The connector has not advised me there is an update available so none of the PC's have been updated or the software reinstalled yet. I am going to test this now.
Is this update available in the US? I get no updates available!
ribouch wrote: Is this update available in the US? I get no updates available!
Yes, it's available World Wide.
ribouch wrote: Is this update available in the US? I get no updates available!
I think you need RTM for that update.
- I had the same problem and I think I've fixed it.
Looking in my Home Server Connector Software folder, I noticed I had two SET*.TMP files that were the same approximate sizes as the SETUP and MSI files but with newer timestamps (6/9 as opposed to 6/7).
I renamed those accordingly, ran SETUP and all now seems to have connected okay.
See if you can do the same. I have Windows Home Server Console: 6.0.1424.2 installed and auto update turned on but still no update!
I get regular windows updates but even when I try the update now button I get nothing! Is it available for download?
- 6.0.1424.2 would be RC (Beta) version, I beleive the updates are only available for the RTM.
The RTM being the one for sale overseas at this point! Which is I asked the question in US or not?
FYI: I am using the eval version in the US. The update has been working perfectly for me so far (server, vista ultimate client, XP pro client). Just a few more machiens to go...
--Gordon
Gordon Smith (eMVP) wrote: FYI: I am using the eval version in the US. The update has been working perfectly for me so far (server, vista ultimate client, XP pro client). Just a few more machiens to go...
--Gordon
What do you mean by "eval version"? I didn't think the 120-day trial version was available yet.
It is. I got it about a month or so ago. I do work for a distributor so it's possible they weren't releasing it out to the general public yet. I'm really not sure.
--Gordon
Thanks for the info Gordon. The announcement is a little confusing:
As with most Microsoft products, updates to Windows Home Server will be delivered throughout the lifecycle of the product. Tomorrow - September 25th, Microsoft will release our first update for Windows Home Server. This update will enhance the usability and improve the out-of-the-box experience for customers. In addition to delivering the update to existing Windows Home Server customers via Windows Update, we have provided the updated software to our OEM and distribution partners.
Well seeing how we were the beta testers who got this product ready you would think we would be considered customers! Even though the product lic doesn't expire untill december I guess thats it for testing! Doesn't seem right but OH well thats the way it is!
Thanks
pjtaylor wrote: I had the same problem and I think I've fixed it.
Looking in my Home Server Connector Software folder, I noticed I had two SET*.TMP files that were the same approximate sizes as the SETUP and MSI files but with newer timestamps (6/9 as opposed to 6/7).
I renamed those accordingly, ran SETUP and all now seems to have connected okay.
See if you can do the same.pjtaylor - Thank you - this has indeed fixed it for me too. THansk for your help!
ribouch wrote: Thanks for the info Gordon. The announcement is a little confusing:
As with most Microsoft products, updates to Windows Home Server will be delivered throughout the lifecycle of the product. Tomorrow - September 25th, Microsoft will release our first update for Windows Home Server. This update will enhance the usability and improve the out-of-the-box experience for customers. In addition to delivering the update to existing Windows Home Server customers via Windows Update, we have provided the updated software to our OEM and distribution partners.
Well seeing how we were the beta testers who got this product ready you would think we would be considered customers! Even though the product lic doesn't expire untill december I guess thats it for testing! Doesn't seem right but OH well thats the way it is!
Thanks
It actually makes a lot of sense to me. The Beta bits are different than the RTM bits. If they released an update for both, it implies having to build and test for 2 products instead of just one. The solution for beta people should be upgrading to RTM bits then applying the update.
This update is only for RTM version.
- I'm curious to hear if the people that are having this problem are rebooting the Windows Home Server after the update?
- And we would if it was avaiable here in the US!
Joel Burt wrote: I'm curious to hear if the people that are having this problem are rebooting the Windows Home Server after the update? Joel
I am not sure if this is how other people did the upgrade, but I thought I would explain my route.
-
Didn't wait for auto-update. I RDC'ed on to WHS and ran Microsoft Update.
-
This gave me 2 priority update. 1 was WHS and the other was IE7
-
I said yes to both install.
-
I think the IE7 was the reason for the reboot.
My thoughts are would a auto-update include IE7 and if so how would WHS handle the re-boot? Given that it is headless would it sit there waiting for someone to RDC?
I'm not sure if this is what you are after, but it might help.
Simon
-
I didnt need the IE7 update, I only did the WHS update and I still had to do a reboot.
Andrew
Joel (or one of the WHS team)
Can you please confirm the correct version numbers for the various element of WHS post update.
Mine are showing as:
Windows Home Server Console: 6.0.1500.0
Windows Home Server Backup & Restore: 6.0.1500.6
Windows Home Server Drive Extender: 6.0.1500.0
Windows Home Server Remote Access: 6.0.1500.0
Windows Home Server Storage Manager: 6.0.1500.0With the discussions about Connector I am not sure what is now right.
Thanks
Simon
Simon,
I have the updates installed and that's the version numbers I have.
HTH,
Colin
Simon
Those are the version numbers on my machine following the update.
Andrew
The team has determined the cause of the problem is working on a resolution. For now you can follow the link here:
or another option is to copy Setup.exe and WHSConnector.msi from the home servers folder c:\whs to "\\server\software\home server connector software"
Gordon Smith (eMVP) wrote: ribouch wrote: Thanks for the info Gordon. The announcement is a little confusing:
As with most Microsoft products..... I guess thats it for testing! Doesn't seem right but OH well thats the way it is!
Thanks
It actually makes a lot of sense to me. The Beta bits are different than the RTM bits. If they released an update for both, it implies having to build and test for 2 products instead of just one. The solution for beta people should be upgrading to RTM bits then applying the update.
Hey people,
I also have version 6.0.1424.2 and would like to upgrade to RTM version. Is it available for download somewhere?
Thanks,
rupioRupio
If you want to upgrade to RTM you have two options:
1 - find a retailer with the RTM code in stock and buy it
2 - very soon you will be able to order a 120 eval copy from the MS WHS website
Andrew
Why it took you so long to respond?! =)
Thanks for the tip Andrew! I'll wait for the eval copy and test it for 4 more months before I decide to buy it.
rupio:-)
I think the eval copy should be available very soon, and 120 days will certainly keep you going.
Andrew
I had this problem - it is fixed by renaming the .tmp files mentioned elsewhere in this thread.
cheers
I am having the connector update problem but don’t have any .tmp files in the \\whs\software\home server connector software folder. So you may only have part of the solution. BTW I did check to make sure that the update did take place.
OK,
pI am really confused, and hopefully it's not just my stupidity. I just ran Windows Update and it said no updates were avaialble, but the resources tab says 6.0.1424.2 for all version information.
I see something about renaming some files, but am completely confused. Is this update only going to work on the RTM version, ar is there something I need to do to get these updates to work?
Thanks in advance,
Erik
Erik
The updates are for the RTM release.
Andrew
I kind of thoujght that was the case, but it wasn't perfectly clear in the previous posts. So now I will jsut wait until I can buy the RTM release.
Thanks,
Erik
:-)
Hopefully you should be able to find somewhere with it in stock now!
Andrew
I found relief in executing your second suggestion. Copy the 2 files from the server into the WHS folder (under Programm Files) in the recipient machine. 3 out of 4 machines took the upgrade flawlessly, the stubborn one needed an axtra kick i.t.A. All four machines are however very much similar (all win XP Home). Tx for the kick. (from Utrecht, Holland)I am getting the same error, "An error occurred that prevented the Windows Home Server Connector from Completing successfully. Run this wizard again to install the Windows Home Server Connector. To Close this wizard, click OK."
I will try the renaming of temp files if they exist [can't remember if they do or not[ or copying from c:\\whs to \\homeserver\software\home_server_connector_software
I am from Sydney and mine is a fresh install of the final release (purchased copy).
John P
