I was able to resolve my issue.
Looks like building a custom .msp with the OCT is not sufficient to do a truly-silent install.
I had to build a config.xml file, and set the silent install options in there as well as in the .msp in order to make the install run completely silent.
config.xml 280 bytes
That may / may not work if you are building a package to install Office 2013. I have been tasked with installing Office 2013 on 219 machines within our Education environment. One configuration for Teachers that includes Outlook and a similar version for students that excludes Outlook. The first step in the process is to use OCT and build two different versions of MSP files. Copy those to your distribution area on your core server. Then use a Managed Script to deploy the software.
Here is a copy of my script configured for our environment please omit or delete the items that do not apply to you. Additionally I did not have to use a config.xml file
FILE=http://<Your Core Server>/packages/OFC2013/<your MSP file Here>.MSP
REMEXEC0=attrib.exe -r /s
REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /p="http://<Your Core Server>/packages/OFC2013/<your MSP file Here>.MSP" /dest="c:\install\MSO2013\updates\<Your MSP file here>.MSP" /lan=90 /wan=60
Using this method I was able to deploy office 2013 Pro Plus w/SP1 without any logged in users.
Hope this helps to anyone who is having this or a similar problem!
Has anybody seen this Failed error message installing Office 2013 Standard. "Unknown status code (0x756B,0:30059) Return code 30059?
I'm not sure what is causing my Office 2013 package to fail.