As you create your enterprise script template, you will need to incorporate a logging mechanism. Logging allows you to capture script output, including informational, warning, and error messages. In typical logging scenarios, you will need to record script actions to either the event log, a log file, or a data collection file, like a
Comma Separated Values (CSV) file. While PowerShell has a transcript which you can invoke, leveraging the start-transcript and stop-transcript cmdlets, it only allows you to record output to a single log file. This doesn't provide for writing to the event log or data collection files.
A popular logging mechanism is to create your own PowerShell logging function. This enables you to pass in parameters into the logging function to tell the script to either write to the event log, log file, or append data to the data collection file. It can also write the actions to the PowerShell window to view progress. This avoids having to write multiple lines...