I Thought We Weren’t Supposed to Change Settings in the Registry?

by Shijaz Abdulla on 04.10.2009 at 21:34

Following is an excerpt taken from a Microsoft Technet article written by the Scripting Guys. It’s about the Windows Registry and I found it rather amusing:

As you probably know, Microsoft has a sort of love-hate relationship with the registry. The registry is the configuration database for Windows and Windows applications, and many options can only be set by manually changing a value in the registry. For example, if you’ve ever read a Microsoft Knowledge Base article, you’ve likely seen a sentence similar to this:

To correct this problem, change the following value in the registry.

Now that’s fine, except that this sentence is invariably followed by a disclaimer similar to this one:

Warning: Don’t ever change a value in the registry. Ever. We know we just told you to do that, but would you jump off a cliff if we told you to? Don’t ever change a value in the registry. Don’t even say the word registry. We know a guy once who said the word registry, and three days later he was hit by a bus. True story. As a matter of fact, you shouldn’t even have a registry on your computer. If you suspect that you do have a registry on your computer, call us and a trained professional will be dispatched to your office to remove the registry immediately. If you accidentally touch the registry, wash your hands with soap and water and call a doctor. Do not swallow the registry or get it in your eyes!

Now, to be honest, some of those fears are a bit exaggerated, and the disclaimer is there largely for legal reasons (remember, this is the day and age when you can order hot coffee in a restaurant and then sue the restaurant when the coffee they give you turns out to be, well, hot). If you do it correctly, changing the registry is perfectly harmless. At the same time, however, it’s true that there are certain values in the registry that should never be changed. In fact, changing them can pretty much wipe your computer out, once and for all. It’s like working on the bomb squad: if you snip the right wire, the bomb is defused and everything is fine. But if you snip the wrong one—Boom! You just created Microsoft Bob!

Um, not that we’re saying Microsoft Bob was a bomb or anything.

New articles for Microsoft Knowledge Base (KB)

by Shijaz Abdulla on 20.03.2008 at 19:15

Two of my articles written for the Microsoft Knowledge Base have been published today:

  • KB556073: Outlook Web Access users are unable to save appointments or respond to meeting requests
  • KB556074: Users are unable to receive meeting requests and meeting updates in Exchange Server 2007

Hope you can solve more of your problems at support.microsoft.com!

Articles on enabling Remote Desktop

by Shijaz Abdulla on 17.02.2008 at 12:38

It’s been some time since I’ve written new articles on shijaz.com 🙂

I have added two new articles on Remote Desktop:

Delayed logins: Change Password feature in ISA 2006 FBA

by Shijaz Abdulla on 13.08.2007 at 08:13

If you have published Outlook Web Access (OWA) using ISA Server 2006 Forms-based authentication (FBA) and decided to use the new Password Management features on ISA Server 2006 FBA instead of the conventional OWA change password feature, you need to read this.

When you have install Windows Server 2003 Service Pack 2 or the Scalable Networking Pack on the computer running ISA Server 2006, you will probably face issues when you enabled ISA Server 2006 Password management features. Users may report that the login process takes a long time (15 seconds or more) when you turn on the password management feature, even if they choose not to change their password while logging on.

I have written an article for a workaround to this, the KB article is now available on the Microsoft Knowledge Base (KB555958) and also on my website.

How to run a command as SYSTEM

by Shijaz Abdulla on 25.07.2007 at 08:51

The SYSTEM account is an internal account used by the Windows operating system that is similar to the administrator account, and has access to all resources, but cannot be fully managed by the user. The SYSTEM account is used internally by the OS for tasks like starting services and running processes.

There is, however, a way by which a normal user can execute commands or start processes in the context of the SYSTEM account. I’ve written an article about it on my website: “How to run a command in the context of the SYSTEM account

Article published on Microsoft Knowledge Base

by Shijaz Abdulla on 10.07.2007 at 09:41

“How to export members of an Exchange distribution group to a text file”

My first contribution to the Microsoft Knowledge Base. An article with my name on it. I look at it with the same ecstacy that an eight year old child would have had when he sees his own name in print.