Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

March 12, 2009 12:00 AM

Q: Can two Active Directory (AD) accounts have identical SIDs? If so, how can I remove the duplicate account?

Windows IT Pro
InstantDoc ID #101495
Rating: (3)

A: Microsoft provides safeguards to ensure that identical SIDs aren't introduced in a Windows domain. By definition, a SID is unique in the context of a Windows domain, but the AD security system can accidentally give two accounts the same SID when the Relative Identifier (RID) master Flexible Single-Master Operations (FSMO) role is transferred from one domain controller (DC) to another.

The DC that hosts the RID master FSMO role keeps track of all RID pools assigned to the different DCs in a domain. The RID master ensures that each DC is given a unique, non-overlapping pool of RIDs. The RID master prevents duplicate SIDs in the domain, because the RID is a portion of a security principal's SID. Each AD account’s SID consists of the domain's SID and a RID, and the RID is unique for each security principal in a domain.

Duplicate SIDs can exist when an administrator transfers (or "seizes," in AD terminology) the RID master role to another DC while the original RID master is offline, such as if it's temporarily disconnected from the network. When the original RID master is brought back online and hasn't received updated AD replication information, including the RID master change, it could issue a RID pool to a DC that's identical to the RID pool that the other RID master already issued to another DC. These two DCs could generate identical RIDs, and thus identical SIDs, for newly created accounts.

Click to expand

To avoid the duplications, after you transfer the RID master role between DCs you should always check AD for duplicate SIDs and clean up the duplicate SIDs. You can check for and clean up duplicate SIDs from the command line using the ntdsutil utility, as shown here.

To check for duplicate accounts, do the following:

  1. Open a command prompt, type ntdsutil, and press Enter.

  2. Type security account management and press Enter.

  3. Type connect to server servername—where servername is the NETBIOS name or Fully Qualified Domain Name (FQDN) of the DC you're connecting to—and press Enter.

  4. Type check duplicate SID and press Enter.

  5. Type q and press Enter to exit the security account management menu.

  6. Type q and press Enter to leave the ntdsutil top menu.

These actions will create a log file called dupsid.log in the file system directory where you started ntdsutil. If any duplicate SIDs exist in your AD, they'll be listed in the dupsid.log file.

To clean up duplicate SIDs, do the following:

  1. Open a command prompt, type ntdsutil, and press Enter.

  2. Type security account management and press Enter.

  3. Type connect to server servername—where servername is the NETBIOS name or FQDN of the DC you're connecting to—and press Enter.

  4. Type cleanup duplicate SID and press Enter. Ntdsutil will then confirm the successful removal of duplicate SIDs.

  5. Type q and press Enter to exit the security account management menu.

  6. Type q and press Enter to leave the ntdsutil top menu.

These actions will delete one of the two account objects that have a duplicate SID—the account with the newest AD GUID. You must then manually recreate the deleted accounts, which will automatically receive new, unique SIDs.

Related Content:

ARTICLE TOOLS

Comments
  • kreangsak
    3 years ago
    Jun 03, 2009

    thx you very much

    http://youngadmin.blogspot.com

  • Smart
    3 years ago
    Apr 01, 2009

    To deal with Duplicate SIDs in the organization use DSM (Duplicate SIDs Monitor) written by Smart-X

    At www.smart-x.com

  • amrendra
    3 years ago
    Mar 27, 2009

    good job

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.