Author: Jeremy_MSFT
Originally published to the Office 365 Preview blog.

Office 365 ProPlus uses Click-to-Run installation technology which changes many aspects from installation to customization and software updating. It also means that there are entirely new processes to monitor and troubleshoot if you are the administrator installing Office for your end users, if they are having installation issues when self-installing, or if you need to contact Microsoft for any questions. As someone who has been troubleshooting Windows and application installations for many years, my immediate response to someone with a hard-to-answer question is, “Can you send me the logs?”

The normal Office 365 ProPlus logs are stored in the %temp% directory in Windows and I covered the controls of how to change the logging path and file name in a previous blog in this series. This is how you define those parameters in the configuration XML used with setup:

<Configuration>

<Add SourcePath="\\YourServer\YourShareName\Office Deployment Tool\"

OfficeClientEdition="32" >

    <Product ID="O365ProPlusRetail">

      <Language ID="en-us" />

    </Product>

</Add>

<Updates Enabled="FALSE" />

<Display Level="None" AcceptEULA="TRUE" />

<Logging Name="OfficeSetup.txt" Path="%temp%" />

</Configuration>

Of course, if you need to determine what is really going on with a repeated failed install, you’ll want to both run an install with Sysinternals Process Monitor filtered to look at the integratedoffice.exe process…

 

Sysinternals Process Monitor capturing Click-to-Run installation processes with integratedoffice.exe

Or you can enable verbose logging on your test system by writing a registry key and DWORD value prior to the installation:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClickToRun\OverRide

DWORD “LogLevel”

Value Data “3”

 

You can also use a scripted REG command to write the value with something based on this command:

REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClickToRun\OverRide " /v LogLevel /d 3 /t REG_DWORD /f

The primary log you will want to look at is the integratedoffice.exe_streamserver(..).log. It contains most of the information about the Click-to-Run installation and will enable you to see to any failed processes prior to the installer exiting. I prefer to use the Configuration Manager Trace Log Tool (cmtrace.exe) from System Center Configuration Manager 2012 to actively view logs and highlight failures easily, but you can also use other tools or notepad. Note that installation logs are stored by default in the %temp% directory.

 

 

Cmtrace.exe displaying intergratedoffice.exe_streamserver(…).log

Now armed with these logs plus ProcMon outputs you can peer into the internals of how Click-to-Run setup works and more importantly if anything fails, you can see what it was. On a reassuring note, we have seen a bit higher success rates on the Click-to-Run installations versus the MSI-based packages, so you won’t be using these tools and approaches too often. And now if someone asks you for the logs from a failed Click-to-Run install you’ll be ready to provide the more detailed ones.

 

Jeremy Chapman

@deployjeremy

Office Deployment Team