Sysprep XP images- A must?

  • Thread starter Thread starter BingoMan
  • Start date Start date
B

BingoMan

Does XP pro HAVE to be sysprep'ed (or have the sid regenerated in some way)
on ghosted (ver8) images that will be rolled out into a win2003 domain.

I would say yes however I can not PROVE it. Is there an authoritive link in
regard to XP and cloning as a must. I found a KB in regard to this however
it did not list XP as an effected system.

I have read , maybe on this board, that MS will not support XP image
deployments that do not use some sort of sid regeneration. Is this true and
is it published some place on the MS web sites?

One final question, if anybody could suggest the type of issue this could
cause in general terms. Things to be on guard for if you will. The
environment is only few thousand client ( :-() ) ... at best. The deployment
is an un sysprep'ed XP pro image installed onto a pc. Then the host name is
manually reset and finally the box is joined to the domain. The pc is then
tailored to the user.

Thx
 
BingoMan interrumpeerde het poetertje met volgende input:
Does XP pro HAVE to be sysprep'ed (or have the sid regenerated in some way)
on ghosted (ver8) images that will be rolled out into a win2003 domain.

I would say yes however I can not PROVE it. Is there an authoritive link in
regard to XP and cloning as a must. I found a KB in regard to this however it
did not list XP as an effected system.

I have read , maybe on this board, that MS will not support XP image
deployments that do not use some sort of sid regeneration. Is this true and
is it published some place on the MS web sites?

One final question, if anybody could suggest the type of issue this could
cause in general terms. Things to be on guard for if you will. The
environment is only few thousand client ( :-() ) ... at best. The deployment
is an un sysprep'ed XP pro image installed onto a pc. Then the host name is
manually reset and finally the box is joined to the domain. The pc is then
tailored to the user.

Thx
Click to expand...

<http://www.sysinternals.com/ntw2k/source/newsid.shtml>

<http://service1.symantec.com/SUPPOR...sf&view=docid&dtype=&prod=&ver=&osv=&osv_lvl=>

<http://techrepublic.com.com/5208-6239-0.html?forumID=49&threadID=138547>

found all of these links using:

<http://www.google.be/search?q=winxp+clone+sid&hl=nl&lr=&start=10&sa=N>

grtz
 
Thanks for the links ... they have helped. KB314828 quoted XP and was
rather absolute in regard to support for non sysprep'ed images.

It seems that there is not an absolute answer, however when MS refuses to
support a certain type of XP deployment that should be a warning. As far as
I can tell there is no change in practice between win2000 Pro and XP Pro
deployments from MS in regard sysprep ... does anybody disagree ?
 
Back
Top