Jump to content

Not joining domain & regional settings


Recommended Posts

Hello

I've created an unattended Windows 7 RC. I join the machine to the domain in phase 4 and add a local account in phase 7 (I'd prefer not to make a local account, but if I don't then it stopped there). When the machine boots up it is not on the domain, but is a member of a workgroup with the name of the domain. Prior to adding the local account, it was joining the domain without a problem.

I have this in phase 4

<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>***</Domain>

<Password>***</Password>

<Username>***</Username>

</Credentials>

</Identification>

</component>

Also it still stops at the regional settings box despite having this in phase 7

<component name="Microsoft-Windows-International-Core" 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">

<InputLocale>en-US</InputLocale>

<SystemLocale>en-US</SystemLocale>

<UILanguage>en-US</UILanguage>

<UserLocale>en-US</UserLocale>

<UILanguageFallback>en-US</UILanguageFallback>

</component>

Any ideas?

thanks

Edited by anthonyqld
Link to comment
Share on other sites


I've now got the machine to join the domain, but when I login I get "The security database on the server does not have a computer account for this workstation relationship" if I use a new computer name when I get prompted, if I use a name of the machine that was there before I get a trust relaionship error. So it appears that the machine thinks it's on the domain, but it isn't. So I need to remove it from the domain and re-add it to make it work.

I still have no luck with the regional settings.

Edited by anthonyqld
Link to comment
Share on other sites

  • 2 months later...

Anthonygld: I had the same problem, what i did to solve was this:

first know what the problem is: if you install from WDS you computer has allready been giving a name when you start to install. if you specify another name later in the process you will get your error.

solution is to uncheck "do not create account in the domain........" and have this line in your unattended.xml:

<ComputerName>*</ComputerName>

(no name here)

Your installation will accept the name of your computer, provided by WDS, and join this computername to your domain. and you are good to go. :-)

Link to comment
Share on other sites

for regional settings i have this:

<settings pass="oobeSystem">

<component name="Microsoft-Windows-International-Core" 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">

<InputLocale>da-DK</InputLocale>

<SystemLocale>da-DK</SystemLocale>

<UILanguage>en-US</UILanguage>

<UILanguageFallback>en-US</UILanguageFallback>

<UserLocale>da-DK</UserLocale>

</component>

at first I had it under "specialize" and I had the same problem, all was in danish but I had to manually click "next", after moving it to "oobeSystem" it works 100% unattended for me.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...