WHS as a File and Media Server

The second major feature Microsoft is pushing with WHS is its use as a file and media server. This is a natural ability for WHS to have since file serving is a core component of Windows Server 2003, and we couldn't imagine Microsoft having not shipped WHS with this feature. As we'll see however, for a file server WHS is surprisingly hit and miss.

It's important to note that the connector software is not only a backup client, but it integrates the computer into the server on an account and file level. WHS does not do active directory domains (important because home versions of Windows can't connect to those) but instead offers a simpler level of integration. When a client is integrated into the server, the default action is to create accounts on the server that are related to the accounts on the client. Here WHS and the connector will copy over the account names and passwords (forcing the account owner to set a real password if they are not using one) and then give every account their own personal folder on the server. WHS will furthermore keep the accounts in sync between the client and the server, so that passwords remain the same on both, particularly important so that clients can access the server's folders without needing to log into the server separately.

By giving each account on each client a server account, this serves to simplify access controls on the server. WHS forgoes the full abilities of Windows' access control lists for a Unix-like read-write/read/none level of permissions for each shared folder for each account. Permissions can only be set at the shared folder level however, and subfolders can only inherit the permissions of the folder that contains them unless the administrator goes outside the bounds of the WHS console.

Besides the account folders, WHS comes with five public folders: music, videos, photos, public, and software, and all accounts automatically get read-write access to these folders. Additional folders can easily be created from the console, with accounts getting no permissions by default. The much loathed guest account also makes an appearance here, and while it's disabled by default it's possible to enable it and give it access rights to all the shared folders the same as any other account.

It's also with the shared folders that the folder duplication feature becomes available. Windows doesn't duplicate backup data (since the data is already at one place: the client) but can duplicate any of the shared folders, including the account folders. From having used WHS so far, the ability to select what folders to duplicate (e.g. photos but not videos) is proving to be incredibly useful.

WHS also offers a degree of local backup protection for these shared folders, besides the redundancy in case of a drive failure. Surprisingly, none of Microsoft's own manuals for WHS mention this, but the shadow copy service on WHS is by default used to also track changes in shared documents, meaning the Previous Versions feature is available to recover old documents should the current ones be damaged/destroyed. This currently is somewhat limited in availability since on the client side only Vista and some XP clients support this feature, but via RDP it's possible to log into the server, which can also use the Previous Versions feature on itself. The buffer for the amount of data shadowed here is fairly small, so these backups are not as robust as the backups done by WHS of whole computers. But since most media seldom changes, it's enough to recover files in the most likely situations.

Finally, all of these shares are offered as a normal Windows SMB share. This is worth noting since there are viable SMB clients available for all the major platforms, so WHS can easily be used as a server even in a mixed network. Furthermore the WHS development team has also been looking at other uses for the shared folders, going so far as to seriously propose using a WHS server as a back end for Mac OS X Leopard's Time Machine backups.

WHS As A Backup Suite, Cont WHS As A File & Media Server, Cont
Comments Locked

128 Comments

View All Comments

  • Aileur - Tuesday, September 4, 2007 - link

    Nice articule!
    First of all, a typo (im guessing)
    Page 7: Simply put, there is no integration between the two. By default WHS and MCE are completely //obvious// to each other.
    Im guessing that should be oblivious?

    And a question:
    On page 6 it is mentionned that there is a solution for non domained networks and all that. Fine, but what if i DO have a domain? Is there any way to integrate it without using that bypass method?
    Can it (whs) be my domain controller?

    Thanks!
  • Ryan Smith - Tuesday, September 4, 2007 - link

    Unfortunately WHS does not have domain controller support. I haven't seen a reason why, but it's a safe assumption this is so there's a greater difference between WHS and 2K3SBS.

    It also doesn't support joining a domain.
  • yyrkoon - Wednesday, September 5, 2007 - link

    Does not even have software RAID support, at least the last time I ran the beta . . .

    cannot believe you guys are just_now writting an article on it, but, I suppose maybe you guys had a NDA in effect ? Anyhow, I have a hard time embracing *any* OS that is supposed to be a server product and does not implement software RAID period, but I supose they think their backup scheme is better ? No reason to 'force' it onto others.

    The main reason I think it does not have a DC is that this is meant for home storage only. I.E. a very limited form of Windows 2003. I ran it on my secondary system for a few days, and decided I would probably rather run XP Pro, or Win2003 datacenter(or one of the other variants, maybe even Linux) at this capacity.
  • PrinceGaz - Wednesday, September 5, 2007 - link

    Just a wild guess from me here, but I think most home-users would be put off by the US$ 2,999 price-tag of Windows 2003 Datacenter edition.
  • mino - Tuesday, September 11, 2007 - link

    Good guess :)

    Anyway, Win2000 is pretty much enough for any home serving and 2nd-hand licences goes pretty cheap (especially when security support is likely to match even extend currently sold XP licences...).

    Just my 2 cents.
  • mino - Tuesday, September 11, 2007 - link

    Win2000 Server, of course.

    Also, as a sidefect of standard win200 kernel it usually does not have problems with TV tuners...
  • tynopik - Wednesday, September 5, 2007 - link

    > Anyhow, I have a hard time embracing *any* OS that is supposed to be a server product and does not implement software RAID period

    1. it's a HOME server, not a corporate server
    2. it is better than RAID (at least for it's intended audience)

    disks of any size can be added or removed at any time, yet files are still physically duplicated on different disks, that is very flexible and powerful

    i love this feature so much i wish they would include it in regular windows
  • leexgx - Tuesday, September 4, 2007 - link

    nothing stopping you seeing it on the network still

Log in

Don't have an account? Sign up now