Introduction Recently, we came across an interesting bug that had been around for awhile ( http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=315875 ). If you do the following: Start-Transcript ipconfig Stop-Transcript If you look at the transcript, you’ll see that the output of ipconfig was not captured. Why is this happening? PowerShell recognizes that ipconfig is a native
Read More...
Read the complete post at http://blogs.msdn.com/powershell/archive/2010/01/04/workaround-for-start-transcript-on-native-processes.aspx
Posted
Jan 04 2010, 03:06 PM
by
Windows PowerShell Blog