i install windows 10 enterprise and i get 2 different language packs installed

Antworten
smallengineguy2014
Beiträge: 9
Registriert: 09 Jul 2019, 22:41

i install windows 10 enterprise and i get 2 different language packs installed

Beitrag von smallengineguy2014 »

i install windows 10 enterprise and i get 2 different language packs installed even tho i have a answer file that has only one in it and i don't think it is being read

my question is where is the answer file suppose to be for windows 10 64 in opis and can i tell opsi to read that file to the installer?

it does install with out any errors but it is just a pain install no passwords installed (they are in the answer file) and it still ask question during the install.

thanks i love the software and want to start helping with the english verson and with service install packs to make it more useable for here in the states
smallengineguy2014
Beiträge: 9
Registriert: 09 Jul 2019, 22:41

Re: i install windows 10 enterprise and i get 2 different language packs installed

Beitrag von smallengineguy2014 »

here is the answer file (yes i did remove the password hash for safety)

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<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">
<AutoLogon>
<Enabled>true</Enabled>
<LogonCount>9999999</LogonCount>
<Username>Administrator</Username>
<Password>
<PlainText>false</PlainText>
<Value>NwA1ADQAMwBYADUAcwA3AFAAYQBzAHMAdwBvAHIAZAA=</Value>
</Password>
</AutoLogon>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Home</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>
</OOBE>
<UserAccounts>
<AdministratorPassword>
<PlainText>false</PlainText>
<Value></Value>
</AdministratorPassword>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Description>admin</Description>
<DisplayName>admin</DisplayName>
<Group>Administrators</Group>
<Name>Administrator</Name>
<Password>
<PlainText>false</PlainText>
<Value></Value>
</Password>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" 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">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>net user Administrator /active:Yes</Path>
<WillReboot>Never</WillReboot>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>2</Order>
<Path>net user Administrator /comment:"admin"</Path>
<WillReboot>Never</WillReboot>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>3</Order>
<Path>net user Administrator /fullname:"admin"</Path>
<WillReboot>Never</WillReboot>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-Security-SPP-UX" 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">
<SkipAutoActivation>true</SkipAutoActivation>
</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">
<CopyProfile>true</CopyProfile>
</component>
<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>unsetup</JoinWorkgroup>
</Identification>
</component>
</settings>
<settings pass="windowsPE">
<component name="Microsoft-Windows-International-Core-WinPE" 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>0409:00020409</InputLocale>
<SystemLocale>en</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en</UserLocale>
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
</component>
<component name="Microsoft-Windows-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">
<Diagnostics>
<OptIn>true</OptIn>
</Diagnostics>
<DynamicUpdate>
<Enable>true</Enable>
<WillShowUI>OnError</WillShowUI>
</DynamicUpdate>
<ImageInstall>
<OSImage>
<Compact>true</Compact>
<WillShowUI>OnError</WillShowUI>
<InstallFrom>
<MetaData wcm:action="add">
<Key>/IMAGE/NAME</Key>
<Value>Windows 10 Enterprise</Value>
</MetaData>
</InstallFrom>
</OSImage>
</ImageInstall>
<UserData>
<AcceptEula>true</AcceptEula>
</UserData>
</component>
</settings>
</unattend>
Benutzeravatar
ThomasT
uib-Team
Beiträge: 529
Registriert: 26 Jun 2013, 12:26

Re: i install windows 10 enterprise and i get 2 different language packs installed

Beitrag von ThomasT »

It is described in the Documentation.
Kein Support per DM!
_________________________
opsi support - https://www.uib.de/
For productive opsi installations we recommend support contracts.
smallengineguy2014
Beiträge: 9
Registriert: 09 Jul 2019, 22:41

Re: i install windows 10 enterprise and i get 2 different language packs installed

Beitrag von smallengineguy2014 »

thanks for the reply and yes i have read that but i have yet to find out why when i install windows it get 2 different languages installed when i have the setting set to US on the control panel and the server setting.

here is what you are referring to in the response

<?xml version="1.0" encoding="UTF-8"?>

-<unattend xmlns="urn:schemas-microsoft-com:unattend">

<!--====================WINDOWSPE SETTINGS====================The windowsPE configuration pass is used to configure settings specific to Windows PE as well as settings that apply to installation.For example, you can specify the display resolution of Windows PE, where to save a log file, and other Windows PE-related settings. -->



-<settings pass="windowsPE">

<!--<component name="Microsoft-Windows-PnPCustomizationsWinPE" 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-instan ... redentials wcm:keyValue="1" wcm:action="add"><Path>C:\drvpe</Path></PathAndCredentials></DriverPaths></component> -->



-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-Setup">


-<DiskConfiguration>

<WillShowUI>OnError</WillShowUI>


-<Disk wcm:action="add">

<DiskID>#@diskindex*#</DiskID>

<WillWipeDisk>false</WillWipeDisk>

<!--<CreatePartitions><CreatePartition wcm:action="add"><Order>1</Order><Type>Primary</Type><Size>20000</Size></CreatePartition></CreatePartitions> -->


<ModifyPartitions>#@modify_partitions*# </ModifyPartitions>

</Disk>

</DiskConfiguration>

<!--<component name="Microsoft-Windows-Deployment" 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-instan ... ousCommand wcm:action="add"><Description>Do something</Description><Order>1</Order><Path>cmd.exe</Path></RunSynchronousCommand></RunSynchronous></component> -->



-<UserData>


-<ProductKey>

<WillShowUI>OnError</WillShowUI>

<Key>#@productkey*#</Key>

</ProductKey>

<AcceptEula>true</AcceptEula>

<FullName>#@fullname*#</FullName>

<Organization>#@orgname*#</Organization>

</UserData>


