Use the PowerShell transcript record

An administrator can create a PowerShell copy of the log. The PowerShell console host--The blue window that starts from the Start menu or Start screen--supports the creation of transcripts. Just run Start-transcript, provide a filename, and then your activities in this window will be captured, including command output, and so on. Each transcript needs to be run space, meaning that each new PowerShell window needs to have its own script. You can close the window directly or run Stop-transcript when you close the file.

You can use any of the running space of the console window with a script, including the Exchange Management shell, the SharePoint Management shell, and any other management shell. These are all running Powershell.exe--powershell console hosts--pre-installed scripts and Plug-ins.

Conversely, the PowerShell Integrated Scripting Environment (ISE) does not support transcripts. Other managed applications, such as the Business Script Editor, are not supported. For these managed applications, administrators need to provide their own logging mechanisms because Ise does not. Otherwise, you'll get into trouble.

If you use remoting, the rules are slightly different.

If you use Enter-pssession to interact remotely with the same machine, the remote machine will not retain transcripts or PowerShell transcripts. This is because the managed application on the remote machine does not support transcripts. However, any commands and return results sent to the remote machine are preserved on the machine. By remote, you do not have to use a true Secureshell (SSH) type of connection. You or the local console output; The complete command is sent to the remote machine for execution, and the result is deserialized back to local control