Systems Management Question
MS Office 2013 managed installation not completing when user not logged in
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?