Not sure if I'm doing something wrong or it's AD/Unattend.

During the specialize process is the only point were you can input your computer name and also do an UnattendedJoin to a Domain, but just before the Vista PC allows you to enter the computer name, the computer account is created in AD.

The computer name is alway sometime like this, LH-XXXXXXXXXXXX. That's a "LH-" then a random mix of 12 characters. Its not the MAC address, or any other type that i'm use to seeing.

Anyway, once i've inputted the computer name, the computer account in AD doesn't change it to the name i've specified, but keeps the one it originally inputted, so when i try and log on to the domain, i can't because the computer is untrusted as it does not have a valid computer account in AD.

How can I get it to accept the name i have entered, or can i stop it from adding the computer account to AD until i have entered the preferred computer name?

The account doing the UnattendedJoin is a Domain Admin, (code below).

<component name="Microsoft-Windows-Shell-Setup" 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">
			<Display>
				<ColorDepth>32</ColorDepth>
				<DPI>96</DPI>
				<HorizontalResolution>1024</HorizontalResolution>
				<RefreshRate>75</RefreshRate>
				<VerticalResolution>768</VerticalResolution>
			</Display>
			<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
			<CopyProfile>false</CopyProfile>
			<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
			<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
			<ProductKey>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</ProductKey>
			<RegisteredOrganization>Org</RegisteredOrganization>
			<RegisteredOwner>Own</RegisteredOwner>
			<ShowWindowsLive>false</ShowWindowsLive>
			<StartPanelOff>false</StartPanelOff>
			<TimeZone>GMT Standard Time</TimeZone>
		</component>
		<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>bw-wan</Domain>
					<Password>password</Password>
					<Username>vista</Username>
				</Credentials>
				<JoinDomain>bw-wan</JoinDomain>
			</Identification>
		</component>

Come on guys, anyone?

Hi!

I can only encourage you to let Vista randomly build your name when joining the computer to the domain using the name property of (*). Once you have reached full blown Windows, let a script that always will be run set the name for you given the naming standard of your corp. That way, the computers will always be unique when joining the domain, and then complying with ur comp naming convention provided from the script. There is loads of examples with vbscript, and others have done the same thing....

Try pre populating the domain with the computer name you specifiy in your unattend.xml file.

Matt

I use this xml created by the wsim and it works fine.

-<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

-<Identification>

-<Credentials>

<Domain>DOMAINNAME</Domain>

<Password>Userpassword</Password>

<Username>Username</Username>

</Credentials>

<JoinDomain>DOMAINNAME</JoinDomain>

<MachineObjectOU>OU=OUNAME,DC=DCNAME,DC=org </MachineObjectOU>

</Identification>

</component>

I'm inclined to agree with Br4tt3, the way I've worked it is to let the unattendxml file do its thing with the LH-Random computer name and then let a script tidy things up.

Since I'm hopeless with VBS I use a program called WSName which does all the renaming for me, including deleting any existing duplicate computer name

Can anyone share the vb rename script they are using for thier corp? How does your script fetch names, and how does it not duplicate names?

Thanks!

what I do is:

boot to PE

run a script that

1) prompts for the machine name

2) merges the entered machine name into the autounattend.xml via a vbscript

3) kicks off setup using the modified autounattend.xml

so far this is working well for me.

what I do is:

boot to PE

run a script that

1) prompts for the machine name

2) merges the entered machine name into the autounattend.xml via a vbscript

3) kicks off setup using the modified autounattend.xml

so far this is working well for me.

Where are you putting the machine name in the autounattend.xml??

I am assuming you are just editing the xml from within WinPE and placing it on a share somewhere and having the build reference it there?? Can you be a little more detailed on how you are getting setup to use the modified autounattend.xml??

Edited February 3, 200719 yr by joshiieeii

Does anyone have any leads on how eschloss is able to "merges the entered machine name into the autounattend.xml via a vbscript"??