Before diving into the content, I’ll say that I know that HP have spent a lot of time testing a wide range of upgrade paths with various server configurations along with Microsoft over the past two weeks to try to understand and mitigate the slow server response users are experiencing when PP1, PVConnect and McAfee are installed at the same time.

However, the fact that they’ve had to publish this advisory tells me the following (and I’ve made these points variously to Microsoft and HP directly):

1. The recommended hardware specification for Windows Home Server must be raised.

The current minimum and recommended memory specification for Windows Home Server is 512Mb. When these specs were created, I’m sure that everyone underestimated the explosion of community and commercial add-ins, and users’ desire to extend the WHS platform. Many home servers out there are underpowered for use with multiple add-ins, and whilst I think it’s fine for Microsoft to retain a minimum specification for Windows Home Server with 512Mb, (for a vanilla home server acting as a closed box “appliance”) the recommended memory specification needs to move up to 1Gb – any lower and you really don’t get the true home server platform experience…. and that’s just with the v1 product. For v2, Microsoft may really shoot themselves in the foot if WHS isn’t positioned as a strong, extensible platform matched with the right level of performance to satisfy a more compelling, extended experience than that provided out of the box.

2. HP (and other OEMs) really need to provide customers with a supported memory upgrade path that does not invalidate their warranty.

Currently those users (like me) who have upgraded their HP MediaSmart Server’s memory have done so at the risk of invalidating our warranty. Much like a consumer electronics device, opening up the MediaSmart Server invalidates the warranty as upgrading components in the home server is more tricky than you’d find on a desktop machine. Whilst I get the logic from a business point of view (and HP aren’t the only OEM to make this restriction), we’re now at the stage where the product is showing it’s resource limitations (albeit temporarily on this particular occasion) which is impacting user experience. The problems highlighted are easily resolved with a memory upgrade, but at the moment, I’m sure many users will not take the risk of opening up their boxes in fear of bricking their systems and then not receiving support. As more add-ins come on to the market, and HP themselves continue to add features to the HP MediaSmart Server (for which they have to be commended), this situation in untenable. Guys, we need you to step up here.

3. I really hope HP manage to sort out a beta testing programme soon.

This particular issue is mostly due to the decision to align the PP1 and HP Update releases – a decision due, in part, to problems experienced by users who tried to upgrade their home servers with the previous release of the MediaSmart Server update.

These current issues, plus the original issues experienced by users could have been spotted early and possibly resolved by HP pre-release if they had a public/private beta testing programme in place  - there’s a whole community of users out there who’d love nothing more than supporting beta tests. I’m sure setting this kind of thing up is not trivial, and there’s a huge amount of logistical, legal and technical detail to work through – but I hope they work through it soon.

Okay, stepping down from the soapbox, let’s take a look at the document. The full text is attached for reference below, but the headlines are as follows:

1. Running the PowerPack 1 update whilst the PVConnect and McAfee add-ins are also running will use up a lot of the available resources on the HP MediaSmart Server, which impacts server response times. Having additional add-ins running on top of these will further impact response times during the update.
2. Once all updates have been completed, the MediaSmart Server will return to normal operation, although the time required for this depends on the number of files you have on your home server (although this is mitigated somewhat if you have mutiple hard-drives). PowerPack 1 requires storage to be rebalanced due to included changes in Drive Extender technology.
3. If you want 64-bit support on  the HP MediaSmart Server, you do have to install both PowerPack 1 updates and the latest HP Update.

HP offer advice based on three user scenarios:

1. You have an HP MediaSmart Server, and you have installed WHS PowerPack 1, but have yet to install HP’s Software Update

Advice here is to wait until PP1 has installed (leave it overnight is my personal advice) then install the HP Software Update. If you want to run both PVConnect and McAfee Anti-Virus add-ins, install PVConnect first, let it complete its database creation (1-4 hours depending on your number of files) then install McAfee anti-virus, which will take around 1 hour to make its initial file scan.

2. If you have a MediaSmart Server, and you have installed HP’s Software Update, including the McAfee Add-in

HP are advising that you ininstall McAfee anti-virus before running the PowerPack 1 update. Given that PP1 is about to come down the line to you today via Automatic Updates, then you should go uninstall McAfee now if you have WHS set to download and install updates automatically.

