PowerShell Profiles and Prompts

To get the path of your PowerShell profile, you can use the built-in $Profile variable. If your profile exists, you can open the profile in notepad using the Invoke-Item cmdlet.

clip_image001

If the profile doesn't exist, as you create it using the New-Item cmdlet. To make sure you can create the file even if part of the path doesn't already exist using the -Force parameter.

Once the profile has been created, you can open it with the Invoke-Item cmdlet.

clip_image002

To customise the PowerShell prompt, you can create a prompt function like I have below.

clip_image003

clip_image004

You could include some Environmental variables in the prompt function to make the PowerShell prompt provide some very useful information, for example:

clip_image005

clip_image006

You can also customise the UI using your profile. This is done by modifying properties of the $Host built-in variable.

clip_image007

clip_image008

Popular posts from this blog

Get local computer UUID/GUID using Windows Powershell

Use the following syntax to get the local computer's UUID/GUID using Windows Powershell: get-wmiobject Win32_ComputerSystemProduct  | Select-Object -ExpandProperty UUID Add -computername after the WMI class to find a remote computer's UUID, example: get-wmiobject Win32_ComputerSystemProduct -computername RANTPC | Select-Object -ExpandProperty UUID
Read more

gPLink and gPOptions

gPLink is a property for sites, domains and organisational units that contains a prioritised list of GPOs linked to the node. gPOptions is a property that contains all Block Policy Inheritance settings for the node. To manage GPO links on a node, you must have read and write access to the gPLink and gPOptions properties.
Read more

PSLoggedOn Getting Started on Windows Server 2008 R2

Image
PSLoggedOn is a tool I downloaded to allow me to find out which computers a user is currently logged on to. Getting it up and running wasn’t exactly easy. I’m running a Windows Server 2008 R2 test environment. The first error I encountered was: Error browing network: The list of servers for this workgroup is not currently available. Note: I kept the spelling mistake from the error message to make it easier to find via search engines. To get past this error, you have to enable and start the “Computer Browser” service. Then I started getting the error telling me that the Administrator is not logged on. That’s simply not true because I am logged onto another server (Name: ELARA): I turned the firewall OFF OFF OFF (It is a test network after all). I enabled Network Discovery and to do that I went on a service starting frenzy: DNS Client, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host, Computer Browser After all that, I ran the script against the se
Read more