Using cmdlets that are installed on local machine but not remote machine.

This topic contains 1 reply, has 2 voices, and was last updated by Profile photo of Richard Siddaway Richard Siddaway 6 months, 1 week ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #36805
    Profile photo of Jason Brynarsky
    Jason Brynarsky
    Participant

    Hi,

    Firstly, thank you for reading this.
    Secondly, please let me know if I'm thinking about this the wrong way.

    I and trying to gather users and groups which are assigned 'Local Admin' rights on about 500 remote servers. I've gotten most of the information using the various scripts out on the internet.

    Just curious of if this is possible.

    I've enabled powershell Remoting at my company.
    I've also been informed of a module called 'Carbon'. Seems to work great on my local workstation. Doesn't seem to be able to call out to a remote server though.

    Can I use 'Invoke Command' to pass the module through to the remote server, run the cmdlet, get the results on my local computer, and lastly uninstall the module from the remote server.

    Again. Am I going about this the hard way?

    Any help would be greatly appreciated.

    Thank you
    Jason

    #36806

    Basically no.

    When you're running Invoke-Command and calling cmdlets – you're calling them on the remote machine. Don't know what the licensing issues are but if its that useful you'll need to get it onto your remote machines.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.