Posts

Showing posts from May, 2019

An update is available to detect and prevent too much consumption of the global RID pool on a domain controller that is running Windows Server 2008 R2

Introduction Active Directory Domain Services (AD DS) assigns unique security identifiers (SIDs) to users, computers, groups, and trusts that are created in Active Directory. SIDs consist of a domain prefix concatenated with a monotonically increasing relative identifier (RID). Each Active Directory domain is assigned a global RID pool that consists of 1 billion RIDs. To enable each Active Directory domain controller to create new security principals, each domain controller is allocated current and standby RID pools from the RID master. When the global RID pool for the domain and for the local pools on individual domain controllers in a domain is exhausted, additional users, computers, and groups can no longer be created in the domain. To work around this issue, you can create and migrate objects and applications to a new domain. This article describes a condition in which a logic failure may result in too many RID pool requests. This leads to global RID pool exhaustio

Active Directory Repadmin Tool

Image
Active Directory Repadmin Tool Table of Contents Introduction The Repadmin tool Capture replication summary status of an entire forest Capture replication status for each naming context (partition) across all Domain Controllers in a forest View replication partners of a Domain Controller Initiate replication event between two replication partners View Replication Metadata for an object Check the replication queue status View connection objects for a Domain Controller View highest Update Sequence Number on a Domain Controller View unreplicated changes between two Domain Controllers Summary Introduction Active Directory (AD) was one of the first LDAP-based directories to adopt and implement multi-master replication model. In a multi master replication model, there is no single "Master" or writable Domain Controller in the  domain. Instead, all Domain Controllers are writable except Read Only Domain Controllers (RODCs). While the multi mast

Troubleshooting IIS Performance Issues or Application Errors using LogParser

Image
Tools and knowledge used in this Troubleshooter Microsoft LogParser ( https://www.microsoft.com/en-us/download/details.aspx?id=24659) ) Command Prompt A basic knowledge of IIS HTTP Status Codes is helpful ( https://support.microsoft.com/kb/943891) ) A basic knowledge of SQL queries is helpful Overview This troubleshooter will help you analyze IIS log files in an effort to determine the cause when an application that is hosted on IIS is failing or experiencing performance issues. Before you begin, it is important to note that all fields IIS can log are not enabled by default. For example,  Bytes Sent  and  Bytes Received  are not selected, but they are very useful when troubleshooting a performance problem. Therefore, the best time to include these additional fields is before you are experiencing system problems. So if you haven't already done so, select these additional fields, they will help you find solutions when problems happen. The following blog which discusses