Office 2016 - You are opening the application "Microsoft AU Daemon" for the first time...

Hi all,

I'm pretty new to JAMF, so please excuse if i'm asking something which is too basic.

I like the idea NOT installing MAU, but how can I handle this?
Is it enough to just applying a script to the Office Installer or do i have to generate a complete new package with composer?

Thank you
Daniel

Sorry to revive this post. Was wondering if there's an easy way to get rid of this message at first ran?

I've used the following with pretty good results. It registers the autoupdate app with Launch Services and suppresses those messages. The key is to do it to both the app and the binary.

if [ -e "/Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate.app" ] then /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -R -f -trusted "/Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate.app"
fi

if [ -e "/Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate.app/Contents/MacOS/Microsoft AU Daemon.app" ] then /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -R -f -trusted "/Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate.app/Contents/MacOS/Microsoft AU Daemon.app"
fi

I use a much more down-n-dirty approach.
I strategically break the MAU by removing the daemon that automatically launches it.

rm /Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate.app/Contents/MacOS/Microsoft AU Daemon.app/Contents/MacOS/Microsoft AU Daemon

It doesn't prevent it from working in the event you have admin users that want to leverage it, but it will not announce itself at first run.

Hi all,

I have prepared new image with AutoDMG,
I'm already fixed issue with "You are opening the application ..."
But have another issue,
Update checking only if you manually put Help/Check_For_Updates in any MS app, (checked this install older version MS Office),
Have you any idea?

Update)
Already find solution,
Need add key "StartDaemonOnAppLaunch" to User/your_username/Library/Preferences/com.microsoft.autoupdate2.plist

</dict> <key>HowToCheck</key> <string>Automatic</string> <key>SendAllTelemetryEnabled</key> <true/> <key>StartDaemonOnAppLaunch</key> <true/>

Searching best way to populate it to all users (and new)

Thanks in advance,

sorry, completely brand new here. First post... Please help me out, it's just me and my mac on our network, and i have partitioned my drive to use one with parallels, and one with office for mac. The office for mac side keeps giving me this prompt randomly 3/4 times i open a microsoft app. I've stopped using the parallels partition, and need to remove, or absorb it, but I was just assuming that was the cause for these prompts. Like it was trying to open the app from the other partition at times...

Long story a bit shorter, I lived with it until stumbling upon jamf and this thread. So I tried AdamH 's solution above from last March. I can post the terminal feed but after running his "rm" order I was asked ? and put y, then the "rm" command was "permission denied"

If anybody is listening, let me know. Thanks!

NewbIam

check here the detail article
https://applenerds.com/2017/11/20/office-2016-mac-suddenly-opening-microsoft-au-daemon-app-fix/

@tomRGA How did you deploy that script? I tried writing a simple bash script with what you wrote, but I keep getting errors in jamf "unexpected exit" etc..

I have a script run via a policy at login and check in set for once per user per computer.

You must capture the current logged in user though and run the commands as them otherwise it will try to execute them as root which won't help the current user.

Where exactly are you getting the errors?