Slashdot Mirror

← Back to Stories (view on slashdot.org)

Ask Slashdot: Moving From *nix To Windows Automation?

Posted by timothy on from the setting-expectation-levels dept.

Zubinix writes "I have a background in doing automation in a Unix/Linux environment using scripting languages such as perl and bash shell, as well as ssh for remote scripting. My next project will be in the Windows environment so what approach and methodology is best for developing, say, the automation required for a test system? I don't want to use things like Cygwin, as I need to integrate with Windows applications such as Exchange and Sharepoint. Is there a list of should and should not dos when it comes to Windows automation?"

2 of 427 comments (clear)

  1. List... by frank_adrian314159 · · Score: 1, Troll

    Is there a list of should and should not dos when it comes to Windows automation?

    Yes.

    1. Do not do Windows automation.

    That is all...

    --
    That is all.
  2. Re:Don't do it... by oakgrove · · Score: 1, Troll
    Hahaha. You actually think ps is a substitute for bash, screen, puppet, openssh, expect, etc.? What a fucking joke. And you got a +5? I know you shills come here because Slashdot is the "happening" spot and fertile Astroturf ground but, trust me, it won't last. What do you do when this site has lost every shred of reputation and credibility because you and your ilk have turned it into a ms circle jerk cesspool? Go back to engadget?

    Posted as me. 'Cause I care.

    --
    The soylentnews experiment has been a dismal failure.