{"id":6142,"date":"2022-03-02T09:38:00","date_gmt":"2022-03-02T07:38:00","guid":{"rendered":"https:\/\/lazyadmin.nl\/?p=6142"},"modified":"2022-03-01T15:42:19","modified_gmt":"2022-03-01T13:42:19","slug":"start-transcript","status":"publish","type":"post","link":"https:\/\/lazyadmin.nl\/powershell\/start-transcript\/","title":{"rendered":"How to use Start-Transcript in PowerShell"},"content":{"rendered":"\n

When running PowerShell scripts automatically you will need a way to log any errors or warnings that occur. One option is to create your own log function<\/a>, but there is an easier way, the Start-Transcript cmdlet. <\/p>\n\n\n\n

The Start-Transcript cmdlet writes everything that happens during a session to a log file. These are the commands that you enter in a PowerShell session and all output that normally appears in the console. You can use this during your normal PowerShell session, but it’s more useful for creating log files.<\/p>\n\n\n\n

In this article, we are going to take a look at how to use the Start-Transcript cmdlet.<\/p>\n\n\n\n

Using Start-Transcript in PowerShell<\/h2>\n\n\n\n

The Start-Transcript cmdlet in PowerShell is pretty straightforward to use. It only comes with a couple of parameters and by default, you don’t even have to specify a file path.<\/p>\n\n\n\n

Parameter<\/th>Description<\/th><\/tr><\/thead>
-Path<\/td>Location of the transcript (log) file<\/td><\/tr>
-Append<\/td>Append content to an existing file<\/td><\/tr>
-Force<\/td>Overwrite files with Read-only flag<\/td><\/tr>
-NoClobber<\/td>Prevent overwriting of existing files<\/td><\/tr>
-IncludeInvocationHeader<\/td>Add the timestamp to a command in the log file<\/td><\/tr>
-UseMinimalHeader<\/td>Prepend a short header instead of the full header (PS6+)<\/td><\/tr>
-OutputDirectory<\/td>Specify the output directory (filename will be created automatically)<\/td><\/tr><\/tbody><\/table>
Start-Transcript parameters<\/figcaption><\/figure>\n\n\n\n

There are two ways to use the Start-Transcript cmdlet in PowerShell. You can either start the transcript in your PowerShell session or include it in your script.<\/p>\n\n\n\n

Without any parameters, the transcript will be saved in the user’s documents folder. The filename will automatically be generated and consists of the device name, random characters followed by a timestamp.<\/p>\n\n\n\n

c:\\users\\name\\documents\\PowerShell_transcript.DEVICENAME.qp9EOTN2.20220301132612.txt<\/pre>\n\n\n\n
The random characters ensure that the filename is unique when two PowerShell sessions are started simultaneously.<\/p>\n\n\n\n
To start the transcript we can simply use the cmdlet Start-Transcript<\/code>. Then after we have executed the scripts that we want to run, we can stop the transcript with Stop-Transcript<\/code>.<\/p>\n\n\n\n
\"start-transcript
Start-Transcript in PowerShell<\/figcaption><\/figure>\n\n\n\n
The transcript will contain all the information that you see in the console as well, including a very detailed header with information of the host that you have used:<\/p>\n\n\n\n
\"Powershell
PowerShell transcript result<\/figcaption><\/figure>\n\n\n\n
Path and Output Directory<\/h3>\n\n\n\n
The default path is great when you are only using PowerShell on your own machine. But most of the time you want to centralize the log files. There are two options for this, we can use the -Path<\/code> parameter or the -OutputDirectory<\/code> parameter for this.<\/p>\n\n\n\n
With path, we will need to specify the full path, including the file name. This is useful when you want to have a single log file for a script and append all the transcripts into a single file.<\/p>\n\n\n\n
# Append the transcript to a mfastatus-result.log file.\nStart-Transcript -Path c:\\logfiles\\mfastatus-result.log -Append\n\n# Or use -NoClobber to prevent overwriting of existing files\nStart-Transcript -Path c:\\logfiles\\mfastatus-result.log -NoClobber<\/pre>\n\n\n\n
You can also use the -path parameter without the append, but keep in mind that the Start-Transcript parameter by default will overwrite any existing content in the file.<\/p>\n\n\n\n
Another option is to use the -OutputDirectory<\/code> parameter. This way we can specify the directory where we want to store the log file, and allow the cmdlet to create the unique filename.<\/p>\n\n\n\n
Start-Transcript -OutputDirectory c:\\temp\\logfiles\n\n# Result:\nTranscript started, output file is c:\\temp\\logfiles\\PowerShell_transcript.WIN11-LAB02.uftVAXsv.20220301045218.txt<\/pre>\n\n\n\n
Minimal header<\/h3>\n\n\n\n
Each transcript starts with a fully detailed header with information about the host. When using this for logging of scripts that run automatically this information is just a bit too much. In PowerShell 6 and higher, we can use the parameter -UseMinimalHeader<\/code> for this.<\/p>\n\n\n\n
This will limit the header information to only a timestamp of when the transcript is started:<\/p>\n\n\n\n
Start-Transcript -OutputDirectory c:\\temp\\logfiles -UseMinimalDeader\n\n# Start of transcript with minimalheader\n**********************\nPowerShell transcript start\nStart time: 20220301135543\n**********************<\/pre>\n\n\n\n
Include Invocation Header<\/h3>\n\n\n\n
The invocation header includes a timestamp before each step or command in the transcript. This is especially useful when you have a large script that takes some time to run.<\/p>\n\n\n\n
Start-Transcript -OutputDirectory c:\\temp\\logfiles -IncludeInvocationHeader\n\n**********************\nTranscript started, output file is c:\\temp\\logfiles\\PowerShell_transcript.WIN11-LAB02.VKwZ2RF5.20220301050111.txt\n**********************\nCommand start time: 20220301050122 \n**********************\nPS C:\\> .\\Temp\\Test-SMTP.ps1<\/pre>\n\n\n\n
Use Start-Transcript inside a PowerShell script<\/h2>\n\n\n\n
Besides starting the transcript manually from the terminal in PowerShell you can of course also include the cmdlet inside your script. Simply start your PowerShell script with the Start-Transcript and end your script with Stop-Transcript:<\/p>\n\n\n\n
Start-Transcript -OutputDirectory c:\\temp\\Logfiles -UseMinimalHeader\n\n# Your script here\n\nStop-Transcript<\/pre>\n\n\n\n
Wrapping Up<\/h2>\n\n\n\n
The Start-Transcript cmdlet is a great tool when you are debugging new scripts that run automatically. Personally, I don’t use it much, I prefer a log function combined with Try-Catch blocks<\/a> for example inside script for better error handling.<\/p>\n\n\n\n
When you want to use the transcript to see your command history then keep in mind that you also can use the Get-History cmdlet in PowerShell. This will show all commands that you have entered during your PowerShell Session.<\/p>\n\n\n\n
If you have any questions, then just drop a comment below.<\/p>\n