You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In 2.11.1 build a normal EXE: NAME="executable.exe /S /user=all"
In 2.12.0 build a normal EXE: NAME="/S /user=all" => "executable.exe" is missing => deployment won't work
To Reproduce
Steps to reproduce the behavior:
Go to 'Deployment' => 'Build'
Click on 'Windows' => 'Install / Uninstall' => 'Execute an exe'
Create an EXE Install and see the info file....
Expected behavior
As of now, the whole deployment feature in 2.12.0 is not really functional (see also #1536). This must change as soon as possible!
The text was updated successfully, but these errors were encountered:
the error is in the adjustments in the file ~/ocsreports/require/teledeploy/PackageBuilder.php
fastest solution as workaround is to use the "old" file (PackageBuilder.php) from 2.11.1, then at least the deployment of Windows works clean again (EXE and CUSTOM EXE - #1536)
something between line 400 and 409 is wrong:
if ($xmlDetails->packagedefinition->ACT == 'LAUNCH' && $xmlDetails->formoption->ISCUSTOM == false) {
// if pkg built from linux bashscript option and not custom package,
// default retrieved if a command but w/ LAUNCH, the agent will be expecting a name
$name = substr($xmlDetails->packagedefinition->COMMAND, strpos($xmlDetails->packagedefinition->COMMAND, ' ') + 1);
$info .= "NAME=\"" . $name . "\" ";
} else if ($xmlDetails->packagedefinition->ACT == 'LAUNCH') {
$info .= "NAME=\"" . $xmlDetails->packagedefinition->COMMAND . "\" ";
}
OCS Inventory version
Version : 2.12.0
Describe the bug
In 2.11.1 build a normal EXE:
NAME="executable.exe /S /user=all"
In 2.12.0 build a normal EXE:
NAME="/S /user=all"
=> "executable.exe" is missing => deployment won't workTo Reproduce
Steps to reproduce the behavior:
Expected behavior
As of now, the whole deployment feature in 2.12.0 is not really functional (see also #1536). This must change as soon as possible!
The text was updated successfully, but these errors were encountered: