karthik's blog

Replication Sequence  

The protocols that are used by Active Directory replication are described in the following table. RPC and SMTP are the replication transport protocols. LDAP is a directory access protocol, and IP is a network wire protocol. Active Directory Access and Replication Protocols   Protocol Description LDAP The primary directory access protocol for Active Directory. Windows Server 2003 family, Windows XP, Windows 2000 Server family, and Windows 2000 Professional clients, as well as Windows 98, Windows 95, and Windows NT 4.0 clients that have the Active Directory client components installed, use LDAP v3 to connect to Active Directory. IP Routable protocol that is responsible for the addressing, routing, and fragmenting of packets by the sending node. IP is required for Active Directory replication. Replication RPC The Directory Replication Service (Drsuapi) RPC protocol, used in the enabling of administration and monitor...

Adding Mail Exchange Servers MX records identify mail exchange servers for the domain. These servers are responsible for processing or forwarding mail within the domain. When you create an MX record, you must specify a preference number for the mail server. A preference number is a value from 0 to 65,535 that denotes the mail server's priority within the domain. The mail server with the lowest preference number has the highest priority and is the first to receive mail. If mail delivery fails, the mail server with the next lowest preference number is tried. You create a MX record by doing the following: In the DNS console, expand the Forward Lookup Zones folder for the server you want to work with. Right-click the domain you want to update, and then from the pop-up menu, choose New Mail Exchanger. This opens the dialog box shown in Figure 19-10. You can now create a record for the mail server by filling in these fields: Host Or Domain Enter the optional host name. Mail Server Ente...

The global catalog is a distributed data repository that contains a searchable, partial representation of every object in every domain in a multidomain Active Directory Domain Services (AD DS) forest. The global catalog is stored on domain controllers that have been designated as global catalog servers and is distributed through multimaster replication. Searches that are directed to the global catalog are faster because they do not involve referrals to different domain controllers. Note In Windows Server® 2003 and Microsoft Windows® 2000 Server, the directory service is named Active Directory. In Windows Server 2008 R2 and Windows Server 2008, the directory service is named Active Directory Domain Services. The rest of this topic refers to AD DS, but the information is also applicable to Active Directory. In addition to configuration and schema directory partition replicas, every domain controller in a forest stores a full, writable replica of a single domain directory partition...

Overview Active Directory is backed up as part of system state, a collection of system components that depend on each other. You must back up and restore system state components together. Components that comprise the system state on a domain controller include: System Start-up Files (boot files). These are the files required for Windows 2000 Server to start. System registry. Class registration database of Component Services. The Component Object Model (COM) is a binary standard for writing component software in a distributed systems environment. SYSVOL. The system volume provides a default Active Directory location for files that must be shared for common access throughout a domain. The SYSVOL folder on a domain controller contains: NETLOGON shared folders. These usually host user logon scripts and Group Policy objects (GPOs) for non-Windows 2000based network clients. User logon scripts for Windows 2000 Professionalbased clients and clients that are running Windows 95, Windo...

Windows Server 2008 System Requirements This software is intended for evaluation and deployment planning purposes only. If you plan to install the software on your primary computer, it is recommended that you back up your existing data prior to installation. To use Windows Server 2008, you need*: Component Requirement Processor • Minimum: 1 GHz (x86 processor) or 1.4 GHz (x64 processor) • Recommended: 2 GHz or faster Note: An Intel Itanium 2 processor is required for Windows Server 2008 for Itanium-Based Systems. Memory • Minimum: 512 MB RAM • Recommended: 2 GB RAM or greater • Maximum (32-bit systems): 4 GB (Standard) or 64 GB (Enterprise and Datacenter) • Maximum (64-bit systems): 32 GB (Standard) or 1 TB (Enterprise and Datacenter) or 2 TB (Itanium-Based Systems) Available Disk Space • Minimum: 10 GB • Recommended: 40 GB or greater Note: Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files. ...

Review the table on this page to determine the minimum and recommended system requirements needed to run Windows Server 2003, Standard Edition, Enterprise Edition, Datacenter Edition, and Web Edition . Requirement Standard Edition Enterprise Edition Datacenter Edition Web Edition Minimum CPU Speed 133 MHz 133 MHz for x86-based computers 733 MHz for Itanium-based computers* 400 MHz for x86-based computers 733 MHz for Itanium-based computers* 133 MHz Recommended CPU Speed 550 MHz 733 MHz 733 MHz 550 MHz Minimum RAM 128 MB 128 MB 512 MB 128 MB Recommended Minimum RAM 256 MB 256 MB 1 GB 256 MB Maximum RAM 4 GB 32 GB for x86-based computers 512 GB for Itanium-based computers* 64 GB for x86-based computers 512 GB for Itanium-based computers* 2 GB Multiprocessor Support ** Up to 4 Up to 8 Minimum 8 required Maximum 64 Up to 2 Disk Space for Setup 1.5 GB 1.5 GB for x86-based computers 2.0 GB for Itanium-based computers* 1.5 GB for x86-based computers 2.0 GB for...

The  BCDEdit /set  command sets a boot entry option value in the Windows boot configuration data store (BCD). Use the  BCDEdit /set  command to configure specific boot entry elements, such as kernel debugger settings, data execution protection (DEP) and processor address extension (PAE) options, and to load alternate hardware abstraction layer (HAL) and kernel files. You can use these boot entry options when you are testing and debugging your driver for Windows Vista, Windows 7, and later versions of Windows. bcdedit /set [{ID}] datatype value Parameters [ { ID }] The  { ID }  is the GUID that is associated with the boot entry. If you do not specify an  { ID } , the command modifies the current operating system boot entry. If a boot entry is specified, the GUID associated with the boot entry must be enclosed in braces  { } . To view the GUID identifiers for all of the active boot entries, use the  bcdedit...