-<ImageInstall>


-<OSImage>


-<InstallFrom>


-<MetaData wcm:action="add">

<Key>/IMAGE/NAME</Key>

<Value>#@imagename*#</Value>

</MetaData>

</InstallFrom>


-<InstallTo>

<DiskID>#@diskindex*#</DiskID>

<PartitionID>#@windows_partition_number*#</PartitionID>

</InstallTo>

<WillShowUI>OnError</WillShowUI>

</OSImage>

</ImageInstall>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-International-Core-WinPE">


-<SetupUILanguage>

<UILanguage>#@winpe_uilanguage*#</UILanguage>

<WillShowUI>OnError</WillShowUI>

</SetupUILanguage>

<InputLocale>#@winpe_inputlocale*#</InputLocale>

<SystemLocale>#@system_language*#</SystemLocale>

<UILanguage>#@winpe_uilanguage*#</UILanguage>

<UILanguageFallback>#@winpe_uilanguage_fallback*#</UILanguageFallback>

<UserLocale>#@winpe_uilanguage*#</UserLocale>

<LayeredDriver>1</LayeredDriver>

</component>

</settings>

<!--=====================GENERALIZE SETTINGS=====================The generalize pass of Windows Setup is used to create a Windows reference image that can be used throughout an organization.A setting in the generalize pass enables you to automate the behavior for all deployments of this reference image.In comparison, a setting associated with the specialize configuration pass enables you to override behavior for a single, specific deployment.When a system is generalized, specific configuration data for a given installation of Windows is removed.For example, during the generalize pass, the unique security ID (SID) and other hardware-specific settings are removed from the image.The generalize configuration pass runs only when you use the sysprep /generalize command.Answer file settings in generalize are applied to the system before sysprep generalization occurs. The system then shuts down. -->


<!--<settings pass="generalize"></settings> -->


<!--=====================SPECIALIZE SETTINGS=====================During the specialize pass of Windows Setup, machine-specific information for the image is applied.For example, you can configure network settings, international settings, and domain information.The specialize pass is used in conjunction with the generalize pass.The generalize pass is used to create a Windows reference image that can be used throughout an organization.From this basic Windows reference image, you can add further customizations that apply to different divisionswithin an organization or apply to different installations of Windows.The specialize pass is used to apply these specific customizations. -->



-<settings pass="specialize">


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-Shell-Setup">

<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>

<ComputerName>#@pcname*#</ComputerName>

<!-- <ProductKey>#@productkey*#</ProductKey> -->


<CopyProfile>false</CopyProfile>

<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>

<DoNotCleanTaskBar>false</DoNotCleanTaskBar>

<ShowWindowsLive>false</ShowWindowsLive>

<StartPanelOff>false</StartPanelOff>

<TimeZone>#@system_timezone*#</TimeZone>


-<WindowsFeatures>

<ShowWindowsMail>false</ShowWindowsMail>

</WindowsFeatures>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-Security-Licensing-SLC-UX">

<SkipAutoActivation>true</SkipAutoActivation>

</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-instan ... /component> -->



-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-RemoteAssistance-Exe">

<CreateEncryptedOnlyTickets>true</CreateEncryptedOnlyTickets>

<fAllowToGetHelp>true</fAllowToGetHelp>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-International-Core">

<InputLocale>#@system_keyboard_layout*#</InputLocale>

<SystemLocale>#@system_language*#</SystemLocale>

<UILanguage>#@system_language*#</UILanguage>

<UILanguageFallback>#@system_language*#</UILanguageFallback>

<UserLocale>#@system_language*#</UserLocale>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-Deployment">


-<RunSynchronous>


-<RunSynchronousCommand wcm:action="add">

<Description>Enable Admin Account</Description>

<Order>1</Order>

<Path>cmd.exe /c net user #@adminName*# /active:yes</Path>

</RunSynchronousCommand>

<!--<RunSynchronousCommand wcm:action="add"><Description>Opsi tasks</Description><Order>2</Order><Path>cmd.exe /c #@winpe_partition_letter*#:\opsi\postinst.cmd</Path></RunSynchronousCommand> -->


<!--<RunSynchronousCommand wcm:action="add"><Description>EnableAdmin_ploc</Description><Order>3</Order><Path>cmd.exe /c net user Administrator_ploc /active:yes</Path></RunSynchronousCommand> -->


</RunSynchronous>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Networking-MPSSVC-Svc">

<DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>

<PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>

<PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Security-Malware-Windows-Defender">

<DisableAntiSpyware>true</DisableAntiSpyware>

</component>

</settings>

<!--=========================OFFLINESERVICING SETTINGS=========================Use the offlineServicing pass to apply unattended Setup settings to an offline Windows image.During this configuration pass, you can add language packs, updates, or other packages to the offline image.The offlineServicing pass runs during Windows Setup. Setup extracts and installs the Windows image, and then executes Package Manager (Pkgmgr.exe).Packages listed in the servicing section of the answer file are applied to the offline Windows image.The Unattend.xml settings in the offlineServicing pass are applied to the offline Windows image.Additionally, you can use Package Manager with an answer file to install packages. -->



-<settings pass="offlineServicing">


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-PnPCustomizationsWinPE">


-<DriverPaths>


-<PathAndCredentials wcm:action="add" wcm:keyValue="1">

<Path>c:\drvpe</Path>

</PathAndCredentials>

</DriverPaths>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-PnpCustomizationsNonWinPE">


-<DriverPaths>


-<PathAndCredentials wcm:action="add" wcm:keyValue="1">

<Path>c:\drv</Path>

</PathAndCredentials>

</DriverPaths>

</component>

</settings>

