Home | Contact Us | Submit Troubleshooting Info | Search | Help


    Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS

SID # on NT Platforms - Potential Problems with Cloning

Applies to

 NT 3.51, 4.0 on Alpha and Intel platforms.

Problem/Causes

 There are a number of potential problems that can result from "cloning" of the NT OS.  The following is intended for reference only.  Before attempting to clone machines, please contact the Response Center.

Workgroup problems

a) SID (Security IDentifier) problems:

  • Cloning the OS will cause the local computer account security database to be identical, compromising security on a workgroup.
  • Share volumes can be accessed by accounts that should not be able to.

b) RID (Relative IDentifier) problems:

  • Consecutive accounts created on the duplicate OS, regardless of name, will have the same RID and will therefore be provided with access identical to the original OS account.

c) Removable devices:

  • NTFS security permissions will be compromised when the NTFS permissions are created on a cloned OS and read from a machine with the same SID.

Domain issues

A BDC or PDC (Domain Controllers) should not be cloned unless it is to replace the current BDC or PDC.  The domain accounts databases will not function properly.

Solution

 For further information, or for details on how to use the new SID generating program, see http://www.sysinternals.com/ntw2k/source/newsid.shtml (use at own risk - not recommended by Microsoft)
 
Contact Landon Guretzki (2021)
Submitted by Landon Guretzki (2021)
Date March 8, 1999

    Copyright © 2005 Creo Inc. All rights reserved. Confidential. Back to top.