remoting - invoke-expression port

I'm having issues using this, and I believe it is because IIS is running
on my remote machine and winrm using port 80.  How do I change the port
that it is listening on?


-- 
bradn901cb

Brad

bradn901cb wrote:
> I'm having issues using this, and I believe it is because IIS is running
> on my remote machine and winrm using port 80.  How do I change the port
> that it is listening on?
> 
> 

Is the remote machine Windows XP?  Does invoke-expression and/or 
start-psjob work locally on that remote machine?

If it turns out that it is IIS causing the problem:

I'd run "stop-service winrm", first, then this is the command:
winrm set winrm/config/Listener?Address=*+Transport=HTTP @{Port="81"}

I actually ran it from DOS because, then I didn't have to worry about 
escaping any characters.

The above assumes you have a pretty default winrm config running now.

Remember to use the -port parameter now.

Marco

-- 
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp

PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:

> Remember to use the -port parameter now.
> 
> Marco
> 

Oh, and remember to open up a new port for incoming TCP connections if 
you're using the client-side firewall.