<!--=====================AUDITSYSTEM SETTINGS=====================The auditSystem pass is an optional pass that enables you to add additional device drivers and applications to the image.This results in fewer required images because a reference image can be created with a minimal set of drivers.The image can be updated with additional drivers during the audit process.You can then test and resolve any operating system issues related to malfunctioning or incorrectly installed devices on the image.For example, you can install additional language packs, updates, or other applications, such as Microsoft Office.See Reseal mode in oobeSystem. -->


<!--<settings pass="auditSystem"></settings> -->


<!--=====================AUDITUSER SETTINGS=====================The auditUser pass is similar to the auditSystem pass.However, the auditUser pass processes these settings after users have logged on, not before they have logged on.Like the auditSystem pass, the auditUser pass is used to test the functionality of the Windows Vista image.See Reseal mode in oobeSystem. -->


<!--<settings pass="auditUser"></settings> -->


<!--=====================OOBESYSTEM SETTINGS=====================The oobeSystem pass configures settings that are applied during the first-boot experience for end users, also called Windows Welcome.oobeSystem settings are processed before a user first logs into Windows.Out-of-Box-Experience (OOBE) runs the first time the user starts a new computer.OOBE runs before the Windows shell or any additional software runs, and performs a small set of tasks necessary to configure and run Windows. -->



-<settings pass="oobeSystem">

<!--<component name="Microsoft-Windows-Deployment" 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-instan ... /component> -->



-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-Shell-Setup">


-<UserAccounts>


-<AdministratorPassword>

<PlainText>true</PlainText>

<Value>#@administratorPassword*#</Value>

</AdministratorPassword>


-<LocalAccounts>

<!--<LocalAccount wcm:action="add"><Password><PlainText>true</PlainText><Value>uib</Value></Password><Description>UIB</Description><Group>Administratoren</Group><Name>UIB</Name><DisplayName>UIB</DisplayName></LocalAccount> -->


</LocalAccounts>

</UserAccounts>

<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>

<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>

<DoNotCleanTaskBar>false</DoNotCleanTaskBar>

<ShowWindowsLive>false</ShowWindowsLive>

<StartPanelOff>false</StartPanelOff>

<TimeZone>#@system_timezone*#</TimeZone>


-<AutoLogon>

<Enabled>true</Enabled>

<LogonCount>1</LogonCount>

<Username>#@adminName*#</Username>


-<Password>

<PlainText>true</PlainText>

<Value>#@administratorPassword*#</Value>

</Password>

</AutoLogon>


-<FirstLogonCommands>


-<SynchronousCommand wcm:action="add">

<Description>Opsi tasks</Description>

<Order>1</Order>

<CommandLine>cmd.exe /c #@winpe_partition_letter*#:\opsi\postinst.cmd</CommandLine>

</SynchronousCommand>

</FirstLogonCommands>

<!--<Display><ColorDepth>32</ColorDepth><DPI>96</DPI><HorizontalResolution>1024</HorizontalResolution><RefreshRate>75</RefreshRate><VerticalResolution>768</VerticalResolution></Display> -->



-<OOBE>

<HideEULAPage>true</HideEULAPage>

<NetworkLocation>Work</NetworkLocation>

<SkipUserOOBE>true</SkipUserOOBE>

<ProtectYourPC>3</ProtectYourPC>

<SkipMachineOOBE>true</SkipMachineOOBE>

</OOBE>


-<OEMInformation>

<Logo>c:\Program Files\opsi.org\opsi-client-agent\opsi-winst\opsi.bmp</Logo>

<Manufacturer>opsi</Manufacturer>

<Model/>

<SupportURL>http://www.opsi.org</SupportURL>

</OEMInformation>

</component>

<!--<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-instan ... /component> -->


</settings>

<cpi:offlineImage xmlns:cpi="urn:schemas-microsoft-com:cpi" cpi:source="wim:y:/install.wim#Windows Vista ULTIMATE"/>

</unattend>
Benutzeravatar
ThomasT
uib-Team
Beiträge: 529
Registriert: 26 Jun 2013, 12:26

Re: i install windows 10 enterprise and i get 2 different language packs installed

Beitrag von ThomasT »

Could you paste your xml within a code block?
At first glance there is something peculiar with some of your xml tags. They seem to start with -<
Kein Support per DM!
_________________________
opsi support - https://www.uib.de/
For productive opsi installations we recommend support contracts.
smallengineguy2014
Beiträge: 9
Registriert: 09 Jul 2019, 22:41

Re: i install windows 10 enterprise and i get 2 different language packs installed

Beitrag von smallengineguy2014 »

Code: Alles auswählen

<?xml version="1.0" encoding="UTF-8"?>

-<unattend xmlns="urn:schemas-microsoft-com:unattend">

<!--====================WINDOWSPE SETTINGS====================The windowsPE configuration pass is used to configure settings specific to Windows PE as well as settings that apply to installation.For example, you can specify the display resolution of Windows PE, where to save a log file, and other Windows PE-related settings. -->



-<settings pass="windowsPE">

<!--<component name="Microsoft-Windows-PnPCustomizationsWinPE" 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"><DriverPaths><PathAndCredentials wcm:keyValue="1" wcm:action="add"><Path>C:\drvpe</Path></PathAndCredentials></DriverPaths></component> -->



-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-Setup">


-<DiskConfiguration>

<WillShowUI>OnError</WillShowUI>


-<Disk wcm:action="add">

<DiskID>#@diskindex*#</DiskID>

<WillWipeDisk>false</WillWipeDisk>

<!--<CreatePartitions><CreatePartition wcm:action="add"><Order>1</Order><Type>Primary</Type><Size>20000</Size></CreatePartition></CreatePartitions> -->


<ModifyPartitions>#@modify_partitions*# </ModifyPartitions>

