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.

PDQ Deploy not installing O365 C2R

Avatar
Jason Leidy

We'd like to use PDQ Deploy to install O365 C2R (2016). We use it to deploy O365 C2R 2013. We want to install from a local source, like we do for 2013. However, it doesn't like something about my config.xml. I have used the MS tool for creating it. I think the issue is my local source? I have downloaded the source files to our share using the ODT. I've attached my config.xml. The "Data" folder which is created when you download the binaries using the ODT is inside of the Office365_2016_Business_C2R folder.

The PDQ Deploy job has a command step that looks like this: "\server\share\Office365_2016_Business_C2R\setup.exe" /configure "\server\share\Office365_2016_Business_C2R\2016config.xml"

<Configuration> <Add OfficeClientEdition="32" Channel="Monthly" SourcePath="\\server\share\Office365_2016_Business_C2R" AllowCdnFallback="TRUE" ForceUpgrade="TRUE"> <Product ID="O365BusinessRetail"> <Language ID="en-us" /> <ExcludeApp ID="Groove" /> <ExcludeApp ID="OneNote" /> <ExcludeApp ID="OneDrive" /> <ExcludeApp ID="Publisher" /> <ExcludeApp ID="Access" /> </Product> </Add> <Property Name="SharedComputerLicensing" Value="0" /> <Property Name="PinIconsToTaskbar" Value="FALSE" /> <Property Name="SCLCacheOverride" Value="0" /> <Updates Enabled="FALSE" /> <Display Level="None" AcceptEULA="TRUE" /> <Logging Level="Standard" Path="%temp%" /> </Configuration>

0

Comments

1 comment
Date Votes
  • Avatar
    victor.heijmerikx

    In my experience the config.xml does not like a network path. I solved it with a multiple step deployment:

    On the PDQ server, I only have setup.exe and configuration.xml. I create one Office install job for every building, since it is 2 GB of data to be copied.

    Step 1 is a file copy step which copies the setup.exe and config file to C:\temp\Office_2016_x64.

    Step 2 is a robocopy step copying from the closest building network location: ROBOCOPY\\server.domain.local\Office_2016_x64\ C:\Temp\Office_2016_x64\ . /S /E /DCOPY:D /COPY:DT /NP /XX /XO /XN /XC /R:0 /W:0

    Step 3 then locally starts the install routine: c:\Temp\Office_2016_x64\setup /Configure c:\Temp\Office_2016_x64\configuration.xml . Note that I have to include the complete path for the xml, even though I start the exe in the same folder.

    Step 4 is a minute of sleep

    Step 5 removes the C:\temp\Office folder and Bob's your uncle.

    Every job has a name with the unique building in it so we can distinguish between them.

    0