Automating the world one-liner at a time…
We recently did a short internal "who are we" video about our organization (MSD). I don't know how it got out into the wild but you can check it out over on YouTube HERE.
It's 3 minutes, fun and there are a couple scenes of me saying things that are either really stupid or really clever. (seemed clever at the time but upon viewing ... well... :-) )
Jeffrey Snover [MSFT] Windows Management Partner Architect Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
Any chance of a JS/PowerShell poster for New Zealand ??
Things that may have seemed good at the time but are really, really, really stupid things to do in the real world, which is where I work. Sometimes I wonder where the world is that MS is in. We configure SSIS on one of our servers and found, that by default, is constantly writing to the event log ending up with a huge log. grrrrrrrrrr!
So being a script guy I like to automate things if possible. I started with borne shell, kshell, awk, dcl, tcl, perl and python.... Finally, MS decides to deliver a shell where most OSs have had it for years. For what should have been part of the OS in the first, I have to go through the stupid "Verify that you have a real copy of windows bs". MS is always reminding you why Linux is good alternative.
But for the present I have to work in a Win environment. Okay, I install Powershell. It looks promising. I mucked around with it for a couple of weeks then I realize by DEFAULT Powershell is writing to the Windows Powershell event log. Whoa!, excuse me!!! Why would a shell be writing to a log without me telling it to do so? Bash does not. KShell didn't. DCL didn't. CShell did not. GRRRRRR! DUDE!
Now I have to go looking around how to turn it OFF. Just when I thought Powershell might be a good tool for us I run into the 'by default logging on install'. Most every one around here uses either Perl or Python. I thought maybe I could end the religious war on the windows platforms by going to Powershell. But I have to tell you that "default logging" is something that really POs the admins around here so they quickly were turned off by Powershell.
> I mucked around with it for a couple of weeks then I realize by DEFAULT Powershell is writing to the Windows Powershell event log
This was part of an effort to get everything in the OS to have a health model. In theory this was a great idea. In practice the value has yet to emerge (at least for us).
Other than being conceptually offensive, does it cause actual harm/degradation of the system?
Jeffrey Snover [MSFT]
Windows Management Partner Architect
Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
Tell us more about PowerShell Nutrition Facts.
Are you hiring ? :) I really like doughnuts .
> Are you hiring ?
The general MS Resume submission tool is via:
External, searching specifically for PowerShell related positions:
Great video - looks like a fun and productive environment to work in.