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?

 

 

 

 
 

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

 

 

MCSE Boot Camp, CCNA Bootcamp, CCNP Boot camp training in UK, USA, JAPAN, India
CCNA Training, MCSE Training, A+ Certification, MCSA, CCNP, Network+, Security+, CISSP, MCSD, CCSP,

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

 

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

 

 

MCSE : Security Specialist

Installing Windows 2000

Minimum hardware requirements

  • 133 MHz Pentium or higher microprocessor (or equivalent).
  • 64 megabytes of RAM recommended minimum 32 MB of RAM is the minimum supported. 4 gigabytes (GB) of RAM is the maximum.
  • 2 GB hard disk with 650 MB of free space.
  • VGA or higher resolution monitor.

Clean Install

Using the Setup startup disks

  • Insert Setup startup Disk 1.
  • Start your computer. Setup starts automatically.
  • Follow on screen instructions.

Using the CD

  • If Windows automatically detects the CD, click Install Windows 2000.
  • If Windows doesn't automatically detect the CD, start Setup from the Run command if you are in windows 9x.
  • Type cd drive:\i386\winnt32.exe
  • If you're using Windows 3.1 or the command prompt, type cd drive:\i386\winnt.exe
  • Follow on screen instructions.

Dual-Boot Configuration

Windows 2000 supports dual booting with the following operating systems

  • Windows NT 3.51, Windows NT 4.0
  • Windows 95, Windows 98
  • Windows 3.1, Windows for Workgroups 3.11
  • MS-DOS
  • OS/2

Start Up

Windows 9x Start Up Process

1) The ROM BIOS Bootstrap Process

  • Power On Self-Test (POST) occurs
  • The master boot record and partition table are read

2) The Master Boot Record and Boot Sector

The master boot record determines the location of the boot partition by reading the partition table located at the end of the master boot record. Once the location of the boot partition is determined, the master boot record passes control to the boot sector in that partition. The boot sector contains the disk boot program and a table of disk characteristics. The boot sector checks the BIOS Parameter Block (BPB) to find the location of the root directory, and then copies the Io.sys file from the root directory into memory.

3) The Io.sys File

  • A minimal file allocation table (FAT) file system is loaded
  • The MSDOS.SYS file is read
  • The Starting Windows message is displayed
  • The Logo.sys file is loaded and displays a startup image on the screen
  • If the Drvspace.ini or Dblspace.ini file exists, the Drvspace.bin or Dblspace.bin file is loaded into memory
  • The Io.sys file opens the System.dat file
  • The Dblbuff.sys file is loaded if the "DoubleBuffer=1" is in the Msdos.sys file
  • If you have multiple hardware profiles , the hardware profile you chose is loaded from the registry
  • The Io.sys file processes the Config.sys file

4) Real-Mode Configuration

Some hardware devices and programs require that drivers or files be loaded in real-mode in order for them to work properly. To ensure backwards compatibility with these types of hardware devices or programs, Windows 95 processes the Config.sys and Autoexec.bat files if they exist.

  • The Config.sys file loads drivers into memory. If the Config.sys file does not exist, the Io.sys file loads the following required drivers Ifshlp.sys, Himem.sys, and Setver.exe
  • Windows reserves all global upper memory blocks (UMBs) for Windows 9x operating system use or for expanded memory support (EMS).
  • The Autoexec.bat file loads files and terminate and stay resident (TSR) programs into memory

The Win.com File and the Windows 95 Environment

  • After the Autoexec.bat file is processed, the Win.com file is run
  • The Win.com file accesses the Vmm32.vxd file. If there is enough available RAM, the Vmm32.vxd file loads into memory, otherwise, it is accessed from the hard disk. This may result in a slower startup time. The Vmm32.vxd file is similar to the Win386.exe file used in earlier versions of Windows
  • The real-mode virtual device driver loader checks for duplicate virtual device drivers (VxDs) in the Windows\System\Vmm32 folder and the Vmm32.vxd file. If a VxD exists in both the Windows\System\Vmm32 folder and the Vmm32.vxd file, the duplicate VxD is "marked" in the Vmm32.vxd file so that it is not loaded.
  • The real-mode virtual device driver loader checks that all required VxDs loaded successfully. If not, it attempts to load the drivers again
  • Once the real-mode virtual device driver loading is logged, driver initialization occurs. If there are any VxDs that require real-mode initialization, they begin their process in real-mode.
  • Vmm32 switches the computer's processor from real-mode to protected- mode
  • After all the static VxDs are loaded, the Krnl32.dll, Gdi.exe, User.exe, and Explorer.exe (the default Windows 95 shell) files are loaded.

Network Environment and Multi-User Profiles

The next step in the startup process is to load the network environment. Once this occurs, the user is prompted to log on to the network that is installed.

Windows 95 allows multiple users to save their custom desktop settings. When a user logs on to Windows 95, their desktop settings are loaded from the registry. If the user does not log on, the desktop configuration uses a default desktop.

 

 


© Vibrant Worldwide Inc.