Seite 1 von 1

Microsoft Visual C++ Runtime 2008 and opsi-client-agent

Verfasst: 24 Jan 2017, 16:44
von SisterOfMercy
Look at this file:

\\opsi\opsi_depot\opsi-client-agent\files\opsi\setup.opsiscript

around line 398 we can find this:

Code: Alles auswählen

set $INST_vcredistx86_installed$ = "false"
if GetRegistryStringValue("[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{1F1C2DFC-2D24-3E06-BCB8-725134ADF989}] DisplayVersion") = "9.0.30729.4148"
	comment "vcredistx86 Version 9.0.30729.4148 is installed"
	set $INST_vcredistx86_installed$ = "true"
endif
if GetRegistryStringValue("[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{FF66E9F6-83E7-3A3E-AF14-8DE9A809A6A4}] DisplayVersion") = "9.0.21022"
	comment "vcredistx86 Version 9.0.21022 is installed"
	set $INST_vcredistx86_installed$ = "true"
endif
However, the current version of the C++ 2008 runtime is 9.0.30729.6161
Shouldn't this be updated, and preferably the package itself with the newer version?
Yes, I know you keep the old versions for compability, but is this advice also given when there are security issues with the runtime? Don't know if this is the case with this exact runtime, but anyway.

Re: Microsoft Visual C++ Runtime 2008 and opsi-client-agent

Verfasst: 25 Jan 2017, 10:16
von ueluekmen
Hi,

you need to have a vcredist in version 9.0 not sp1. This is because cpython for windows is compiled for that vcredist version. We had many problems in the past with updates or installation of vcredist versions. So we check, if the targets have a right version installed. Since windows 7 the vcredist versions are shipped directly with the os and will normally upgraded over the os. So we don't install vcredist in all situations.

We want to cleanup some parts of opsi in the next bigger version. For that reason, we will check all dependencies of the opsi-client-agent package too. We will check the vcredist in the next time, but we will not update it, if we have no good reason to do that. Because every failure at this point will impact the opsi infrastructure at the users side (not starting opsiclientd-service).

You can try to update your vcredist versions with a own opsi-package. You have to do that already, if you need more then one version of vcredist.