Seite 1 von 1

WAN Client mshotfisx wird nicht installiert

Verfasst: 07 Jul 2026, 08:02
von jknill
Hallo
wir haben mehrere Homeoffice Arbeitsplätze die wir per WAN eingerichtet haben ( die Installation erfolgt über den OPSI cache Mode )
das funktioniert auch gut aber ich hab da ein paar WAN Clients welche die mshotfix immer mit Fehler beenden status failed:cached() failed

das ist dann das protokoll vom Server

[1] [2026-07-06 11:38:11.003] [] opsi-script 4.12.20.2 started at >> 06.07.2026 11:38:10
[1] [2026-07-06 11:38:11.003] [] opsi-script log file with encoding utf8
[1] [2026-07-06 11:38:11.003] [] ssl library path: C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-script\libssl-3.dll
[1] [2026-07-06 11:38:11.003] [] ssl library path: C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-script\libcrypto-3.dll
[1] [2026-07-06 11:38:11.004] [] Load library: C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-script\libcrypto-3.dll
[1] [2026-07-06 11:38:11.004] [] Load library: C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-script\libssl-3.dll
[1] [2026-07-06 11:38:11.004] [] OpenSSL version: OpenSSL 3.0.19 27 Jan 2026
[1] [2026-07-06 11:38:11.004] [] startmessage opsi-script created at CentralForm.FormCreate: 06.07.2026 11:38:10
[1] [2026-07-06 11:38:11.004] [] Detected Language is:de
[1] [2026-07-06 11:38:11.004] [] Loading skin from: C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-script\skin
[1] [2026-07-06 11:38:11.004] [] Called with parameter: /opsiservice\r\nhttps://127.0.0.1:4441\r\n/clientid\r\natlgasd0124.comp.ropetrans.int\r\n/username\r\natlgasd0124.comp.ropetrans.int\r\n/password\r\n***(confidential)***
[1] [2026-07-06 11:38:11.004] [] Depot path from readconfig: C:\opsi.org\cache\depot 06.07.2026 11:38:10
[1] [2026-07-06 11:38:11.004] [] startmessage StartProgramModes and create log: 06.07.2026 11:38:10
[1] [2026-07-06 11:38:11.004] [] Compiled with FPC 3.2.2 for Win32-i386 at 13:55:47 on 2026/05/07
[1] [2026-07-06 11:38:11.004] [] program mode: pmBuildPC_service
[1] [2026-07-06 11:38:11.004] [] startmessage start opsi service connection: 06.07.2026 11:38:10
[1] [2026-07-06 11:38:11.004] [] startmessage: opsidata initialized: 06.07.2026 11:38:10
[1] [2026-07-06 11:38:11.004] [] atlgasd0124.comp.ropetrans.int
[1] [2026-07-06 11:38:11.004] [] Starting Servicecall: backend_info
[1] [2026-07-06 11:38:11.004] [] Success Servicecall: backend_info
[1] [2026-07-06 11:38:11.004] [] Exception in readConfigFromService: Object reference is Nil 06.07.2026 11:38:10
[1] [2026-07-06 11:38:11.004] [] Could not read configs from service
[1] [2026-07-06 11:38:11.004] [] startmessage create log: 06.07.2026 11:38:10
[1] [2026-07-06 11:38:11.004] [] Cleanup old part files at 06.07.2026 11:38:10
[1] [2026-07-06 11:38:11.004] [] Backup old log files at 06.07.2026 11:38:10
[1] [2026-07-06 11:38:11.004] [] Initiate new log file at 06.07.2026 11:38:10
[1] [2026-07-06 11:38:11.004] [] force_min_loglevel: 4
[1] [2026-07-06 11:38:11.004] [] default_loglevel: 7
[1] [2026-07-06 11:38:11.004] [] debug_prog: false
[1] [2026-07-06 11:38:11.004] [] debug_lib: true
[1] [2026-07-06 11:38:11.099] [] Computername:atlgasd0124.comp.ropetrans.int
[1] [2026-07-06 11:38:11.099] [] Computername according to Environment Variable :ATLGASD0124
[1] [2026-07-06 11:38:11.099] [] opsi service URL https://127.0.0.1:4441
[1] [2026-07-06 11:38:11.134] [] default_loglevel reset to: 7
[1] [2026-07-06 11:38:11.376] [mshotfix]
[1] [2026-07-06 11:38:11.376] [mshotfix] ============ Version 4.12.20.2 script "C:\opsi.org\cache\depot\mshotfix\setup.opsiscript"
[1] [2026-07-06 11:38:11.376] [mshotfix] used script encoding: utf8
[1] [2026-07-06 11:38:11.376] [mshotfix] used system encoding: cp1252
[1] [2026-07-06 11:38:11.376] [mshotfix] start: 2026-07-06 11:38:11
[1] [2026-07-06 11:38:11.376] [mshotfix] installing product: mshotfix_202606-1
[1] [2026-07-06 11:38:11.376] [mshotfix] on client named "atlgasd0124.comp.ropetrans.int"
[1] [2026-07-06 11:38:11.376] [mshotfix] loggedin user ""
[1] [2026-07-06 11:38:11.376] [mshotfix] opsi-script running as "SYSTEM"
[1] [2026-07-06 11:38:11.376] [mshotfix] opsi-script running with admin privileges
[1] [2026-07-06 11:38:11.376] [mshotfix] opsi-script running in standard script mode
[1] [2026-07-06 11:38:11.376] [mshotfix] Scaling for screen DPI: 120
[1] [2026-07-06 11:38:11.376] [mshotfix] executing: "C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-script\opsi-script.exe"
[1] [2026-07-06 11:38:11.376] [mshotfix] system infos:
[1] [2026-07-06 11:38:11.377] [mshotfix] 04-F0-EE-ED-xx-xx - PC hardware address
[1] [2026-07-06 11:38:11.377] [mshotfix] atlgasd0124.comp.ropetrans.int - IP name
[1] [2026-07-06 11:38:11.377] [mshotfix] 192.168.xx.xx - IP address
[1] [2026-07-06 11:38:11.377] [mshotfix] DEU - System default locale
[1] [2026-07-06 11:38:11.377] [mshotfix] MS Windows 11.0 (10.0) 64 Bit, Release: 24H2, Edition: Enterprise Edition
[1] [2026-07-06 11:38:11.380] [mshotfix] opsi service version : 4 (4.3.53.10)
[1] [2026-07-06 11:38:11.380] [mshotfix]
[4] [2026-07-06 11:38:11.469] [mshotfix] Property not existing in GetProductProperty - using default
[4] [2026-07-06 11:38:11.480] [mshotfix] Got no property from service - using default
[1] [2026-07-06 11:38:31.801] [mshotfix] ___________________
[1] [2026-07-06 11:38:31.801] [mshotfix] script finished: success
[1] [2026-07-06 11:38:31.801] [mshotfix] 0 errors
[1] [2026-07-06 11:38:31.801] [mshotfix] 2 warnings
[1] [2026-07-06 11:38:31.801] [mshotfix] Exitcode will be: 0
[1] [2026-07-06 11:38:31.801] [mshotfix]
[1] [2026-07-06 11:38:31.801] [mshotfix] handled product: mshotfix Version: 202606-1
[1] [2026-07-06 11:38:31.802] [mshotfix]
[1] [2026-07-06 11:38:31.888] [mshotfix] product mshotfix set to update
[1] [2026-07-06 11:38:31.888] [mshotfix] Update script name:
[1] [2026-07-06 11:38:31.888] [mshotfix] we have no update script

wo soll ich da jetzt suchen?

( auf der platte des Client sind noch mehr als 100GB frei )

LG Jürgen

Re: WAN Client mshotfisx wird nicht installiert

Verfasst: 09 Jul 2026, 09:18
von ThomasT
Hallo Jürgen,

das Cachen wird vom opsiclientd gemacht und vermutlich wird sich im Log des opsiclientd auch ein Hinweis finden.
Ich würde das Caching mal triggern, z.B. über das Timer Event und dann im C:\opsi.org\log\opsiclientd.log mal nach Hinweisen suchen