I had not upgraded my OCS-NG server and agent configuration for some time. Today I upgraded our server to 188.8.131.52. All seems to be working fine on that end.
Next step was to upgrade the 32bit 184.108.40.206 agent to the newest 220.127.116.11 version.
Q1) Which version should one select to upgrade existing 32-bit agent installations, 32- or 64-bit?
In any case, I went ahead and used OCS-packager 2.6 to create an ocspackage.exe package based on the 64-bit agent. I also used ocslogon.exe to install this file to an existing 18.104.22.168 32-bit installation.
To do so I executed:
ocslogon.exe /packager /gpo /server=https://teiresias.pieria.pkm.gov.gr/ocsinventory /deploy=22.214.171.124
... on a command line to simulate GPO-based deployment. It went well and the server is correctly receiving updates from the agent.
However, the new agent was installed in the existing directory, c:\program files (x86)\ocs... instead of c:\program files\ocs... Under the latter, a "plugins" subdirectory exists but nothing else.
Q2) Is this normal behaviour?
Q3) Will the 64-bit agent understand where it should download plugins deployed to it?
Q4) Finally, if I want to deploy say officepack to my systems, which path should be specified in the package deployment page, in order for the path to work for all systems? C:\Program Files (x86)\ocs... , c:\program files\ocs..., or some macro (%programfiles% / %programfiles(x86)% for example).
Thank you for any information provided.