I've been doing a bit of Grails development lately, and if anyone is interested in a plugin that lets them use the U of MN Web template, just drop me an email.
I'm also working on a plugin for using Central Authentication via Spring Security. I'll post when that is finished and available.
I had to setup a new print server today, and though Windows Server Core would be appropriate. As I typically administer Linux boxes, it seemed like a good idea.
I was able to get the server installed, setup, and joined to AD in a relatively short amount of time. In fact I only had to issue 9 commands before I was finished. This is on par with what I need to setup Linux servers. It gave me a warm fuzzy feeling I hadn't had since the days of MS DOS 6.22.
Then it came time to manage this server using Microsoft's Print Management Server. My setup is a 64-bit Enterprise Windows 7 workstation, and my Windows Server 2008 r2 box was also 64-bit. I was able to connect to the print server, install a handful of 64-bit printer drivers and install the TCP/IP printer ports.
I hit a wall while trying to add a printer. Why? It appears that the "Add Printer" wizard in the Print Management MMC console only knows how to list 32-bit drivers! This was very very annoying. I had to setup and install an entirely separate 32-bit Windows 7 Enterprise workstation, join it to the domain, and install 32-bit drivers via Print Management console before I was able to "Use an existing printer driver on the computer".
