Explore topic-wise InterviewSolutions in .

Group POLICY applies to the user or COMPUTER in a MANNER that depends on where both the user and the computer objects are located in Active Directory. However, in some cases, users may NEED policy applied to them based on the location of the computer object alone. You can use the Group Policy loopback feature to APPLY Group Policy Objects (GPOs) that depend only on which computer the user logs on to.

Group Policy applies to the user or computer in a manner that depends on where both the user and the computer objects are located in Active Directory. However, in some cases, users may need policy applied to them based on the location of the computer object alone. You can use the Group Policy loopback feature to apply Group Policy Objects (GPOs) that depend only on which computer the user logs on to.

Name servers in delegations are identified by name, rather than by IP address. This MEANS that a RESOLVING name server must issue another DNS request to find out the IP address of the server to which it has been referred. If the name given in the delegation is a subdomain of the DOMAIN for which the delegation is being provided, there is a CIRCULAR dependency. In this case the name server providing the delegation must also provide one or more IP addresses for the authoritative name server mentioned in the delegation. This information is called glue. The delegating name server provides this glue in the form of records in the additional section of the DNS response, and provides the delegation in the answer section of the response.

For EXAMPLE, if the authoritative name server for example.org is ns1.example.org, a computer trying to resolve www.example.org first resolves ns1.example.org. Since ns1 is contained in example.org, this requires resolving example.org first, which presents a circular dependency. To break the dependency, the name server for the top level domain org includes glue along with the delegation for example.org. The glue records are address records that provide IP addresses for ns1.example.org. The resolver uses one or more of these IP addresses to query one of the domain’s authoritative servers, which allows it to complete the DNS query.

Name servers in delegations are identified by name, rather than by IP address. This means that a resolving name server must issue another DNS request to find out the IP address of the server to which it has been referred. If the name given in the delegation is a subdomain of the domain for which the delegation is being provided, there is a circular dependency. In this case the name server providing the delegation must also provide one or more IP addresses for the authoritative name server mentioned in the delegation. This information is called glue. The delegating name server provides this glue in the form of records in the additional section of the DNS response, and provides the delegation in the answer section of the response.

For example, if the authoritative name server for example.org is ns1.example.org, a computer trying to resolve www.example.org first resolves ns1.example.org. Since ns1 is contained in example.org, this requires resolving example.org first, which presents a circular dependency. To break the dependency, the name server for the top level domain org includes glue along with the delegation for example.org. The glue records are address records that provide IP addresses for ns1.example.org. The resolver uses one or more of these IP addresses to query one of the domain’s authoritative servers, which allows it to complete the DNS query.

dnscmd COMMAND can be used for CREATING a RESOURCE Record on DNS server.

Below is the command:

dnscmd [&LT;ServerName&GT;] /recordadd <ZoneName> <NodeName> <RRType> <RRData>

dnscmd command can be used for creating a Resource Record on DNS server.

Below is the command:

dnscmd [<ServerName>] /recordadd <ZoneName> <NodeName> <RRType> <RRData>

FCInfo UTILITY or Storage Explorer (windows 2008) can be used to CHECK the same.

FCInfo utility or Storage Explorer (windows 2008) can be used to check the same.

Windows 2003 Boot Process:

1. POST
2. The MBR reads the boot sector which is the first sector of the active partition.
3. Ntldr looks path of OS from boot.ini
4. Ntldr to run ntdedetect.com to get information about installed hardware.
5. Ntldr reads the REGISTRY files then select a hardware profile, control set and loads device drivers.
6. After that Ntoskrnl.exe takes over and starts winlogon.exe which starts lsass.exe

Windows Server 2008 Boot process.

1. System is powered on
2. The CMOS loads the BIOS and then runs POST
3. Looks for the MBR on the bootable device
4. Through the MBR the boot sector is located and the BOOTMGR is loaded
5. BOOTMGR looks for active partition
6. BOOTMGR reads the BCD file from the boot directory on the active partition
7. The BCD (boot configuration database) contains various configuration parameters( this information was previously stored in the boot.ini)
8. BOOTMGR transfer control to the Windows Loader (winload.exe) or winresume.exe in case the system was hibernated.
9. Winloader loads drivers that are set to start at boot and then TRANSFERS the control to the windows kernel.

