Windows – Monitor daily, weekly and monthly bandwidth usage totals in Windows Server 2008 R2

Windows Server 2008 and Windows Server 2008 SP2 are the same operating system, just at a different service pack level (Windows Server 2008 started at the SP1 level because it was released quite a bit after Windows Vista and SP1 was already out).

Windows Server 2008 R2 is the server release of Windows 7, so it's version 6.1 of the O.S.; it introduces quite a lot of new features, because it's actually a new release of the system. This is a good place to start: http://www.microsoft.com/windowsserver2008/en/us/whats-new.aspx.

There are also differences at the GUI level, because WS2008R2 uses the same new GUI introduced with Windows 7 (new taskbar, etc.).

Depending on what kind of applications you're developing, they may or may not encounter problems on different O.S. releases; you should definitely check MSDN.

The single most important point: Windows Server 2008 R2 exists only for 64-bit platforms, there's no x86 version anymore.

I don't know of a utility that provides this directly but it's fairly straightforward to build a script (using powershell, perl, python ..) to identify the files that meet your criteria, drop the fully qualified names (e.g. d:\incoming\something\filename.ext ) into a flat text file, one file name per line and then have your compression utility create an archive from that list file e.g.

7z -a output.zip @filelist.txt

If you wrap the whole thing inside the script then it's trivially easy to assign the type of archive names that you specified.

Added a Powershell example.

$archiveroot="c:\temp"
$oldest = (get-date) - (new-timespan -day 31)
$archivename="Incoming-" + $oldest.year + "-" +$oldest.month+".7z"
$filelist= get-childitem $archiveroot -recurse | where-object {$_.lastwritetime -gt $oldest}
$filelist | format-table -hideTableHeaders FullName | out-file -encoding utf8 -filepath lastmonthsfiles.txt
& .\7z.exe a $archivename `@lastmonthsfiles.txt

It's not quite a one liner, you will need to point it properly at the 7-Zip exe, add some parameter handling, some logging\error handling and it should clean up the working files but it's a pointer in the right direction.