I tried various attempts with msiexec /p CustomOCT.msp to add the remaining Office 2013 components, but encountered the Lync activation issue PLUS Lync running a repair on first launch, plus some inconsistent behaviour of sometimes seeing the first-run wizard (disabled in the MSP), or having to accept the license (accepted in the MSP). That was just last week to try to resolve some different issues, so pretty sure I have the latest and greatest there. I've updated to the latest OCT and imported my existing MSP. Other than that, my deployment would be perfect. Also the Lync icon in the task bar looks like the OneNote icon for that first launch. Then mere seconds after you click Close, it succeeds.Īfter that, it's fine for future launches of Lync. But it has one flaw if part of Office 2013 was previously installed: Lync starts up and says it failed to activate.This works perfectly for people who have no part of Office 2013 already.Now it's time to deploy the rest of Office 2013 and remove Office 2010.Lync installs, and just runs perfectly on first launch and every launch Deploying 32-bit Office 2013 just like we did with Office 2010.

SP1 is integrated into the Office 2013 source being used, and I used the OCT that comes with the SP1 DVD.Deployed Lync 2013 (as part of Office 2013 Pro Plus), along side Office 2010.I'll try to be brief as possible, but I've been through a lot of testing to get here.

Office 2013 pro plus activator