Windows 2003 Boot Process:

Windows Server 2008 Boot process.

FIRSTLY, schmmgmt.dll has to be REGISTERED. Then ADSI Edit tool can be USED to edit schema.

Firstly, schmmgmt.dll has to be registered. Then ADSI Edit tool can be used to edit schema.

Here’s the brief DESCRIPTION of Windows Server 2008 Boot process:

1. System is powered on
2. The CMOS loads the BIOS and then runs POST
3. Looks for the MBR on the bootable device
4. Through the MBR the boot sector is located and the BOOTMGR is loaded
5. BOOTMGR looks for ACTIVE partition
6. BOOTMGR READS the BCD file from the boot directory on the active partition
7. The BCD (boot configuration database) contains various configuration parameters( this information was previously stored in the boot.ini)
8. BOOTMGR transfer control to the Windows Loader (winload.exe) or winresume.exe in case the system was hibernated.
9. Winloader loads drivers that are set to START at boot and then transfers the control to the windows kernel.

Here’s the brief description of Windows Server 2008 Boot process:

It can be troubleshooted by repmon command that GENERATES the error RESULT in eventvwr. DNS can be CHECKED between two destination. Network/Firewall issue

It can be troubleshooted by repmon command that generates the error result in eventvwr. DNS can be checked between two destination. Network/Firewall issue

You can use AD inbuilt features to TROUBLESHOOT group policy issue LIKE RSOP.msc or can RUN RSOP by selecting users in Active Directory users and computers, gpresult -V, gpt.ini in sysvol under Group Policy GUID folder can be checked to find out the GPO settings configured.

You can use AD inbuilt features to troubleshoot group policy issue like RSOP.msc or can run RSOP by selecting users in Active Directory users and computers, gpresult -v, gpt.ini in sysvol under Group Policy GUID folder can be checked to find out the GPO settings configured.

WINDOWS DEBUGGER (WinDbg.EXE) TOOL

Dumpchk,exe

Windows Debugger (WinDbg.exe) tool

Dumpchk,exe

Host A records of replication partners (Domain CONTROLLERS), SRV Records to FIND out the Domain Controllers GUID in _msdcs ZONE (DC Locator)

Host A records of replication partners (Domain Controllers), Srv Records to find out the Domain Controllers GUID in _msdcs zone (DC Locator)

To generate a complete MEMORY dump FILE:

1. Click Start &GT; right-click Computer and select Properties in the MENU.
2. Click Advanced > Settings > Startup and Recovery > Settings > Write DEBUGGING information > Complete memory dump.
3. Click OK twice.

To generate a complete memory dump file:

A superscope is an administrative feature of Dynamic Host Configuration Protocol (DHCP) servers running Windows Server 2008 that you can create and manage by using the DHCP Microsoft Management Console (MMC) snap-in. By using a superscope, you can group multiple scopes as a SINGLE administrative entity. With this feature, a DHCP server can:

• Support DHCP clients on a single physical network segment (such as a single Ethernet LAN segment) where multiple logical IP networks are used. When more than one logical IP network is used on each physical subnet or network, such configurations are often called multinets.
• Support remote DHCP clients LOCATED on the far side of DHCP and BOOTP relay AGENTS (where the network on the far side of the relay agent uses multinets).

In multinet configurations, you can use DHCP superscopes to group and activate individual scope ranges of IP addresses used on your network. In this way, the DHCP server can activate and provide leases from more than one scope to clients on a single physical network.

• Superscopes can resolve specific types of DHCP deployment issues for multinets, including situations in which:
• The available address pool for a currently active scope is nearly depleted, and more computers need to be added to the network. The original scope INCLUDES the full addressable range for a single IP network of a specified address class. You need to use another range of IP addresses to extend the address space for the same physical network segment.
• Clients must be migrated over time to a new scope (such as to renumber the current IP network from an address range used in an existing active scope to a new scope that contains another range of IP addresses).
• You want to use two DHCP servers on the same physical network segment to manage separate logical IP networks.

