I'm sorry if this has been answered.  I searched and couldn't find anything.

I'm attempting to set-up a rollout/upgrade to MS Office 2013 for about 400 clients running MS Office 2007.

Ideally my plan is to do this after hours.  I will:

- Use WOL to fire up clients

- Launch my managed installation (which has been tested and works fine when a user is logged in)

- Run a "force check-in" script.

The problem I'm running into is that the installation goes through all three attempts and times out if the client is on, but not logged on to the domain.  If I put my or anyone else's credentials in and force the check-in the installation goes fine.

What am I missing?

Thank you.

Answer Summary:
2 Comments   [ - ] Hide Comments


  • By default, Office creates a log in the %TEMP% folder. Have you looked in that?
  • Thank you, but there is nothing MS Office related in the temp folder. I checked both C:\temp and C:\
Please log in to comment

Community Chosen Answer


The workaround that we have is to loop a check for the explorer.exe in the process by another script before attempting to start the installation.
Answered 09/15/2014 by: dj_xest
Fifth Degree Black Belt

  • Thank you. Would it be possible to post an example of the script?
Please log in to comment
Answer this question or Comment on this question for clarity


I figured it out.  When I upgraded from 5.x to 6.0, I failed to check "Active Directory Single Sign On" in Control Panel > Security Settings.

I'm able to roll out MS Office 2013 without a user logged in after I had it rejoin the domain and enabled SSO.

My procedure is to wake up workstations using WOL, launch the managed installation, and finally run the "Force Check-in" script for 50 or less clients at a time.

Thanks to all...
Answered 09/19/2014 by: piobaireachd
Orange Senior Belt

Please log in to comment