MCSE Certification Boot Camp

New Features in the Windows Server 2003 Family

In the Windows Server 2003 family of operating systems, Microsoft has improved the function of the Account Lockout feature on both servers and client computers.

Computers Running Windows Server 2003 That Act As Network Servers

To improve the experience for users and to decrease the overall total cost of ownership, Microsoft made the following changes to the behavior of domain controllers in the Windows Server 2003 family:

•	Password history check (N-2): Before a Windows Server 2003 operating system increments badPwdCount, it checks the invalid password against the password history. If the password is the same as one of the last two entries that are in the password history, badPwdCount is not incremented for both NTLM and the Kerberos protocol. This change to domain controllers should reduce the number of lockouts that occur because of user error.
•	Single user object on demand replication: See the "Urgent Replication" section in this document for more information.
•	Optimized replication frequency: The default frequency for replication between sites is to replicate every 15 minutes with a 3-second offset to stagger the replication interval. This optimization improves the replication of a password change in a site because it decreases the chances that the domain controller would have to contact the PDC operations master.

Computers Running Windows Server 2003 Family Acting As Network Clients

Microsoft has added the following features in the Windows Server 2003 family to gather the process ID that is using the credentials that fail authentication:

•

Auditing logon changes: There are entries for all logon and logoff events (528 and 540, as well as 529 through 539).

•

Auditing of processes encountering authentication failures: New information is added to the Security event log when authentication failures occur:

•	Caller User Name
•	Caller Domain
•	Caller Logon ID
•	Caller Process ID

Note:

To use the process ID, turn on success auditing for Audit process tracking events so that you can obtain the process identifier (PID) for the associated Event 592. If you do not do this, the PID is not useful after the process stops. To view audit process tracking, in the Group Policy Microsoft Management Console (MMC), in the console tree, double-click Computer Configuration, double-click Windows Settings, double-click Security Settings, double-click Local Policies, and then double-click Audit Policy.

Microsoft has added the following administrative enhancements to provide more account lockout information than the information that is available in the default configuration of the Windows Server 2003 family:

•	AcctInfo.dll: The AcctInfo.dll file is a property page extension for user objects in the Active Directory Users and Computers MMC that provides detailed information about user password attributes. An administrator can use the AcctInfo.dll file to reset user account passwords on a domain controller that is in the user's Active Directory site.
•	LockoutStatus.exe: The LockoutStatus.exe tool displays bad password count and time information from all of the domain controllers that are in a domain. You can run this tool as either a stand-alone tool or as an extension to the AcctInfo.dll file when you place it in the Systemroot\System32 folder on your computer.

Payless MCSE Boot camp offers Payless MCSE boot camp, MCSE training boot camp, MCSE certification boot camp, MCSE Cisco Boot camp, MCSE Certification training boot camp. MCSE Training certification boot camp, MCSE Boot Training Camp, MCSE boot certification camp, MCSE UK Boot camp, MCSE san Mateo Boot camp, MCSE Japan boot camp, MCSE USA Boot camp, MCSE Europe Boot camp, MCSE guaranteed boot camp.

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?

Click here to continue :

MCSA : MCSE : MCSE + Security : CCNA : CCNP : Bootcamp : MCSE training : Vibrant MCSE : Vibrant CCNA : Vibrant CCNP : camp :
Home : links : Resources : Ref1 : Ref2

MCSE Bootcamp Training : Exchange Server Training - Microsoft MCSE certification

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

MCSE : Security Specialist

Loading drivers

Windows 9x

Windows 9x automatically installs and configures most Plug and Play–compliant devices. For devices that are not automatically configured, the Add New Hardware Wizard, installs and configures legacy and Plug and Play devices that require installation information, such as the driver location.

For many devices, you must use Device Manager in the System option in Control Panel for configuration if you need to make manual changes.

Windows 2000

You must be logged on as an administrator or a member of the Administrators group to configure a device using the Add/Remove Hardware wizard in Control Panel or Device Manager.

For a device to work properly with Windows 2000, software known as a device driver must be loaded onto the computer. Each device has its own unique device driver, which is typically supplied by the device manufacturer. However, some device drivers are included with Windows 2000.

You can configure devices using the Add/Remove Hardware wizard in Control Panel or the Device Manager.

If the device is Plug and Play, or it is a necessary startup device like the hard disk, this detection happens automatically. However, for some older devices, after you connect it to your computer, you may have to restart your computer. Windows 2000 then attempts to detect your new device.

If the device is not Plug and Play, you may have to use the Add/Remove Hardware wizard in Control Panel to tell Windows 2000 what type of device you are installing. After the device is detected, or you identify the device using the Add/Remove Hardware wizard, Windows 2000 may ask you to insert the Windows 2000 CD-ROM or the manufacturer's floppy disk so it can load the proper device drivers.

After the device drivers are loaded onto your system, Windows 2000 configures the properties and settings for the device. Although you can manually configure device properties and settings, you should let Windows 2000 do it. When you manually configure properties and settings, the settings become fixed, which means Windows 2000 cannot modify them in the future if a problem arises or there is a conflict with another device.

Run appropriate set up utility

Key files used for Windows 98 Setup