Once the update is complete, you can go ahead and reinstall McAfee.

3. If you have a brand new HP MediaSmart Server

The HP update will be installed as part of the initial server setup. The add-ins will be waiting for you, but make sure you install PP1 first before adding any media to your home server, and then installing the add-ins you want. As above, install PVConnect first, and then McAfee anti-virus.

Good Luck – and let us know how you get on.

More Info: HP Install Recommendations (MS Word Doc)

• HP Respond to Criticism on MediaSmart Server Performance Issues
• HP Respond to MediaSmart Update Installation Issues
• HP MediaSmart Server Update Arrives, With New Media Streaming, Anti-Virus Capabilities
• Exclusive: Avast Anti-Virus for Windows Home Server - Preliminary Details
• HP MediaSmart Server Update Now Available

Native QAM support is a very nice feature to see, but I am beginning to understand why there are rumors regarding Microsoft’s possible release only to OEM’s.  Do you really want to reinstall Vista to get these new Media Center features?

Originally spotted over at Ian Dixon’s Blog.  The original endgadgetHD report is here.

• Windows Media Center TV Pack Already Released
• Is It Now Official, TV Pack for OEMs Only?
• Fiji x 2 for Media Center? Just for DirecTV?
• DirecTV Missing the Flight to Fiji?
• Windows Home Server Power Pack 1 RC Publically Available

Although the source code has been available to anyone to compile, the OML project took its first step into the mainstream with its first beta release on July 29.  The OML Google Code page now plays host to version 0.1b in both x64 and x86 flavors.  The OML Forum is already abuzz with bug reports and feature requests and the OML team is actively listening.

Features completed as of version 0.1b:

I am already a few days late in noticing the update, but I will play with the beta release this weekend and will be back with my impressions next week.  In the meantime, I look forward to hearing what you guys think of it.

• Add-In: Firefly for Windows Home Server
• How To: Play DVD’s in Windows Media Center Stored On Your Windows Home Server
• Controlling Media Center From Your Windows Mobile Device
• MyMovies Media Center Plug-in
• SageTV for Windows Home Server v6.4.2 Beta Released

Mike Craven (aka The Office Maven) is working on just such a solution.  WHS Outlook allows you to use Microsoft Outlook via the Windows Home Server Console.  It does require you to install Outlook on your server, and he has stated that it requires Office 2002 or newer.  You can store the “PST” files (which contains all of your mail and a number of settings) on either the system partition or on the network shares.  He recommends using Power Pack 1, and if you are going to store the PST Files on network shares, you will need to have Power Pack 1 installed or they will likely become corrupt.

I can quickly see a couple of downsides to this Add-In: Everyone that will have access to this will need to know the server’s password, that only one person at a time will be able to access it, and that everyone would be using the same installation of Outlook.  Depending on your household, this may not be a problem.  I know that for me that this won’t be a problem as I am the only tech nerd in my household. And I suspect a number of others fall into the same boat as I.

Just to clarify, WHS Outlook is soon to be in beta, so it is not ready for release quite yet.  Though if you are definitely interested in actively beta testing this add-In, head over to this thread on the WGS Forums and let Mike know! Note that availability of the beta is limited (first come, first serve) and Mike has said that active participants in the beta program will receive a final release copy of the program at no charge as thanks for their help in testing out the program.  So hurry now and sign up!

Also, Mike has stated WHS Outlook will work with a trial version of Outlook so if you don’t have a spare copy, you can always use a trial. Although, it will prompt you to upgrade to the full version, so if you don’t mind annoying pop ups, this is a great way to test it.

For those wondering, this will be a commercial add-in. Mike has said that he isn’t certain about the price right now, and that the beta testing will help determine the pricing for it.  He is estimating that he will sell it for $25.95USD once it is ready.

It should be ready for beta testing in the next day or so, and you can definitely expect a review by myself then.

• Microsoft KB 955690: Outlook Personal Folder Files & Database Files Unsupported via Network on Windows Home Server
• Time to Get Ready for Windows Home Server Power Pack 1
• Is Windows Home Server Power Pack 1 Ready for Release?
• WHS: Beta 2 - What’s in the Package?
• A Guide to Windows Home Server Power Pack 1 Beta - Part 2

