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

CCNA Training, MCSE Training, A+ Certification, MCSA, CCNP, Network+, Security+, CISSP, MCSD, CCSP,

MCSE Exam, free Real Exam Test, Guide, Prepare MCSE

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

Dual boot Windows 9x/Windows NT 4.0/2000

Windows 2000 supports multiple booting with MS-DOS, OS/2, Windows 3.x, Windows 95, Windows 98, Windows NT 3.51, and Windows NT 4.0.

If you intend to create a dual-boot system with Windows NT 4.0 and Windows 2000 as the only installed operating systems, you must ensure that you have installed Service Pack 4 for Windows NT 4.0. Windows 2000 will automatically upgrade any NTFS partitions it finds on your system to NTFS 5. Windows NT 4.0 requires Service Pack 4 to be able to read and write files on an NTFS 5 volume.

Each operating system should be installed on a separate drive or disk partition.

You should use a FAT file system for dual-boot configurations. Although using NTFS in a dual boot is supported, such a configuration introduces additional complexity into the choice of file systems.

You cannot install both Windows 95 and Windows 98 in a multiple-boot configuration. Windows 98 is intended as an upgrade to Windows 95 and will try to use the same boot file.

To set up a dual-boot configuration between MS-DOS or Windows 95 and Windows 2000, you should install Windows 2000 last. Otherwise, important files needed to start Windows 2000 could be overwritten.

For a dual boot between Windows 98 and Windows 2000, it isn't necessary to install the operating systems in a particular order.

For a dual boot of Windows 2000 with Windows 95 or MS-DOS, the primary partition must be formatted as FAT; for a dual boot with Windows 95 OSR2 or Windows 98, the primary partition must be formatted as FAT or FAT32, not NTFS.

If you're upgrading a dual-boot computer, you can't gain access to NTFS partitions from any operating system other than Windows NT 4.0 with SP4.

If you install Windows 2000 on a computer that dual boots OS/2 and MS-DOS, Windows 2000 Setup configures your system so you can dual boot between Windows 2000 and the operating system (MS-DOS or OS/2) you most recently used before running Windows 2000 Setup.

Don't install Windows 2000 on a compressed drive unless the drive was compressed with the NTFS file system compression utility.

Windows 95 or Windows 98 might reconfigure hardware settings the first time you use them, which can cause problems if you're dual booting with Windows 2000. So run these OS's first before installing 2000.

If you want your programs to run on both operating systems on a dual-boot computer, you need to install them from within each operating system. You can't share programs across operating systems.