Re: sysprep and nosidgen


"barrymdonahue" <barrymdonahue.3j53c1@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:barrymdonahue.3j53c1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Zaphod Beeblebrox;1078089 Wrote:
"barrymdonahue" <barrymdonahue.3j4tkb@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote
in message news:barrymdonahue.3j4tkb@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I have been using sysprep to prepare Windows 2000, XP and Windows
2003
images for Virtual Machine testing. When I prep the images I always
select nosidgen. I am trying to get Vista and Windows 2008 images
ready
for test but there seems to be no equivalent to nosidgen. The
images
are
only used for testing and only live for the lenth of the test. It's
important for the SID not to be changed or some of the software
I've
installed will not work. Anybody know if there is a way to prevent
SID
generation in Vista sysprep?


The only thing that looks promising to me is /audit, which is the
same
as -factory in XP's sysprep. Might be worth a try. Another
possibility
would be to wait until after un-sealing before installing your
software,
then capture the image for use in your testing. Finally, there are
utilities that are supposed to let you change the SID, perhaps using
one
to force the desired SID might work.

In my case I can't change the image after first boot. These images
are used to test Virtual Machines on top of our system. The test
harness
needs them to be ready to go as is.
Thanks anyway,


What about /audit mode? Will that do it for you? If not, then I don't
know what else to suggest.

--
Zaphod

No matter where you go, there you are!


.

Relevant Pages