[i3igi3yrd]

I know there is an issue with joining a machine to the domain with the unattended xml, but I can't quite get a grasp on it.

I am using Ghost to capture the sysprepped image and deploying via PXE with winPE, so I'm not using any of the .wim images or MS deployment methods.

I'm trying to emulate the same steps that we go through with our existing answer file for XP (seen below).
No prompts during setup except for naming the computer, the admin account enabled, and the machine being joined to the domain.

Any assistance is needed since I'm not familiar with the new System Image Manager.

;SetupMgrTag
[Unattended]
    OemSkipEula=Yes
    InstallFilesPath=C:\sysprep\i386

[SysprepMassStorage]


[GuiUnattended]
    AdminPassword=XXXXX
    OEMSkipRegional=1
    TimeZone=20
    OemSkipWelcome=1

[UserData]
    ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
    FullName="Corporate User"
    OrgName="XXXXX Corporation"
    
[Display]
    BitsPerPel=32
    Xresolution=1024
    YResolution=768
    Vrefresh=75

[TapiLocation]
    CountryCode=1
    Dialing=Tone
    AreaCode=205
    LongDistanceAccess="9"

[SetupMgr]
    DistFolder=C:\sysprep\i386
    DistShare=windist

[Identification]
    JoinDomain=Corporate
    DomainAdmin=XXXXX
    DomainAdminPassword=XXXXXX

[Networking]
    InstallDefaultComponents=Yes

This post has been edited by i3igi3yrd: 01 February 2012 - 01:51 PM

[IcemanND]

Use the system image manager, manually creating the Win7 unattend.xml answer file is near impossible. Just use the install.wim from your install media as the reference image when asked.

There is a good blog here with most of the info you would be looking for.

For the domain join you either need to pre-create the computer account in AD and the provided account has rights to join, or supply the OU the machine will be created in and the provided account has rights to create the object and join to it.

[i3igi3yrd]

When we are doing deployments of 200+ machines at a time, creating the objects in AD is not the preferable option. Is there not a scripting option out there?

[IcemanND]

If all of the machines are going into the same OU you won't have a problem, or if you have a staging OU and then move them from there to their permanent OU. Otherwise if you change the <machineobjectOU> value before the machine attempts to do the join you'll be fine. I do this right after applying the image to the machine before rebooting. If you are using Ghost version 11.x you should be able to do the same thing.

        <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <Identification>
                <Credentials>
                    <Domain>contoso.com</Domain>
                    <Password>joinpassword</Password>
                    <Username>joinaccount</Username>
                </Credentials>
                <JoinDomain>contoso.com</JoinDomain>
                <MachineObjectOU>OU=Computers,OU=finance,DC=contoso,DC=com</MachineObjectOU>
            </Identification>        </component>

[i3igi3yrd]

What pass is that in? I'm about to try that now.

[IcemanND]

Specialize

[lil754boy]

Where is this located. i do not see the string anywhere.

[IcemanND]

In the Windows Image System Manager, load the Install.wim:

Components\
	x86_Microsoft-Windows-UnattendedJoin_6.1.7601.17514_neutral\
		Identification\
			Credentials

Add to pass Specialize