Home

WAC should has ability to instruct powershell to connect client via port 80

%3CLINGO-SUB%20id%3D%22lingo-sub-729426%22%20slang%3D%22en-US%22%3EWAC%20should%20has%20ability%20to%20instruct%20powershell%20to%20connect%20client%20via%20port%2080%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-729426%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20what%20I%20understand%20is%20windows%20admin%20center%20using%20PowerShelI%20to%20connect%20to%20targets%20%2Cthat%20is%20manage%20target%20via%20Powershell%20%2C%20However%2Cin%20my%20case%2C%20the%20default%20port%205985%20is%20block%20by%20security%20software%20on%20my%20windows%2010%20client.%20But%20winrm%20can%20listen%20on%205985%20and%2080%20at%20the%20same%20time%2C%20by%20enable%20EnableCompatibilityHttpListener%20%2Cthan%20poewershell%20can%20reach%20remote%20target%20with%2080%20%2C%20but%20in%20WAC%20there%20is%20no%20way%20to%20instruct%20powershell%20to%20use%20another%20port%20%2Conly%20the%20default%20behavior.WAC%20should%20make%20an%20improvement%20on%20this%20matter.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20do%20you%20think%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-729434%22%20slang%3D%22en-US%22%3ERE%3A%20WAC%20should%20has%20ability%20to%20instruct%20powershell%20to%20connect%20client%20via%20port%2080%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-729434%22%20slang%3D%22en-US%22%3EFor%20this%20question%20I%20already%20post%20in%20UserVoice%20%2C%20but%20no%20one%20care.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-730880%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%20should%20has%20ability%20to%20instruct%20powershell%20to%20connect%20client%20via%20port%2080%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-730880%22%20slang%3D%22en-US%22%3Eany%20one%20%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-735447%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%20should%20has%20ability%20to%20instruct%20powershell%20to%20connect%20client%20via%20port%2080%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-735447%22%20slang%3D%22en-US%22%3ESeems%20no%20discuss%20here%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-745546%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%20should%20has%20ability%20to%20instruct%20powershell%20to%20connect%20client%20via%20port%2080%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-745546%22%20slang%3D%22en-US%22%3E%3CP%3EHere%20is%20the%20appropriate%20uservoice%20item%20that%20is%20tracking%20this%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwindowsserver.uservoice.com%2Fforums%2F295071%2Fsuggestions%2F33981802%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwindowsserver.uservoice.com%2Fforums%2F295071%2Fsuggestions%2F33981802%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
alexluplus
New Contributor

Hello, what I understand is windows admin center using PowerShelI to connect to targets ,that is manage target via Powershell , However,in my case, the default port 5985 is block by security software on my windows 10 client. But winrm can listen on 5985 and 80 at the same time, by enable EnableCompatibilityHttpListener ,than poewershell can reach remote target with 80 , but in WAC there is no way to instruct powershell to use another port ,only the default behavior.WAC should make an improvement on this matter.

 

How do you think?

 

4 Replies
For this question I already post in UserVoice , but no one care.
Related Conversations
IIS extension is not working - WAC 1909
HotCakeX in Windows Admin Center on
11 Replies
PacketMon Components are not loading in WAC 1909
HotCakeX in Windows Admin Center on
2 Replies
Remove-CalendarEvents cmdlet does not work
kirboronin in Office 365 on
8 Replies
Skype Room System app on Windows Store
David Phillips in Skype for Business IT Pro on
23 Replies