Skip to main content

Giving Thanks

This post may be a little off topic, so please bare with me.

These past few weeks I have been providing Windows and PowerShell training in Asia and the south Pacific. We took a longer than usual lunch break yesterday so the Sailors of the United States Navy in my class can enjoy the one Thanksgiving meal that they will get this year.

What ever nation you claim as your own, please remember your sons and daughters who have volunteered to spend their time away from their families so you can be free to spend time with yours. Not far from where I am right now, freedom is only a distant light on the horizon. A beacon of hope for a brighter future. Be thankful that you may stand in that light and not gaze at it from a distance.

To all of my Brothers and Sisters who have volunteered to keep us all free,  Happy Thanksgiving.

10670134_10153282105405715_2436738459856340706_n

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

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