Remove IIS Log Files (4-2) --- Make Server Allows ports for PowerShell Remoting

Note: This article was published on 02/27/2025.

Although this topic is ndependent, but it was derived from the Remove IIS Log Files project. So we merge this article into the series of articles for REmove IIS Log Files.

This series of articles are to discuss a task to remove IIS Log Files. We start from doing the task manually, then make automation, and the last deploy the automation to pipelines (different servers):

• Remove IIS Log Files (1) --- Manually
• Remove IIS Log Files (2) --- Automation by Windows Task Scheduler
  • Remove IIS Log Files (2-1) --- Handle Group User Accounts 
  • Remove IIS Log Files (2-2) --- Add "Log on as a batch job" Right to a user 
• Remove IIS Log Files (3) --- Deploy VBScript Automation by Pipeline
• Remove IIS Log Files (4) --- Deploy PowerShell Automation by Pipeline
  • Remove IIS Log Files (4-1) --- Managing Sensitive Info in AWS
  • Remove IIS Log Files (4-2) --- Make Server Allows ports for PowerShell Remoting  --- this article
  • Remove IIS Log Files (4-3) --- AWS security group on the ec2 needs to Allows ports for PowerShell Remoting

This is a working note to use AI to solve a specific problem. AI tool, we use Microsoft Copilot,

Issue

Solution by AI assistance

Instruction: "does server allow ports for PowerShell remoting?",

Instruction:"How to check if server allows ports for PowerShell remoting?"

Check:

A good server should be like this:

Instruction: "how to make server allows ports for PowerShell remoting?"

Implementation:

Instruction: configure HTTPS for more secure communication

Implementations:

AI-2:

AI-3, 4

Ai-5, 6

Recheck the status:

It seems still not working. Run the pipeline, got more specific error and suggestion:

Run it:

Ask AI to do it:

Following AI:

ReCheck --- good