Recent windows client and server operating systems like Windows 10, Windows Server 2008 onwards, supports advanced firewall versions and they have mainly 3 profiles.DomainPublicPrivate profile.To get the setting using GUI, you need to search in the box Windows Firewall with Advanced Security or Windows Defender Firewall with Advanced Security. Then you can see in the console that 3 available profiles.The above same settings can be viewed with the PowerShell Get-NetFirewallProfile command.PS C:\> Get-NetFirewallProfile Name : Domain Enabled : True DefaultInboundAction : NotConfigured DefaultOutboundAction : NotConfigured AllowInboundRules : NotConfigured AllowLocalFirewallRules : NotConfigured AllowLocalIPsecRules : NotConfigured AllowUserApps : NotConfigured AllowUserPorts : NotConfigured ... Read More

Earlier days we were using telnet clients to check the remote port connectivity, in fact, we are still using it with cmd and PowerShell but this feature is not by default installed in OS and some companies have restrictions on installing new features including telnet.We can leverage PowerShell to test remote port connectivity without installing telnet and with the use of the Test-NetConnection command. This command is also very useful for other diagnostics but we are focusing here for the remote port check.To check if the remote port is open or not we can use the Test-NetConnection command and it ... Read More

To change, add or remove security permissions on the files or folder using PowerShell you can use the Set-Acl command. The best way to set the permission is to copy the permissions from another file or folder if you need the same permissions on the destination path.For example, I want the same folder permissions of the source C:\Shared\ to the destination folder path c:\shared1 path. You can use any destination path, it could be the remote shared UNC path.See the difference in the above security permissions, the Shared named folder has one additional permission assigned (LABDOMAIN\Delta). We will copy the ... Read More

To view the NTFS permission with PowerShell, we use the Get-ACL command. This command is supported in PowerShell version 5.1 or later. Generally how we get the security permission of the folder in the Windows OS using GUI, To get the same permissions shown above using PowerShell, use the below command.Get-Acl C:\SharedPS C:\> Get-Acl C:\Shared Directory: C:\ Path      Owner     Access ----      -----     ------ Shared BUILTIN\Administrators NT AUTHORITY\SYSTEM Allow FullControl...You can compare the first image with the above output. You can compare the Owner of the folder and it ... Read More

Get-Error cmdlet was introduced in PowerShell v7. It displays the most recent error messages from the current session.When you check the get member of this command, its output is in the form of PSExtendedError so whatever the output is produced by this command is in a detailed manner and so this command is very helpful in troubleshooting error messages.PS C:\> Get-Error | gm TypeName: System.Management.Automation.ErrorRecord#PSExtendedErrorWe will write one command in the PowerShell console which is ultimately generate an error.PS C:\> Get-ChildItem c:otexist Get-ChildItem: Cannot find path 'C:otexist' because it does not exist.The above directory does not exist. Let’s get a ... Read More

$Errorview variable determines the display format of the error message in PowerShell. Before PowerShell 7 there were mainly two views, Normal View (Default view)Category ViewWith PowerShell version 7, one new additional error view category is included and now there are 3 $ErrorView categories for version 7.Concise View (Default)Normal ViewCategory ViewWe will understand each view one by one.A ) Normal ViewIt is the default view before PowerShell version 7 and it produces the detailed multiline errors and bit noisy. It includes the exception name, category, line number of the error, etc.$ErrorView = 'NormalView' Get-ChildItem C:\NoDirectoryOutputGet-ChildItem : Cannot find path 'C:\NoDirectory' because ... Read More

PowerShell version 7 has introduced a few new null operators. They are as below.Null-Coalescing operator - ??Null Conditional Assignment Operators - ??=Null Conditional member access operators - ?. and ?[]a. Null-Coalescing operator - ??Null Coalescing operator ??evaluates the left-hand side condition or operand and if it is null then evaluates the right-hand side operand otherwise provides the value of the left-hand side operand.For example, Without the Null-Coalescing operator, we would have written a script like as shown below, $Name = $null if($Name -eq $null){"Name is Null"} Else {"PowerShell"}The above same condition can be written with the ?? operator.$name = $null ... Read More

The validateCount attribute in PowerShell function is to validate the length of an array, which means that you can pass the specific number of arguments into the parameter. In the below example we need array should contain a minimum 1 and maximum 4 values when we pass the values. For that, we will write the below script, Function ValidateArray {    Param (       [ValidateCount(1, 3)]       [String[]]$Animals    )    return $PSBoundParameters }OutputPS C:\> ValidateArray -Animals Cow, Dog, Cat Key Value --- ----- Animals {Cow, Dog, Cat}The above output is valid but when we pass ... Read More

The ValidateScript attribute is to validate the script before entering inside the function. For example, let say you want to validate the path of the file, validate the remote computer connectivity, etc. We will take here remote server connectivity example.Without the ValidateScript attribute, we would have written the script as shown below.Function Check-RemoteServer {    param (       [string]$Server    )    if(Test-Connection -ComputerName $Server -Count 2 -Quiet -ErrorAction Ignore) {       Write-Output "$server is reachable"    } else {       Write-Output "$Server is unreachable"    } }OutputPS C:\> Check-RemoteServer -Server asde.asde asde.asde is ... Read More

The ValidateLength attribute in PowerShell is used to validate the length of the String. Generally how we write the command without the mentioned attribute is using the Length method and if/else condition for the string. For Example, Function ValidateStorageName {    param (       [String]$StorageName    )    if(($StorageName.Length -gt 3) -and ($StorageName.Length -lt 15)) {       Write-Output "`nStorage Name validated"    } else {       Write-Output "`nStorage Name validation failed"    } }Output−PS C:\> ValidateStorageName -StorageName Alpha Storage Name validated PS C:\> ValidateStorageName -StorageName CN Storage Name validation failedWith the ValidateLength attribute, else ... Read More