PowerShell Transcript

Have you ever worked on trying to figure out how to get a specific chuck of data out from deep within an object, only to forget how you did it once you found it. Or maybe you need to back track you steps but the screens veritcle buffer is full so you cannot see what you are doing? Try using PowerShell’s transcript capability. It is very easy to use. Just type Start-Transcript in the shell. It will save the transcript file to your Documents folder. When you are finished, or want to start a new log, just type Stop-Transcript. Below is a quick example. You will not see the Start-Transcript command in the log file because the log file is opened after the command is typed.

The ISE does not have the Start-Transcript cmdlet. Here is an article from the Scripting Guy to help you get the same capability in the ISE.

**********************

Windows PowerShell transcript start

Start time: 20120810103917

Username : Jason-PC\Jason

Machine : JASON-PC (Microsoft Windows NT 6.1.7601 Service Pack 1)

**********************

Transcript started, output file is C:\Users\Jason\Documents\PowerShell_transcript.20120810103917.txt

PS C:\Users\Jason> cls

PS C:\Users\Jason> get-service

Status Name DisplayName

------ ---- -----------

Stopped AdobeFlashPlaye... Adobe Flash Player Update Service

Stopped AeLookupSvc Application Experience

Running ALG Application Layer Gateway Service

Stopped AppIDSvc Application Identity

Running Appinfo Application Information

…. Section removed for brevity ….

Running WSearch Windows Search

Running wuauserv Windows Update

Running wudfsvc Windows Driver Foundation - User-mo...

Stopped WwanSvc WWAN AutoConfig

PS C:\Users\Jason> Stop-Transcript

**********************

Windows PowerShell transcript end

End time: 20120810104259

**********************

Comments

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...

Jason Yoder, MCT

Search This Blog