forum.opsi.org

Well, I'm sorry to say it, but I see a couple of errors in the provided script. - productid has spaces and capitals - delete -sf doesn't end with a backslash - if you have delsub.opsiscript the update script will run the uninstall If it still does not work after fixing these errors, then try the win...

One of the tools you can use is SysTracer. There must be others out there.

I use 7zip, innounp, lessmsi and msix to extract various installers.
I also use insted to look into msi files.

if (CompareDotSeparatedNumbers($INST_MsVersion$, "=", "10.0")) DosInAnIcon_join_domain_win10_wmic WINST /SysNative else DosInAnIcon_join_domain_wmic WINST /SysNative endif [DosInAnIcon_join_domain_wmic] ; Join domain "%SystemRoot%\system32\wbem\wmic.exe" /interactive:o...

You have exitcode -2147217361. Convert this to hex, and you get this code: FFFFFFFF8004102F
0x8004102F is thus the error code that works better on a search machine:

WBEM_E_INVALID_METHOD_PARAMETERS
2147749935 (0x8004102F)
Parameters provided for the method are not valid.

This is on RHEL or CentOS?

Any chance of more details from the logs? /var/log/opsi/opsiconfd/opsiconfd.log for instance.

Have you already tried opsi-setup --set-rights?

My installscript manually copies files. [Actions] requiredWinstVersion >= "4.11.5.14" DefVar $LogDir$ DefVar $ProductId$ DefVar $MinimumSpace$ DefVar $InstallDir32$ DefVar $ExitCode$ DefVar $INST_SystemType$ DefVar $INST_MsVersion$ DefStringList $ProductInfo$ DefVar $DisplayVersion$ DefVar...

I have the exact issue with a self-compiled iPXE. FreeBSD with bhyve as VM host. Bhyve does not support legacy booting windows, uefi only. Bhyve currently does not support network booting, so my workaround is to start iPXE, just like stuff like ReFind does. My elilo.conf has been changed slightly, s...

Hat jemand hier einen besseren Weg? If the boot image is available seperately, why not put that iso file on a USB stick, and boot of off that? Of course you need to fill in all information, but perhaps you can change some configuration file, so it's only hostname. Or perhaps see if you can boot to ...

I have this for our office 2016 package. It seems to have worked, otherwise I think I would have seen a lot more errors about trying to install a 64-bit office together with a 32-bit office. [ProductDependency] action: setup requiredProduct: microsoft-office-2007 requiredStatus: not_installed requir...