Problem Setting the hostname

[carles]

Dear friends,

I'm experiencing a problem with opsi setting the hostnames, in the past when I created the client or defined the hostname inside the ncurses menu on the pxe boot, the windows installation had this hostname when it boot up, being this a really nice behaviour, but now, I don't know why but probably related with the unattend.xml file, when I do a windows7 x64 installation the hostname is NAMEORG-2V0ACTF . Somebody knows why this is happening?

Here an extract of my unattend.xml file :

</UserAccounts>
<ComputerName>#@pcname*#</ComputerName>
<ProductKey>####-####-####-####-####</ProductKey>
<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
<DoNotCleanTaskBar>false</DoNotCleanTaskBar>
<ShowWindowsLive>false</ShowWindowsLive>
<StartPanelOff>false</StartPanelOff>

Thank you very much in advance

[ueluekmen]

Hi,

first you should check, if this is a problem from your unattend.xml-file. To test these, you can safe your unattend.xml from custom-Directory and copy the unattend.xml.template from opsi directory to your custom directory, you must rename the file by copy to unattend.xml. When that works, you should make diff with your own file to find the difference.

[carles]

Thanks for your answer ueluekmen,

I did as you suggested, and the problem is in the unattend.xml, and it's related with the fact that i'm trying to join the domain using the unattended file, I think that is a better method than using the localboot script, anyway I have both working, do you have any idea why this is happening? IT's opsi not dessigned to join the domain using the unattended file?

What I have configured now looks like this:

<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>
<Credentials>
<Domain>MIDOTI.NET</Domain>
<Password>**********</Password>
<Username>************</Username>
</Credentials>
<!-- <DebugJoin>true</DebugJoin> -->
<JoinDomain>MIDOTI.NET</JoinDomain>
<!-- <JoinWorkgroup>joinworkgroup</JoinWorkgroup> -->
<MachineObjectOU>ou=Computers,ou=Base,dc=midoti,dc=net</MachineObjectOU>
<!-- <MachinePassword>machinepassword</MachinePassword>
<UnsecureJoin>true</UnsecureJoin> -->
</Identification>
</component>

Thank you very much, we don't want to have any computer out of the domain so doing this we save some time, the localboot joindomain script is a little bit slow, requires a few reboots with the local admin.

Carles Cortes

[wolfbardo]

T's opsi not dessigned to join the domain using the unattended file?

opsi uses a normal unattended Windows 7 Installation via the unattended.xml but you have to edit !!!carefully!!! the unattended.xml

Thank you very much, we don't want to have any computer out of the domain so doing this we save some time, the localboot joindomain script is a little bit slow, requires a few reboots with the local admin.

Give http://download.uib.de/opsi4.0/products ... 1.0-2.opsi a try

regards,

Bardo Wolf

[carles]

Thank you Wolfbardo, problem solved editing the unattended file more carefully