</Disk>

</DiskConfiguration>

<!--<component name="Microsoft-Windows-Deployment" 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"><RunSynchronous><RunSynchronousCommand wcm:action="add"><Description>Do something</Description><Order>1</Order><Path>cmd.exe</Path></RunSynchronousCommand></RunSynchronous></component> -->



-<UserData>


-<ProductKey>

<WillShowUI>OnError</WillShowUI>

<Key>#@productkey*#</Key>

</ProductKey>

<AcceptEula>true</AcceptEula>

<FullName>#@fullname*#</FullName>

<Organization>#@orgname*#</Organization>

</UserData>


-<ImageInstall>


-<OSImage>


-<InstallFrom>


-<MetaData wcm:action="add">

<Key>/IMAGE/NAME</Key>

<Value>#@imagename*#</Value>

</MetaData>

</InstallFrom>


-<InstallTo>

<DiskID>#@diskindex*#</DiskID>

<PartitionID>#@windows_partition_number*#</PartitionID>

</InstallTo>

<WillShowUI>OnError</WillShowUI>

</OSImage>

</ImageInstall>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-International-Core-WinPE">


-<SetupUILanguage>

<UILanguage>en-US</UILanguage>

<WillShowUI>OnError</WillShowUI>

</SetupUILanguage>

<InputLocale>0409:00020409</InputLocale>

<SystemLocale>en</SystemLocale>

<UILanguage>en-US</UILanguage>

<UILanguageFallback>en-US</UILanguageFallback>

<UserLocale>en</UserLocale>

<LayeredDriver>1</LayeredDriver>

</component>

</settings>

<!--=====================GENERALIZE SETTINGS=====================The generalize pass of Windows Setup is used to create a Windows reference image that can be used throughout an organization.A setting in the generalize pass enables you to automate the behavior for all deployments of this reference image.In comparison, a setting associated with the specialize configuration pass enables you to override behavior for a single, specific deployment.When a system is generalized, specific configuration data for a given installation of Windows is removed.For example, during the generalize pass, the unique security ID (SID) and other hardware-specific settings are removed from the image.The generalize configuration pass runs only when you use the sysprep /generalize command.Answer file settings in generalize are applied to the system before sysprep generalization occurs. The system then shuts down. -->


<!--<settings pass="generalize"></settings> -->


<!--=====================SPECIALIZE SETTINGS=====================During the specialize pass of Windows Setup, machine-specific information for the image is applied.For example, you can configure network settings, international settings, and domain information.The specialize pass is used in conjunction with the generalize pass.The generalize pass is used to create a Windows reference image that can be used throughout an organization.From this basic Windows reference image, you can add further customizations that apply to different divisionswithin an organization or apply to different installations of Windows.The specialize pass is used to apply these specific customizations. -->



-<settings pass="specialize">


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-Shell-Setup">

<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>

<ComputerName>#@pcname*#</ComputerName>

<!-- <ProductKey>#@productkey*#</ProductKey> -->


<CopyProfile>false</CopyProfile>

<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>

<DoNotCleanTaskBar>false</DoNotCleanTaskBar>

<ShowWindowsLive>false</ShowWindowsLive>

<StartPanelOff>false</StartPanelOff>

<TimeZone>#@system_timezone*#</TimeZone>


-<WindowsFeatures>

<ShowWindowsMail>false</ShowWindowsMail>

</WindowsFeatures>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-Security-Licensing-SLC-UX">

<SkipAutoActivation>true</SkipAutoActivation>

</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>domain</Domain><Password>password</Password><Username>username</Username></Credentials><DebugJoin>true</DebugJoin><JoinDomain>joindomain</JoinDomain><JoinWorkgroup>joinworkgroup</JoinWorkgroup><MachineObjectOU>machineobjectou</MachineObjectOU><MachinePassword>machinepassword</MachinePassword><UnsecureJoin>true</UnsecureJoin></Identification></component> -->



-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-RemoteAssistance-Exe">

<CreateEncryptedOnlyTickets>true</CreateEncryptedOnlyTickets>

<fAllowToGetHelp>true</fAllowToGetHelp>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-International-Core">

<InputLocale>#@system_keyboard_layout*#</InputLocale>

<SystemLocale>#@system_language*#</SystemLocale>

<UILanguage>#@system_language*#</UILanguage>

<UILanguageFallback>#@system_language*#</UILanguageFallback>

<UserLocale>#@system_language*#</UserLocale>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-Deployment">


-<RunSynchronous>


-<RunSynchronousCommand wcm:action="add">

<Description>Enable Admin Account</Description>

<Order>1</Order>

<Path>cmd.exe /c net user #@adminName*# /active:yes</Path>

</RunSynchronousCommand>

<!--<RunSynchronousCommand wcm:action="add"><Description>Opsi tasks</Description><Order>2</Order><Path>cmd.exe /c #@winpe_partition_letter*#:\opsi\postinst.cmd</Path></RunSynchronousCommand> -->


<!--<RunSynchronousCommand wcm:action="add"><Description>EnableAdmin_ploc</Description><Order>3</Order><Path>cmd.exe /c net user Administrator_ploc /active:yes</Path></RunSynchronousCommand> -->


</RunSynchronous>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Networking-MPSSVC-Svc">

<DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>

<PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>

<PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Security-Malware-Windows-Defender">

<DisableAntiSpyware>true</DisableAntiSpyware>

</component>

</settings>

