The key AD database files—edb.log, ntds.dit, res1.log, res2.log, and edb.chk—all of which reside in %systemroot%ntds on a domain controller (DC) by default. During AD installation, Dcpromo lets you specify alternative locations for these log files and database files NTDS.DIT

NTFS Version 5 features Encryption is possible We can enable Disk Quotas File compression is possible Sparse files Indexing Service NTFS change journal In FAT file system we can apply only share level security. File level protection is not possible. In NTFS we can apply both share level as well as file level security NTFS supports large partition sizes than FAT file systems NTFS supports long file names than FAT file systems

There is a four way negotiation process b/w client and server DHCP Discover (Initiated by client) DHCP Offer (Initiated by server) DHCP Select (Initiated by client) DHCP Acknowledgment (Initiated by Server) DHCP Negative Acknowledgment (Initiated by server if any issues after DHCP offer)

Implicit Trusts Explicit Trusts—NT to Win2k or Forest to Forest

Client will not get IP and it cannot be participated in network . If client already got the IP and having lease duration it use the IP till the lease duration expires.

DNS is a Domain Naming System, which resolves Host names to IP addresses. It uses fully qualified domain names. DNS is a Internet standard used to resolve host names WINS is a Windows Internet Name Service, which resolves Netbios names to IP Address. This is proprietary for Windows

There is no difference between in DC and ADC both contains write copy of AD. Both can also handles FSMO roles (If transfers from DC to ADC). It is just for identification. Functionality wise there is no difference.

PDC contains a write copy of SAM database where as BDC contains read only copy of SAM database. It is not possible to reset a password or create objects with out PDC in Windows NT.

Application Server mode is introduced in windows 2003 Possible to configure stub zones in windows 2003 DNS Volume shadow copy services is introduced Windows 2003 gives an option to replicate DNS data b/w all DNS servers in forest or All DNS servers in the domain. Refer Question 1 for all Enhancements

NT SAM database is a flat database. Where as in windows 2000 active directory database is a hierarchical database. In windows NT only PDC is having writable copy of SAM database but the BDC is only read only database. In case of Windows 2000 both DC and ADC is having write copy of the database Windows NT will not support FAT32 file system. Windows 2000 supports FAT32 Default authentication protocol in NT is NTLM (NT LAN manager). In windows 2000 default authentication protocol is Kerberos V5. Windows 2000 depends and Integrated with DNS. NT user Netbios names Active Directory can be backed up easily with System state data

ACTIVE DIRECTORY Easier Deployment and Management ADMT version 2.0—migrates password from NT4 to 2000 to 20003 or from 2000 to 2003 Domain Rename— supports changing Domain Name System and/or NetBios name Schema Redefine— Allows deactivation of attributes and class definitions in the Active directory schema AD/AM— Active directory in application mode is a new capability of AD that addresses certain deployment scenarios related to directory enabled applications Group Policy Improvements—-introduced GPMC tool to manage group policy UI—Enhanced User Interface Grater Security Cross-forest Authentication Cross-forest Authorization Cross-certification Enhancements IAS and Cross-forest authentication Credential Manager Software Restriction Policies Improved Performance and Dependability Easier logon for remote offices Group Membership replication enhancements Application Directory Partitions Install Replica from media Dependability Improvements— updated Inter-Site Topology Generator (ISTG) that scales better by supporting forests with a greater number of sites than Windows 2000. FILE AND PRINT SERVICES Volume shadow copy service NTFS journaling file system EFS Improved CHDSK Performance Enhanced DFS and FRS Shadow copy of shared folders Enhanced folder redirection Remote document sharing (WEBDAV)   IIS Fault-tolerant process architecture—– The IIS 6.0 fault-tolerant process architecture isolates Web sites and applications into self-contained units called application pools Health Monitoring—- IIS 6.0 periodically checks the status of an application pool with automatic restart on failure of the Web sites and applications within that application pool, increasing application availability. IIS 6.0 protects the server, and other applications, by automatically disabling Web sites and applications that fail too often within a short amount of time Automatic Process Recycling— IIS 6.0 automatically stops and restarts faulty Web sites and applications based on a flexible set of criteria, including CPU utilization and memory consumption, while queuing requests Rapid-fail Protection—- If an application fails too often within a short amount of time, IIS 6.0 will automatically disable it and return a “503 Service Unavailable” error message to any new or queued requests to the application Edit-While-Running