Current project is to push Sophos Connect and a connection profile by GPO. The context in which SCCLI is run matters, but is not documented. What I found:
If run it as SYSTEM (via Computer Policy) to import a .PRO file via SCCLI, it appears to work. The profile is created, and connections can be made. However, the connection does not persist across Windows sessions or for other users. My thought was that the profile could be imported once, since it's not user-specific, and saved at the computer level, then be applied to all users, which would then download their individual configurations to be saved to the user profile.
But, empirically, it must be run in user context. That needs to be documented.
Heheh, I keep returning to this project in fits and starts, and every time, I bump up against something else.
There's no mention that the utility is case-sensitive.
SCCLI add -f d:\path\filename.pro works.
SCCLI ADD -f d:\path\filename.pro does not.
Of course, the parameters should NOT be case-sensitive. But that's another matter.
Really, guys. Using screenshots of the online help text is easy, but inadequate. Users get the same info by using the --help switch, so what's the point?
But that said, case-sensitivity of the commands SHOULD also be in the online help text. That is, until it's fixed so it's no longer case-sensitive.
If SCCLI supports all the file types that the GUI does, that ALL needs to be documented, too. This is from the Import dialog box in the GUI, v2.2.90.1104.
Which raises another question. *.INI files? Is THAT documented somewhere?
And why there's a file filter for pictures & HTML is beyond me. Surely you can't import a JPG of a connection? But if you can, please make sure that's documented, too!