Microsoft has added a lot more safety checking and verification to the disk removal process, as well as the new Server Backup Disk type, and WHS Disk Management has had to evolve as well to accomodate these changes. A full list of changes in the PP1 version is available.

This release has had a lot of testing by members of the closed beta group, but because of all the changes the author recommends that you install this on your test WHS system before putting it on your production server.

The beta is available for download from Tentacle Software and you can discuss your experiences and post any bugs on the WGS forums

Remember to uninstall any previous version before installing this version; your current settings will be preserved. Copy the new MSI to \\server\Software\Add-Ins, then install the new version of the Add-In from the WHS Console.

Note: PP1 RC4 is required to be installed on the server. If you do not have PP1 installed, you should use the latest 1.0.8.x release (v1.0.8.6).

• Add-In Update: WHS Disk Management v1.0.9.8
• Add-in: Windows Home Server Disk Management v1.0.8.6 Released
• Add-In Update: WHS Disk Management 1.0.4
• A Guide to Windows Home Server Power Pack 1 Beta - Part 2
• Diskeeper 2008 Beta - 50 Places Up for Grabs

The Live Mesh team had indicated on their forums that this wider release was specifically for US users, but that international users could participate by changing their Windows region and language settings to EN-US.  Mick pointed out in the comments that he was able to sign up from the UK.  He did not mention whether he had to change the language and region settings, but at least it is confirmation from someone we know that international customers can indeed join in.

Ken asked the question I’m sure came immediately to mind for a lot of us: So when can we expect to get Live Mesh to work with my Windows Home Server?  The obvious answer is: Who knows., but there is a long sticky post on the Live Mesh forums for feature requests.  I haven’t read all sixteen pages yet, but I would imagine someone has asked a similar question there.  I do recommend anyone interested in the future of Live Mesh try reading through at least part of the list.  There are some neat ideas in there and enough consensus on some requests that Microsoft will almost certainly take heed.

Colin Walker was the first to comment the other day, lamenting the lack of mobile support.  Not being much of a mobile phone user, I have no idea how useful it is, but LiveSide was tipped off that the mobile portal for Live Mesh has gone live over at http://m.mesh.com.  You still can’t add mobile devices to the Live Mesh desktop or the client-side software and there is no mobile client software yet, but it seems to be a start in the right direction. 

Finally, there was a bit of discussion in the comments about how to accomplish specific tasks with Live Mesh, such as synching folders between devices directly, without passing through the cloud.  For anyone interested in tutorials on specific Live Mesh applications, I would suggest checking out Redmond Pie’s Live Mesh Scenarios Directory.  There’s not much there yet, but I suspect it will become a valuable resource in the future.  If any of our readers decide to post a tutorial there, be sure to drop us line and let us know.

As I mentioned, I am withholding judgement on Live Mesh until I can play with it a bit more.  Additionally, it is important to keep in mind that this is a technical preview, so I am sure that things will change a great deal in the future, but Live Mesh is shaping up to be an important component in Microsoft’s Windows Live strategy.

• Live Mesh Now Live…Sorta
• Windows Live Hotmail
• Don’t All Shoot At Once :)
• Configuring Windows Home Server: User Accounts
• Windows XP SP3 Update Breaks Windows Home Server Remote Access?

Unfortunately, my wife is not a geek. A few nights ago she called my boys over to my laptop to check out a website that my Grandmother had sent a link to.  My suspicions were immediately aroused.  It was a site obviously designed to appeal to little old ladies with a sweet prayer, cute animated backgrounds and music, and a message at the top instructing the visitor to be sure to wait until the entire site had loaded before beginning the long scroll down.  Sure enough, the link had been passed along in an unsolicited forwarded e-mail which seemed to be written in stilted, mechanistic English.

I immediately removed the laptop from the network and set up a dedicated Internet connection for the laptop so that I could gain access to an online scanner.  I do not use an anti-virus program, but I have been a part of the Microsoft OneCare beta for years.  I use those beta licenses on the family computers and have been generally impressed with the OneCare online scanner since it launched.

