Installation opsi-client-agent fehlerhaft

ChrisBe3
Beiträge: 8
Registriert: 29 Feb 2012, 12:58

Installation opsi-client-agent fehlerhaft

Beitragvon ChrisBe3 » 29 Feb 2012, 14:22

Hallo,

der automatische deploy des opsi-client-agents scheitert bei Win7 clients. Wenn ich es manuell über die Console anstoß habe ich folgendes szenario:

Mit diesem Befehl funktioniert es nicht:

Code: Alles auswählen

./opsi-deploy-client-agent -v -u "Administrator" -p "geheim" be3x1002

Mit diesem Befehl funktioniert es:

Code: Alles auswählen

 ./opsi-deploy-client-agent -v -u "be3x1002\Administrator" -p "geheim" be3x1002

Kann das ein Grund sein, warum der opsi client agent nicht automatisch installiert wird?

Mfg

Chris
Zuletzt geändert von ChrisBe3 am 29 Feb 2012, 14:52, insgesamt 1-mal geändert.

ChrisBe3
Beiträge: 8
Registriert: 29 Feb 2012, 12:58

Re: Deploy Opsiclient Agent

Beitragvon ChrisBe3 » 29 Feb 2012, 14:47

Hallo nochmal,

das ist ein das opsiconfd/ pcname.log

Code: Alles auswählen

[4] [Feb 29 14:27:13] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:13] Application 'opsi linux bootimage 20110926' on client '10.46.5.106' did not send cookie (workers.py|161)
[5] [Feb 29 14:27:13] New session created (session.py|74)
[5] [Feb 29 14:27:13] Authorization request from host be3x1002.bccn.local@10.46.5.106 (application: opsi linux bootimage 20110926) (workers.py|186)
[4] [Feb 29 14:27:13] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:14] -----> Executing: backend_getInterface() (JsonRpc.py|123)
[4] [Feb 29 14:27:14] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:14] -----> Executing: configState_getClientToDepotserver([], u'be3x1002.bccn.local', True, []) (JsonRpc.py|123)
[4] [Feb 29 14:27:14] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:14] -----> Executing: productOnDepot_getIdents(u'dict', {'depotId': u'be3osd01.bccn.local', 'productType': u'NetbootProduct', 'productId': u'win7-x64'}) (JsonRpc.py|123)
[4] [Feb 29 14:27:14] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:14] -----> Executing: product_getObjects([], {'packageVersion': u'5', 'id': u'win7-x64', 'productVersion': u'4.0.1'}) (JsonRpc.py|123)
[4] [Feb 29 14:27:14] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:14] -----> Executing: backend_setOptions({u'addProductPropertyStateDefaults': True}) (JsonRpc.py|123)
[4] [Feb 29 14:27:14] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:14] -----> Executing: productPropertyState_getObjects([], {'objectId': u'be3x1002.bccn.local', 'productId': u'win7-x64'}) (JsonRpc.py|123)
[4] [Feb 29 14:27:14] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:15] -----> Executing: backend_setOptions({u'addConfigStateDefaults': True}) (JsonRpc.py|123)
[4] [Feb 29 14:27:15] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:15] -----> Executing: configState_getObjects([], {'objectId': u'be3x1002.bccn.local'}) (JsonRpc.py|123)
[4] [Feb 29 14:27:15] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:15] -----> Executing: user_getCredentials(u'pcpatch', u'be3x1002.bccn.local') (JsonRpc.py|123)
[4] [Feb 29 14:27:15] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:15] -----> Executing: host_getObjects([], {'type': u'OpsiDepotserver', 'id': u'be3osd01.bccn.local'}) (JsonRpc.py|123)
[4] [Feb 29 14:27:15] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:15] -----> Executing: productOnClient_updateObjects(<ProductOnClient clientId 'be3x1002.bccn.local', productId 'win7-x64', installationStatus 'unknown', actionRequest 'None'>) (JsonRpc.py|$
[4] [Feb 29 14:27:15] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:15] -----> Executing: auditHardware_getConfig(None) (JsonRpc.py|123)
[4] [Feb 29 14:27:19] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:19] -----> Executing: auditHardwareOnHost_setObsolete(u'be3x1002.bccn.local') (JsonRpc.py|123)
[4] [Feb 29 14:27:22] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:22] -----> Executing: auditHardwareOnHost_updateObjects([<AuditHardwareOnHost hostId 'be3x1002.bccn.local', hardwareClass 'AUDIO_CONTROLLER', name '82801JD/DO (ICH10 Family) HD Audio Contr$
[4] [Feb 29 14:27:35] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:35] -----> Executing: backend_setOptions({u'addProductPropertyStateDefaults': False}) (JsonRpc.py|123)
[4] [Feb 29 14:27:35] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:35] -----> Executing: productOnClient_getObjects([], {'clientId': u'be3x1002.bccn.local'}) (JsonRpc.py|123)
[4] [Feb 29 14:27:35] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:35] -----> Executing: productOnClient_deleteObjects([]) (JsonRpc.py|123)
[4] [Feb 29 14:27:56] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:56] -----> Executing: productOnClient_updateObjects(<ProductOnClient clientId 'be3x1002.bccn.local', productId 'win7-x64', installationStatus 'unknown', actionRequest 'none'>) (JsonRpc.py|$
[4] [Feb 29 14:27:56] Failed to read opsi modules file '/etc/opsi/modules': Signature not found (Backend.py|371)
[5] [Feb 29 14:27:56] -----> Executing: log_write(u'bootimage', u'Feb 29 14:26:29 [opsiinit] opsi init script started\nFeb 29 14:26:29 [opsiinit] opsi linux bootimage version: 20110926\nFeb 29 14:26:29 [ops$


Vielen Dank schonmal

Chris

Benutzeravatar
Thomas_H
Beiträge: 480
Registriert: 09 Jun 2010, 11:57
Wohnort: Havelland

Re: Installation opsi-client-agent fehlerhaft

Beitragvon Thomas_H » 01 Mär 2012, 16:28

Moinsens...

na klar, der Rechner muss doch wissen, woher der Nutzer Administrator kommt. Ist es der Domänenadmin oder der Lokale, oder der Nutzer "Administrator", der vielleicht vom Opsi-Server kommt?
Mit "<rechnername>\administrator" wird diese Frage beantwortet und der Rechner kann die Berechtigung des angegebenen Nutzers prüfen... :)

Gruß

Thomas_H
Kennst Du schon die WIKI für OPSI-Scripte? Fertige Installationsscripte bekommen und ablegen unter OPSI-Wiki
Aus dem Glashaus :) : UIB bietet auch Schulungen und Supportverträge für Opsi an.
Bild

