How to get around UAC when installing Office365 (2016) Click To Run via Kace

We currently run the original Office365 Click to Run. It was installed and is updated through a file share. We're now planning to upgrade to Office365 (2016 version) and I've gotten as far as getting the setup.exe /configure configuration.xml file to launch. However, no matter what I try, whether scripted or managed, it says it can't install due to the UAC. I have a batch file run that will disable UAC but that requires a reboot, which I'm trying to avoid. I have the install for Office in a batch file which calls the setup.exe and the .xml file. Has anyone run into this issue, and if so, how did you get around UAC?

1 Comment   [ + ] Show comment
  • Create a batch file and launch it with Powershell. This command will give elevated rights (same as run as admin) Powershell Start-Process powershell -verb runas <pathtofile>:\xxxx.bat - JLester710 6 years ago
    • Thanks for your reply. My batch file will run fine on its own after I allow the UAC. However, when I try to run it with your language above it still prompts for UAC access to run. If I click OK, my additional issue is that it tells me that it's going to upgrade to 2016 as well (since we are trying to just install over the top of 2013 Click to Run.

      I'm having my script copy the .bat file locally and then having Powershell call it from its local location.

      Batch file includes: @echo off

      cd "C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\129"
      setup.exe /configure <path to file>\configuration.xml - kabbas75 6 years ago

Answers (1)

Posted by: five. 6 years ago
Second Degree Green Belt
Do a scripted install and choose "Microsoft Windows" as your OS, this will open up the "Windows Run As" options. Then choose an administrator on the machine. If you choose a local admin, you will have to do the file share mapping in your batch file. That's how we do it. I suppose you could also create a credential for an admin that also has file share permissions and that might be easier for you, haven't tried that method before.

Our environment has UAC turned on and local users are not admins. This is how we have to do installs to get around UAC and administrator issues. Scripted installs for everything.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