I'm having trouble getting Office 2013 Pro Plus installs to work in SCCM 2012 SP1. I initially used the OCT to create a .MSP file which set a few things like Organization Name and SETUP_REBOOT = Never, etc, along with ticking the checkboxes to apply our MAK Volume License key, input the key, accept the License Agreement, and set the display level to none. I put this .msp into the Updates folder in the installation source and distributed the source to the server, creating a Package for the installer which runs the program "setup.exe" in the root of the installer folder.
(I basically followed the instructions in Ronni Pedersen's How-To at http://gallery.technet.microsoft.com/office/How-to-Deploying-Office-0f954e7f , but used a package rather than an application to deploy the software)
This first method apparently resulted in Office being installed on the client, but on first run of any app (Word), the user was still prompted to activate the software in the activation wizard and then presented with an annoying "welcome to office"-type interface. The deployment status on the SCCM side would actually report these installs as "Failed" because the "run time [was] exceeded".
I know that in this first case this was not a problem with our MAK key or anything like that, because as soon as I would click to "activate the software" in the window, activation would succeed without a problem and without me having to re-enter the key.
Because this didn't work (I want the activation to happen automatically and the welcome screen to go away), I switched to trying the custom config.xml method. I can provide a log file from this attempt if needed. In the config file I set the same values for Username, Company Name, PIDKEY and SETUP_REBOOT, uncommented those lines, and saved the file as config.xml in the proplus.ww folder of the install share. Looking at the installer log on the client machine after this install runs (I still ran it as a package with the program setup.exe /config [UNC path to the config file]), it says that the PIDKEY, CompanyName and Username elements are successfully parsed. This time, the install reports as successful in SCCM, but the result is the same: on first run the user gets the Activation Wizard and the Welcome to Office thingy.
Any ideas?
Sylvie Andrews