I have a shower door handle that doesn’t want to stay connected to the shower door. I’ve tried two different kinds of epoxy, and if you look at the handle, you can see remnants of both kinds. I probably should have been diligent enough to remove all traces of the first glue before applying the second, but I didn’t think it would matter. It did.
Microsoft gave us disk quotas with the NTFS file system at least as far back as Windows 2000. (In the olden days, Novell used to beat up Microsoft on this point, because NetWare had quotas and NT didn’t.) NTFS quotas weren’t perfect – they only work per-volume, per-user, and they only report overages through the event log. So along comes Server 2008, with a new quotas capability. You have to install the File Server role and use the File Server Resource Manager console to implement these “new” quotas.
Problem is, the new quotas aren’t perfect, either. They work per-folder, which is good, and the overage notification is more flexible (also good); but the per-user feature is missing from the management console. Worse, the new quotas don’t interact with NTFS quotas. Microsoft even states on their website that “the two systems are not designed to work together.”
It’s increasingly easy to look at Windows and see all those layers of glue.
Recent posts:
Profiling PingWare
Some Java with your Java?
Fun with Server Core, Part II
