Skip to main content

Automatically create a log of your PowerShell sessions

In my October 3rd article, I wrote about using the PowerShell transcript feature to create a log file of everything you do.  This is a good idea, but it is a manual task.  Here is how you make it automatic.  We are going to use your PowerShell profile.  If you have not yet created a profile, take a look at my blog entry on September 24, 2012.

First, create a location to store your transcripts.  This file will contain a lot so it is best to get it organized now. My file is in My Documents in the PowerShell\Transcript folder.  You put yours where it makes sense to you.

Now, open your profile.  In PowerShell, type PowerShell_ise $Profile.

Enter this set of code in your profile.

# -- Automate PowerShell Transcription --
#
Create a filename based on a time stamp.
$Filename = ((Get-date).Month).ToString()+"-"+`
((
Get-date).Day).ToString()+"-"+`
((
Get-date).Year).ToString()+"-"+`
((
Get-date).Hour).ToString()+"-"+`
((
Get-date).Minute).ToString()+"-"+`
((
Get-date).Second).ToString()+".txt"
# Set the storage path.
$Path = "C:\Users\Jason\Documents\PowerShell\Transcript"
# Turn on PowerShell transcripting.
Start-Transcript -Path "$Path\$Filename"
# ---------------------------------------

This will start the transaction functionality every time you start the PowerShell environment, and put it in the folder specified in the –Path parameter.  Now save your profile.  Close the shell and reopen it.


Your session will start similar to this:


Windows PowerShell
Copyright (C) 2012 Microsoft Corporation. All rights reserved.


Transcript started, output file is C:\Users\Jason\Documents\PowerShell\Transcript\8-12-2012-19-32-48.txt
PS C:\Users\Jason>


Take a look in your designated log location, you now have transcripts starting automatically for each session.


image

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

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.