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

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

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 .

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...