<!--=========================OFFLINESERVICING SETTINGS=========================Use the offlineServicing pass to apply unattended Setup settings to an offline Windows image.During this configuration pass, you can add language packs, updates, or other packages to the offline image.The offlineServicing pass runs during Windows Setup. Setup extracts and installs the Windows image, and then executes Package Manager (Pkgmgr.exe).Packages listed in the servicing section of the answer file are applied to the offline Windows image.The Unattend.xml settings in the offlineServicing pass are applied to the offline Windows image.Additionally, you can use Package Manager with an answer file to install packages. -->



-<settings pass="offlineServicing">


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-PnPCustomizationsWinPE">


-<DriverPaths>


-<PathAndCredentials wcm:action="add" wcm:keyValue="1">

<Path>c:\drvpe</Path>

</PathAndCredentials>

</DriverPaths>

</component>


-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-PnpCustomizationsNonWinPE">


-<DriverPaths>


-<PathAndCredentials wcm:action="add" wcm:keyValue="1">

<Path>c:\drv</Path>

</PathAndCredentials>

</DriverPaths>

</component>

</settings>

<!--=====================AUDITSYSTEM SETTINGS=====================The auditSystem pass is an optional pass that enables you to add additional device drivers and applications to the image.This results in fewer required images because a reference image can be created with a minimal set of drivers.The image can be updated with additional drivers during the audit process.You can then test and resolve any operating system issues related to malfunctioning or incorrectly installed devices on the image.For example, you can install additional language packs, updates, or other applications, such as Microsoft Office.See Reseal mode in oobeSystem. -->


<!--<settings pass="auditSystem"></settings> -->


<!--=====================AUDITUSER SETTINGS=====================The auditUser pass is similar to the auditSystem pass.However, the auditUser pass processes these settings after users have logged on, not before they have logged on.Like the auditSystem pass, the auditUser pass is used to test the functionality of the Windows Vista image.See Reseal mode in oobeSystem. -->


<!--<settings pass="auditUser"></settings> -->


<!--=====================OOBESYSTEM SETTINGS=====================The oobeSystem pass configures settings that are applied during the first-boot experience for end users, also called Windows Welcome.oobeSystem settings are processed before a user first logs into Windows.Out-of-Box-Experience (OOBE) runs the first time the user starts a new computer.OOBE runs before the Windows shell or any additional software runs, and performs a small set of tasks necessary to configure and run Windows. -->



-<settings pass="oobeSystem">

<!--<component name="Microsoft-Windows-Deployment" 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"><Reseal><Mode>Audit</Mode></Reseal></component> -->



-<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-Shell-Setup">


-<UserAccounts>


-<AdministratorPassword>

<PlainText>true</PlainText>

<Value>#@administratorPassword*#</Value>

</AdministratorPassword>


-<LocalAccounts>

<!--<LocalAccount wcm:action="add"><Password><PlainText>true</PlainText><Value>uib</Value></Password><Description>UIB</Description><Group>Administratoren</Group><Name>UIB</Name><DisplayName>UIB</DisplayName></LocalAccount> -->


</LocalAccounts>

</UserAccounts>

<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>

<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>

<DoNotCleanTaskBar>false</DoNotCleanTaskBar>

<ShowWindowsLive>false</ShowWindowsLive>

<StartPanelOff>false</StartPanelOff>

<TimeZone>#@system_timezone*#</TimeZone>


-<AutoLogon>

<Enabled>true</Enabled>

<LogonCount>1</LogonCount>

<Username>#@adminName*#</Username>


-<Password>

<PlainText>true</PlainText>

<Value>#@administratorPassword*#</Value>

</Password>

</AutoLogon>


-<FirstLogonCommands>


-<SynchronousCommand wcm:action="add">

<Description>Opsi tasks</Description>

<Order>1</Order>

<CommandLine>cmd.exe /c #@winpe_partition_letter*#:\opsi\postinst.cmd</CommandLine>

</SynchronousCommand>

</FirstLogonCommands>

<!--<Display><ColorDepth>32</ColorDepth><DPI>96</DPI><HorizontalResolution>1024</HorizontalResolution><RefreshRate>75</RefreshRate><VerticalResolution>768</VerticalResolution></Display> -->



-<OOBE>

<HideEULAPage>true</HideEULAPage>

<NetworkLocation>Work</NetworkLocation>

<SkipUserOOBE>true</SkipUserOOBE>

<ProtectYourPC>3</ProtectYourPC>

<SkipMachineOOBE>true</SkipMachineOOBE>

</OOBE>


-<OEMInformation>

<Logo>c:\Program Files\opsi.org\opsi-client-agent\opsi-winst\opsi.bmp</Logo>

<Manufacturer>opsi</Manufacturer>

<Model/>

<SupportURL>http://www.opsi.org</SupportURL>

</OEMInformation>

</component>

<!--<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>#@system_keyboard_layout*#</InputLocale><SystemLocale>#@system_language*#</SystemLocale><UILanguage>#@system_language*#</UILanguage><UILanguageFallback>#@system_language*#</UILanguageFallback><UserLocale>#@system_language*#</UserLocale></component> -->


</settings>

<cpi:offlineImage xmlns:cpi="urn:schemas-microsoft-com:cpi" cpi:source="wim:y:/install.wim#Windows Vista ULTIMATE"/>

</unattend>
Benutzeravatar
ThomasT
uib-Team
Beiträge: 529
Registriert: 26 Jun 2013, 12:26

Re: i install windows 10 enterprise and i get 2 different language packs installed

Beitrag von ThomasT »

Our default unattend.xml looks like this and the setup.exe is quite peculiar with formatting and syntax errors. So please double Check it.