ChrisBe3
Beiträge: 8
Registriert: 29 Feb 2012, 12:58

Re: Installation opsi-client-agent fehlerhaft

Beitragvon ChrisBe3 » 01 Mär 2012, 18:19

Hallo,

ok, das war mir fast klar. Gibt es da eine Einstellung wie man es verändern kann? Haben andere mit domain Join das gleiche Problem? Wie wurde das gelöst?


Viele Grüße

Chris

ChrisBe3
Beiträge: 8
Registriert: 29 Feb 2012, 12:58

Re: Installation opsi-client-agent fehlerhaft

Beitragvon ChrisBe3 » 02 Mär 2012, 12:42

Hallo,

irgendjemand ne idee? Ist es nur eine Einstellungssache?

Viele Grüße

Chris

othiman
Beiträge: 126
Registriert: 09 Sep 2009, 14:15
Wohnort: Aachen, Germany

Re: Installation opsi-client-agent fehlerhaft

Beitragvon othiman » 02 Mär 2012, 14:45

Hallo,

wie soll der opsi client agent denn automatisch installiert werden? Eigentlich doch genau mit dem Befehl, oder? Also wo liegt das Problem?

Solange das nicht genau beschrieben ist, wird wohl auch keiner eine passende Antwort haben...

Gruß
Thomas

PS: Man kann wahrscheinlich auch

Code: Alles auswählen

./opsi-deploy-client-agent -v -u ".\Administrator" -p "geheim" be3x1002
benutzen, da .\ immer den lokalen Benutzer wählt. Vielleicht hilft das ja weiter?

ChrisBe3
Beiträge: 8
Registriert: 29 Feb 2012, 12:58

Re: Installation opsi-client-agent fehlerhaft

Beitragvon ChrisBe3 » 02 Mär 2012, 18:30

Siehe Post 1.

Ich weiss nicht, was ich noch beschreiben soll. Wenn ich windows auf den Clients installiere, will ich doch auch das der Opsiclient agent ( wie bei winxppro ohne probleme ) installiert ist. Und das ohne das ich auf der Console den Client deployen muss. Bei Winxppro geht alles ohne Probleme. Bei Win7 nicht. Und jetzt kommts aus Post 1:
Mit den Befehlen auf der Console funktionierts, nach der Windows Installtion automatisch passiert garnix.

Viele Grüße

Chris

othiman
Beiträge: 126
Registriert: 09 Sep 2009, 14:15
Wohnort: Aachen, Germany

Re: Installation opsi-client-agent fehlerhaft

Beitragvon othiman » 02 Mär 2012, 18:40

OK, jetzt verstehe ich das Problem. Wie wurde denn die unattended.xml erstellt? Hört sich danach an als würde da der Fehler liegen.

