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

  • mindless1 - Wednesday, September 5, 2007 - link

    See "Cause" on http://support.microsoft.com/kb/122920">this MS KB page.
  • leexgx - Wednesday, September 5, 2007 - link

    i got an windows 2000 pc setup as an server (think its win2k pro) when we had windows XP installed the 10 connection limit was an problem so we just put the old one back in and set up the file shareing on that one (+ 15 computers)

    only XP and vista has this limit and probly windows server when setup in Per license mode win2k and less have no 10 connection limit even thught that KB says so
  • Gholam - Sunday, September 9, 2007 - link

    The 10 simultaneous connections limit goes back as far as NT4 workstation.
  • BigLan - Tuesday, September 4, 2007 - link

    Strange, I've never had a problem sharing files in XP. True, I turn off simple file sharing (in windows Explorer - tools - folder options - view tab, bottom of advanced settings) but that's all. I've even added machines with a different workgroup name and been able to share files using \\machine name\c$.

    Also, you'd have thought that at least a couple of businesses would have complained by now if you couldn't browse network shares.
  • yyrkoon - Wednesday, September 5, 2007 - link

    Yeah, I share media from WinXP to WinXP, Win2000, Win2003, and Linux dailey, It is not exactly rocket science . . . I suppose if you think it should be confiured straight out of the box working perfectly then . . . whatever(heh).
  • leexgx - Tuesday, September 4, 2007 - link

    WHS is little more then just an XP computer thats file shareing
    as it has auto mirroring of files (if more then 2 disks are used)
    not tested it but it supports M$ MCE stuff (poorly from what been revewed) it allso supports none windows based media extenders

    i like to find out how this WHS works when running p2p apps on it as well as it dislikes you wanting to loging onto it
  • BigLan - Tuesday, September 4, 2007 - link

    There's already a torrent plug-in for it, and you could use any p2p app that has a web server interface. I hear it works very well.
  • sc3252 - Tuesday, September 4, 2007 - link

    Its called debian, not server's for idiots.
  • Sunbird - Tuesday, September 4, 2007 - link

    What if you want to have 2 WHSs on the same network. Say one would be the file server and the second one (with even more HDD space) would be used to backup the file server and all the home PCs. Would it be possible?
  • Ryan Smith - Tuesday, September 4, 2007 - link

    I haven't tested this, so I can't be sure. The only problem I could see is the backup client, it automatically searches out the network for the WHS. 2 servers may work, but I'd be a bit surprised if they did.

Log in

Don't have an account? Sign up now