Office 365 Pro Plus silent install "At bootup" and "Anytime" both have issues. How do you go about deploying Office 365?

I'm a bit confused about how this works. I have an Office 365 Pro Plus Managed Installation I need to push out to the whole office and I would like to install it "at bootup". I was under the impression that the splash screen would show upon boot and stay up until the installation has finished. Unfortunately, the splash screen shows up for about 2 seconds then disappears, immediately allowing the user to sign in. The installation then completes with the user logged in, IF they don't screw it up during the process.

There are three reasons I want to be able to complete the installation before the user is allowed to log in.

One, because I can't seem to do a truly silent installation when running it with the user logged in. A black console window pops up with the path to setup.exe in the title bar. It's blank, but if the user closes it, it cancels the install. Two, because if they sign in and immediately open Outlook like most of them do, the install will fail. Three, because I want to be able to tell the users to reboot their computers whenever they're ready to update, instead of trying to schedule down time with them.

Any help on this would be awesome. I feel like this should be so simple. Running the setup command locally in a folder containing the Office installation files does a truly silent install but with KACE it doesn't seem to be able to. Ideally I just want to install after a reboot and before the user logs in. 


1 Comment   [ + ] Show comment
  • If I run it as a script it is silent. You schedule the script to run early and use a smart label for machines with out Office 365 and uncheck the "Run on next connection if offline". Could also do the notice before run to tell people to close office apps and take lunch or something. - danflynn 4 years ago

Answers (1)

Posted by: chucksteel 5 years ago
Red Belt
We scheduled our Office install to run without a user logged in and limited the deployment hours to be outside of the regular business day. We then temporarily change our standard sleep settings to make sure computers will be powered on during the evening and will update their inventory. We can also force an inventory towards the end of the day to make sure computers check in and install the upgrade.

  • I wish I could do something like that but unfortunately all of our devices are laptops that are off network at home with the users every night, so doing a nighttime rollout isn't doable for us. If the K1000 can reach the laptop, the user is likely signed in and active, so I really need a way to have the user initiate the install, but lock the machine until it's done. Like Windows Update does when it reboots to install updates. Thanks for the idea though! I appreciate it. - danielelias90 5 years ago
    • Would publishing the managed install in the user portal work? If you don't use self-service, then that would be a problem.

      Are using the notifications letting the user know that the install is about to happen not enough? Include that there will be a black box appearing and not to close the window. - chucksteel 5 years ago
      • That is likely going to be what I have to do, just rely on the message and hope they read it thoroughly. It's not like a whole lot can go wrong, but you'd be surprised at how difficult it is to get people to pay attention to that where I work. Unfortunately we don't use the user portal at the moment, so I think user education on that would be too much all at once. - danielelias90 5 years ago
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