Comments on: Add-In: Windows Home Server Disk Management

By: Add-In: Windows Home Server Disk Management Updated « MS Windows Home Server

Mon, 28 Jan 2008 21:36:26 +0000

[...] January 28, 2008 — Philip Churchill The Windows Home Server Disk Management add-in which we discussed here has been updated to version 1.0.3. for those of you not in the know, this add-in is an extension of [...]

By: Dileep K (WHS Team)

Dileep K (WHS Team) — Wed, 16 Jan 2008 18:06:07 +0000

We haven’t got any data so far which indicates that the storage tab from WHS is displaying incorrect information. If that is not the case for any user, please file a feedback through MS Connect and we will look into it promptly. The WHS team specifically wanted to hide the per-disk statistics from the end user since with Drive Extender technology, all the hard disks become a single big pool of virtual storage.

By: XTC

XTC — Wed, 16 Jan 2008 17:20:19 +0000

Why is the WHS drive manager so different than the above add-in when reporting memory? In fact, the creator of the add-in claims, “I believe my add-in is more accurate than the WHS Server Storage tab”.

If actually true, then the Windows Home Server Team needs to explain why WHS is not actually reporting the reality.

I think an explanation would be helpful…

How great is Windows Management Instrumentation when it doesn’t really know what the underlying hardware is?

It seems more and more of the time, software is becoming more script language based, than based upon real efficient, power saving and reduced footprint, like assemble code. Rather than simplification, everyone is building upon yet another higher level language, introducing even more errors, bugs and proprietary code.

Of course, Microsoft claims that the purpose of WMI was to define a non-proprietary set of environment-independent specifications which allow management information to be shared between management applications.

By: Henry

Henry — Wed, 16 Jan 2008 16:53:48 +0000

WHS remains to be a beta testing product…

> The current WMI crawl is very slow.
> The “Repair” button isn’t hooked up yet.
> add-in to identify the hard drives via a visual display.
> You’ll see your CPU spike during this time.

Nice to have add-ins, but obviously not a polished nor finished experience for the customers. Perhaps, sometime ahead, WHS might be working right, and without the data corruption issue which remains without a resolution even still. See: http://www.support.microsoft.com/kb/946676