Win7-x64 Installationsproblem

rns
Beiträge: 7
Registriert: 09 Apr 2013, 19:46

Win7-x64 Installationsproblem

Beitrag von rns »

Hallo,

ich habe ein Problem mit meiner Win7 64bit unattended Installation. WinPE startet, das Windows Setup auch. Nach dem Setup bleibt jedoch WinPE mit offener Konsole mit Pfad X:\Windows\System32 stehen.
Die Windows-Installation finde ich unter Laufwerk d:, das WinPE Setup, welches vom Opsi PXE-Linux angelegt wurde auf Laufwerk c:
Ich habe in das Windows Setup keine zusätzlichen Treiber o.ä. integriert

Folgende Installationsparameter habe ich in OPSI gewählt:
  • additional_drivers =
  • askbeforeinst = false
  • blockalignment = true
  • boot_partition_label = BOOT
  • boot_partition_letter = -
  • boot_partition_size = 0
  • data_partition_create = false
  • data_partition_label = DATA
  • data_partition_letter = D
  • fullname = Name
  • imagename = WINDOWS 7 PROFESSIONAL
  • orgname = Orgname
  • productkey = xxxx...
  • system_keyboard_layout = 0407:00000407
  • system_language = de-DE
  • system_timezone = W. Europe Standard Time
  • use_raid1 = false
  • windows_partition_label = WINDOWS
  • windows_partition_size = 100%
  • winpe_uilanguage = de-DE
  • winpe_uilanguage_fallback = de-DE
  • winpe_networkmode = true
Ich verwende folgende Opsi Versionen:
  • opsi-atftpd 0.7.dfsg-2.1
  • opsi-configed 4.0.3.2.1
  • opsi-depotserver 4.0.3.1
  • opsi-linux-bootimage 201
  • opsi-utils 4.0.3.1
  • opsiconfd 4.0.3.1
  • opsipxeconfd 4.0.3.1
  • python-opsi 4.0.3.1
Das win7-x64 OPSI-Paket hat die Version 4.0.3-2


Kann mir hier jemand weiterhelfen ?
Benutzeravatar
d.oertel
uib-Team
Beiträge: 3327
Registriert: 04 Jun 2008, 14:27

Re: Win7-x64 Installationsproblem

Beitrag von d.oertel »

Hi,

Anpassungen an der unattend.xml vorgenommen ?

gruß
d.oertel


Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.

Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.

uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de


rns
Beiträge: 7
Registriert: 09 Apr 2013, 19:46

Re: Win7-x64 Installationsproblem

Beitrag von rns »

Hallo ,

ich habe den Product-key in der unattend.xml auskommentiert, sowie das Administrator-Passwort geändert.
Ansonsten ist die unattended.xml so, wie sie im opsi-paket ausgeliefert wurde.
bmsoft
Beiträge: 43
Registriert: 02 Feb 2012, 12:30

Re: Win7-x64 Installationsproblem

Beitrag von bmsoft »

rns hat geschrieben: ich habe den Product-key in der unattend.xml auskommentiert,
Evtl. zuviel auskommentiert? Ein erster Syntax-Check geht mit xmlstarlet val unattend.xml ganz gut.
rns
Beiträge: 7
Registriert: 09 Apr 2013, 19:46

Re: Win7-x64 Installationsproblem

Beitrag von rns »

Hallo,

