Tip

Avoid Active Directory's one-way streets

James Michael Stewart, Contributor

For those of you holding or pursuing CISSP certification, you should be familiar with the concept of change management as it relates to operational security. One of the primary goals of change management is to prevent changes to an environment from reducing security. Another important aspect of change management is the ability to roll back changes if they are determined after-the-fact to have a detrimental effect.

I'm sure we can all agree that being able to reverse changes is a good thing. However, there are numerous necessary configuration activities within Windows 2000, specifically dealing with Active Directory, that are permanent and irreversible.

This tip serves as a reminder and a warning. Make sure you understand what you are doing before you do it. If you are not careful, you may find yourself at the end of a one-way street with nowhere to go.

One of the best-known dead-ends is the migration of an Active Directory domain from mixed mode to native mode. This is an activity that should not be considered lightly. If you initiate this transformation, your domain will forever be restricted to Windows 2000+ servers as domain controllers. You will no longer be able to use Windows NT 4.0 servers as domain controllers. With over 60% of the private and government organizations still relying upon Windows NT, this is a trip you probably don't want to take.

Domain naming is irreversible, too. Once a domain is named, it must be destroyed and rebuilt

    Requires Free Membership to View

in order to rename it. Make sure you plan out your naming scheme and inter-forest domain relationships before you start implementing. There is no easy way to correct mistakes.

Many network services, native applications and third-party software employ installations that cannot be undone. If you are not certain that you want a specific application or service to be present on a system throughout its lifetime, you should think twice about installing it temporarily on important systems. I recommend testing the uninstallation capabilities of desired products before putting them onto production systems.


James Michael Stewart is a partner and researcher for ITinfopros, a technology-focused writing and training organization.


This was first published in April 2003

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.