SYSPREP initial setup...

[Guest]

I have a question on the initial setup of creating sysprep image as I'm
getting ready for my first run at it.

In MS KB302577 it says to setup a workstation with OS and all applications
etc. that you want on it. In doing so, can my source computer already be
joined to the domain or does it make a difference?
Also, can I specify the wallpaper and desktop icons as well on the sysprep
image?
Lastly, I've read thru the sysprep parameters, but which one do I use to NOT
duplicate the SID? Since these will be workstations joined to a domain, they
will need to have different names and SIDS. I'm kinda confused with the
"Microsoftese" wording on the parameters.
Thanks in advance and please excuse my ignorance on this.

 

[Rafael]

Ken,

Sysprep requires that the source machine NOT be part of a domain as the
sysprep.inf [Identification] section will (if the correct info is provided)
join the target machine to whatever domain specified. Part of what sysprep
does is remove the SID from the target computer and generate a new one as
the OS gets installed on the target computer.

To specify a default wallpaper for the desktop, you can use a registry hack
as described on this page:

http://www.winguides.com/registry/display.php/103/.

It's also easy to create desktop icons by adding them to the all users or
default users Desktop so every user can get the same icons.

Hope this helps.

Rafael

 

[Hunter1]

I have a question on the initial setup of creating sysprep image as I'm
getting ready for my first run at it.

In MS KB302577 it says to setup a workstation with OS and all applications
etc. that you want on it. In doing so, can my source computer already be
joined to the domain or does it make a difference?

Remove it from the domain before running Sysprep, you can set it to
automatically join the domain in sysprep.inf.

Also, can I specify the wallpaper and desktop icons as well on the sysprep
image?

Yep, just create your default user profile from the profile with the
look and feel you want prior to launching sysprep.

Lastly, I've read thru the sysprep parameters, but which one do I use to NOT
duplicate the SID? Since these will be workstations joined to a domain, they
will need to have different names and SIDS. I'm kinda confused with the
"Microsoftese" wording on the parameters.

setupcl.exe which should be living in your sysprep directory will redo
the SID's for you, and it will do this automatically unless you use
/nosidgen.

 

[Daniel Sinclair]

Sysprep requires that the source machine NOT be part of a domain as the

sysprep.inf [Identification] section will (if the correct info is
provided)

Actually, it doesn't matter either way. When the machine is sysprepped it
will happily downgrade to a workgroup OR rejoin the domain if you wish.
However, when you sysprep a machine that is a domain member it does not
remove the machine account from the domain, you need to do that separately.
This also means, that if you sysprep a machine that was previously in the
domain, and you want to rejoin the domain, the account you use for this must
have enough permissions to OVERWRITE the existing machine account, not just
create a new one.

 

[Guest]

Thanks everyone for your responses. Today I'll be setting up the source
workstation and walking thru a sysprep trial.
I gotta tell ya that I still feel kinda dumb not knowing exactly what I'm
suppose too, even though I've had the classes and the certs as well. Kinda
puts a whole new meaning to being "paper certified" if you've never actually
had to perform a setup this way but have passed a test that had this info. on
it.
Thanks again I'll keep posted as to how it went.