Skip to main content

Let PowerShell Read for You

As a Chief Petty Officer in the US Navy, I often find myself with a really long article or email to read.  This can be a bit of a pain when I have a lot of work to do.  Don’t get me wrong, I go through everyone.  I just do it a bit of a different way.  Back in August of 2013, I published my Out-Voice cmdlet.  It simply uses the Windows Text-to-Speech converter to read what ever strings you send it.  Below is my Read-Article cmdlet.

To use it, just copy your long email or article into a text file and let it go. I’m including this in the source code that I am sending my PowerShell students home with since it gives two examples of basic error handling. If you need a copy of Out-Voice, you can get it here.  I have it loading as one of my PowerShell modules.

 

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

 

Function Read-Article

{

<#

.SYNOPSIS

Reads a text file.

 

.DESCRIPTION

Reads a text file.  The cmdlet Out-Voice must be loaded in memory.  You can get

a copy of Out-Voice at:

http://mctexpert.blogspot.com/2013/08/have-powershell-verbally-provide.html

 

.PARAMETER $File

The name of the txt file to read.

 

.PARAMETER $Voice

Allows for the default choice to be changed using the

default voices installed on Windows 8. Acceptable values are:

US_Male

UK_Female

US_Female

 

.EXAMPLE

Read-Article News.txt

 

Reads the text file News.txt

 

.NOTES

===============================================================================

== Cmdlet: Read-Article                                                      ==

== Author: Jason A. Yoder                                                    ==

== Company: MCTExpert of Arizona                                             ==

== Date: February 11, 2015                                                   ==

== Copyright: All rights reserved.                                           ==

== Version: 1.0.0.0                                                          ==

== Legal: The user assumes all responsibility and liability for the usage of ==

== this PowerShell code.  MCTExpert of Arizona, Its officers, shareholders,  ==

== owners, and their relatives are not liable for any damages.  As with all  ==

== code, review it and understand it prior to usage.  It is recommended that ==

== this code be fully tested and validated in a test environment prior to    ==

== usage in a production environment.                                        ==

==                                                                           ==

== Does this code make changes: NO                                           ==

== Requirements: Out-Voice must be in memory.  To get a copy of Out-Voice:   ==

== http://mctexpert.blogspot.com/2013/08/have-powershell-verbally-provide.html

===============================================================================

#>

#>

[CmdletBinding()]

Param

(  

    [parameter(Mandatory=$true)]

    [String]

    $File,

 

    [ValidateSet("US_Male", "UK_Female", "UK_Female")]

    [String]

    $Voice = "US_Female"

)

 

# Verify that the cmdlet Out-Voice is present in memory.

Try {Get-Command -Name Out-Voice -ErrorAction Stop}

Catch {Write-Host "The Cmdlet Out-Voice is not in memory,"}

 

# Load the file

Try {$A = Get-Content -Path $File -ErrorAction Stop}

Catch {Write-Host "File not found"}

 

$A | Out-Voice -VoiceType $Voice

 

} # END: Function Read-Article

 

Comments

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...