Push Installation
Why Push Installation
If your environment has mobile PCs that do not frequently log on to the domain, you can configure a local installation of Octoscan2 for metering information to be more accurate. When you use the Push Installation feature, Octoscan2 installs and updates itself locally on the machine at first scan or when the original Octoscan2.exe file gets modified on the network share.
Octoscan2 then configures itself to start whenever the user logs on to the system.
Push Install only makes sense together with Metering enabled and ImmediateMeteringOut set to false in most cases.
Push Installation may trigger alerts in your anti-virus software. Test carefully and configure the appropriate rules in your anti-virus software before using this feature.
In the Octoscan.config file specify:
PushLocal=true
Metering=true
ImmediateMeteringOutput=false
Try to avoid the PushLocal setting if it is not really needed. If you can differentiate between connected and mobile devices, enable PushLocal only on the mobile devices using conditional expressions.
PushLocal considerably complicates your setup. Do not set it to true before you have all connected devices scanning reliably for a week or so.
How Push Installation Works
The first time Octoscan2 is started with PushLocal set to true, it will copy itself locally to the machine into the user's AppData/Local/Octosoft/Octoscan2 folder.
This local copy will start at every user logon through the 'Run' registry setting. If the network is not available, the scanner will just write its metering information to the AppData/Local/Octopus folder.
If the network becomes available and Octoscan2 is started from the network share, it will stop the already running local instance of Octosan2, update its local copy if needed, and finally include the accumulated metering data into the freshly generated .scan file.