How to package an MS Fix It file to be deployed via SCCM2012 and run passively?

I'm not used to SCCM 2012, but from that log I note it says it's executing it "with user context".  Unless your users are administrators, it will need to run with administrative rights.

Having said that, the log does show that the package appears to be returning exit code 0 (success).  What error do you see occur on the client?  Anything in its Application Event Log?

Thanks for responding!  Logged on users in test environment are admins, fully decremented UAC, I attached the logs for when I try to just run the msi via command line using "msiexec /a microsoftfixit".  What is odd to me is when I run msiexec /I from a command line, it runs, just requires me to answer the prompts and elevate the uninstall.  Using that same exact syntax as the program within SCCM I get the failure:
"This advertised application will not be installed because it might be unsafe.  Contact your administrator to change the installation user interface option of the package to basic."

As this is my second day wrestling with SCCM, I assume I am missing something basic, but any guidance would be appreciated.
MSI-Install-Fail-Application-Log.txt

I don't know the SCCM 2012 interface, but in SCCM 2007 we always tick the box to allow it to interact with the desktop, always select to download and run locally (but hidden), run with admin rights and I usually wrap a batch file round it.  In your case I'd be simply doing this:
start /wait msiexec /i MicrosoftFixIt.msi /quiet /norestart
Make sure that your source folder has the MSI unblocked before you package it up - ie right-click it and select Unblock on the properties sheet, as by default its coming from the Internet Zone will make it appear dangerous.

Sorry for this next question, and thanks for the last response: how would you suggest wrapping a batch file around it?  I have been providing the commands I can think of in the programs field when building the application: specifically variations of /administrative with the /passive option, though /qf and /qb have not been working either. Curious how I would be able to tell msiexec where the msi would be located?

Would it be the creation of a batch file (new to me) that would run the install and I would point to as the program for the install?

Other msi based application installs, chrome enterprise for instance, work as expected.

Thanks!  I appreciate the white gloving without condescension.

Tried this and the behavior is the same; it codes as a successful install but the fixit does not run and does not uninstall Office 2007 as intended.  Giving up on this approach, going with  a program that points at the the uninstall.xml from the  source media.  Problem has been the incredible lengths it can take to uninstall: limiting it to run for a half hour and then it will be up to my Service Desk to assist.

Thanks again!

Sean

Very generous of you to award points when I've not solved your problem!

We schedule Office 2010 installs out of hours since they take so long; it doesn't surprise me that the uninstall is just as slow.
In my experience, if the run time of a package is exceeded (e.g. whilst waiting for a user who locked the workstation to respond to a prompt when they next log in - e.g. to close an app so it can be upgraded), an error is returned and logged on the SCCM server but the package does continue to run (providing it is still alive)!

You earned it via providing foundational information which I will build on as I learn and a sanity check in a polite manner.