Skip to main content

Playing with the ISE Profile

Since PowerShell 3 and 4, I’ve been teaching more of my PowerShell classes using the ISE rather than using the shell.  This is because the Intellisense really helps my students learn PowerShell.  One thing that I did not like about the ISE is that the cmdlet Start-Transcript could not be used in the ISE.  Now with PowerShell V5, you can. 

For those who have taken my PowerShell classes know that I have transcripts starting automatically in my Shell profile.  Well, time to do the same thing in the ISE.  My goal is to provide my students with a transcript of my activates from the ISE for their review after class.  First off, I need to create a profile for the ISE.

I can do this by Simply creating the correct profile file in my WindowPowerShell directory in my profile.

1

2

if (!(test-path $profile ))

{new-item -type file -path $profile -force} 

Here is the result:

     Directory: C:\Users\JASON\Documents\WindowsPowerShell

 

 

Mode                LastWriteTime         Length Name                                          

----                -------------         ------ ----                                          

-a----        3/15/2015   5:27 PM              0 Microsoft.PowerShellISE_profile.ps1    

 

image

Next I open the Microsoft.PowerShellISE_Profile.ps1 file and add in my transcript naming code.

1

2

3

4

5

6

7

8

9

10

11

12

13

# -- Automate PowerShell Transcription --

# Create a filename based on a time stamp.

$Filename = "$(Get-Date -Format "yyyy-MM-dd hh-mm-ss").txt"

$HD = $Env:HomeDrive

$HP = $Env:HomePath

$Path = "$($HD)$($HP)\Documents\WindowsPowerShell\ISE Transcripts"

# Turn on PowerShell transcripting.

Start-Transcript -Path "$Path\$Filename" -IncludeInvocationHeader

 

# Remove all trascript files older that 100 days.

Get-ChildItem -Path $Path |

    Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-100)} |

    Remove-Item

This code is very simple.  It creates a custom Date-Time stamped transcript file.  This helps if I have multiple ISE sessions open.  It also deletes old transcripts that are over 100 days old.  Close the ISE and open it.  You should be good to go.

Just remember, these transcript log files will get big, fast.  You may need to adjust the auto delete from 100 days to something less.  In line 12, the value –100 is the one to change.

Comments

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

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.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...