To the point, I strive to avoid wasting my time/money or that of my customers on Microsoft's current offerings, other than when it is forced on me. This was the case today at about 12:30 EDT today when a 2000 DHCP server failed, and I assisted in diagnosing a resulting problem in an application. If this was the first failure in the past quarter or two, it would be one thing; it was the second this week. To anticipate the question, yes, there was a alternate server and a bevy of MS-certified monkey spankers were asked to lend their insights. "Uh, server needs a reboot.". So much for manageability.
In the case of Squeaky Server 7, I had enough from versions 4.21a to 6.5, period. I have reliable reports from sources I trust as to the comparative merits of SS7, and I am indeed blessed to not have to deal with it personally. My reporters have the breadth and depth of experience to know the difference between you-know-what ( SS7 ) and Shinola ( DB2, Oracle ). They are far from the typical group of MS-certified Windows-addled computer-operated mouse monkeys one finds flogging the Windows log.
There's an old saying: burn me once, shame on you; burn me twice, shame on me. This applies nicely to Microsoft's feeble server products. As a matter of fact, MS Feeble Server sounds like a pretty descriptive product name, I'll have to remember to use it here more often. |
