Thanks for the replies, although some of you are still answering it from your "I installed this product and here is what I like" perspective. Try the other hat on .... here is what my household members think of it ... (Note: only works if you live with other people).
"Bucko" provided a good synopsis of selling points trying to convince a prospective customer, but "j and v" really hit the nail on the head. How do I convince my wife that I can spend $xxx to buy this, or better yet how do I convince her to buy it for "us" for my birthday?
"dubbug" provided an interesting challenge and asked for a synopsis of quotes from "confused end users". Sounds like a great topic for a future blog post. I have read some interesting things in the home server forums, which has led me to firmly believe that 2 things are needed:
Hopefully, you have all had time to read the Getting Started Guide and the Reviewers Guide for Windows Home Server posted on http://connect.microsoft.com/WindowsHomeServer (click on "Downloads" on the left). So today's question is:
What additional documentation / knowledge can we share with you? If I could produce a 5-6 page document, what would be the title of it?
The number one issue I have had to fight and looked for information on is dealing with firewalls.
For example, it took a fair bit of digging to find out port 3389 is used for something (not sure what), 4125 is the RDP port and backups run on 8912.
A common practice on securing a home network has been to turn off "Client for Microsoft Networks" since most home users do not need this. The WHS Connector installation does not currently check if this is turned off. You need to manually turn it on.
The one I still have to find out how to fix the problem with remote access. Right now it works somewhat without the same subnet. One problem is the wireless network drivers, at least on XP, connect to the network under a user account. As only one account can be logged it will log out the account that has the open network connection and then become "unavailable" for remote connect. This is likely something in my configuration. Access from outside the subnet is a whole separate issue.
Maybe this is already covered in the documentation, but having a "quick guide to network configuration" would be good.
Can you please document a little of the technical workings of Drive Extender?
I'd also like to know what I can do with IIS without breaking it. (I don't have much in mind)
I would like to become an MVP for the upcoming WHS community, and am looking forward to supporting this product, and AVIDLY encouraging sales.
Thanks for keeping up the fight, Team Q.
My Windows Home Server is still going great, I haven't had a monitor plugged in to it for weeks and I
Hi WHS team,
I think It would be graet to have a documentation, how to integrate XBOX360 or other devices with WHS.
I would like to see a list for techies of how or what can be extended. What is safe and what is not. For example if I want to modify the home page to add some additional things, what is the safe thing to do. What are the areas of safe extensibility etc. Can I add SQL Server Express if I want a home sql server? etc. There more things I could add but I think you would get the picture.
Glad I could help! Currently my wife sees the need for the server, but we haven't had an emergency as yet (knock on wood).
As for documentation, I would love to see the following:
- "Small Business Server or Windows home server - A brief look at the differences and benefits of each."
- "Technical advances for the server in the home." - This should explain the details of the drive extender and duplication technologies (non-RAID) of the WHS
- "Windows Home Server is here to serve you!" - This document should explain the non-technical things such as the media sharing, remote access, backups and a non-technical explanation of adding drives to the pool.
Actually our frustration with is it is we are an all-vista household that share a laptop. The public music and public photos folder is clearly identified in vista. My wife keeps habitually going there to look for her photos and whatnot because of the vista graphical cues and its name.
I wrote a suggestion somewhere on connect about this, but anyway the problem is you cannot relocate the public folders like you can user account folders. For some reason they are stuck on the C:\ drive... not a good place for mounds of data files.
Oops, I should clarify, we now have two "Public Photos" areas now, one on the Home Server, and one within Vista.
My wife is pretty tech savvy, but folks like my dad are going to get frustrated.
I think this goes hand in hand with OneCare integration as well. OneCare likes to think of itself as the central backer-upper guy. How are you folks going to absorb functionallity from other microsoft applications that are commonplace.
I think "j and v" with
"Windows Home Server is here to serve you!" - This document should explain the non-technical things such as the media sharing, remote access, backups and a non-technical explanation of adding drives to the pool. - The user docs do say it a good way with a non-tecnical way but i think the media sharing needs more info and what about infomation on if you have a MCE PC
And also "bpschoch" is spot on the, the user docs just say dont change some stuff, so can we change/add the other stuff?
Both please :-)
Most everyone here, because of our technical view, want technical information. Even the comment that was posted about a non-technical document about media-sharing, remote access, etc. is somewhat off the mark (though much closer than most...and this type of docemnt is needed too).
What is really needed is an incredibly non-technical explanation of how WHS will save your precious photos of your family when one of the family PCs (likely mom and dad's) dies. Or, when one of the kids (high school, college, or even mom/dad's college stuff) PC dies with that all important "thesis". Or how about those DV movies that were taken at the son/daughter's graduation or wedding, how do I share those among the home PCs.
This documentation has to be written assuming a low-level of understanding by the audience. It needs to use analogies that non-computer folks (even though they have one or more computers at home) can grasp.
What does WHS buy me for my family?
My 2 cents....
I concur in that a document should be published that contains information on what WHS will do for the whole family. It should provide information that would help the computer illiterate, of which I am to large extent. I want to load the software, (or purchase a WHS out of the box) and be in business. FYI, many small businesses will be using this WHS in their business because on startup they may not be able to hire and IT expert. I have had an interesting startup of the WHS beta 2, to whit, client computers can not access the SERVER but can be visible on the network could be "A common practice on securing a home network has been to turn off "Client for Microsoft Networks" since most home users do not need this. The WHS Connector installation does not currently check if this is turned off. You need to manually turn it on." by CoryB is or may be, one my problems and the other is Vista 64 bit, that I can fix.