plugins are only run in 32bit mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OCS Inventory: Windows Agent |
Fix Committed
|
Low
|
Didier Liroulet |
Bug Description
Hi,
I'm about to implement the msofficekey plugin
http://
It is unable to detect a 64bit Office 2010 on a 64bit Win7 because of the plugin is run in a 32bit environment.
proof:
on 64bit system, run from within a "normal" cmd.exe (which is 64bit)
cscript /nologo msofficekey.vbs
and the key for the office is seen.
Start a 32bit cmd.exe (from Windows\syswow64) and do the same call (which will have the affect, that virtualisation
comes into the game and the 32bit version of cscript will be run)
cscript /nologo msofficekey.vbs
and the 64bit office key is invisible.
So what to do?
Apparently the OCS agent should be enabled to run 64bit plugins, or at least to start the 64bit cscript.exe
A programming former colleague of mine had to implement a similar thing: call a 64bit cmd.exe
from within a 32bit programm.
He told me that there is a flag with which you can disable this 32bit Virtualisation.
so the code sequence must be
disable virtualisation
exec %windir%
enable virtualisation
if we would like to run a plugin in 64bit mode.
So I'd suggest to implement an additional directory for plugins that should be run in 64bit mode
(and are 64bit aware), which then only comes into the game on 64bit systems.
No, not so good: this 64bit plugin would not be called on 32bit systems.
delivering both plugins would then lead to running both on 64 bit systems, or the 32bit vbs plugin
would need code to detect if the current is a 64bit system and then do nothing ...
What if the vbs plugins would always be executed from a 64bit cscript.exe?
Anything speaking against this idea?
Best regards
Gerold
description: | updated |
Hi Gerold,
This is a huge enhancement, so, we will look for this in a future major release.
But there is also a workaround using VBscript.
Cheers