Code: Alles auswählen

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <!--
	====================
	WINDOWSPE SETTINGS
	====================
	The windowsPE configuration pass is used to configure settings specific to Windows PE as well as settings that apply to installation.
	For example, you can specify the display resolution of Windows PE, where to save a log file, and other Windows PE-related settings.
	-->
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-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">
            <DiskConfiguration>
                <WillShowUI>OnError</WillShowUI>
                <Disk wcm:action="add">
                    <DiskID>#@diskindex*#</DiskID>
                    <WillWipeDisk>false</WillWipeDisk>
                    <ModifyPartitions>
                        #@modify_partitions*#
                    </ModifyPartitions>
                </Disk>
            </DiskConfiguration>
            <UserData>
                <ProductKey>
                    <WillShowUI>OnError</WillShowUI>
                    <Key>#@productkey*#</Key>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
                <FullName>#@fullname*#</FullName>
                <Organization>#@orgname*#</Organization>
            </UserData>
            <ImageInstall>
                <OSImage>
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Key>/IMAGE/NAME</Key>
                            <Value>#@imagename*#</Value>
                        </MetaData>
                    </InstallFrom>
                    <InstallTo>
                        <DiskID>#@installdiskindex*#</DiskID>
                        <PartitionID>#@windows_partition_number*#</PartitionID>
                    </InstallTo>
                    <WillShowUI>OnError</WillShowUI>
                </OSImage>
            </ImageInstall>
        </component>
        <component name="Microsoft-Windows-International-Core-WinPE" 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">
            <SetupUILanguage>
                <UILanguage>#@winpe_uilanguage*#</UILanguage>
                <WillShowUI>OnError</WillShowUI>
            </SetupUILanguage>
            <InputLocale>#@winpe_inputlocale*#</InputLocale>
            <SystemLocale>#@system_language*#</SystemLocale>
            <UILanguage>#@winpe_uilanguage*#</UILanguage>
            <UILanguageFallback>#@winpe_uilanguage_fallback*#</UILanguageFallback>
            <UserLocale>#@winpe_uilanguage*#</UserLocale>
            <LayeredDriver>1</LayeredDriver>
        </component>
        <component name="Microsoft-Windows-PnPCustomizationsWinPE" 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">
            <DriverPaths wcm:keyValue="1">
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path wcm:keyValue="1">c:\drvpe</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <!--
	=====================
	GENERALIZE SETTINGS
	=====================
	The generalize pass of Windows Setup is used to create a Windows reference image that can be used throughout an organization.
	A setting in the generalize pass enables you to automate the behavior for all deployments of this reference image.
	In comparison, a setting associated with the specialize configuration pass enables you to override behavior for a single, specific deployment.
	When a system is generalized, specific configuration data for a given installation of Windows is removed.
	For example, during the generalize pass, the unique security ID (SID) and other hardware-specific settings are removed from the image.
	The generalize configuration pass runs only when you use the sysprep /generalize command.
	Answer file settings in generalize are applied to the system before sysprep generalization occurs. The system then shuts down.
	-->
    <!--
	<settings pass="generalize">
	</settings>
	-->
    <!--
	=====================
	SPECIALIZE SETTINGS
	=====================
	During the specialize pass of Windows Setup, machine-specific information for the image is applied.
	For example, you can configure network settings, international settings, and domain information.
	The specialize pass is used in conjunction with the generalize pass.
	The generalize pass is used to create a Windows reference image that can be used throughout an organization.
	From this basic Windows reference image, you can add further customizations that apply to different divisions
	within an organization or apply to different installations of Windows.
	The specialize pass is used to apply these specific customizations.
	-->
    <settings pass="specialize">
        <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">
            <ComputerName>#@pcname*#</ComputerName>
            <UserAccounts>
                <AdministratorPassword>
                    <PlainText>true</PlainText>
                    <Value>#@administratorPassword*#</Value>
                </AdministratorPassword>
            </UserAccounts>

        </component>

        <component name="Microsoft-Windows-RemoteAssistance-Exe" 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">
            <CreateEncryptedOnlyTickets>true</CreateEncryptedOnlyTickets>
            <fAllowToGetHelp>true</fAllowToGetHelp>
        </component>
        <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>#@system_keyboard_layout*#</InputLocale>
            <SystemLocale>#@system_language*#</SystemLocale>
            <UILanguage>#@system_language*#</UILanguage>
            <UILanguageFallback>#@system_language*#</UILanguageFallback>
            <UserLocale>#@system_language*#</UserLocale>
        </component>
        <component name="Microsoft-Windows-Deployment" 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">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Description>Enable Admin Account</Description>
                    <Order>1</Order>
                    <Path>cmd.exe /c net user #@adminName*# /active:yes</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>Passwd Admin Account</Description>
                    <Order>2</Order>
                    <Path>cmd.exe /c net user #@adminName*# #@administratorPassword*#</Path>
                </RunSynchronousCommand>

            </RunSynchronous>
        </component>
        <component name="Networking-MPSSVC-Svc" 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">
            <DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
            <PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
            <PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
        </component>
    </settings>
    <!--
	=========================
	OFFLINESERVICING SETTINGS
	=========================
	Use the offlineServicing pass to apply unattended Setup settings to an offline Windows image.
	During this configuration pass, you can add language packs, updates, or other packages to the offline image.
	The offlineServicing pass runs during Windows Setup. Setup extracts and installs the Windows image, and then executes Package Manager (Pkgmgr.exe).
	Packages listed in the servicing section of the answer file are applied to the offline Windows image.
	The Unattend.xml settings in the offlineServicing pass are applied to the offline Windows image.
	Additionally, you can use Package Manager with an answer file to install packages.
	-->
    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" 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">
            <DriverPaths>
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path>c:\drv</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <!--
	=====================
	AUDITSYSTEM SETTINGS
	=====================
	The auditSystem pass is an optional pass that enables you to add additional device drivers and applications to the image.
	This results in fewer required images because a reference image can be created with a minimal set of drivers.
	The image can be updated with additional drivers during the audit process.
	You can then test and resolve any operating system issues related to malfunctioning or incorrectly installed devices on the image.
	For example, you can install additional language packs, updates, or other applications, such as Microsoft Office.
	See Reseal mode in oobeSystem.
	-->
    <!--
	<settings pass="auditSystem">
	</settings>
	-->
    <!--
	=====================
	AUDITUSER SETTINGS
	=====================
	The auditUser pass is similar to the auditSystem pass.
	However, the auditUser pass processes these settings after users have logged on, not before they have logged on.
	Like the auditSystem pass, the auditUser pass is used to test the functionality of the Windows Vista image.
	See Reseal mode in oobeSystem.
	-->
    <!--
	<settings pass="auditUser">
	</settings>
	-->
    <!--
	=====================
	OOBESYSTEM SETTINGS
	=====================
	The oobeSystem pass configures settings that are applied during the first-boot experience for end users, also called Windows Welcome.
	oobeSystem settings are processed before a user first logs into Windows.
	Out-of-Box-Experience (OOBE) runs the first time the user starts a new computer.
	OOBE runs before the Windows shell or any additional software runs, and performs a small set of tasks necessary to configure and run Windows.
	-->
    <settings pass="oobeSystem">

        <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>#@system_timezone*#</TimeZone>
            <AutoLogon>
                <Enabled>true</Enabled>
                <LogonCount>1</LogonCount>
                <Username>#@adminName*#</Username>
                <Password>
                    <PlainText>true</PlainText>
                    <Value>#@administratorPassword*#</Value>
                </Password>
            </AutoLogon>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <RequiresUserInput>false</RequiresUserInput>
                    <Description>Opsi tasks</Description>
                    <Order>1</Order>
                    <CommandLine>cmd.exe /c #@winpe_partition_letter*#:\opsi\postinst.cmd</CommandLine>
                </SynchronousCommand>
            </FirstLogonCommands>

            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <ProtectYourPC>3</ProtectYourPC>
                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                <HideLocalAccountScreen>true</HideLocalAccountScreen>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
            </OOBE>

        </component>
	<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>#@system_keyboard_layout*#</InputLocale>
            <SystemLocale>#@system_language*#</SystemLocale>
            <UILanguage>#@system_language*#</UILanguage>
            <UILanguageFallback>#@system_language*#</UILanguageFallback>
            <UserLocale>#@system_language*#</UserLocale>
        </component>

    </settings>
    <cpi:offlineImage cpi:source="wim:c:/temp/win10_/win10-x64/installfiles/sources/install.wim#Windows 10 Pro N" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Kein Support per DM!