A superscope is an administrative feature of Dynamic Host Configuration Protocol (DHCP) servers running Windows Server 2008 that you can create and manage by using the DHCP Microsoft Management Console (MMC) snap-in. By using a superscope, you can group multiple scopes as a single administrative entity. With this feature, a DHCP server can:

In multinet configurations, you can use DHCP superscopes to group and activate individual scope ranges of IP addresses used on your network. In this way, the DHCP server can activate and provide leases from more than one scope to clients on a single physical network.

Strict Replication is a mechanism developed by Microsoft DEVELOPERS for Active Directory Replication. If a domain controller has the Strict Replication enabled then that domain controller will not get “Lingering Objects” from a domain controller which was isolated for more than the TombStone Life Time. TSL is 180 days by default on a Forest created with Windows Server 2003 SP1. A domain controller shouldn’t be outof sync for more than this period. Lingering Objects may appear on other domain controllers if replication happens with the outdated domain controllers. These domain controllers will not replicate with the outdated domain controllers if you have set the below MENTIONED registry key.You must set the following registry setting on all the domain controllers to ENABLE the Strict Replication:

KEY NAME:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNTDSParameters

Registry Entry: Strict Replication Consistency

Value: 1 (enabled), 0 (DISABLED)

Type: REG_DWORD

Strict Replication is a mechanism developed by Microsoft developers for Active Directory Replication. If a domain controller has the Strict Replication enabled then that domain controller will not get “Lingering Objects” from a domain controller which was isolated for more than the TombStone Life Time. TSL is 180 days by default on a Forest created with Windows Server 2003 SP1. A domain controller shouldn’t be outof sync for more than this period. Lingering Objects may appear on other domain controllers if replication happens with the outdated domain controllers. These domain controllers will not replicate with the outdated domain controllers if you have set the below mentioned registry key.You must set the following registry setting on all the domain controllers to enable the Strict Replication:

KEY Name:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNTDSParameters

Registry Entry: Strict Replication Consistency

Value: 1 (enabled), 0 (disabled)

Type: REG_DWORD

• Read-Only DOMAIN CONTROLLERS
• Fine-Grained Password POLICIES
• Restartable ACTIVE Directory Service
• BACKUP and Recovery
• SYSVOL Replication with DFS-R
• Auditing Improvements
• UI Improvements

UNICAST:

Unicast is a one-to one connection between the client and the server. Unicast uses IP delivery methods such as Transmission Control Protocol (TCP) and User Datagram Protocol (UDP), which are session-based protocols. When a Windows Media Player client connects USING unicast to a Windows Media server, that client has a direct relationship to the server. Each unicast client that connects to the server takes up ADDITIONAL bandwidth. For example, if you have 10 clients all playing 100-kilobits per second (Kbps) streams, those clients as a group are taking up 1,000 Kbps. If you have only one client playing the 100 Kbps stream, only 100 Kbps is being used.

Multicast:

Multicast is a true broadcast. The multicast source relies on multicast-enabled routers to forward the packets to all client subnets that have clients listening. There is no direct relationship between the clients and Windows Media server. The Windows Media server generates an .nsc (NetShow channel) file when the multicast station is FIRST created. Typically, the .nsc file is delivered to the client from a Web server. This file contains information that the Windows Media Player needs to listen for the multicast. This is similar to tuning into a station on a radio. Each client that listens to the multicast adds no additional OVERHEAD on the server. In fact, the server sends out only one stream per multicast station. The same load is experienced on the server whether only one client or 1,000 clients are listening

http://support.microsoft.com/kb/291786

Unicast:

Unicast is a one-to one connection between the client and the server. Unicast uses IP delivery methods such as Transmission Control Protocol (TCP) and User Datagram Protocol (UDP), which are session-based protocols. When a Windows Media Player client connects using unicast to a Windows Media server, that client has a direct relationship to the server. Each unicast client that connects to the server takes up additional bandwidth. For example, if you have 10 clients all playing 100-kilobits per second (Kbps) streams, those clients as a group are taking up 1,000 Kbps. If you have only one client playing the 100 Kbps stream, only 100 Kbps is being used.

