Opened 4 years ago
Closed 12 months ago
#1271 closed Bug / Defect (fixed)
Fail to install OpenVPN silent on Windows 7
| Reported by: | ulfper | Owned by: | Samuli Seppänen |
|---|---|---|---|
| Priority: | major | Milestone: | release 2.5.4 |
| Component: | Generic / unclassified | Version: | OpenVPN 2.4.7 (Community Ed) |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | Installation certificates silent |
| Cc: | tct, stipa |
Description
We try to install OpenVPN 2.4.7 silent, but the TAP driver installation pop up a confirmation dialogue (trust OpenVPN Inc). We have tried to pre-load certificates to avoid this confirmation dialogue without luck. Which certificates should be pre-loaded and to which "section" in the "certificate store"?
Or is there another way to install OpenVPN silent?
Change History (8)
comment:1 Changed 4 years ago by
| Cc: | tct added |
|---|---|
| Owner: | set to tct |
| Status: | new → assigned |
comment:2 Changed 4 years ago by
| Owner: | tct deleted |
|---|
comment:3 Changed 3 years ago by
| Owner: | set to Samuli Seppänen |
|---|
comment:4 Changed 3 years ago by
| Cc: | stipa added |
|---|---|
| Milestone: | release 2.4.7 → release 2.5.3 |
comment:5 Changed 2 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | assigned → closed |
I say we just close this. It looks like a local problem - if it was not, many people would have commented in here. Plus this is 2.4.7 (soon EOL) and Windows 7 (already EOL).
If you disagree please reopen.
comment:6 Changed 2 years ago by
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
I think we should at least test if 2.5 / .msi supports proper silent mode, including installation of all drivers contained. This is important for proper software maintenance with automatic rollout and updates.
comment:7 Changed 2 years ago by
| Milestone: | release 2.5.3 → release 2.5.4 |
|---|
comment:8 Changed 12 months ago by
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Since we do fully automated testing of the MSI installer now, we definitely have fixed this
Is this something that the .msi installer does better for 2.5?
If not, we maybe should try to fix this for 2.5.3
Fixing for 2.4.x is unlikely, as we're a bit short on manpower to invest into NSIS installers.