Skip to main content

Automatically create a log of your PowerShell sessions

By

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

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