Closed jrcmilanez closed 4 years ago
Same problem with a computer win 7 64bit and office 2013. No detection but ok for office 2007
Hi, guys...I have fresh install Ubuntu 18.04.2 + OCSNG 2.6RC and a lot of plugins. Everythiong seems to work, but Office plugin (last version, branch: rework) is not showing me Office 365. Office 2010 works fine.
Office 365
Office 2013
MySQL ocs tables
I have everything in last versions...
VBS script
'---------------------------------------------------------- ' Plugin for OCS Inventory NG 2.x ' Script : Retrieve Microsoft Office informations ' Version : 2.24 ' Date : 14/06/2017 ' Author : Creative Commons BY-NC-SA 3.0 ' Author : Nicolas DEROUET (nicolas.derouet[gmail]com) ' Contributor : Stéphane PAUTREL (acb78.com) '---------------------------------------------------------- ' OS checked [X] on 32b 64b (Professionnal edition) ' Windows XP [X] ' Windows Vista [X] [X] ' Windows 7 [X] [X] ' Windows 8.1 [X] [X] ' Windows 10 [X] [X] ' Windows 2k8R2 [X] ' Windows 2k12R2 [X] ' Windows 2k16 [X] ' --------------------------------------------------------- ' NOTE : No checked on Windows 8 ' Included : Office 2016 and 365 versions
How can I fix it?
Hi guys, may i ask you to try my patched version here : https://github.com/PluginsOCSInventory-NG/officepack/blob/5fe18ee62fcc388117ea930a6a2f08e00377039e/agent/msofficekey.vbs
There is a PR rotting for months, it doesn't seems it will be merged soon, but if people say it resolves their issues maybe it will https://github.com/PluginsOCSInventory-NG/officepack/pull/41
Maybe it is problem with different architecture between OS and OFFICE? Windows x64 X Office x86?
MACHINE 1 - OS Windows 10 x64 + Office 2013 x86 (wrong patch to OSPP.vbs) Issue still there....I have VBS script from you, but the script maybe incorrectly detect path to OSPP.VBS
Output from VBS script
Output.txt
My version is Office 2013 and If I run OSPP.VBS with correct path...
It works on machine with Office 2013 installed only if I edit VBS script (delete Office 2016 version)
Dim aOffID(4,1) aOffID(0,0) = "XP" aOffID(0,1) = "10.0" aOffID(1,0) = "2003" aOffID(1,1) = "11.0" aOffID(2,0) = "2007" aOffID(2,1) = "12.0" aOffID(3,0) = "2010" aOffID(3,1) = "14.0" aOffID(4,0) = "2013" aOffID(4,1) = "15.0"
MACHINE 2 - OS Windows 10 x64 + Office 365 x64 (correct path to OSPP.vbs) If I have Office 365 installed, everything works fine (even if it is trial version), so I have output.txt with all data, last VBS script, but still - no information in OCSNG server for the machine (pictures below)
Data from OCSNG from this machine with Office 365 trial (not activated)
And list of plugins (all works corretly I think - I have data in OCSNG)
MACHINE 2 (the same machine as above) - OS Windows 10 x64 + Office 365 x86 (correct patch to OSPP.vbs)
MACHINE 2 debug OCSNG (see row with officepack)
_
Starting OCS Inventory NG Agent on Friday, March 29, 2019 09:33:48.
AGENT => Running OCS Inventory NG Agent Version 2.4.0.0
AGENT => Using OCS Inventory NG FrameWork Version 2.4.0.0
AGENT => Loading plug-in(s)
DLL PLUGIN => Searching for Plug-in DLL(s) in folder <C:\Program Files (x86)\OCS Inventory Agent\plugins>
DLL PLUGIN => 0 DLL Plug-in(s) successfully loaded on 0 DLL(s) found
AGENT => Using network connection with Communication Server
COM PROVIDER => Loading Communication Provider <C:\Program Files (x86)\OCS Inventory Agent\ComHTTP.dll>
AGENT => Using Communication Provider
How to continue?
Hi @bajlek :
I did a little patch on my modified script to rely on SKU ID to write output to XML. I was previously only relying on PRODUCT ID but after some checks (hopefully i have some 2013 licences at my company !), there is no PRODUCT ID on the Office 2013 OSPP.VBS output... so it could not work.
It would have work in certain cases (both 2013 and 365 or 2016 installed, or the presence of a more recent OSPP file).
To explains how it works, the script try to execute the OSPP.vbs in every path it should be present, at each execution, it will output an output.txt file even if there is no OSPP.vbs present (because path does not exists), that's why you're having an output.txt with an invalid path. Each time it generate an output.txt, it tries to read this file and get office informations from it, if it's the case it's outputting to the xml, and then it continues to next version.
So if you have an office 2013, it will try the Office15 directory at some points, output to ouput.txt and output to xml then continue to next version, Office16 path, which is maybe invalid, output to output.txt, no xml (because there was no OSPP.vbs on that path) and then stop because it's the last version to check.
This last output.txt is "Invalid path (this is the one from Office16), that does not mean it didn't find any good informations before. And it will remains in your user directory.
The only thing to rely on to check if it's working is : "Do you have an XML output when i run the script manually". If this is the case, the plugin works, if not, i need to do some more debug !
So please, try the new one i've put above and tell me if there is any case you don't have XML output to the screen. If it's working here, you may have another inconsistency elsewhere (Database, server, etc.)
@gehasia
In fact, your Office 2013 search did not work in your previous script. Now I downloaded the script with your last fixes (from the link above) and it works perfectly - Office 2013 is detected again.
Thanks a lot for your work in correct operation and improvement of the plugin! I do not understand why your corrections are not included in the official version, it's a shame.
I must admit, that all is fully functional now, but it is strange because I dont update all computers by GPO, only testing one, and now...suddenly all computers and office versions being detected. But as my father says..if it functional, don't touch it
@gehasia I have noticed another problem in your latest script that was not before. Office 2010 is detected as Office 14 and only the last part of the key is displayed (second entry), and yet it is possible to draw the entire key for Office 2010 from the Windows registry (the first entry).
Hi,
A new release is available for officepack. The detection has been fixed.
Best regards, Charlene Auger
No detection of Office 2016 and Office 2019. OS is Windows 10 Pro. Offices are 64 bit version.