JLospinoso
commented
5 years ago Hi @raforg, thanks for submitting! Looking for some help to work through these issues. Thanks!
Open raforg opened 5 years ago
JLospinoso
commented
5 years ago Hi @raforg, thanks for submitting! Looking for some help to work through these issues. Thanks!
Hi,
I recently tried to install Beamgun on all the PCs at work. There was a mixture of Windows 7, 8.1 and 10. It was a little while ago and my memory probably can't be trusted but here goes. This should probably be several issues but I think the final point subsumes most of the earlier ones.
(1) I wasn't able to install it on any of the Windows 7 or 8.1 PCs. Or I could install it and it seemed OK initially but it didn't start again automatically when the user next logged in.
(2) Some installs and uninstalls failed with a message like:
"There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personel or package vendor."
But of course there was no mention of which program failed nor any error message from the program that failed so that's probably not too helpful.
(3) An error message that was consistently reported by Beamgun itself:
"Unable to connect to update server. Version string portion was too short or too long."
(4) I think that one of the reasons that Beamgun failed to install was because it seems to install only for the user who is logged in installing it. It doesn't start automatically for any other user. Trying to subsquently install it for the other users on the same PC fails (with the message above in point 2). The fact that it appears in the Programs Control Panel indicates that it is installed into the system but it only applies to a single user. That's a problem for PCs with multiple users. No doubt, there's a way to manually get it to start automatically for all users but it would be better if it happened as part of the installation.
(5) Wishlist: I would really prefer it if Beamgun could be installed by the system administrator and be started automatically for all users. Ideally, it should be a service owned by a system user (with access to the desktop) so that normal users (who don't have administrator rights here) would not be able to stop the process even if they (or an adversary) wanted to. This would also mean that it wouldn't need password protection as suggested in another issue. It would probably also mean that protection against devices that claim to be USB network adapters would work no matter who was logged in at the time.
P.S. Thanks heaps for Beamgun. I thought I'd have to write it myself (but I'm really not a Windows programmer).