Following a number of recent murmurs online regarding performance of HP MediaSmart Servers running PowerPack 1 and HP’s latest MediaSmart Server update (v1.3), HP have today published an advisory note guiding users on how to best install Windows Home Server Power Pack 1 in conjunction with HP’s Update (notably the PVConnect and McAfee anti-virus add-ins which are supplied with the update).
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:
- 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.
- 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.
- 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)
August 13th, 2008 at 2:31 pm
Hear Hear!
Will be checking option 2 out tonight. Luckily I had already uninstalled McAfee. Hoping some other brave soul will see how McAfee runs after PP1 & 1.3 are on with std memory
August 14th, 2008 at 11:15 pm
I must admit this has probably got to be the most frustrated I have been with a company in a very long time (and I buy and use quite a lot of tech products… and a lot of them fall short of expectations, which is another story altogether).
My MediaSmart has 2Gb RAM & 2Tb of drives (4 x 500GB Seagates). Sure, the warranty has been invalidated but let me just say it ran super smoothly prior to the update. (As it should with those specs, right?)
Yes, it has lots of pics on there, as in 50+Gb - we shoot plenty o’digital shots & just keep em.
PP1 installed without my knowing. When I logged on, I got a message telling me that there were 2 HP Addins. I checked for other updates… nothing. Checked the OS Version… saw that it was up to date so installed BOTH the plugins.
I pretty much lost the device for about 12 days - all the no response issues that people were screaming about… no access to the Console, ridiculous transfer times, dropping off the network, etc.
RDP would eventually get me in but all I could see was the processor burning at 100% constantly.
After about 12 days and no real helpful information coming from HP (or any other source), the only option I had was to either turn it off or uninstall both Addins via RDP (no access via WHS Console).
Now my system is ticking along but it thinks that the two Addins are still installed - and I can’t convince it otherwise. It also keeps on looking for the next update circa 1/1/1970…
It just feels like I have a tainted piece of equipment… which is just so sooo disappointing.
HP - shame on you. You’ve really damaged the goodwill you had with this excellent package (for a while there it was as close to an appliance as any piece of equipment I’ve bought - it just worked!).
Even though they can’t voice it externally, I hope someone in HP at least had the conscience to think “Shite - what have we done!?!”
Finally, I just want to say thanks Terry. The effort you have put into covering WHS and related products (HP rightly got good coverage) through your site has given you a significant position of influence. Your attention to the cries for help has likely brought this situation much more (needed) attention than it was getting.
October 27th, 2008 at 10:36 pm
The MS Word link seems to be broken, for me at least.