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 Testing and Exam resources Free

 

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

 

 
Windows 2000/XP SP Reinstallation

You do NOT have to Reinstall Windows 2000 or Windows XP Service Packs after system state changes...

After you have installed the service pack, you do not need to reinstall it if you add a device or new software to your computer. For example, Windows 2000 and Windows XP include a file named Driver.cab, which contains all of the files potentially installed by Plug and Play (PnP)-class installers. Setup and other components use this file to install the drivers for new devices (for example, a PCMCIA card or a USB keyboard) without requiring access to the Windows CD or the network.

The service pack does not update the Driver.cab file itself; instead, the Update.exe program installs an additional driver file named Sp1.cab (or other if the SP number is greater). This file contains only updated versions of drivers that exist in the original Windows 2000 or Windows XP Driver.cab file. In addition to the Sp1.cab file, the Update.exe program installs a new Drvindex.inf that points to Sp1.cab for all of the updated drivers and also points to Driver.cab for all of the remaining drivers.

Update.exe installs a Layout.inf file. Layout.inf ensures that the correct software is installed and that all the correct updates are made to Windows 2000 or XP when you remove services from or add services to your computer. For example, if you remove a service from Microsoft Windows NT 4.0 and then reinstall it there, you must reinstall the service pack after you reinstall the service. This is unnecessary in Windows XP. The Layout.inf file is updated automatically to determine which files must be installed from the original Windows CD or from the service pack and, if necessary, the file prompts for the appropriate media.

When you install a Windows 2000 or XP service pack, the Update.exe tool performs the following actions:

  • The Layout.inf file is updated with an additional source for the Windows service pack files. When you change or add components, the Layout.inf file points to the correct source.
  • The source location is stored in the following registry key:

  • The source might be a network share for the Windows service pack, the Windows XP/2000 service pack CD-ROM, or if you install the service pack by using the Express Installation feature from the Web, the %SystemRoot%\Servicepackfiles folder.
  • The Drvindex.inf file is updated to point to an additional .cab file for drivers that are updated in the Windows service pack. The .cab file is named Sp n.cab (where n is the service pack version number). This file is installed in the %SystemRoot%\Driver Cache\I386 folder.
  • A new Sp n.cat file (where n is the service pack version number) is installed for the updated files. This file replaces any previously installed Sp n.cat file that was installed with a Windows XP/2000 hotfix.
  • The Sp n.cat file is installed in the %SystemRoot%\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} folder
  • Windows service packs also perform version checking on files so that post-Windows SP n hotfixes (where n is the service pack number) remain in place.

You do not have to reinstall hotfixes after you install the service pack. For example, when you install Windows XP SP1, hotfixes that you installed before you install Windows XP SP1 are updated to the Windows XP SP1 files. Hotfixes that you install after you install Windows XP SP1 are not replaced.

Note that hotfixes do not update the Layout.inf file. Therefore, if you install a hotfix and system state changes occur, you may have to reinstall the hotfix.

 


© Vibrant Worldwide Inc.