We have not heard of anyone having an issue with the Local Agent Installer on Sever 2012. As an option you could try the Remote Agent Installer to install the agent to the Server 2012 file box.
I branched this off to its own discussion so that in case others are experiencing it they can find it more easily
We haven't been able to reproduce this in the lab since you reported it, so we're not quite sure what's going on. Our best guess is a different configuration or policy (AV even) than we're testing against.
Did the 6.0 installer work without any trouble on the same system? Do you have the same problem with the 6.0.1 installer on other systems?
Remote installer as Joel suggested might be a workaround, but I'm curious to see if others are running into this or if it's some kind of fluke, too.
Definitely feels flukey to me.
I did the remote workaround - no problems.
I tried the 6.0.1 installer on a 2008 R2 box this morning - no problems.
So far as I can tell, I could only make it fail on one 2012 box.
The 6.0 installer worked on that same box without issue.
It's a puzzler, but if no one else has seen it, then I'll bet a dollar it's something to do with that particular box.
Thanks for the help!
I've run into this today. Out of 10 agent (6.1) installs, 3 of them failed with the "Installer User Interface Mode Not Supported".
According to google, the error has to do with the installer not able to recognize the version of OS.
Running the installer in “windows 7 compatibility mode” solved it.
1 of 1 people found this helpful
Little late response..
I had same problems with Agent v6.1.0 on Windows 2012.
Resolution: compatibility mode
"Run this program in compatibility mode for Windows 7" solved my problem.