SIDS in an AD 2003 Domain

Archived from groups: microsoft.public.win2000.active_directory,microsoft.public.windows.server.active_directory,microsoft.public.windowsxp.customize,microsoft.public.windowsxp.setup_deployment (More info?)

ALL XP Pros...


I am working in an environment where all workstations have the same SID
because SYSPREP was never ran on the workstations...will there be issues to
this deployment of and the clients?

Please provide Microsoft documents and link if possible thanks...

I know duplicate SIDS should not be used period, but I need documentations -
also is there a documents that says MS does NOT support duplicate SIDs in an
evironment - thanks.

Archived from groups: microsoft.public.win2000.active_directory,microsoft.public.windowsxp.customize,microsoft.public.windowsxp.setup_deployment,microsoft.public.windows.server.active_directory (More info?)

You will have issues..basically one big security hole..

Here is Microsofts policy statement..

http://support.microsoft.com/defau [...] -us;314828



"KT" wrote:

> ALL XP Pros...
>
>
> I am working in an environment where all workstations have the same SID
> because SYSPREP was never ran on the workstations...will there be issues to
> this deployment of and the clients?
>
> Please provide Microsoft documents and link if possible thanks...
>
> I know duplicate SIDS should not be used period, but I need documentations -
> also is there a documents that says MS does NOT support duplicate SIDs in an
> evironment - thanks.
>
>
>

Archived from groups: microsoft.public.win2000.active_directory,microsoft.public.windows.server.active_directory,microsoft.public.windowsxp.customize,microsoft.public.windowsxp.setup_deployment (More info?)

In the future if you want to avoid syspred, remove the workstation from
the domain before imaging.

Carey Frisch [MVP] wrote:

> "When you clone a Windows NT/2000/XP installation to many computers,
> the destination computers have the same SID and computer name as the source
> Windows installation. Because Windows NT/2000/XP networks use each computer's
> SID and computer name to uniquely identify the computer on the network, you must
> change the SID and computer name on each destination (client) computer after cloning."
>
> The Microsoft Policy Concerning Disk Duplication of Windows XP Installations
> http://support.microsoft.com/defau [...] duct=winxp
>
> How to change the SID on a Windows XP, Windows 2000, or Windows NT computer
> http://service1.symantec.com/SUPPO [...] 0308324125
>
> How to use the Sysprep tool to automate successful deployment of Windows XP
> http://support.microsoft.com/defau [...] duct=winxp
>
> Description of New Features in Sysprep for Windows XP
> http://support.microsoft.com/defau [...] duct=winxp
>
> How to Use Sysprep with Windows Product Activation or Volume License Media to Deploy Windows XP
> http://support.microsoft.com/defau [...] duct=winxp
>
> How To Add Customized User Settings When You Run Sysprep
> http://support.microsoft.com/defau [...] duct=winxp
>
> Unsupported Sysprep scenarios
> http://support.microsoft.com/defau [...] duct=winxp
>
> Summary of the limitations of the System Preparation tool
> http://support.microsoft.com/defau [...] duct=winxp
>
> Windows XP Service Pack 2 Deployment Tools
> http://www.microsoft.com/downloads [...] laylang=en
>