In answer to the last question regarding Project and Visio. Microsoft allow you to exclude Visio and Project from the RemoveMSI option of the config xml file. ( docs.microsoft.com/en-us/deployoffice/configuration-options-for-the-office-2016-deployment-tool ) However, make sure that your version of Office 365 is the same architecture as your pre-installed Project and Visio, otherwise this will cause you an issue.
Hey there! Based on Microsoft's documentation (blogs.technet.microsoft.com/odsupport/2015/09/23/office-365-proplus-2016-couldnt-install-error-30029-1007-0-when-trying-to-install-using-the-office-deployment-tool-odt/), this generally occurs when you have a relative path in your SourcePath. If this isn't the case, I'd reach out to our support team at support@pdq.com on this issue for further troubleshooting. If you do, please export a copy of your package to XML and attach that, as well as your O365 configuration XML, to your email for them to take a look at. Thanks!
I followed these instructions and pushed this to my test computer and after 2 minutes and 18 seconds it returned the following: Command script returned error code - 1073740791
I would recommend checking out this KB article; community.pdq.com/posts/691-office-2016-click-to-run-deployment-returns-error--1073740791-despite-install-being-successful I hope this helps.
It does indeed run from a share only. Well, you could copy over the files first and then run locally, but that's a lot of overhead. The particular error you are is receiving (translates to 0xC0000005 in hex) usually indicates some type of access violation and is thrown by Windows or the Office installer. So, it could be AV software preventing the install, incorrect user credentials (unlikely, as the connection to the target machine would have thrown an error initially), different versions of Office (trying to install x86 where x64 Office exists). The error is pretty ambiguous, but there could be more information in the Event Viewer logs on the target where the installation failed, typically in System or in the Application logs. In this case, I would also see if you can replicate the issue on more than one computer. It might be something specific to that machine (e.g. needs a reboot) or something impacting multiple machines.
In answer to the last question regarding Project and Visio. Microsoft allow you to exclude Visio and Project from the RemoveMSI option of the config xml file. ( docs.microsoft.com/en-us/deployoffice/configuration-options-for-the-office-2016-deployment-tool ) However, make sure that your version of Office 365 is the same architecture as your pre-installed Project and Visio, otherwise this will cause you an issue.
got an error code 1603
What happens when you follow the steps, exactly as shown, but you get the "Couldn't install" Error Code 30029-1007
I am running an Enterprise PDQ license and trying to setup a deployment of O365.
Hey there!
Based on Microsoft's documentation (blogs.technet.microsoft.com/odsupport/2015/09/23/office-365-proplus-2016-couldnt-install-error-30029-1007-0-when-trying-to-install-using-the-office-deployment-tool-odt/), this generally occurs when you have a relative path in your SourcePath.
If this isn't the case, I'd reach out to our support team at support@pdq.com on this issue for further troubleshooting.
If you do, please export a copy of your package to XML and attach that, as well as your O365 configuration XML, to your email for them to take a look at.
Thanks!
I followed these instructions and pushed this to my test computer and after 2 minutes and 18 seconds it returned the following: Command script returned error code - 1073740791
I would recommend checking out this KB article; community.pdq.com/posts/691-office-2016-click-to-run-deployment-returns-error--1073740791-despite-install-being-successful I hope this helps.
Does it run from a share only?
and what is return code: -1073741819?
It does indeed run from a share only. Well, you could copy over the files first and then run locally, but that's a lot of overhead. The particular error you are is receiving (translates to 0xC0000005 in hex) usually indicates some type of access violation and is thrown by Windows or the Office installer. So, it could be AV software preventing the install, incorrect user credentials (unlikely, as the connection to the target machine would have thrown an error initially), different versions of Office (trying to install x86 where x64 Office exists). The error is pretty ambiguous, but there could be more information in the Event Viewer logs on the target where the installation failed, typically in System or in the Application logs. In this case, I would also see if you can replicate the issue on more than one computer. It might be something specific to that machine (e.g. needs a reboot) or something impacting multiple machines.
can we please see a office 2019 deploy video?
We should have one within the next few weeks.
Has this been completed?