Use the right tool for the job. If Windows fits your/ the companies' needs, then it's the right tool. If it's another OS, then that's fine too.
On Jan 27, 2011, at 9:13 PM, Michael Ryder wrote: > Yes, Atom, that's exactly what I meant. > > And no, Robert, I wouldn't be sitting on my hands waiting for months for a > solution, I'd be working with tech support to find a resolution, or scripting > my way around the problem. > > In my experience, at least in the last 5 years, the Windows tools I use are > all stable, all work and all do what I need. Why settle for less? > > Wait. Are you all telling me that I'm somehow lacking because I don't go in > "under the covers?" I'm not really concerned about doing a good job unless > I'm writing code? I'm a "new person" because I manage Windows systems? That > I'm using training wheels? > > If that's the prevailing opinion of LOPSA members, then I think I may have > identified why you seem to be light on Windows sysamins. Actually, it's not. I don't want to hack at code. I want to get my job done. It may be a question of what under the covers is, but I'm not really wanting to fight the products that I've bought. ---- I've used Windows for years, admin-ing things from SBS & Exchange from 5.5 on. I've also been heavily involved in running linux systems. The vast majority of windows SA's just aren't interested in the user groups the same way as coders & *nix SA's are. There is a much higher level of the One True Way (MSFT's) in windows, dictated by the way the software works. You aren't going to use another DHCP server, or DNS server most of the time. You'll use MSFT's. It's nicely integrated into your HA distributed LDAP/Kerberos servers, and works fairly well. Linux lets you choose around the edge cases more, but you have to pay for that with effort. On the other hand, loading data into a GUI can be.. painful, vs using text tools to do so for a text file. Integrating a copy of a database table into the mail servers to create incoming accounts is just not going to be a happy thing in Windows. Then again, really solid calendaring isn't nicely built into Linux. I will say that the most knowledgeable Windows SA's I know are big fans of Powershell. Group Policies give enormous power. The flip side is that *nix has a history of being to automate things below the gui- and gui's are just plain hard to automate, unless they're instrumented. The ability to build 50 servers to do slightly different things is substantially easier right *now* in the *nix world, if it's not what MSFT thought you'd want to do. The world has come far from needing 1 SA for every 20? machines. Matthew _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
