Category: Powershell (Page 2 of 2)

A sample implementation of windows balloon notification for powershell is as follows:

Add-Type -AssemblyName System.Windows.Forms

function FnShowBalloon {

    [CmdLetBinding()]
    param($title, 
           $message, 
           [string] $icon = 'info', 
           [int] $delay = 20000, 
           [int] $sleep=0)

    Switch($icon.ToString().ToLower()) {
        'warn' {$iconInstance = [System.Windows.Forms.ToolTipIcon]::Warning}
        'error' {$iconInstance = [System.Windows.Forms.ToolTipIcon]::Error}
        'info' {$iconInstance = [System.Windows.Forms.ToolTipIcon]::Info}
        default {$iconInstance = [System.Windows.Forms.ToolTipIcon]::None}
    }

    $notification = New-Object System.Windows.Forms.NotifyIcon
    $path = (Get-Process -id $pid).Path
    $notification.Icon = [System.Drawing.Icon]::ExtractAssociatedIcon($path)
    $notification.BalloonTipIcon = $iconInstance
    $notification.BalloonTipTitle = $title
    $notification.BalloonTipText = $message
    $notification.Visible = $true
    $notification.ShowBalloonTip($delay)

    if ($sleep -gt 0) {
        Start-Sleep -s $sleep
        $notification.Dispose()
    }
}

The FnShowBalloon  function can be used as follows:

FnShowBalloon -title "Hello World" -message "This is a sample message" -icon info

It is recommended to have the following command somewhere in the beginning of the powershell script file:

cd /d $PSScriptRoot

The presence of this will run all the commands after it with respect to the location of the running powershell script file.

Instead of using > to redirect the output into a file, pipe it to out-file cmdlet.

The out-file cmdlet allows some useful parameters as follows:

To redirecting the output of the dir command to dir.txt file, use the following command:

dir | out-file -encoding ascii -filepath "dir.txt"

This setting is necessary for TLS handshake.

Update the your powershell profile with the following:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

Reference

• https://docs.microsoft.com/en-us/dotnet/api/system.net.servicepointmanager?view=netframework-4.7.1
• https://docs.microsoft.com/en-us/dotnet/api/system.net.securityprotocoltype?view=netframework-4.7.1

1. Execute the following to check the PROFILE variable:

   Get-Variable | Where-Object {$_.Name -like "PROFILE"}

2. Test if its actually existing on the disk using the following command:

   Test-Path $PROFILE

   This will return True if the profile is already existing on the disk and ready for editing. If this returns False execute the following command:

   New-Item -Path $PROFILE -ItemType "file" -Force

1. Get the current execution policy using the following command and remember it:

   Get-ExecutionPolicy

2. Set the execution policy to unrestricted using the following command:

   Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Unrestricted

3. Execute the unsigned script.
4. Return the back execution policy to what it was (i.e. from step 1). Using the following command syntax similar to step 2:

   Note: This is not required if you know that you are only running the script that you trust.

   Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy <EXECUTION_POLICY_FROM_STEP1>

Using the default network credentials

(New-Object System.Net.WebClient).Proxy.Credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials

Using a different credentials

Using Get-Credential

(New-Object System.Net.WebClient).Proxy.Credentials = Get-Credential

Using NetworkCredential Object

(New-Object System.Net.WebClient).Proxy.Credentials = New-Object System.Net.NetworkCredential(<username>, <password>)

Note: You can add any one of these to your powershell profile to allow it to have network connectivity by default using proxy.