Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

SID as

1) Help me to clarify the concept of computer SID on hypothetical situation:

suppose, I want to secure a network cable (for ex., from a workstation to the nearest switcher).

What should I minimally add to this cable in order to enable it security identifiable with SID:

  • RAM?
  • HDD (hard disk)?
  • CPU?
  • Operating system?

2) Having a Windows XP machine joined to AD domain, will a parallel (multiboot) installation of a second Windows XP bring to machine the same host/computer SID or a new one?

3) If I use an image copy of hard disk (or hard disk) with Windows XP Pro from computer A to boot from computer B, with which computer SID - of PC A or of PC B - such booted Windows XP be identified by domain controller?

share|improve this question

closed as not a real question by John Gardeniers, Chris Thorpe, splattne Aug 2 '10 at 6:33

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

You have a fundamental misunderstanding of what a SID is and how it works. – MDMarra Jul 31 '10 at 14:34
up vote 4 down vote accepted

You misunderstand how the SID is generated in Windows. There are two parts to the SID. One part is domain dependent, the second part is a generated value and is unique to that workstation. The generation process does not include any hardware inputs, it is simply a random number. It is created during the install process, and stored in the registry. When it is domained, it gets a domain SID, which is the combination of the Domain's SID and the local machine's SID.

1: That is not how the SID works in windows. The SID belongs to the workstation only.

2: Assuming both XP installs were created through the normal install process, each parallel installation will have a unique SID. As far as AD is concerned, you have two machines on your workstation.

3: If PC B was created as an exact copy of PC A, the two will share a SID. There was a single install process where the SID was created and the registry populated. The Registry was copied as part of the imaging process. The Domain Controller will identify them as the same machine (mostly, but explaining would take a lot more text).

Users also have a SID, but that's not needed for this discussion.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.