Ooh. Popeye's red beans and rice. I haven't had that in a while since they closed the Popeye's on this side of town.
Totally agree on SQL 2008. We're just now trying to migrate our DBs to SQL 2005. We're trying to leverage 64-bit 2005 for some heavy apps and are running into all kind of problems with DB connector compatibility.
Also torn on Exchange 2007. New MMC 3.0 interface for the Admin Console really blows in my opinion. From what I hear it's also unstable as all get out. Whoever decided that some functions had to be performed via PowerShell should be slowly tortured. All functions should be available via the Admin Console with PowerShell available for scripting if it's so desired.
SCCM 2007 is not much different from SMS 2003 R2 with all of the feature packs. The OS deployment components are really targeted for WIM images (Vista). We're probably going to skip Vista entirely and go to Windows 7 in 2009/2010. I'll probably wait for SCCM 2007 R2 which is currently in beta.
Hyper-V can't hold a candle to VMware ESX VI3.
The free software is what I really wanted.
...lunch at Popeye's would be a bonus.[Dinner]
Open source? Too funny. We have a ton of software, much of it not suited to a Linux client or server. We have a few RedHat servers that do basic things like log aggregation. Heavy lifting with open source is a PITA. MySQL just doesn't compare to Oracle.
I have 64-bit Ultimate running on this desktop in another partition in order to take full advantage of the memory. I have a 32-bit newsreader app that locks the system up hard (have to give it the finger). So much for application isolation. 64-bit also doesn't want to play nicely with the Xbox 360 as a media extender. If you think your new Vista system is fast, you'll be surprised how much faster it is with XP. When I'm on XP, I find I'm not watching the spinning blue ******* or watching applications fade to white when they become unresponsive or crash. Did I mention that Vista blows?
...but I also spent a couple of hours today trying to figure out why my 15" Macbook Pro (Leopard 10.5.2) would connect to an 802.11g network fine with WEP, but would connect to WPA but not pull a DHCP address. Apparently all of the upgrades and patches goobered up the keychain on the system. I deleted the multiple entries for the WPA SSID, recreated the WPA connection which created a new single key, and voila, WPA connection with a valid DHCP address. So much for Apple being the answer to whatever was the question. Apple systems are expensive, they fail much more often than our standard HP desktops and notebooks, and we require 1 person to support 80 Macs. Mac users seem to need a lot more hand-holding. We have 2 people supporting 20,000 PCs.
This stuff is hard.[Faint]
Nice talkin' shop with you guys. At least I'm not opinionated about anything...
