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

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 .

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

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services. The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database. Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet. Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS. You may want to make sure the database is being backed up and also have a restore plan in place. Should the database become corrupt, the application that uses that database will fail. This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...

Jason Yoder, MCT

Search This Blog