Skip to content

AvoidUsingComputerNameHardcoded.md

Latest commit

 

History

History
56 lines (43 loc) · 1.08 KB

AvoidUsingComputerNameHardcoded.md

File metadata and controls

56 lines (43 loc) · 1.08 KB
description Avoid Using ComputerName Hardcoded
ms.date 06/01/2026
ms.topic reference
title AvoidUsingComputerNameHardcoded

AvoidUsingComputerNameHardcoded

Severity Level: Error

Description

Hard-coded computer names can expose sensitive information and reduce script portability. The ComputerName parameter should always be parameterized or dynamically assigned to ensure scripts are flexible and secure. Use parameters, environment variables, or dynamic values instead of hard-coded computer names.

Example 1

Noncompliant

Function Invoke-MyRemoteCommand ()
{
    Invoke-Command -Port 343 -ComputerName HardcodedRemoteHostname
}

Compliant

Function Invoke-MyCommand ($ComputerName)
{
    Invoke-Command -Port 343 -ComputerName $ComputerName
}

Example 2

Noncompliant

Function Invoke-MyLocalCommand ()
{
    Invoke-Command -Port 343 -ComputerName HardcodedLocalHostname
}

Compliant

Function Invoke-MyLocalCommand ()
{
    Invoke-Command -Port 343 -ComputerName $env:COMPUTERNAME
}