Diverse Probs..

Spoxs
Beiträge: 108
Registriert: 16 Jun 2011, 14:25

Re: Diverse Probs..

Beitrag von Spoxs »

Hmm.
Also ich habe am Template gar nichts gemacht und nur die im Ordner custom angepasst.
rabadag
Beiträge: 17
Registriert: 09 Jul 2011, 12:54

Re: Diverse Probs..

Beitrag von rabadag »

und genau die geht bei mir nicht. sobald ich die mit WAIK bearbeite geht nichts mehr.
oder nur Teilweise..

Kannst du mir mal deine zum testen zur Verfügung geben?
Spoxs
Beiträge: 108
Registriert: 16 Jun 2011, 14:25

Re: Diverse Probs..

Beitrag von Spoxs »

Ich habe die unattend.xml.template nach /win7/custom kopiert ind in unattend.xml umbenannt nach dem ich die andere weggesichert habe.
Dann habe ich folgende Änderungen vorgenommen:
Zeile 53 den Inhalt zwischen <Key> und </Key> entfernt, da hier mein KMS für die Installation des Product Keys sorgt.
Zeile 57 die Variable bei Fullname durch einen festen Eintrag ersetzt
Zeile 58 die Variable Organization durch einen festen Eintrag ersetzt.

Mehr habe ich nicht geändert.
rabadag
Beiträge: 17
Registriert: 09 Jul 2011, 12:54

Re: Diverse Probs..

Beitrag von rabadag »

hmm..

Dann ist vermutlich die Lösung das Template Manual ab-zufüllen mit den gewünschten
Erweiterungen. das muss ich mal testen..
Spoxs
Beiträge: 108
Registriert: 16 Jun 2011, 14:25

Re: Diverse Probs..

Beitrag von Spoxs »

Das Template muss nicht geändert werden.
Soehnke
Beiträge: 46
Registriert: 08 Mär 2011, 11:18

Re: Diverse Probs..

Beitrag von Soehnke »

rabadag hat geschrieben:hmm..

Dann ist vermutlich die Lösung das Template Manual ab-zufüllen mit den gewünschten
Erweiterungen. das muss ich mal testen..
Du kannst das Template auch mit Variablen befüllen, die du dann im opsi vor der installation definieren kannst, so haben wir das z.b. mit einem standart Benutzer der frei wählbar ist gelöst.
rabadag
Beiträge: 17
Registriert: 09 Jul 2011, 12:54

Re: Diverse Probs..

Beitrag von rabadag »

Interessant.. Das Produkt OPSI wird mir immer sympathischer.. so viel Freiheiten..

Werde das jetzt mal testen ob es mit der manuellen Anpassung funktioniert.
rabadag
Beiträge: 17
Registriert: 09 Jul 2011, 12:54

Re: Diverse Probs..

Beitrag von rabadag »

Melde mich zurück..

Also der versuch die Template unattend.xml manuell mit den benötigten Infos zu bearbeiten
hat den gewünschten Erfolg erbracht.

Nun funktioniert der Domain Beitritt einwandfrei.

Mann sollte im Manaul Starting Anleitung eventuell den Hinweis eintragen, das WIAK das
unattend.xml beim zuweisen einer neuen Windows Version "install.wim" Einstellung löscht und
die Ganze Installation nur bedingt funktioniert.

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

Nach Bearbeitung mit WIAK
<cpi:offlineImage cpi:source="wim://opsi/opt_pcbin/install/win7/installfiles/sources/install.wim#Windows 7 ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

Und genau mit dieser Verknüpfung werden diverse Einstellungen nicht gespeichert.

Jetzt kann ich mich an die Software Verteilung ran machen.

Somit ist dieser beitrag als gelöst zu beachten.



Hier noch für andere User die über das selbe stolpern meine unattend.xml.

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:\drv</Path>
				</PathAndCredentials>
			</DriverPaths>
		</component>
		
		<component name="Microsoft-Windows-Setup" 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">
			<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>
						#@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></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>OnError</WillShowUI>
				</OSImage>
			</ImageInstall>
		</component>
		
		<component name="Microsoft-Windows-International-Core-WinPE" 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">
			<SetupUILanguage>
				<UILanguage>de-DE</UILanguage>
				<WillShowUI>OnError</WillShowUI>
			</SetupUILanguage>
			<InputLocale>0407:00000407</InputLocale>
			<SystemLocale>#@system_language*#</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="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">
			<BluetoothTaskbarIconEnabled>true</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="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">
			<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>meineDomain</Domain>
                    <Password>meinPassword</Password>
                    <Username>meinUsername</Username>
                </Credentials>
                <DebugJoin></DebugJoin>
                <DebugJoinOnlyOnThisError></DebugJoinOnlyOnThisError>
                <JoinDomain>meineDomain</JoinDomain>
                <UnsecureJoin>false</UnsecureJoin>
            </Identification>
		</component>
		
		
		<component name="Microsoft-Windows-RemoteAssistance-Exe" 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">
			<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="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>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="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">
			<DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
			<PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
			<PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
		</component>
		
		<component name="Security-Malware-Windows-Defender" 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">
			<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="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:\drv</Path>
				</PathAndCredentials>
			</DriverPaths>
		</component>
		
		<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" 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:\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 name="Microsoft-Windows-Shell-Setup" 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">
			<UserAccounts>
				<AdministratorPassword>
					<PlainText>true</PlainText>
					<Value>password</Value>
				</AdministratorPassword>
				<DomainAccounts>
				  <DomainAccountList wcm:action="add">
				  <Domain>widex</Domain>
				  <DomainAccount wcm:action="add">
				  <Group>Administratoren</Group>
				  <Name>wininstall</Name>
				  </DomainAccount>
				 </DomainAccountList>
			      </DomainAccounts>
			</UserAccounts>
			<BluetoothTaskbarIconEnabled>true</BluetoothTaskbarIconEnabled>
			<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
			<DoNotCleanTaskBar>false</DoNotCleanTaskBar>
			<ShowWindowsLive>false</ShowWindowsLive>
			<StartPanelOff>false</StartPanelOff>
			<TimeZone>#@system_timezone*#</TimeZone>
			<!--
			<AutoLogon>
				<Password>
					<PlainText>true</PlainText>
					<Value>uib</Value>
				</Password>
				<Enabled>true</Enabled>
				<LogonCount>1</LogonCount>
				<Username>UIB</Username>
			</AutoLogon>
			-->
			<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>Open PC Server Integration</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 Vista ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Spoxs
Beiträge: 108
Registriert: 16 Jun 2011, 14:25

Re: Diverse Probs..

Beitrag von Spoxs »

Danke für die Information.
Wenn ich das richtig verstehe, hast Du nur die Schema Zeile von Vista auf Win7 geändert und die notwendigen Informationen zum Domänenbeitritt geändert?
rabadag
Beiträge: 17
Registriert: 09 Jul 2011, 12:54

Re: Diverse Probs..

Beitrag von rabadag »

Nein..

Das Schma ist bei mir noch das ORG als Vista für die Installation von Win7.

Wenn man aber mit WIAK das Schama anpasst weil WIAK motz das das vindows vista nicht in der install.wim enthalten ist verhaut es die Konfig.
Antworten