Multicast:

Multicast is a true broadcast. The multicast source relies on multicast-enabled routers to forward the packets to all client subnets that have clients listening. There is no direct relationship between the clients and Windows Media server. The Windows Media server generates an .nsc (NetShow channel) file when the multicast station is first created. Typically, the .nsc file is delivered to the client from a Web server. This file contains information that the Windows Media Player needs to listen for the multicast. This is similar to tuning into a station on a radio. Each client that listens to the multicast adds no additional overhead on the server. In fact, the server sends out only one stream per multicast station. The same load is experienced on the server whether only one client or 1,000 clients are listening

http://support.microsoft.com/kb/291786

A majority NODE SET is a single quorum resource, from a server CLUSTER PERSPECTIVE; HOWEVER, the data is actually stored on multiple disks across the cluster. Each cluster node stores the configuration on a local disk it can have access to when it starts up. By default, the location is pointed to %systemroot%clusterResourceGUID

Further Explained :- http://www.yourcomputer.in/windows-cluster-interview-questions-and-answers/

If the configuration of the cluster changes, that change is replicated across the different disks

A majority node set is a single quorum resource, from a server cluster perspective; however, the data is actually stored on multiple disks across the cluster. Each cluster node stores the configuration on a local disk it can have access to when it starts up. By default, the location is pointed to %systemroot%clusterResourceGUID

Further Explained :- http://www.yourcomputer.in/windows-cluster-interview-questions-and-answers/

If the configuration of the cluster changes, that change is replicated across the different disks

Both do the same thing like forwarding the requests to appropriate name servers who are authoritative for the DOMAINS in the queries. However, there is difference in both, Stub Zone are Dynamic and Conditional forwarder are static.

Conditional Forwarding –  Where you want DNS clients in separate networks to resolve each others’ names without having to query DNS servers on the Internet, such as in the case of a company merger, you should configure the DNS servers in each network to forward queries for names in the other network. DNS servers in one network will forward names for clients in the other network to a specific DNS server that will BUILD up a large cache of information about the other network. When forwarding in this WAY, you create a direct point of contact between two networks’ DNS servers, reducing the need for recursion.

Stub Zone– Stub-Zones are dynamic -A stub zone is like a secondary zone in that it obtains its resource records from other name servers (one or more master name servers). A stub zone is also read-only like a secondary zone, so administrators can’t manually add, REMOVE, or modify resource records on it. But the differences end here, as stub zones are quite different from secondary zones in a couple of significant ways.First, while secondary zones contain copies of all the resource records in the CORRESPONDING zone on the master name server, stub zones contain only three kinds of resource records:

• A copy of the SOA record for the zone.
• Copies of NS records for all name servers authoritative for the zone.
• Copies of A records for all name servers authoritative for the zone.

Both do the same thing like forwarding the requests to appropriate name servers who are authoritative for the domains in the queries. However, there is difference in both, Stub Zone are Dynamic and Conditional forwarder are static.

Conditional Forwarding –  Where you want DNS clients in separate networks to resolve each others’ names without having to query DNS servers on the Internet, such as in the case of a company merger, you should configure the DNS servers in each network to forward queries for names in the other network. DNS servers in one network will forward names for clients in the other network to a specific DNS server that will build up a large cache of information about the other network. When forwarding in this way, you create a direct point of contact between two networks’ DNS servers, reducing the need for recursion.

Stub Zone– Stub-Zones are dynamic -A stub zone is like a secondary zone in that it obtains its resource records from other name servers (one or more master name servers). A stub zone is also read-only like a secondary zone, so administrators can’t manually add, remove, or modify resource records on it. But the differences end here, as stub zones are quite different from secondary zones in a couple of significant ways.First, while secondary zones contain copies of all the resource records in the corresponding zone on the master name server, stub zones contain only three kinds of resource records: