This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 57.99999999999999%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
I am having an issue when running a provisioning package made with configuration designer. Currently trying to have Office 365 installed during provisioning using ODT and a batch script. It takes 3.5-4 hours for the office installer to complete, however when I run that same batch script directly on the PC (Not during provisioning) it takes about 20-45 minutes to complete. I have tried batch/power shell, running the script from device and context commands but can't get office to install any faster. Any ideas on what could be causing the difference in install time?
It seems the problem is NOT a MCM related problem, it's more related to Windows Configuration Designer, I add the tag Windows so that the experts who are familiar with that topic may help.