_________________________
opsi support - https://www.uib.de/
For productive opsi installations we recommend support contracts.
smallengineguy2014
Beiträge: 9
Registriert: 09 Jul 2019, 22:41

Re: i install windows 10 enterprise and i get 2 different language packs installed

Beitrag von smallengineguy2014 »

i found it and i have tested the fix for me

what would i need to do to start working to better the project
smallengineguy2014
Beiträge: 9
Registriert: 09 Jul 2019, 22:41

Re: i install windows 10 enterprise and i get 2 different language packs installed

Beitrag von smallengineguy2014 »

i did this to the file in /var/lib/opsi/depot/win10-x64/custom

and it gives me a all english install

Code: Alles auswählen

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <!--
	====================
	WINDOWSPE SETTINGS
	====================
	The windowsPE configuration pass is used to configure settings specific to Windows PE as well as settings that apply to installation.
	For example, you can specify the display resolution of Windows PE, where to save a log file, and other Windows PE-related settings.
	-->
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-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">
            <DiskConfiguration>
                <WillShowUI>OnError</WillShowUI>
                <Disk wcm:action="add">
                    <DiskID>#@diskindex*#</DiskID>
                    <WillWipeDisk>false</WillWipeDisk>
                    <ModifyPartitions>
                        #@modify_partitions*#
                    </ModifyPartitions>
                </Disk>
            </DiskConfiguration>
            <UserData>
                <ProductKey>
                    <WillShowUI>OnError</WillShowUI>
                    <Key>#@productkey*#</Key>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
                <FullName>#@fullname*#</FullName>
                <Organization>#@orgname*#</Organization>
            </UserData>
            <ImageInstall>
                <OSImage>
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Key>/IMAGE/NAME</Key>
                            <Value>Windows 10 Enterprise</Value>
                        </MetaData>
                    </InstallFrom>
                    <InstallTo>
                        <DiskID>#@installdiskindex*#</DiskID>
                        <PartitionID>#@windows_partition_number*#</PartitionID>
                    </InstallTo>
                    <WillShowUI>OnError</WillShowUI>
                </OSImage>
            </ImageInstall>
        </component>
        <component name="Microsoft-Windows-International-Core-WinPE" 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">
            <SetupUILanguage>
                <UILanguage>en-US</UILanguage>
                <WillShowUI>OnError</WillShowUI>
            </SetupUILanguage>
            <InputLocale>0409:00020409</InputLocale>
            <SystemLocale>en</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UILanguageFallback>en-US</UILanguageFallback>
            <UserLocale>en</UserLocale>
            <LayeredDriver>1</LayeredDriver>
        </component>
        <component name="Microsoft-Windows-PnPCustomizationsWinPE" 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">
            <DriverPaths wcm:keyValue="1">
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path wcm:keyValue="1">c:\drvpe</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <!--
	=====================
	GENERALIZE SETTINGS
	=====================
	The generalize pass of Windows Setup is used to create a Windows reference image that can be used throughout an organization.
	A setting in the generalize pass enables you to automate the behavior for all deployments of this reference image.
	In comparison, a setting associated with the specialize configuration pass enables you to override behavior for a single, specific deployment.
	When a system is generalized, specific configuration data for a given installation of Windows is removed.
	For example, during the generalize pass, the unique security ID (SID) and other hardware-specific settings are removed from the image.
	The generalize configuration pass runs only when you use the sysprep /generalize command.
	Answer file settings in generalize are applied to the system before sysprep generalization occurs. The system then shuts down.
	-->
    <!--
	<settings pass="generalize">
	</settings>
	-->
    <!--
	=====================
	SPECIALIZE SETTINGS
	=====================
	During the specialize pass of Windows Setup, machine-specific information for the image is applied.
	For example, you can configure network settings, international settings, and domain information.
	The specialize pass is used in conjunction with the generalize pass.
	The generalize pass is used to create a Windows reference image that can be used throughout an organization.
	From this basic Windows reference image, you can add further customizations that apply to different divisions
	within an organization or apply to different installations of Windows.
	The specialize pass is used to apply these specific customizations.
	-->
    <settings pass="specialize">
        <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">
            <ComputerName>#@pcname*#</ComputerName>
            <UserAccounts>
                <AdministratorPassword>
                    <PlainText>true</PlainText>
                    <Value>#@administratorPassword*#</Value>
                </AdministratorPassword>
            </UserAccounts>

        </component>

        <component name="Microsoft-Windows-RemoteAssistance-Exe" 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">
            <CreateEncryptedOnlyTickets>true</CreateEncryptedOnlyTickets>
            <fAllowToGetHelp>true</fAllowToGetHelp>
        </component>
        <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>0409:00020409</InputLocale>
            <SystemLocale>en</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UILanguageFallback>en-US</UILanguageFallback>
            <UserLocale>en</UserLocale>
        </component>
        <component name="Microsoft-Windows-Deployment" 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">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Description>Enable Admin Account</Description>
                    <Order>1</Order>
                    <Path>cmd.exe /c net user #@adminName*# /active:yes</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>Passwd Admin Account</Description>
                    <Order>2</Order>
                    <Path>cmd.exe /c net user #@adminName*# #@administratorPassword*#</Path>
                </RunSynchronousCommand>

            </RunSynchronous>
        </component>
        <component name="Networking-MPSSVC-Svc" 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">
            <DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
            <PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
            <PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
        </component>
    </settings>
    <!--
	=========================
	OFFLINESERVICING SETTINGS
	=========================
	Use the offlineServicing pass to apply unattended Setup settings to an offline Windows image.
	During this configuration pass, you can add language packs, updates, or other packages to the offline image.
	The offlineServicing pass runs during Windows Setup. Setup extracts and installs the Windows image, and then executes Package Manager (Pkgmgr.exe).
	Packages listed in the servicing section of the answer file are applied to the offline Windows image.
	The Unattend.xml settings in the offlineServicing pass are applied to the offline Windows image.
	Additionally, you can use Package Manager with an answer file to install packages.
	-->
    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" 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">
            <DriverPaths>
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path>c:\drv</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <!--
	=====================
	AUDITSYSTEM SETTINGS
	=====================
	The auditSystem pass is an optional pass that enables you to add additional device drivers and applications to the image.
	This results in fewer required images because a reference image can be created with a minimal set of drivers.
	The image can be updated with additional drivers during the audit process.
	You can then test and resolve any operating system issues related to malfunctioning or incorrectly installed devices on the image.
	For example, you can install additional language packs, updates, or other applications, such as Microsoft Office.
	See Reseal mode in oobeSystem.
	-->
    <!--
	<settings pass="auditSystem">
	</settings>
	-->
    <!--
	=====================
	AUDITUSER SETTINGS
	=====================
	The auditUser pass is similar to the auditSystem pass.
	However, the auditUser pass processes these settings after users have logged on, not before they have logged on.
	Like the auditSystem pass, the auditUser pass is used to test the functionality of the Windows Vista image.
	See Reseal mode in oobeSystem.
	-->
    <!--
	<settings pass="auditUser">
	</settings>
	-->
    <!--
	=====================
	OOBESYSTEM SETTINGS
	=====================
	The oobeSystem pass configures settings that are applied during the first-boot experience for end users, also called Windows Welcome.
	oobeSystem settings are processed before a user first logs into Windows.
	Out-of-Box-Experience (OOBE) runs the first time the user starts a new computer.
	OOBE runs before the Windows shell or any additional software runs, and performs a small set of tasks necessary to configure and run Windows.
	-->
    <settings pass="oobeSystem">

        <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>#@system_timezone*#</TimeZone>
            <AutoLogon>
                <Enabled>true</Enabled>
                <LogonCount>1</LogonCount>
                <Username>#@adminName*#</Username>
                <Password>
                    <PlainText>true</PlainText>
                    <Value>#@administratorPassword*#</Value>
                </Password>
            </AutoLogon>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <RequiresUserInput>false</RequiresUserInput>
                    <Description>Opsi tasks</Description>
                    <Order>1</Order>
                    <CommandLine>cmd.exe /c #@winpe_partition_letter*#:\opsi\postinst.cmd</CommandLine>
                </SynchronousCommand>
            </FirstLogonCommands>

            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <ProtectYourPC>3</ProtectYourPC>
                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                <HideLocalAccountScreen>true</HideLocalAccountScreen>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
            </OOBE>

        </component>
	<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>0409:00020409</InputLocale>
            <SystemLocale>en</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UILanguageFallback>en-US</UILanguageFallback>
            <UserLocale>en</UserLocale>
        </component>

    </settings>
    <cpi:offlineImage cpi:source="wim:c:/temp/win10_/win10-x64/installfiles/sources/install.wim#Windows 10 Pro N" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Antworten