[SOLVED] Domain join working but after setup finished position of trust bad

[x23piracy]

Hi,

 

i got it all time working but today i realised that something must been broken with my setup.

After Windows is installed i can see that the computer joined the domain but if i try to login

at the domain windows tells me that the position of trust to the domain is broken.

 

So i have to temporary leave the domain, rejoin it and the all is fine.

 

But what may happended here?

 

Before first logon i've been asked for the computername, then afaik it joins the domain,

then lauching wtk installer, when this is finished first login is proceeded.

 

What can break the position of trust to the domain this was working for days and days.

Iam not sure what now causes that in my setup.

 

 

Greetz X23

Edited March 11, 2013 by x23piracy

[x23piracy]

Hi,

 

i think i may found my problem.

Is it true that unattend.xml is working like a batch?

 

This is a part of my unattend.xml:

 

        <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" 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>                <JoinWorkgroup>ARBEITSGRUPPE</JoinWorkgroup>                <Credentials>                    <Domain>blub.local</Domain>                    <Password>password</Password>                    <Username>Administrator</Username>                </Credentials>                <JoinDomain>haan.local</JoinDomain>            </Identification>        </component>        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">            <TimeZone>W. Europe Standard Time</TimeZone>        </component>

 

Should i sort Microsoft-Windows-Shell-Setup before Microsoft-Windows-UnattendedJoin?

 

If my theory is true setup join domain with a temporary name and after that asks me for hostname without

doing that with domain credentials. Then it's no wondern that the position of trust is broken.

 

 

Greetz X23

Edited March 10, 2013 by x23piracy

[x23piracy]

Hi,

 

strange i'Ve tested this since i removed computername * computername from unattend.xml

computer joins as retsch-xxxxxxxx (8 variable signs) to the domain and then it asks me for

computername... hmm i thougth it uses the supplied computername then to join domain. argh.

 

I've checked the computername at our domain controller its not what i input it's still the name

it generates automatically.

 

 

Any ideas?

 

 

Greetz X23

Edited March 10, 2013 by x23piracy

[x23piracy]

Hi,

 

it seems that this is a normal cautious of windows 7 setup:

http://www.msfn.org/board/topic/144257-unattend-will-not-join-domain/

 

So it seems if i want to change the name when unattend.xml is joining domain,

i need to create a unique.xml that is triggered with the setup. bahh

 

Else i need to change the computername after the first logon with credentials.

 

I hope someone has better news.

 

 

Greetz X23

Edited March 10, 2013 by x23piracy

[x23piracy]

Hi,

 

i can confirm that this is normal so its needed to change the hostname after firstlogon with valid credentials.

Only way is to use an unattend.xml with wanted hostname.

 

 

Greetz X23

[bphlpt]

Yes it does appear to be "normal", that is if you agree that something that MS has apparently admitted is a Sysprep bug that has existed since at least 2007 can be considered "normal".  Following your links, I thought this one, this one, and this one to be the most enlightening.

 

Cheers and Regards