Skip to main content

I little bit of Netiquette

Like most other MCTs, I do a lot of research. I read a lot of blogs from other trainers and generally have a positive experience. I do want to remind everyone that we can respectfully disagree with each other in a professional manner. I’ve read some downright nasty comments to some people’s posts. Written communication is very difficult to interpret. When we communicate we have the ability to use inflection in our voices to convey a message. We can also use body language to convey that message and to see if it was received as intended. In written communications, we have neither immediate feedback nor any way of determining if the message that we sent was received as intended.


Here is a quick exercise that I use while teaching leadership to our Naval personnel. On a piece of paper, write down all the ways that people communicate with each other while standing face-to-face. After you have completed your list, cross out everything that is not valid when you communicate via e-mail. You will see what you have to work with is very small.


In short, if we want to disagree with someone, first finish reading the post. Often, I read comments that sound like they were formed in the first 3 sentences of a two paragraph post. Then, disagree in a respective fashion if you still feel the need to.


As for the authors (I’m guilty on this one), be careful in your choice of words. Authors need to select words that will properly convey their meaning. Often I've had my posts or comments that I've made taken completely out of context because I did not take the time to choose the correct words.

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