[MSH] Local and remote cmdlet access in PowerShell v1?

Discussion in 'Scripting' started by Andrew Watt [MVP], Apr 25, 2006.

  1. I have been listening to an Exchange 12 webcast this evening. One of
    the interesting snippets of information is that 90% of "Exchange
    cmdlets" (my term) can access a remote machine.

    My understanding is that "ordinary" PowerShell v1 wasn't to have
    remote access functionality.

    Can someone from the team explain the situation please? Have I
    misunderstood something? Or, if I understood correctly, why do
    Exchange cmdlets get remote access capabilities and ordinary cmdlets
    don't?

    Thanks

    Andrew Watt [MVP]
     
    Andrew Watt [MVP], Apr 25, 2006
    #1
    1. Advertisements

  2. I'm not from "the team", but just a wild guess: Exchange implemented remote
    access by having their cmdlets talk directly to remote Exchange servers via
    some network protocol like DCOM/HTTP etc.

    In a same way one could write cmdlets for SQL Server and the remoting would
    be done with ADO.NET/SMO using TDS behind the covers.
     
    Jouko Kynsijärvi, Apr 25, 2006
    #2
    1. Advertisements

  3. This is correct. Exchange's cmdlets include their own custom communication
    capabilies.
     
    Lee Holmes [MSFT], Apr 25, 2006
    #3
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.