While I waited for the online scanner to locate and help me eradicate the trojan that my wife had unwittingly downloaded, I found myself once again wondering why we still did not have a OneCare for Windows Home

Server.  This has been a frequent question and sore point on the beta forums and newsgroups since before the release of OneCare 2.0.  There are areas of overlap between the two products, particularly relating to system monitoring and backup, but there is little reason why the basic client could not be stripped down to focus on security monitoring as part of a WHS add-in.  It seems to be an obvious market and one that Microsoft should have been tapping from day one.

When Microsoft first let slip that they were preparing a version of OneCare for servers, there was a great deal of speculation that this would finally bring support for WHS.  Alas, this was not to be.  OneCare for Servers is limited to certain versions of Windows Server based on the Server 2008 kernel.  This immediately rules out support for WHS which is based on Windows Server 2003. 

Assuming that the next version of WHS is based on Windows Server 2008, it is quite possible that we will see OneCare support for WHS added.  It will require that OneCare for Servers be adjusted to operate in the WHS console and there will probably need to be changes made to the OneCare client to more effectively adjust its monitoring to avoid overlap with automated WHS functions.  With OneCare 2.5 already in the market, we will likely have to wait not only for WHS v2, but also for OneCare 3.0. 

Even with all of these pieces in place, we will have wait and see how Microsoft handles its licenses.  OneCare provides licenses for three computers.  One of these three computers can be put in charge of monitoring all three computers, designating it the hub for a circle of care.  This circle of care also shares the Live ID that is required for managing the OneCare licenses.  Add a fourth computer to your network and you need to start a new circle of care with a different Live ID.  I have not been able to try the OneCare for Server beta, but it is hard to imagine a small business wanting to juggle multiple Live IDs so hopefully this has changed with OneCare for Server and we can expect OneCare for WHS to monitor a circle of 10 installations with a single Live ID.  Otherwise, OneCare for Windows Home Server, when it finally comes, may be more trouble than it is worth for many WHS users.

• Will We See OneCare for Windows Home Server?
• Exclusive: Avast Anti-Virus for Windows Home Server - Preliminary Details
• avast! Anti-Virus WHS Edition Released - 3 Licences Up for Grabs
• Avast to Release Windows Home Server Anti-Virus Product
• Windows Home Server Public Beta - Home Computer Restore CD (Dual Boot)

Until recently, accessing the technical preview of Live Mesh has required submitting your name at Microsoft Connect, Microsoft’s beta community site, and crossing your fingers that you might be selected to join in the meshing fun.  Now word comes from Liveside.net that the doors have been flung open, at least a bit. 

If you are interested in trying out Live Mesh, head over to www.mesh.com. 

A few caveats do await.  This is still a technical preview and will be for some time.  Anything you set up or use in this technical preview may be lost when Live Mesh enters its next iteration.  You must have a valid Windows Live ID.  At the moment, anyone in the US can join.  International users will have to change their Windows region and language settings EN-US to join in.  Finally, space is limited.The Live Mesh team is using this change to the sign-up process to double the number of people accessing the preview.

I have been looking forward to having a crack at Live Mesh and will post my thoughts after I have had a chance to really try it out.  I look forward to hearing your thoughts on Live Mesh and how you are putting it to use.

• Make the Most of Live Mesh
• Update to the Windows Live Custom Domains Terms of Service for Windows Home Server
• Windows Home Server Documentation Updated
• Windows Home Server Power Pack 1 RC Publically Available
• Windows Home Server Toolkit Webcast Available

A few days ago we mentioned that EngadgetHD was reporting on rumors that Fiji, the forthcoming update for Windows Media Center, was no longer going to include support for the long anticipated DirecTV tuner.  Well, EngadgetHD is back with an update.

Evidently the Media Center beta testers are still all atwitter, but EngadgetHD is reporting that they have received new information that indicates that the DirecTV and H.264 support were taking too long to implement and had to be cut because Microsoft had promised an update to OEMs by the end of July.  Said update is still expected to be called the Windows Media Center TV Pack and will be bringing a host of tuner support improvements to WMC.  There will be ISDB-T and BML support for Japan, clear QAM support for the US, and new support for DVB-T and DVB-S tuners for Europe.  Windows Vista Ultimate may also be getting a boost with official support for four tuners, though Home Premium users will still be limited to two.

