Seite 1 von 1

Fehler bei win7-x64 Installation

Verfasst: 04 Sep 2015, 12:06
von MarcMuc
Hallo zusammen!

Ich probiere jetzt schon 3 Tage den Fehler zu finden. Kein Erfolg.

Situation:

opsi Server 4.0.5.20 ist installiert und läuft. Software-Installation auf Clients funktioniert.
WinPE wurde mit "amd64" erstellt und nach depot/win7-x64/winpe kopiert.
Windows 7 Prof. 64-bit OEM DVD wurde nach win7-x64/installfiles kopiert.
Rechte wurden mit opsi-setup gesetzt (bei beiden Verzeichnissen).

Neuer Testclient (VM) wurde mit dem opsi-Linux-Image via netboot in die Clientliste aufgenommen. Funktioniert.

Jetzt will ich eine Win7-x64 Installation unattended via netboot ausführen. Das WinPE wird auch gestartet und auch die Mounts im Netzwerk scheinen zu funktionieren. Er startet dann das Setup und nach ein paar Sekunden kommt die Meldung:

"Die für die Installation verfügbaren Abbilder konnten nicht angezeigt werden."

Danach lande ich wieder im cmd. Wenn ich dann im installfile-Ordner die setup.exe von Hand aufrufe, würde die Installation starten (ich bekomme den Auswahldialog, welche Sprache und welches Land, etc.).

Mit dism.exe habe ich überprüft, ob das gewählte Abbild in der install.wim vorhanden ist. Ist es.

Was ist falsch? Ich vermute es hängt mit der unattended.xml zusammen. Die habe ich aber bis auf das Admin-Passwort und den Domänen-Join nicht verändert. Was kann da noch falsch sein?

Ich wäre sehr dankbar für Hilfe!

Gruß Marc

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>Always</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>
						#@modify_partitions*#
					</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>Always</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>0</DiskID>
						<PartitionID>#@windows_partition_number*#</PartitionID>
					</InstallTo>
					<WillShowUI>Always</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>Always</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 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>#@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 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>XXX.dom</Domain>
					<Password>xx12345</Password>
					<Username>Administrator</Username>
				</Credentials>
				<DebugJoin>true</DebugJoin>
				<JoinDomain>XXX.dom</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>#@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 administrator /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 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>xx12345</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>Administrator</Username>
				<Password>
					<PlainText>true</PlainText>
					<Value>xx12345</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 (x86)\opsi.org\opsi-client-agent\opsi-winst\opsi.bmp</Logo>
				<Manufacturer>opsi</Manufacturer>
				<Model></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 cpi:source="wim:y:/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Re: Fehler bei win7-x64 Installation

Verfasst: 04 Sep 2015, 12:32
von n.wenselowski
Hallo Marc,

ich würde den Inhalt der Installations-DVD nochmal auf den Server kopieren und dabei darauf achten, dass im Binärmodus übertragen wird.
Für den Test empfehle ich dabei erstmal die originale unattended.xml zu verwenden und das Passwort erst zu ändern wenn die eigentliche Installation funktioniert.


Gruß

Niko

Re: Fehler bei win7-x64 Installation

Verfasst: 04 Sep 2015, 12:39
von MarcMuc
Hallo Niko,

ich habe die Daten via Netzwerk (Windows Explorer) kopiert. Auf dem opsi-Server gibt es ja die Freigabe depot_rw
Da kann ich kein Binärmodus wählen. Aber ich werde nochmal einen Kopierversuch mit WinSCP versuchen.Im Binärmodus.

Ich hab natürlich die originale unattended.xml überschrieben. Liegt die ausser im custom Ordner noch woanders?

Re: Fehler bei win7-x64 Installation

Verfasst: 04 Sep 2015, 13:21
von MarcMuc
Isch werd bekloppt!

Nachdem ich jetzt einen Binär-Copy mit WinSCP gemacht habe und die unattended.xml wieder auf Originalzustand gesetzt habe, startet das Setup und er installiert Windows!

Danke für den Tipp.

Gruß Marc