MCT Tip - Life on the Road

Hello my fellow Road Warriors:

Here are some more tips on how to keep your costs down. Stay in a suite. I've found out that Extended Stay America will accept a Price Line bid of $26-$28 a night. Talk about savings. I also recommend going to the grocery store. Staying in to eat will lower your expenses and that adds up to more money in your pocket. Lodging and meal expenses for a week is around $215. Lodging and meals staying at other hotels and eating out is approximatley $440 a week. That is a savings of about $225 dollars. Streach that out to twice a month for a year and it comes to $5400. Now do I have your attention?

Here is another one. Go for a run (or a walk). Instead of looking for evening entertainment that pulls dollars from your wallet, go hiking. For a State Park, it is usually a few bucks to get in. You will not dish out a movie ticket, and an $8.00 soda. You will also get that thing that we don't always get because we hover over a computer all day and night. You know....exercise.

Comments

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

Jason Yoder, MCT

Search This Blog