Hi all,
In our Windows-based environment I'm responsible for deploying the latest official Spark release (2.7.0.671) to a large number of desktops. These desktops are currently using the last official Spark 2.6.3.12555 release. As with the last Spark release, I've opted to use our startup script (applied by Group Policy) to silently install Spark 2.7.0 when the machines boot up.
So, within the startup script, I'm launching the Spark 2.7.0 installer like this:
> spark_2_7_0.exe -q
And it's not installing. I can see that it tries to install, however it doesn't do it - instead it hangs for a period of time and just fails silently. Meanwhile in the windows Event Logs, I see an entry that something tried to write to the registry but failed because it lacked permission (no info is given on exactly what it was, though).
Meanwhile if a logged on user with admin privileges runs the same install command as above, all works well.
After troubleshooting this quite a bit, I've run across what I think may be the cause of the problem: the "installer manifest" in the spark_2_7_0.exe installer is not set to ask for or require administrative privileges in Windows. As evidence, if you take a look at the old Spark 2.6.3 installer and compare it with the latest 2.7.0 installer, you'll see that the Spark 2.6.3 installer has the "administrator shield" on the icon, while the 2.7.0 installer does not. I'll also add that I'm able to successfully install Spark 2.6.3 via the startup script without issue.
So, is there any hope that the 2.7.0 installer can be recompiled so that it requires administrative privileges like the old 2.6.3 installer? FYI, I found this link on the install4j site that explains how: Elevation Of Privileges. I'm open to any other ideas as well, but this seems to be the simplest resolution to our problem.
Thanks!