Unhandled mismatch when OcsLogon.exe launcher looks for the installed OCS Agent through Active Directory GPO

If it is used a deployment strategy based on Active Directory GPO, using startup script with the launcher OcsLogon.exe, and the parameter /DEPLOY=a.b.c.d is not configured, the launcher returns versión 0.0.0.0 if no agent was found installed. This causes that the installer does nothing, and in its effects, the agent is not deployed, but de launcher ends correctly, as it is shown in OcsLogon.log:

********************************************************
Starting OCS Inventory NG Logon Installer 2.1.0.1 on 18/11/2013 at 14:06:03
Checking if not already running...OK
Parsing command line arguments...OK
Searching OCS Inventory NG Agent installed version...OK (0.0.0.0)
OCS Inventory NG Agent version 0.0.0.0 already installed, skipping setup. << ERROR!
Windows does not automatically start OCS Inventory NG Service, so starting Agent <C:\WINDOWS\TEMP\ocs-ng\Ocsinventory.exe>...OK (exit code is 18)
All done, exiting ;-)

The launcher must returns that no version is installed.