Errata

Windows PowerShell Best Practices

Errata for Windows PowerShell Best Practices

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
PDF Page 6
Second paragraph - last line

In the "Installing PS" section there is a line thats states "You can also install on Windows 8...". This is at odds with the MS official line mentioned in "http://blogs.msdn.com/b/powershell/archive/2013/10/25/windows-management-framework-4-0-is-now-available.aspx"

David Zemdegs  Jan 21, 2014 
PDF Page 368
2nd Paragraph

On pages 368-369, the output of ConvertFrom-SecureString is described as a "hash" of the password. This is incorrect; a "hash" is a one-way operation, and the original password cannot be retrieved from a hash.

The output from ConvertFrom-SecureString is an encrypted password, which can be decrypted back to its original value as needed. (More information on this encryption / decryption, performed by the Data Protection API, is provided in Lee Holmes' on page 371.)

Dave Wyatt  Jan 28, 2014 
PDF Page 430
script block

On Page 429 the $drives variables is populatded as a hash table and that is how the text describes it. The code on page 430 however populates this variable as an array. It still works but it's not consistent with the text description.

David Zemdegs  Jan 21, 2014 
PDF Page 553
Whole Page

On Page 553 a description of a script which tests for Administrator privileges is outlined. On Page 414 a mention is made about the new V4 #Requires option. Maybe some reference to that is needed around Page 553?

David Zemdegs  Jan 21, 2014