Skip to main content

Organizing your PowerShell Workspace

By

If you are like me, you have multiple monitors stretched across your desk. Hey, I will admit it, I am a PowerUser.  As both a Microsoft Certified Trainer, Network Administrator, and PowerShell evangelist, I need real estate.  I often develop my PowerShell code with the ISE and multiple Shell windows.  That way I can code in one, test in another, lookup help files, and test small chunks of code.  The problem comes around to which window is used for what?

Years ago, while visiting a software development company that was acquired by the company that I was working for, I observed one of their techniques for keeping track of which script was running what task.  Each script was monitoring a specific project or log on a server.  Each one of these tasks were assigned a foreground and a background color.  With this in mind, you can set specific foreground and background colors schemes for your development. Tack a look at this code.


Function Switch-HostColor
{
<# ========================================================
    Cmdlet: Switch-HostColor
    Author: Jason A Yoder
    Company: MCTExpert, Inc.
    Version: 1.0
    Date: June 10, 2013
   ======================================================== #>
[CmdletBinding()]
Param ([Parameter(Mandatory=$True)]
       [ValidateSet("RedOnBlack", "BlueOnBlack", "GreenOnBlack",
                    "YellowOnBlack","CyanOnBlack","MagentaOnBlack",
                    "BlackOnBlue")]
       $ColorScheme)
 
    Switch ($ColorScheme)
    {
         "BlueOnBlack"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Blue"
            $(Get-Host).UI.RawUI.BackgroundColor = "Black"
        }
        "RedOnBlack"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Red"
            $(Get-Host).UI.RawUI.BackgroundColor = "Black"
        }
        "GreenOnBlack"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Green"
            $(Get-Host).UI.RawUI.BackgroundColor = "Black"
        }
        "YellowOnBlack"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Yellow"
            $(Get-Host).UI.RawUI.BackgroundColor = "Black"
        }
        "CyanOnBlack"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Cyan"
            $(Get-Host).UI.RawUI.BackgroundColor = "Black"
        }
        "MagentaOnBlack"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Magenta"
            $(Get-Host).UI.RawUI.BackgroundColor = "Black"
        }
        "BlackOnBlue"
        {
            $(Get-Host).UI.RawUI.ForegroundColor = "Black"
            $(Get-Host).UI.RawUI.BackgroundColor = "Blue"
        }
    } # End: Switch ($ColorScheme)
   
    # Clear the host to enable
    Clear-Host
<#
.SYNOPSIS
Change the host color scheme.
 
.DESCRIPTION
Changes the host color scheme to help keep tasks performed in
different shells organized.
 
.PARAMETER ColorScheme
Specify a preset color scheme to change the host foreground and
background colors to.
 
.EXAMPLE
Switch-HostColor -ColorScheme BlueOnBlack
 
Clears the screen and displays all text in blue foreground and
black background.
#>
} # End: Function Switch-HostColor



This code has several defined color formats for you to use as examples.  Notice the use of the ValidateSet parameter attribute.  This provides for tab completion of the possible values for the parameter ColorScheme.  You can provide any color scheme that you wish.  One word of caution, make sure to use two sets of colors that will have a high contrast and not hurt your eyes.  One of the color schemes that I observed in use was magenta text on a bright yellow background.  Not a good idea.
Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Error icon when creating a GPO Preference drive map

By
You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the ma...
1 comment
Read more