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 - Cheapest, Fast, Guaranteed 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

Windows NT

To create setup disks

You will need four blank, formatted, 1.44-MB floppy disks. Label them Setup Disk One, Setup Disk Two, and Setup Boot Disk.

Insert disk into the floppy disk drive

Insert the Windows NT CD-ROM into the CD-ROM drive

From Windows 9x click Start, and then click Run

Type cd drive:\i386\winnt /ox

From Windows NT click Start, Type cd drive:\i386\winnt /ox

Follow the screen prompts

Windows 2000

To create setup disks

You will need four blank, formatted, 1.44-MB floppy disks. Label them Setup Disk One, Setup Disk Two, Setup Disk Three, and Setup Disk Four

Insert disk into the floppy disk drive

Insert the Windows 2000 CD-ROM

Click Start, and then click Run

Type d:\bootdisk\makeboot a:

Follow the screen prompts

You can also create these setup disks from the DOS command line.

Safe Mode

Windows automatically initiates Safe Mode if it detects that system startup failed , or if the registry is corrupted.

Safe Mode bypasses startup files, including the registry, Config.sys, Autoexec.bat, and the [Boot] and [386Enh] sections of System.ini, and provides you with access to the Windows configuration files. You can make any necessary configuration changes, and then restart Windows normally.

Windows in Safe Mode, only the mouse, keyboard, and standard VGA device drivers are loaded.

Safe Mode With Networking is not supported in Windows 98.

Safe Mode Command Prompt Only loads the Command.com and DoubleSpace or DriveSpace files (if present). It does not load Himem.sys, Ifshlp.sys, or Windows .

Step-by-Step Confirmation allows you to specify which commands and drivers the system should process by confirming each line of the startup files.

Safe Mode and Windows 2000

Options

Safe Mode - Starts Windows 2000 using only basic files and drivers (mouse, except serial mice; monitor; keyboard; mass storage; base video; default system services; and no network connections).

Safe mode with Networking - Starts Windows 2000 using only basic files and drivers, plus network connections.

Safe Mode with Command Prompt - Starts Windows 2000 using only basic files and drivers. After logging on, the command prompt is displayed instead of the Windows desktop.

Enable Boot Logging - Starts Windows 2000 while logging all the drivers and services that were loaded (or not loaded) by the system to a file. This file is called ntbtlog.txt and it is located in the windir directory. Safe Mode, Safe Mode with Networking, and Safe Mode with Command Prompt add to the boot log a list of all the drivers and services that are loaded. The boot log is useful in determining the exact cause of system startup problems.

Enable VGA Mode - Starts Windows 2000 using the basic VGA driver. The basic video driver is always used when you start Windows 2000 in Safe Mode (either Safe Mode, Safe Mode with Networking, or Safe Mode with Command Prompt).

Last Known Good Configuration - Starts Windows 2000 using the registry information that Windows saved at the last shutdown. Use only in cases of incorrect configuration. Last known good configuration does not solve problems caused by corrupted or missing drivers or files. Also, any changes made since the last successful startup will be lost.

Debugging Mode - Starts Windows 2000 while sending debug information through a serial cable to another computer.