[gelöst] Nach Installation trotz dem keine Software vorhanden
Verfasst: 07 Feb 2018, 23:02
Moin, Moin,
nachdem nun schon über einer Woche verzweifelt versuche den CitrixReceiver zu packen muss ich kapitulieren. Das Problem: Ich habe einen komplett neuen OPSI-Server aufgesetzt in aktuellster Version. Nach der Installation von Win10 64bit Pro wollte ich den CitrixReceiver in der Version 4.10.1 packen und installieren. Dabei habe ich mich zu 100% an folgende Anleitung gehalten: wiki/doku.php?id=userspace:wie_man_dies ... schreibung allerdings habe ich natürlich folgendes Template benutzt: wiki/doku.php?id=userspace:citrix_receiver Auch habe ich wieder das Template zu 100% übernommen. Nach dem Packen und veröffentlichen, versuche ich das Paket auf dem Client zu installieren. Ich erhalte an keiner Stelle auch nur die geringste Fehlermeldung. Auch das Windows-Log verzeichnet noch nicht mal ansatzweise etwas "rotes". Das Log aus Opsi schaut so aus:
Keine Fehler,- keine Warnungen,- nichts.
Die Dateien sind auch genau so ablegt wie es das Template und die Anleitung erwartet:
Während der Installation wird aber auch nichts im tmp-Verzeichnis von Windows angelegt. Die "Installation" selbst ist in maximal 3 Sekunden durch.
Ich bin am verzweifeln. Hat jemand einen Tipp für mich?
Danke und Gruß aus Hamburg
nachdem nun schon über einer Woche verzweifelt versuche den CitrixReceiver zu packen muss ich kapitulieren. Das Problem: Ich habe einen komplett neuen OPSI-Server aufgesetzt in aktuellster Version. Nach der Installation von Win10 64bit Pro wollte ich den CitrixReceiver in der Version 4.10.1 packen und installieren. Dabei habe ich mich zu 100% an folgende Anleitung gehalten: wiki/doku.php?id=userspace:wie_man_dies ... schreibung allerdings habe ich natürlich folgendes Template benutzt: wiki/doku.php?id=userspace:citrix_receiver Auch habe ich wieder das Template zu 100% übernommen. Nach dem Packen und veröffentlichen, versuche ich das Paket auf dem Client zu installieren. Ich erhalte an keiner Stelle auch nur die geringste Fehlermeldung. Auch das Windows-Log verzeichnet noch nicht mal ansatzweise etwas "rotes". Das Log aus Opsi schaut so aus:
Code: Alles auswählen
(0)
(1) [1] [Feb 07 22:44:46:720] --
(2) [1] [Feb 07 22:44:46:720] --
(3) [1] [Feb 07 22:44:46:720] c:\opsi.org\log\\opsi-script-part-Oh38Va07.log
(4) [1] [Feb 07 22:44:46:728] opsi-script 4.12.0.12 started at >>
(5) [1] [Feb 07 22:44:46:728] opsi-script log file with encoding utf8
(6) [1] [Feb 07 22:44:46:728] startmessage opsi-script created at CentralForm.FormCreate: 07.02.2018 22:44:43
(7) [1] [Feb 07 22:44:46:728] Loading skin from: C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-winst\winstskin
(8) [1] [Feb 07 22:44:46:728] Called with parameter: /opsiservice\r\nhttps://192.168.0.160:4447/rpc\r\n/clientid\r\n1.xyz.com\r\n/username\r\n1.xyz.com\r\n/password\r\n***(confidential)***\r\n
(9) [1] [Feb 07 22:44:46:760] Depot path from readconfig: p:\ 07.02.2018 22:44:43
(10) [1] [Feb 07 22:44:46:761] startmessage StartProgramModes and create log: 07.02.2018 22:44:43
(11) [1] [Feb 07 22:44:46:761] pm: 5 07.02.2018 22:44:43
(12) [1] [Feb 07 22:44:46:761] startmessage start opsi service connection: 07.02.2018 22:44:43
(13) [1] [Feb 07 22:44:46:761] startmessage: opsidata initialized: 07.02.2018 22:44:43
(14) [1] [Feb 07 22:44:46:761] 1.xyz.com
(15) [1] [Feb 07 22:44:46:761] got debug_lib: false
(16) [1] [Feb 07 22:44:46:761] got debug_prog: false
(17) [1] [Feb 07 22:44:46:761] got default_loglevel: 7
(18) [1] [Feb 07 22:44:46:761] got config: opsi-script.global.force_min_loglevel
(19) [1] [Feb 07 22:44:46:761] got force_min_loglevel: 0
(20) [1] [Feb 07 22:44:46:761] readConfigFromService: ok
(21) [1] [Feb 07 22:44:46:761] startmessage create log: 07.02.2018 22:44:46
(22) [1] [Feb 07 22:44:46:761] force_min_loglevel: 0
(23) [1] [Feb 07 22:44:46:761] default_loglevel: 7
(24) [1] [Feb 07 22:44:46:761] debug_prog: false
(25) [1] [Feb 07 22:44:46:761] debug_lib: false
(26) [7] [Feb 07 22:44:46:769] JSON service request https://192.168.0.160:4447/rpc getDepotId
(27) [7] [Feb 07 22:44:47:582] JSON service request https://192.168.0.160:4447/rpc getProductOrdering
(28) [7] [Feb 07 22:44:48:367] JSON service request https://192.168.0.160:4447/rpc productOnClient_getObjects
(29) [6] [Feb 07 22:44:48:681] Computername:1.xyz.com
(30) [6] [Feb 07 22:44:48:681] Computername according to Environment Variable :1
(31) [6] [Feb 07 22:44:48:681] opsi service URL https://192.168.0.160:4447
(32) [6] [Feb 07 22:44:48:681] Depot path: p:\
(33) [6] [Feb 07 22:44:48:681]
(34) [7] [Feb 07 22:44:48:692] bootmode from registry: BKSTD
(35) [6] [Feb 07 22:44:48:692] bootmode BKSTD
(36) [6] [Feb 07 22:44:48:692] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(37) [6] [Feb 07 22:44:48:692] Resolved sequence of products (07.02.2018 22:44:48):
(38) [6] [Feb 07 22:44:48:693] Product 3 citricreceiver : setup
(39) [6] [Feb 07 22:44:48:693] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(40) [7] [Feb 07 22:44:48:694] JSON service request https://192.168.0.160:4447/rpc getProduct_hash
(41) [7] [Feb 07 22:44:48:972] in TOpsi4Data.initProduct : citricreceiver
(42) [7] [Feb 07 22:44:48:973] JSON service request https://192.168.0.160:4447/rpc productOnClient_getObjects
(43) [6] [Feb 07 22:44:49:248] Actionrequest for product: citricreceiver is (original/actual): (setup / setup)
(44) [6] [Feb 07 22:44:49:361] [citricreceiver] Actionrequest for Product: citricreceiver is: setup
(45) [7] [Feb 07 22:44:49:361] [citricreceiver] JSON service request https://192.168.0.160:4447/rpc getProductProperties_hash
(46) [7] [Feb 07 22:44:49:716] [citricreceiver] JSON service request https://192.168.0.160:4447/rpc getProduct_hash
(47) [7] [Feb 07 22:44:49:989] [citricreceiver] in TOpsi4Data.initProduct : citricreceiver
(48) [7] [Feb 07 22:44:49:991] [citricreceiver] JSON service request https://192.168.0.160:4447/rpc productOnClient_getObjects
(49) [6] [Feb 07 22:44:50:264] [citricreceiver] scriptname: "setup.ins", special path: "p:\citricreceiver\"
(50) [7] [Feb 07 22:44:50:265] [citricreceiver] JSON service request https://192.168.0.160:4447/rpc productOnClient_updateObject
(51) [6] [Feb 07 22:44:50:620] [citricreceiver] Using old Depot path: p:\
(52) [1] [Feb 07 22:44:50:788] [citricreceiver]
(53) [1] [Feb 07 22:44:50:788] [citricreceiver] ============ Version 4.12.0.12 script "p:\citricreceiver\setup.ins"
(54) [1] [Feb 07 22:44:50:788] [citricreceiver] used script encoding: cp1252
(55) [1] [Feb 07 22:44:50:788] [citricreceiver] used system encoding: cp1252
(56) [1] [Feb 07 22:44:50:788] [citricreceiver] start: 2018-02-07 22:44:50
(57) [1] [Feb 07 22:44:50:788] [citricreceiver] installing product: citricreceiver_4.10.1-2.0
(58) [1] [Feb 07 22:44:50:788] [citricreceiver] on client named "1.xyz.com"
(59) [1] [Feb 07 22:44:50:790] [citricreceiver] loggedin user "Administrator"
(60) [1] [Feb 07 22:44:50:791] [citricreceiver] opsi-script running as "SYSTEM"
(61) [1] [Feb 07 22:44:50:791] [citricreceiver] opsi-script running with admin privileges
(62) [1] [Feb 07 22:44:50:791] [citricreceiver] opsi-script running in standard script mode
(63) [1] [Feb 07 22:44:50:791] [citricreceiver] executing: "C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-winst\winst32.exe"
(64) [1] [Feb 07 22:44:50:791] [citricreceiver] system infos:
(65) [1] [Feb 07 22:44:50:800] [citricreceiver] 00-50-56-93-75-1F - PC hardware address
(66) [1] [Feb 07 22:44:50:800] [citricreceiver] 1 - IP name
(67) [1] [Feb 07 22:44:50:800] [citricreceiver] 192.168.0.14 - IP address
(68) [1] [Feb 07 22:44:50:800] [citricreceiver] DEU - System default locale
(69) [7] [Feb 07 22:44:50:800] [citricreceiver] Registry started readonly
(70) [7] [Feb 07 22:44:50:801] [citricreceiver] Registry started without redirection (64 Bit)
(71) [6] [Feb 07 22:44:50:801] [citricreceiver] Registry key [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion] opened
(72) [6] [Feb 07 22:44:50:801] [citricreceiver] Key closed
(73) [1] [Feb 07 22:44:50:801] [citricreceiver] MS Windows 10.0 64 Bit, Release: 1709, Edition: PRODUCT_PROFESSIONAL
(74) [1] [Feb 07 22:44:50:801] [citricreceiver] opsi service version : 4
(75) [1] [Feb 07 22:44:50:801] [citricreceiver]
(76) [7] [Feb 07 22:44:50:802] [citricreceiver] Registry started readonly
(77) [7] [Feb 07 22:44:50:802] [citricreceiver] Registry started without redirection (64 Bit)
(78) [6] [Feb 07 22:44:50:803] [citricreceiver] Registry key [HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion] opened
(79) [6] [Feb 07 22:44:50:803] [citricreceiver] Key closed
(80) [1] [Feb 07 22:44:50:928] [citricreceiver] ___________________
(81) [1] [Feb 07 22:44:50:928] [citricreceiver] script finished: success
(82) [1] [Feb 07 22:44:50:928] [citricreceiver] 0 errors
(83) [1] [Feb 07 22:44:50:928] [citricreceiver] 0 warnings
(84) [1] [Feb 07 22:44:50:928] [citricreceiver]
(85) [1] [Feb 07 22:44:50:928] [citricreceiver] installed product: citricreceiver Version: 4.10.1-2.0
(86) [1] [Feb 07 22:44:50:929] [citricreceiver]
(87) [7] [Feb 07 22:44:50:929] [citricreceiver] JSON service request https://192.168.0.160:4447/rpc setProductActionRequest
(88) [1] [Feb 07 22:44:51:256] [citricreceiver] product citricreceiver set to update
(89) [1] [Feb 07 22:44:51:257] [citricreceiver] Update script name:
(90) [1] [Feb 07 22:44:51:257] [citricreceiver] we have no update script
(91) [7] [Feb 07 22:44:51:257] [citricreceiver] BuildPC: update switches .....
(92) [7] [Feb 07 22:44:51:258] [citricreceiver] JSON service request https://192.168.0.160:4447/rpc productOnClient_updateObject
(93) [7] [Feb 07 22:44:51:505] Registry started with redirection (32 Bit)
(94) [6] [Feb 07 22:44:51:505] Registry key [HKLM\SOFTWARE\opsi.org\winst] opened
(95) [6] [Feb 07 22:44:51:505] Variable "RebootRequested" is keeping its value "0"
(96) [6] [Feb 07 22:44:51:506] Variable "LastLogFilename" is keeping its value "c:\opsi.org\log\opsi-script.log"
(97) [6] [Feb 07 22:44:51:506] Variable "ContinueLogFile" is keeping its value "0"
(98) [6] [Feb 07 22:44:51:506] Variable "NumberOfErrors" is keeping its value "0"
(99) [6] [Feb 07 22:44:51:506] Key flushed
(100) [6] [Feb 07 22:44:51:506] Key closed
(101) [5] [Feb 07 22:44:51:516] -------- submitted part of log file ends here, see the rest of log file on client ----------
Die Dateien sind auch genau so ablegt wie es das Template und die Anleitung erwartet:
Während der Installation wird aber auch nichts im tmp-Verzeichnis von Windows angelegt. Die "Installation" selbst ist in maximal 3 Sekunden durch.
Ich bin am verzweifeln. Hat jemand einen Tipp für mich?
Danke und Gruß aus Hamburg