Windows Home Server was released as a product through the OEM (Original Equipment Manufacturer or “hardware manufacturer”) and System Builder channels the primary support responsibilities fall on the OEMs and System Builders. OEMs work closely with Microsoft through their Technical Account Managers (TAMs) and the Microsoft Support team to escalate issues, provide “repro” (reproduction) steps, collect logs and other information.
A good place to get started and learn about all of the resources available to you is through the Support for Windows Home Server page available from the Microsoft web site. It has links to the Getting Started Guide, Reviewer’s Guide, Release Documentation, Technical Briefs, Knowledge Base articles and lots more.
System Builders often leverage online resources to learn and figure things out. The Windows Home Server Community Forums are testament to the learning process, as some people have a hard time learning what hardware they should use, and others are trying to learn the ins and outs of the Windows Home Server software. And others are learning how to extend the functionality of their home server offerings through the Developers forum that discusses tips for building Add-Ins.
The Windows Home Server team works closely with the Microsoft Support team to understand the issues and escalate when necessary. The key thing for the development team is to be able to know how to “repro” an issue – which often includes a lot of details, about the home computer, home network, home server hardware, relevant logs and the exacts steps that a user is taking and the exact text of all error messages. The Windows Home Server Toolkit was released to help the OEM and Microsoft Support teams to be able to collect logs and other information from a user’s home computers and home servers. You can download the toolkit to your home computer from the Microsoft Download Center.
Windows Home Server, WHS, Support, Developers, Releases, Team, Platform, Hardware, Microsoft