Keep domain membership after sysprep /oobe

[MagellanTX]

I am joining a machine to the domain via a script in the auditUser pass and it is working the way it should. The problem is that when I sysprep /oobe to get back into OOBE mode and to process my OOBE.XML I keep losing the domain membership. I am not running a generalize with my sysprep just sysprep /oobe /reboot /unattend:c:\windows\panther\oobe.xml.

Is there some trick I need to know in order to keep the machine in the domain?

Thanks!!

[anyweb]

taken from microsoft's technet

Sysprep runs only if the computer is a member of a workgroup, not a domain. If the computer is joined to a domain, Sysprep removes the computer from the domain.

http://technet.microsoft.com/en-us/library/cc721940.aspx

Limitations of Sysprep

Sysprep has the following limitations:

* You must use only the version of Sysprep that is installed with the Windows image that you intend to configure. Sysprep is installed with every version of Windows and must always be run from the %WINDIR%\system32\sysprep directory.

* Sysprep must not be used on upgrade installation types. Run Sysprep only on clean installations.

* If you plan to use the imagex /apply command to apply a Windows image to a computer, the partition layout on the reference and destination computers must be identical. For example, if you capture a customized Windows image on drive D, you must always deploy that image onto drive D of the destination computer. The following list describes the partition settings that must be identical across the reference and destination computers when you use the imagex /apply command.

o The partition number where Windows Vista is installed must match.

o The partition type (primary, extended, or logical) must match.

o If the partition is set to active on the reference computer, the destination computer must also be set to active.

o If you have another active partition for Bootmgr and BCD stores on the reference system, you must also capture this partition and apply it to the same partition on the destination computer.

This limitation applies only to the imagex /apply command. If you run Setup and reinstall Windows, you can change the drive letters where Windows is installed.

noteNote

In some cases, customized applications that are installed before the Windows image is recaptured might require a consistent drive letter. Some applications store paths that include the drive letter of the system. Uninstallation, servicing, and repair scenarios might not function appropriately if the drive letter of the system does not match the drive letter specified in the application. Deploying customized Windows images to different drive letters is not supported.

The recommended practice is, if you are installing customized applications, to deploy your Windows image to the same drive letter.

* When you copy Windows images between computers, the reference and destination computers do not need to have compatible hardware abstraction layers (HALs). The /detecthal option in the Boot Configuration Data (BCD) will enable a system that has already run Sysprep to install the correct HAL.

* The Plug and Play devices on the reference and destination computers, such as modems, sound cards, network adapters, and video cards, do not have to be from the same manufacturer. However, the drivers for these devices must be included in the installation.

* You cannot automate the running of Sysprep by using a RunSynchronous command in auditUser configuration pass. You can automate the running of Sysprep only by using a FirstLogonCommand in the oobeSystem pass.

* The clock for activation begins its countdown the first time Windows starts. You can use Sysprep for a maximum of three times to reset the clock for Windows Product Activation. After the third time you run Sysprep, the clock can no longer be reset.

* ImageX, third-party disk-imaging software, or disk-duplicating hardware devices are required for image-based Setup. These products create binary images of a computer's hard disk and either duplicates the image to another hard disk or stores the image in a file on a separate disk.

* Sysprep runs only if the computer is a member of a workgroup, not a domain. If the computer is joined to a domain, Sysprep removes the computer from the domain.

* If you run Sysprep on an NTFS file system partition that contains encrypted files or folders, the data in those folders becomes completely unreadable and unrecoverable.

* Sysprep converts the %COMPUTERNAME% environment variable to uppercase characters. However, the actual name of the computer does not change.

* Running Sysprep will cause Windows Welcome to prompt you for a product key. You can use an answer file with Sysprep to prevent Windows Welcome from prompting you for a product key. If you specify a valid product key in the ProductKey setting of the Microsoft-Windows-Shell-Setup component during the specialize pass, then Windows Welcome will not prompt you for a product key.

[MagellanTX]

Thanks for the reply, that definitly answers that question. I guess I'll have to take another approach.

[cluberti]

You could use a command like netdom to rejoin, but you can't keep it through sysprep.

[gotenks98]

You are not going to want to keep the domain membership after a sysprep. As it would totally screw up your active directory setup. All the pcs would have different SID all pointing to the same hostname.

[Minus30]

You can add an unattend.xml to your sysprep, where you can add the PC to the domain again. I actually work with 3 xml files for my unattended vista installs...

[ipodtrip]

Hello Minus 30 can I see how you did your unattend.xml file that allows you to join the domain.

Thanks