Group Policy Management Console Overview (Administering Group Policy with Group Policy Management Console)

In the past, administrators have been required to use several Microsoft tools to manage Group Policy, such as the Active Directory Users and Computers, Active Directory Sites and Services, and Resultant Set of Policy snap-ins. GPMC integrates the existing Group Policy functionality exposed in these tools into a single, unified console, along with several new capabilities.

Built-in to GPMC is support for managing multiple domains and forests, making it possible for administrators to easily manage Group Policy across an enterprise. Administrators have complete control of which forests and domains are listed in GPMC, making it possible to display only pertinent parts of an environment.

By default, the first time GPMC is started it loads the forest and domain containing the user object logged on to the computer. Administrators can then specify which forests and domains to display. When the console is closed, GPMC automatically saves the last view and will return to that view the next time the user opens that console.

The console tree on the left side of the snap-in contains GPMC’s root node Group Policy Management. Each forest appears as a sub node of GPMC’s root node, and is named after the forest root domain for that forest, pre-pended with the word “Forest.” Each forest has either three or four sub nodes of its own: Domains, Sites, Group Policy Modeling, and Group Policy Results. The Group Policy Modeling node is only shown in a forest that has the Windows Server 2003 schema for Active Directory. To perform a Group Policy Modeling analysis, you must also have at least one domain controller that is running Windows Server 2003.

 

  • Do you want to become  Real MCSE, CCNA or CCNP certified?
     
  • Do you want to Payless for certification?
     
  • Do you want to finish in 2/3 weeks?

 

 

 
 
 
 

CCNP - GlobalNet Trainings CCNP 11 Day Cisco Certification Boot Camp

CCNP - GlobalNet Training's CCNP 11-Day boot camp. Cisco has announced new requirements for it's Cisco Certified Network Professional, or CCNP, program.
 

NetworkLearning: BootCamp Provider

CCIE RS Written Bootcamp · R&S CCIE Prep Info -- Security CCIE Prep Info ... CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, Cisco IOS, Cisco Systems, ...
 

MCSE Boot camp, MCSE CCNA CCNP Boot camp, MCSE / MCSA Boot camp ...

Offers boot camp training on Microsoft MCSE, MCSD.NET, MCDBA, Cisco CCNA, CCNP, Citrix CCA, Oracle, Java J2EE, CompTIA, Check Point and Red Hat Linux ...
 

CCNP Boot Camp: Boston University

The Boston University Corporate Education Center offers unmatched programs in technology training. As a Microsoft Gold Certified Partner, BUCEC delivers ...
 

Cisco CCNP Boot Camp

The Training Camp offers intense cisco ccna boot camp training sessions guaranteed to end in industry certification.
 

Cisco CCNP Boot Camp certification training classes for CCNP

Cisco CCNP Boot Camp for Certification training Class.Get Certified Fast. Boot Camps location Nationally.
 

MCSE CCNA CCNP Boot Camp classes and Boot camp certification training

MCSE Boot Camp Certification training classes nationally. Oracle and CCNP Boot Camps as well as MCSA, MOUS, UNIX, MCSD, MCAD, Linux, CCSP, CISSP and A+.
 
 

Unitek: Training: Cisco: 13-Day Official CCNP Boot Camp

Unitek Information Sytems offers high-end IT training, consulting and contracting services. Unitek is an authorized microsoft certified training education ...
 

Cisco CCNA Boot Camp Training - One Week CCNA BootCamp

We Specialize in Cisco CCNA & CCNP Boot Camp Training and Microsoft MCSE and MCSA Boot Camp Training Courses.
 

Institute for Advanced Technology Training - Overview ...

The most important pre-requisite for the CCNP bootcamp is the CCNA certification. You must be CCNA certified before you start the CCNP bootcamp. ...
 

 

 

MCSE Bootcamp Training - Microsoft MCSE certification

 

MCSE Boot Camp, CCNA Bootcamps, CCNP Boot camp Certification Training

MCSE Guide

Free MCSE
Free MCSE Training
MCSE
MCSE 2003
MCSE Books
MCSE Boot Camp
MCSE Brain dumps
MCSE Certification
MCSE Exam
MCSE Free
MCSE Jobs
MCSE Logo
MCSE Online
MCSE Online Training
MCSE Practice
MCSE Practice Exams
MCSE Practice Tests
MCSE Requirements
MCSE Resume
MCSE Salary
MCSE Self Paced Training Kit
MCSE Study
MCSE Study Guide
MCSE Study Guides
MCSE Test
MCSE Testing
MCSE Training
MCSE Training Kit
MCSE Training Video
MCSE Windows 2003
Microsoft MCSE Training
Training MCSE
Windows 2003 MCSE

 

 

Method #2 - By using Netdom.exe

This method is considered by most professionals to be much safer and better than the first method. By using the Netdom.exe tool, you ensure that there is little or no disturbance for the domain and client operations.

Important: To rename a domain controller using the Netdom.exe tool, the domain functional level must be set to Windows Server 2003.

In order to use Netdom.exe you must first install the Windows Server 2003 Support Tools. Double-click the Suptools.msi file found on the \Support\Tools folder on the installation CD (also see Download Windows 2003 SP1 Support Tools
).

To rename a DC with the name from SERVER101 in the DPETRI.NET domain to ZEUS follow the next steps:

  1. Open Command Prompt and type:

 

This command will update the service principal name (SPN) attributes in Active Directory for this computer account and register DNS resource records for the new computer name. The SPN value of the computer account must be replicated to all domain controllers for the domain and the DNS resource records for the new computer name must be distributed to all the authoritative DNS servers for the domain name. If the updates and registrations have not occurred prior to removing the old computer name, then some clients may be unable to locate this computer using the new or old name.

You can verify the new name was indeed added to the computer object by viewing it through Adsiedit.msc (like Netdom.exe, installed when you install the Windows Server 2003 Support Tools). Navigate to the computer object and right-click it. Select Properties:

 

Scroll down in the list of available attributes till you reach the attribute called msDS-AdditionalDnsHostName:

 

Notice that the new name should appear in the attribute's properties.

  1. Ensure the computer account updates and DNS registrations are completed, then type:

 

Again, you can inspect the change with Adsiedit.msc. Scroll down in the list of available attributes for the computer object (notice how the server now appears with the new name) till you reach the attribute called msDS-AdditionalDnsHostName:

 

Notice that the old name should appear in the attribute's properties.

  1. Restart the computer.

  2. From the command prompt, type:

 

  1. Make sure that the changes have successfully been replicated to all the DCs.

Renaming a domain controller requires that you first provide a FQDN as a new computer name for the domain controller. All of the computer accounts for the domain controller must contain the updated SPN attribute and all the authoritative DNS servers for the domain name must contain the host (A) resource record for the new computer name. Both the old and new computer names are maintained until you remove the old computer name. This ensures that there will be no interruption in the ability of clients to locate or authenticate to the renamed domain controller, except when the domain controller is restarted.

 


© Vibrant Worldwide Inc.