Mit dem Domainjoin hat das sicher nichts zu tun, denn die Installation des opsi-client-agents wird nicht vom Server angestossen, sondern durch den Client selber bei der Installation.

Gruß
Thomas

ChrisBe3
Beiträge: 8
Registriert: 29 Feb 2012, 12:58

Re: Installation opsi-client-agent fehlerhaft

Beitragvon ChrisBe3 » 02 Mär 2012, 19:04

Ich habe die Sample Datei angepasst. Anbei 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="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>true</WillWipeDisk>
               
               <CreatePartitions>
                  <CreatePartition wcm:action="add">
                     <Order>1</Order>
                     <Type>Primary</Type>
                     <Size>20000</Size>
                  </CreatePartition>
               </CreatePartitions>
         
            
               <ModifyPartitions>
                  #@modify_partitions*#
               </ModifyPartitions>
            </Disk>
         </DiskConfiguration>
         -->
         <DiskConfiguration>
               <Disk wcm:action="add">
                   <CreatePartitions>
                       <CreatePartition wcm:action="add">
                           <Order>1</Order>
                           <Size>100000</Size>
                           <Type>Primary</Type>
                       </CreatePartition>
                       <CreatePartition wcm:action="add">
                           <Extend>true</Extend>
                           <Order>3</Order>
                           <Type>Logical</Type>
                       </CreatePartition>
                       <CreatePartition wcm:action="add">
                           <Order>2</Order>
                           <Type>Extended</Type>
                           <Extend>true</Extend>
                       </CreatePartition>
                   </CreatePartitions>
                   <ModifyPartitions>
                       <ModifyPartition wcm:action="add">
                           <Active>true</Active>
                           <Extend>false</Extend>
                           <Format>NTFS</Format>
                           <Label>Windows</Label>
                           <Letter>C</Letter>
                           <Order>1</Order>
                           <PartitionID>1</PartitionID>
                       </ModifyPartition>
                       <ModifyPartition wcm:action="add">
                           <Active>false</Active>
                           <Extend>false</Extend>
                           <Format>NTFS</Format>
                           <Label>DATA</Label>
                           <Letter>D</Letter>
                           <Order>2</Order>
                           <PartitionID>2</PartitionID>
                       </ModifyPartition>
                   </ModifyPartitions>
                   <DiskID>0</DiskID>
                   <WillWipeDisk>true</WillWipeDisk>
               </Disk>
               <WillShowUI>OnError</WillShowUI>
           </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>#@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>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>#@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="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>DOMAIN.LOCAL</Domain>
               <Password>********</Password>
               <Username>admin</Username>
            </Credentials>
            <DebugJoin>true</DebugJoin>
            <JoinDomain>bccn.local</JoinDomain>
                        <JoinWorkgroup>joinworkgroup</JoinWorkgroup>

            <MachineObjectOU>machineobjectou</MachineObjectOU>
            <MachinePassword>machinepassword</MachinePassword>
            
            <UnsecureJoin>false</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>********</Value>
            </AdministratorPassword>
            <LocalAccounts>            
               <LocalAccount wcm:action="add">
                  <Password>
                     <PlainText>true</PlainText>
                     <Value>*********</Value>
                  </Password>
                  <Description>pcpatch</Description>
                  <Group>Administratoren</Group>
                  <Name>pcpatch</Name>
                  <DisplayName>PCPatch</DisplayName>
               </LocalAccount>
               
            </LocalAccounts>
         </UserAccounts>
         <BluetoothTaskbarIconEnabled>false</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>




Ich habe inzwischen den Domain join raus genommen und es geht auch nicht. Vielleicht findest du ja etwas :-/

Viele Grüße

Chris

othiman
Beiträge: 126
Registriert: 09 Sep 2009, 14:15
Wohnort: Aachen, Germany

Re: Installation opsi-client-agent fehlerhaft

Beitragvon othiman » 05 Mär 2012, 09:54

Hallo,

ich sehe gerade, dass einige Passwörter mit ***** ausgefüllt sind. Ich denke das ist im Nachhinein so gemacht worden?

Direkt unter den Passwörtern gibt es die Sektion AutoLogon, wo noch das alte Passwort des Users pcpatch eingetragen ist. Damit schlägt natürlich die Anmeldung dieses Users fehl, der vermutlich die Installation des opsi-client-agent vornimmt. Ich denke, dass der User eh nur für diesen Zweck angelegt und nach der erfolgreichen Installation wieder gelöscht wird. Gesehen hab ich pcpatch jedenfalls nie als User auf den OPSI Systemen. Insofern würde ich auf jeden Fall die originalen Werte an der Stelle bestehen lassen. Um so weniger man in der unattend.xml ändert, um so besser. Wie man an dem Beispiel sieht, entstehen schnell unnötige Probleme.

Viele Grüße
Thomas