Skip to main content
By -

 

How to Create Log File using Start-Transcript cmdlet in PowerShell


What is Start-Transcript?


As per MSDN, The Start-Transcript cmdlet creates a record of all or part of a PowerShell session to a text file. The transcript includes all commands that the user types and all output that appears on the console. Starting in Windows PowerShell 5.0, Start-Transcript includes the hostname in the generated filename of all transcripts.

When & Where to use?


As system admin/DevOps, we are doing much automation inside the servers and it’s mandatory to capture all the details (maybe error or success ran) in the log to make an analysis if required. In simple, if you running PowerShell scripts automatically you need a way to log any errors or warnings that occur. Usually, we will create your own log function (the same I did for my previous automation, please refer to my implemented method), but there is an easier way which I found during my team discussion and thought to share with all of you. This is especially useful when your enterprise’s logging is centralized.

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 also refer : Try/Catch , Error Handling , Error Logging

Source: https://dotnet-helpers.com/powershell/how-to-create-log-file-using-start-transcript-cmdlet-in-powershell/

Comments

Post a Comment

We appreciate your valuable feedback and comments

Popular posts from this blog

How to Checkout External Repositories in Azure DevOps Build Pipeline: A Step-by-Step Guide

By -
  Introduction Efficiently integrating code from external Azure DevOps repositories is crucial for collaborative projects and streamlined development workflows. This comprehensive guide provides a step-by-step approach to accessing and utilizing external repositories within your Azure DevOps pipelines (Checkout External Repositories). We’ll cover essential steps, including creating Personal Access Tokens (PATs), configuring service connections, and referencing external repositories in your YAML pipelines. By following these instructions, you’ll enhance your development process by seamlessly incorporating code from various sources across different subscriptions. Accessing an External Azure DevOps Repository Across Subscriptions Accessing a repository from another Azure DevOps subscription can be essential for projects where resources are distributed across different organizations or accounts. This article provides a step-by-step guide on using a Personal Access Token (PAT) and a se...
Read more

Cache Purging in Azure Front Door with Azure PowerShell and CLI

By -
Introduction Azure Front Door is a global, scalable entry point for fast delivery of your applications. It provides load balancing, SSL offloading, and caching, among other features. One critical task for maintaining optimal performance and ensuring the delivery of up-to-date content is cache purging. This article provides a step-by-step guide to performing cache purging in Azure Front Door using Azure PowerShell and the Azure Command-Line Interface (CLI). What is AFD Cache Purging? Cache purging, also known as cache invalidation, is the process of removing cached content from a caching layer. This is essential when the content served to the end users needs to be updated or deleted. In the context of Azure Front Door, purging ensures that the latest version of your content is delivered to users instead of outdated cached versions. For more details on this topic please click here 
Read more
By -
  How To Monitor a Folder changes using Powershell In our environment, large numbers of users are working on a daily basis and it very difficult to track what file they have modified and which time. To handle this scenario, my team was requested to monitor a directory for any file changes and receive alerts of those changes when they trying to update/Delete/renamed/created in a specific location inside the service and this requirement made me create this post. In this post, we will discuss how to monitor changes in the folder including sub-files, and log in to the log text file. STEP #1 To monitor a folder for new files in Windows with PowerShell, we can use a .NET class called FileSystemWatcher.  This class is in the System.IO namespace and can be created with the New-Object cmdlet. $filewatcher = New-Object System.IO.FileSystemWatcher please refer the source :  https://dotnet-helpers.com/powershell/how-to-monitor-a-folder-changes-using-powershell/ 
Read more