The upshot to all of this is that EngadgetHD’s sources are now optimistic that the DirecTV support will still be arriving this year, it will simply arrive a bit later. 

So what does it all mean?

Last time, I tried to provide some thoughts on what all of the rumors implied for the near-term future of Windows Media Center.  These newer rumors do potentially clear up my question about the validity of the name: Windows Media Center TV Pack.  Microsoft’s announcement of the TV Pack for Japan is nearly three weeks old now, but these updated rumors would explain why that name is popping back up again now.  The possibility that it had been promised to OEMs by the end of July may also be why early reports suggested that the update would be an OEM-only release.  Hopefully that whole rumor was, as I suggested, a matter of crossed wires, even if it wasn’t necessarily the wires I expected.

The rumors swirling around the DirecTV tuner and H.264 support remain.  It is not impossible to imagine a scenario in which Microsoft felt that it needed to delay the DirecTV tuner.  There could be driver issues, hardware malfunctions, incompatibilities between DirecTV’s software and Media Center, or even issues properly integrating the EPG sub-systems.  But why delay support for H.264?

The DirecTV tuner requires H.264, but adding H.264 support to Media Center should not require the DirecTV tuner.  Any enthusiast willing to download a codec pack can add H.264 support to Media Center right now.  Windows Media Center uses DirectShow filters to provide the interface between the video renderer and supplemental codecs.  Given the right filters, just about any codec support can be enabled in WMC. Unless…

The scary possibility is that all of this relates to DRM, and the H.264 support that Microsoft is adding is going to be so hobbled that it will only be of use in specific, limited scenarios.  The other possibility is that all of this relates to DRM, and the H.264 support that Microsoft is adding is intended to also provide support for something else; Blu-ray support may be closer than we think.

As I mentioned above, Windows Media Center uses DirectShow filters to interface with codecs, but Microsoft has already baked DirectShow’s replacement into Vista in the form of Media Foundation.  Moving Media Center over to Media Foundation and its enhanced video renderer would serve to make Media Center Protected Media Path-compliant, one of the requirements necessary for Blu-ray support.

Of course, basing Media Center’s H.264 support on Media Foundation might complicate things for users.  Would Media Center be able to use Media Foundation and DirectShow simultaneously?  If not, a whole lot of Media Center applications are going to break.  Any application or codec using a Directshow filter would need to be reengineered to access the enhanced video renderer through a Media Foundation Transform instead.  I suspect that DirectX 10 compatible GPUs would become a WMC requirement.  It is also possible, depending on how the Protected Media Path is enabled, that an HDCP-compliant video connection would be a requirement in order to play back any H.264 material.

In the end, perhaps I am reading too much into these rumors of delays.  Either way we will wait with bated breath to see what Microsoft is planning.

• DirecTV Missing the Flight to Fiji?
• Windows Media Center TV Pack Already Released
• Installation of the Vista Media Center RTM TV Pack
• WMC Plugin: MediaControl 5.3
• New Xbox Media Hub On the Way?

Beta 3 brings the following changes;

Bugs Smashed:

• Added support for French installations of Windows Home Server. (Used to be a problem with the spelling of Videos)
• Fixed the Media Center Scheduler service going bonkers. (Modified how the service is changed to run under the current user instead of LocalSystem)
• Fixed the Problem downloading Guide data bug. (Was a result of changing the account the scheduler service ran under. Fixed by changed the permissions on first run of the client)

Features Scratched off the List:

• Added logging to the TV Manager client. (You’ll get a dialog box telling you to check the event log with the TV Manager category)
• Automatically loads and refreshes the data for the TV Manager Console Tab.
• Exit context menu shows up when right clicking the client icon in the system tray.

Download: TV Manager Beta 3 | Discussion and Support

• Add-In: TV Manager (Beta) Released
• Add-In: Recorded TV Manager
• Add-in: Recorded TV Manager for Windows Home Server (Beta)
• Add-in Update: Recorded TV Manager 3.4.5 & MCE Collections Beta
• SageTV for Windows Home Server v6.4.2 Beta Released