1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Office 2013 VL-based deploy stalls until timeout

Avatar
Aleksandr Auzers

I'm attempting to deploy Office 2013 Standard (volume licensed product) to Windows 7 workstations with Office 2010 on them already.  I've followed the Admin Arsenal knowledgebase instructions for OCT-based deployment of 2010, and watched the video for 2013, and even with (nearly) the exact same settings, my install stalls until timing out at the 1 hour mark.

PDQ Deploy successfully copies the installer files to the target PC, and with Task Manager I can see that "Microsoft Setup Bootstrapper" is running, but the amount of RAM it consumes stays about the same, and CPU usage is low, so it's like the setup program isn't doing anything.  Additionally, Office 2010, which is set in the MSP file to be removed, stays unchanged.

There are no spaces in the /adminfile parameter, nor do I forget to add .msp to the end of the filename.  I've also been careful to set the display level to none, with completion notice unchecked.  Suppress modal and no cancel are also checked:

The only setup property that's modified is AUTO_ACTIVATE (set to 1), and migration of user settings is disabled.

Here's the (only) deployment step I've configured and run:

What am I doing wrong?

0

Comments

1 comment
Date Votes
  • Avatar
    Bouma, Colby

    Does your deployment work on machines that DON'T have 2010? Are you trying to install 2013 alongside 2010, or replace it?

    I don't know if it matters, but these are the Setup properties that I use:


    0