xmlstarlet meldet, dass das XML valide sei.
Ich habe die unattend.xml in der Form angehängt, wie ich sie in WinPE unter x:\unattend.xml vorgefunden habe.

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="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:\drvpe</Path>
				</PathAndCredentials>
			</DriverPaths>
		</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">
			<DiskConfiguration>
				<WillShowUI>OnError</WillShowUI>
				<Disk wcm:action="add">
					<DiskID>0</DiskID>
					<WillWipeDisk>false</WillWipeDisk>
					<!--
					<CreatePartitions>
						<CreatePartition wcm:action="add">
							<Order>1</Order>
							<Type>Primary</Type>
							<Size>20000</Size>
						</CreatePartition>
					</CreatePartitions>
					<ModifyPartitions>
						<ModifyPartition wcm:action="add">		<Active>true</Active>		<Format>NTFS</Format>		<Label>WINDOWS</Label>		<Letter>C</Letter>		<Extend>false</Extend>		<Order>1</Order>		<PartitionID>1</PartitionID>	</ModifyPartition>		<ModifyPartition wcm:action="add">		<Active>false</Active>		<Label>WINPE</Label>		<Letter>X</Letter>		<Extend>false</Extend>		<Order>2</Order>		<PartitionID>2</PartitionID>	</ModifyPartition>
					</ModifyPartitions>
					-->
				</Disk>
			</DiskConfiguration>
			<!--
			<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>Do something</Description>
						<Order>1</Order>
						<Path>cmd.exe</Path>
					</RunSynchronousCommand>
				</RunSynchronous>
			</component>
			-->
			<UserData>
				<!-- <ProductKey>
					<WillShowUI>OnError</WillShowUI>
					<Key>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</Key>
				</ProductKey> -->
				<AcceptEula>true</AcceptEula>
				<FullName>Name</FullName>
				<Organization>Orgname</Organization>
			</UserData>
			<ImageInstall>
				<OSImage>
					<InstallFrom>
						<MetaData wcm:action="add">
							<Key>/IMAGE/NAME</Key>
							<Value>Windows 7 PROFESSIONAL</Value>
						</MetaData>
					</InstallFrom>
					<InstallTo>
						<DiskID>0</DiskID>
						<PartitionID>1</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>de-DE</UILanguage>
				<WillShowUI>OnError</WillShowUI>
			</SetupUILanguage>
			<InputLocale>0407:00000407</InputLocale>
			<SystemLocale>de-DE</SystemLocale>
			<UILanguage>de-DE</UILanguage>
			<UILanguageFallback>de-DE</UILanguageFallback>
			<UserLocale>de-DE</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 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">
			<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
			<ComputerName>win7test</ComputerName>
			<!--  <ProductKey>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</ProductKey>  -->
			<CopyProfile>false</CopyProfile>
			<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
			<DoNotCleanTaskBar>false</DoNotCleanTaskBar>
			<ShowWindowsLive>false</ShowWindowsLive>
			<StartPanelOff>false</StartPanelOff>
			<TimeZone>W. Europe Standard Time</TimeZone>
			<WindowsFeatures>
				<ShowWindowsMail>false</ShowWindowsMail>
			</WindowsFeatures>
		</component>

		<component name="Microsoft-Windows-Security-Licensing-SLC-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-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>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 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="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>0407:00000407</InputLocale>
			<SystemLocale>de-DE</SystemLocale>
			<UILanguage>de-DE</UILanguage>
			<UILanguageFallback>de-DE</UILanguageFallback>
			<UserLocale>de-DE</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 administrator /active:yes</Path>
				</RunSynchronousCommand>
				<!--
				<RunSynchronousCommand wcm:action="add">
					<Description>Opsi tasks</Description>
					<Order>2</Order>
					<Path>cmd.exe /c X:\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 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>

		<component name="Security-Malware-Windows-Defender" 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">
			<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 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>
				<PathAndCredentials wcm:keyValue="1" wcm:action="add">
					<Path>c:\drvpe</Path>
				</PathAndCredentials>
			</DriverPaths>
		</component>

		<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-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">
			<Reseal>
				<Mode>Audit</Mode>
			</Reseal>
		</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">
			<UserAccounts>
				<AdministratorPassword>
					<PlainText>true</PlainText>
					<Value>MeinPasswort</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>W. Europe Standard Time</TimeZone>
			<AutoLogon>
				<Enabled>true</Enabled>
				<LogonCount>1</LogonCount>
				<Username>Administrator</Username>
				<Password>
					<PlainText>true</PlainText>
					<Value>MeinPasswort</Value>
				</Password>
			</AutoLogon>
			<FirstLogonCommands>
				<SynchronousCommand wcm:action="add">
					<Description>Opsi tasks</Description>
					<Order>1</Order>
					<CommandLine>cmd.exe /c X:\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 (x86)\opsi.org\opsi-client-agent\opsi-winst\opsi.bmp</Logo>
				<Manufacturer>Ich</Manufacturer>
				<Model></Model>
				<SupportURL>http://www.rnssystems.de</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>0407:00000407</InputLocale>
			<SystemLocale>de-DE</SystemLocale>
			<UILanguage>de-DE</UILanguage>
			<UILanguageFallback>de-DE</UILanguageFallback>
			<UserLocale>de-DE</UserLocale>
		</component>
		-->
	</settings>
	<cpi:offlineImage cpi:source="wim:y:/install.wim#Windows Vista ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
TastaturHacker
Beiträge: 20
Registriert: 23 Jan 2013, 14:55

Re: Win7-x64 Installationsproblem

Beitrag von TastaturHacker »

Hi,
Versuch doch mal anstatt in der Unattend.xml den Product key auszukommentieren, einfach ein Leerzeichen als key im Config Editor an zu geben.
Also in der Unattend.xml nur das Adminkennwort ändern, den Key manuell auf " " setzen.
Glaube ich hatte das Problem auch mal, könnte sein das das geholfen hat..

mfg TastaturHacker
rns
Beiträge: 7
Registriert: 09 Apr 2013, 19:46

Re: Win7-x64 Installationsproblem

Beitrag von rns »

TastaturHacker hat geschrieben:Hi,
Versuch doch mal anstatt in der Unattend.xml den Product key auszukommentieren, einfach ein Leerzeichen als key im Config Editor an zu geben.
Also in der Unattend.xml nur das Adminkennwort ändern, den Key manuell auf " " setzen.
Glaube ich hatte das Problem auch mal, könnte sein das das geholfen hat..

mfg TastaturHacker
Hi,

hat leider keinen Effekt auf mein Problem. Auch ein komplett leerer Product Key endet damit, dass die cmd offen stehen bleibt.
TastaturHacker
Beiträge: 20
Registriert: 23 Jan 2013, 14:55

Re: Win7-x64 Installationsproblem

Beitrag von TastaturHacker »

Mhm...
Was andres fällt mir leider nich ein..
Benutzeravatar
d.oertel
uib-Team
Beiträge: 3327
Registriert: 04 Jun 2008, 14:27

Re: Win7-x64 Installationsproblem

Beitrag von d.oertel »

Hi,

funktioniert es mit der orginal opsi unattend.xml ?

gruß
d.oertel


Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.

Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.

uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de


rns
Beiträge: 7
Registriert: 09 Apr 2013, 19:46

Re: Win7-x64 Installationsproblem

Beitrag von rns »

Hi,

also die Original opsi unattend.xml hat keine Änderung gebracht.
Antworten