The fact that you turned UAC off is why it worked, it means you didn't
have bumper guards on. The Symantec install should be smart enough to
ask for escalation when someone is running UAC, I would expect that much
out of such a large company who is allegedly dedicated to security.
Another way that likely would have worked would have been to open an
escalated command prompt and then fire the executable via command line
from there. I do that all of the time with UAC enabled and haven't seen
an issue with it for those apps that are older or from smaller
companies. Larger companies like Symantec I would beat mercilessly to
get them to fix their crap. There is little reason why something they
have released in the last 6-12 months shouldn't work with UAC.
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition www.joeware.net
---O'Reilly Active Directory Third Edition now available--- http://www.joeware.net/win/ad3e.htm
Hurricane Andrew wrote:
> That's odd. I was able to install 10.2 with "my" adminstrator account
> (i.e. not "administrator"). I installed on my work domain PC in managed
> mode, and it had no trouble installing or communicating with the parent
> server. I also installed unmanaged on a standalone PC unmanaged, and
> that went fine as well.
> Did you select the option to disable Windows Defender?
> One side note, I do have UAC turned off, so perhaps try turning that off
> temporarily and then installing? It's worth a shot.