joeware - never stop exploring... :)

Information about joeware mixed with wild and crazy opinions...

PowerShell

by @ 6:54 pm on 3/28/2008. Filed under tech

I don’t use it, don’t really intend to use it unless absolutely forced kicking and screaming to. Will not write a provider for AdFind nor AdMod nor any of my tools for it.

 

     love joe

Rating 3.00 out of 5

8 Responses to “PowerShell”

  1. Darren says:

    And, if someone were to write a powershell version of adfind or admod, would you tacitly and begrudgingly support it or would you kick them in the teeth the first chance you got???

  2. Laura says:

    As an AD person, I don’t see it. Really. I just don’t see the AD efficiencies that I’m meant to obtain from PoSh that I don’t already have with adfind/mod.

    Maybe it’s a lack of an actual predictable verb-noun syntax for AD within Powershell, which is apparently what a lot of the hype is about, and I’ll change my mind once we get that.

  3. Jeffrey Snover says:

    If you have no need – why would you?
    Most people don’t find themselves as content as you are so PowerShell is an investment they are willing to make. We treat that investment with a lot of respect and try to make it a REALLY good deal.

    We are, above all else, advocates of whatever works for the user.

    Cheers!

    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

  4. Brandon says:

    Joe… wheres the love?

    Powershell is your savior. It can save you hours of coding 🙂

    Really, Dean needs to do a better job explaining the glory that is Powershell.

  5. joe says:

    Darren: Well I wouldn’t support it as in if someone has a problem I will figure it out, but as I told JoeK when he mentioned writing .NET versions of AdFind/AdMod… go for it (still waiting on that one…). 😉 If someone asks about it I will say I really don’t know too much about it just like I currently do with the ds* toolset.

    Laura: No comment. 😉

    Jeffrey: Hi! Good response. I am not telling anyone else not to use it, in many cases for many people it is probably their best bet, in fact I just responded to someone the other day when they asked what scripting language they should be learning, they should *probably* pick up PowerShell if they intended to do everything in the MSFT world (and didn’t need to do anything *on*[1] Server Core).

    Brandon: LOL. Actually this post was a direct result of a conversation with Dean but it wasn’t him trying to convince me of anything. He knew what my responses would be. He was telling me what someone else said and that it was said I should make providers for my tools for PowerShell… I started laughing. Just not going to happen.

    I was asked to join the MONAD beta early on and did. I was initially pretty excited, then once I saw all of the .NET dependendies I walked away from it. .NET may make some people’s lives easier and great but I don’t see it for me, at least not for Fat Client stuff. I know I know, people are all saying, that will change!!! Maybe… but then I had people in 1996 telling me how I was going to be learning to write in Java too and I said it was highly unlikely but if it happened it happened. That company was gung ho do lets use Java and sent most everyone to classes for it, I still haven’t written a single line of Java, still don’t have a desire to, and I don’t believe they do it anymore either.

    I am really disappointed in Exchange using that exclusively for managing stuff in 2007. Stupid move. WMI and CDOEXM sucked but they weren’t as fat and slow and inefficient as what they did with PowerShell for Exchange. When they were talking about it on the EHLO blog way back when I made my thoughts known on the model. It doesn’t scale very well. Say you want to run a script across a whole enterprise of 200,000 mailboxes spread globally across some 50-75 Exchange servers… How fast is that going to run as you pull back info you have no need for? If they were going to do a major change, it should have been to put all the functionality into really using AD properly and then anyone who could manage AD properties and objects could then manage Exchange and can use any platform and any language they are familiar with.

    joe

    [1] Note I am not saying against, I am saying on. So please no one tell me how you can run something remotely against Server Core… Sure got it, I want to run things on server core machines though. There is a high probability in fact one of my main desktop machines will be a Server Core machine.

  6. Brandon says:

    Joe, That someone that Dean was talking about was me 🙂

    I completely get that you (joe) would not need or care about Powershell, but it will help your users tremendousely. There is a HUGE advantage you get when dealing with objects over TxT.

    To be clear, I greatly appreciate your time and effort for ADFind/ADMod and the willingness to give it away. I am sure you could make a ton of money with it.

    Anyway, Dean says he is very excited to hear us talk about this in person 🙂

  7. Brandon says:

    p.s. Another thing I will give you. .NET is horribly slow compared to directly calling the APIs.

  8. joe says:

    Brandon: The tools that I put together are first and foremost things I need and want to use; then I share them with others if I feel there would be enough interest. I will add features to existing tools but building something from scratch that I don’t personally need doesn’t make sense to me as I won’t fully appreciate the need. Possibly if I thought I could make money on doing something for PoS I would do it, but even then I would be hesitant, lots of things I could likely make money on that I do enjoy.

[joeware – never stop exploring… :) is proudly powered by WordPress.]