Seite 1 von 1

Opsi Client Agent wird nicht installiert

Verfasst: 12 Jul 2012, 09:32
von Stefan W
Hallo zusammen,

ich bin gerade dabei das mitgelieferte unattend.xml File für Windows 7 zu modifizieren. In einem vorherigen Eintrag im Forum habe ich gelesen, dass man keine Veränderungen mit dem "Windows System Image Manger" vornehmen soll da es danach wohl nicht mehr so läuft wie gewollt. Habe mir die Backup template aus dem Opsi verzeichnis geholt und diese mit Hilfe von Notepad modifiziert. Das Problem ist sobald ich eine kleine Veränderung an dem File vornehme wird nach der Installation von Windows 7 kein Opsi-Client-Agent installiert. Hat jemand eine Idee woran das liegen könnte? Das File funktioniert, alle konfigurationen werden übernommen jedoch nicht der Opsi-Client-Agent. Grundsätzlich erstelle ich eine Partition von 50GB, nehme das System in die Domäne auf und lege einen zusätzlichen lokalen Administrator im System an. Es reicht schon aus, dass ich WillWipeDesk auf true setze.

Re: Opsi Client Agent wird nicht installiert

Verfasst: 12 Jul 2012, 10:54
von tobias
die XML bitte nur im CUSTOM verzeichnis anpassen niemals im OPSI verzeichnis.

Re: Opsi Client Agent wird nicht installiert

Verfasst: 12 Jul 2012, 11:10
von Stefan W
Das XML-File wurde im Custom Verzeichnis angepasst

Re: Opsi Client Agent wird nicht installiert

Verfasst: 12 Jul 2012, 11:34
von tobias
dann poste mal deine angepasste XML

Re: Opsi Client Agent wird nicht installiert

Verfasst: 12 Jul 2012, 12:59
von Stefan W
<?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">
<UserData>
<ProductKey>
<Key>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</Key>
<WillShowUI>OnError</WillShowUI>
</ProductKey>
<AcceptEula>true</AcceptEula>
<FullName>Firma</FullName>
<Organization>Firma</Organization>
</UserData>
<DiskConfiguration>
<WillShowUI>OnError</WillShowUI>
<Disk wcm:action="add">
<CreatePartitions>
<CreatePartition wcm:action="add">
<Order>1</Order>
<Size>51200</Size>
<Type>Primary</Type>
</CreatePartition>
</CreatePartitions>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
<ModifyPartitions>
<ModifyPartition wcm:action="add">
<Active>true</Active>
<Format>NTFS</Format>
<Label>System</Label>
<Order>1</Order>
<Letter>C</Letter>
<PartitionID>1</PartitionID>
</ModifyPartition>
</ModifyPartitions>
</Disk>
</DiskConfiguration>
<ImageInstall>
<OSImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>1</PartitionID>
</InstallTo>
<InstallToAvailablePartition>false</InstallToAvailablePartition>
<WillShowUI>OnError</WillShowUI>
<InstallFrom>
<MetaData wcm:action="add">
<Value>3</Value>
<Key>/IMAGE/INDEX</Key>
</MetaData>
</InstallFrom>
</OSImage>
</ImageInstall>
<EnableFirewall>false</EnableFirewall>
</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>Do something</Description>
<Order>1</Order>
<Path>cmd.exe</Path>
</RunSynchronousCommand>
</RunSynchronous>
</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>
</SetupUILanguage>
<InputLocale>de-DE</InputLocale>
<SystemLocale>de-DE</SystemLocale>
<UILanguage>de-DE</UILanguage>
<UserLocale>de-DE</UserLocale>
</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>
<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>
<DebugJoin>true</DebugJoin>
<JoinDomain>XXX.XX</JoinDomain>
<MachineObjectOU>OU=XX, OU=XX, DC=XX, DC=XX</MachineObjectOU>
<Credentials>
<Domain>XX.de</Domain>
<Password>XXXXX</Password>
<Username>XXXXX</Username>
</Credentials>
</Identification>
</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>#@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">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<SkipUserOOBE>true</SkipUserOOBE>
<ProtectYourPC>3</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
</OOBE>
<AutoLogon>
<Password>
<Value>dwBpAG4ANwBsAHYAbQBQAGEAcwBzAHcAbwByAGQA</Value>
<PlainText>false</PlainText>
</Password>
<Enabled>true</Enabled>
<LogonCount>1</LogonCount>
<Username>Administrator</Username>
</AutoLogon>
<TimeZone>W. Europe</TimeZone>
<UserAccounts>
<AdministratorPassword>
<PlainText>false</PlainText>
<Value>bgB0ADEAMgAzAEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA==</Value>
</AdministratorPassword>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>cwBkAHcAZAB3AGIAZAB2AGkAUABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<DisplayName>User</DisplayName>
<Group>Gruppe</Group>
<Name>UserName</Name>
<Description>Lokaler Administrator</Description>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
<DoNotCleanTaskBar>false</DoNotCleanTaskBar>
<ShowWindowsLive>false</ShowWindowsLive>
<StartPanelOff>false</StartPanelOff>
<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>
-->

<OEMInformation>
<Logo>c:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-winst\opsi.bmp</Logo>
<Manufacturer>Organisation</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:c:/windows7/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Re: Opsi Client Agent wird nicht installiert

Verfasst: 13 Jul 2012, 14:49
von tobias
wär gut wenn du da jez noch markieren könntest was du verändert hast ;)

und schau dir eventuell mal das an. Ich habe bei mir die XML dahingehend angepasst das automatisch ein Lokaler Benutzer angelegt wird.
wiki/userspace:windows_7_create_localadmin

wenn du immer das selbe PW nutzen willst kannst du die ganze Paketierungsgeschichte mit Host-Parameter oder ProductPropertys weglassen und passt nur die XML an.

Zum anpassen kopierst du dir einfach die xml.template aus dem OPSI ordner in den CUSTOM ordner. Dann nach jeder Änderung testen ob noch alles funktioniert ;)

Re: Opsi Client Agent wird nicht installiert

Verfasst: 08 Aug 2012, 09:18
von Stefan W
Habe den Fehler gefunden. Die Partitionierung geschieht nicht im XML-File sondern wird schon vorher gemacht. Wenn ich den WillWipe Befehl im XML-File setze wird das was vorher geschieht nichtig. Von daher habe ich die Anpassung im Win-Pe bereich weg gelassen.