Bad Assumptions About Computer Use

There is a tendency to think that everyone uses computers of some sort today and that all of these computers are connected in some way to the Internet. When I use the term computer here, I mean some sort of device that contains a processor and runs applications. What you may have is actually a smartphone and not a computer in the conventional sense, but even so, a smartphone contains a processor and runs applications. So, when you define the term that broadly, there is an expectation that everyone is connected. The fact is that not everyone is connected. According a recent eWeek article entitled, “One in Five U.S. Adults Does Not Use the Internet: Pew” 62,318,383 people in the US don’t have an Internet connection (based on a US Census Bureau estimated population of 311,591,917 in 2011). That’s a lot of people.

So, why is this statistic even important? If you write computer books and articles as I do, the statistic doesn’t affect you at all. However, if you’re currently selling a product online and don’t offer a catalog for that product, you could be missing out on 20 percent of your possible sales. When you want to communicate with family members, there is a 20 percent chance you won’t reach the party you want to reach if you only rely on computer technology to do it. As I move more and more into self-sufficiency topics, I’ll need to consider the effect of print media on my books sales because 20 percent of my potential audience may lack the capability of using an e-book (see my post The e-Book in Your Future for my thoughts on e-book usage).

Every once in a while, I need my perceptions of the world around me stirred up and challenged. I get stuck in a pattern of thought that could be invalid or downright harmful for those around me. Finding information that challenges your view of the world is helpful and useful because it forces you to think through the assumptions that you’re making. If you’re a vendor, you may have thought about getting rid of your paper catalogs because you assume that everyone shops online, but that may not be the case.

Of course, you also need to read the report further to really understand the ramifications of the data it presents. For example, 95 percent of teenagers are currently connected to the Internet, which means that if you’re targeting a younger audience, chances are good that you’ll reach them using the Internet. Of course, that 5 percent is still a huge number. Whether you exclude them as a component of your sales, information, or other campaign has to be based on the focus of that campaign. The point is, assumptions are simply a bad idea if they’re never challenged, revised, and reevaluated.

What sorts of assumptions have you made lately that affect your world view of computers or any other technology for that matter? When was the last time you challenged your assumptions? Let me know at [email protected].

 

Working with Net User

The Net User command on page 142 of Windows Command-Line Administration Instant Reference seems to have generated a bit of confusion. The /Add command line switch is straightforward; /LogonPasswordChg isn’t. For one thing, the /LogonPasswordChg command line switch doesn’t appear to be documented, even in Windows 7. Here’s the help provided with Net User now:

NetUser01

As you can see, not even a mention for /LogonPasswordChg. Microsoft doesn’t help matters. For example, if you look at the “How to Use the Net User Command” Knowledge Base article, you won’t find any mention of this command line switch. While writing the book, I had found a tantalizing clue at Manage XP and Vista Users Using DOS Commands and decided to try it on Windows 7 as well. The command works fine when used correctly in Windows 7.

However, here is where the plot thickens. It seems that the command line switch doesn’t work in Windows XP. When you execute the command shown on page 142 you get an error message reading something like, “The option /LOGONPASSWORDCHG:YES is unknown.” Somewhere between Windows XP and Vista, Microsoft added the /LogPasswordChg command line switch to Net User and then didn’t tell anyone about it. Consequently, the command shown on page 142 won’t work under Windows XP.

There is another problem that occurs when using the /LogonPasswordChg command line switch. If the account currently has the Password Never Expires option checked as shown here:

NetUser03

the command appears to succeed, but doesn’t change anything. In order to make the command work properly, you must first set the password to expire using the WMIC Path Win32_UserAccount Where Name=’UserName’ Set PasswordExpires=True command. So, the sequence to set an existing account to force a password change during the next logon is like this:

NetUser04

When you execute these two commands, you’ll see the user account settings to change to appear like this:

NetUser05

which means the user must change the password during the next logon.

So, why does the command on page 142 work without this extra step? In this case you’re adding a new user and the Password Never Expires option is disabled by default. Creating the combined command works fine because there is nothing to hinder it with a new account. Please let me know if you encounter any problems with this particular command at [email protected].