Creating a Cloned Image of a WinXP Pro System for Installation in a Domain

[Gary]

I am trying to deploy multiple WinXP Pro systems in a domain. Using
Sysprep and PowerQuest's Image Center, I have made several images of
systems but always for a workgroup environment. Now, I'm looking at
doing the same thing for a Domain environment and need to know if the
domain issue changes how the image needs to be created.

My process for workgroups was:

1. Install the operation system (logging on to workgroup).
2. Create a user with admin rights.
3. Log in as that user and install all OS updates, service packs,
user's applications, etc.
4. Configure OS preferences, desktop preferences, toolbars, etc.
5. Clear out any IE cache, history, cookies, etc.
6. Log off and log on as local Administrator.
7. Copy user profile (from step 2) to default user and set "permit to
use" to Everyone.
8. Copy sysprep files to hard drive.
9. Run setup manager and create answer file for sysprep install.
10. Run sysprep choosing the "reseal", "Use mini-setup" options.
11. Use PowerQuest Image Center to image the hard drive to the server.

So, I guess my question is, can I follow this same procedure and then
when running the mini-setup program after applying the image to a new
computer, choose the option to join the computer to the domain? Or,
do I need to join the computer to the domain from the start (in step
one)? Also, for a domain environment, would I need to log in as a
domain user with local admin rights in step 2 or can I still just log
in as a local user with admin rights? End users will not have a local
computer account and their domain accounts will not be a member of the
local computer's administrators group - probably just a member of the
Users or Power Users group.

Thanks!

 

[Jonathan]

Running sysprep essentially removes the machine from the domain. When you
bring up the deployed image it will be in workgroup model regardless of
whether or not it was in a domain model before running sysprep.

You need to add the following to your sysprep.inf answer file in order to
automate joining the domain during mini-setup: (this is from the join
domain section of the deploy.chm file - found in the
support\tools\deploy.cab folder on the product cd.)

The [Identification] section contains entries for specifiying the network
identification of a computer. If these entries are not present, Setup adds
the computer to the default workgroup. If there is not enough information
for this entry, Setup prompts the end user to provide this information.

Entry Description
DomainAdmin Specifies the name of the user
account in the domain that has permission to create a computer account in
that domain
DomainAdmin Password Specifies the password of
the user account as defined by the DomainAdmin entry.
JoinDomain Specifies the name of the
domain in which the computer participates.
JoinWorkgroup Specifies the name of the workgroup
in which the computer participates.
MachineObjectOU Specifies the full Lightweight
Directory Access Protocol (LDAP) path name of the organizational unit (OU)
in which the computer belongs.


Sample
This sample demonstrates one use of the [Identification] section of
Unattend.txt.

[Identification]
DomainAdmin = PatC
DomainAdminPassword = abcdef123
JoinDomain = MYDOMAIN
JoinWorkgroup = MYUSERGROUP
MachineObjectOU = "OU = myou,OU = myparentou,DC = mydom,DC = mycompany,DC =
com"





I hope this helps

 

[Ulrich Wurst]

Gary schrieb:

For the domain your installation process can be change to:

My process for workgroups was:

1. Install the operation system (logging on to workgroup).

Same, only join Domain.

2. Create a user with admin rights.

Not required. The lokal administrator should work fine.

3. Log in as that user and install all OS updates, service packs,
user's applications, etc.

Only install applications. Distribute SP + hotfixes via SUS (Microsoft
Software-Update-Server)

4. Configure OS preferences, desktop preferences, toolbars, etc.

Don't. Use group policies for that whereever possible.

7. Copy user profile (from step 2) to default user and set "permit to
use" to Everyone.

Don't. Copy the Profile to \\%LOGONSERVER%\NETLOGON\DefaultUser.

8. Copy sysprep files to hard drive.
9. Run setup manager and create answer file for sysprep install.
10. Run sysprep choosing the "reseal", "Use mini-setup" options.
11. Use PowerQuest Image Center to image the hard drive to the server.

Same here.

So, I guess my question is, can I follow this same procedure and then
when running the mini-setup program after applying the image to a new
computer, choose the option to join the computer to the domain?

You will have to rejoin the domain since running sysprep will remove you
from the domain.

Uli