Deploing with or without sysprep?

[Bulakov Alexy]

Do I really need to use SYSPREP to deploy many WinXPs with all needed
applications and SMS installed on it? Or it is enough to remove one from
domain, delete specific drivers and clone it to all another?

 

[Mike Brannigan [MSFT]]

Do I really need to use SYSPREP to deploy many WinXPs with all needed
applications and SMS installed on it? Or it is enough to remove one from
domain, delete specific drivers and clone it to all another?

You should use SYSPREP. You need to have the machine generate the
appropriate unique security identifiers etc.

--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions, please use these
newsgroups

 

[Bulakov Alexy]

One of the system administrators in company I work for insists that I
shouldn't use it because unique SID is generated when machite is added to
domain. No arguments I told him could convinece him of using SYSPREP. But I
think we must use SYSPREP. Can you give me some heavy arguments why should
we use it and what will happen if we don't?

 

[Mike Brannigan [MSFT]]

Bulakov,

The machine does generate a unique SID for its Domain Membership BUT it's
local SID will still be duplicated, you also may have problems with support
from Microsoft and third parties for any security related issues until in
each case you prove that the problem can also occur on a properly built
machine.

So heavy arguments
- do you want to be supported easily or go through an extra layer of testing
to prove it is not related to your not using SYSPREP to correctly deploy the
machines.
- you are still a security risk with duplicated machines in the environment,
regardless of Domain Membership.
- we (Microsoft) have always reserved the right to use the internal data
structures (SIDs/GUIDs) of machines for any purpose in the future. Your
duplicate machines may cause problems with future updates or products.
- Do it now, it will save you potential problems in the future and why not?
It is just a simple step in the deployment process. Not doing it does not
really save you anything and will help prevent problems.


--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions, please use these
newsgroups