Office 2010 Deployment - This update package could not be opened
I am attempting to deploy Office 2010 from a network share with Desktop Central. I have had success in the past doing so, but it seems like lately any time I try, I get a failure.
Tried with the client's Windows firewall on and off, and there's no third party AV or firewall installed yet.
I have ensured the Admin$ share is enabled, file and print sharing is turned on, and so on. Both sets of fixes from these two files have been applied as well:
http://www.manageengine.com/products/desktop-central/enableFirewallSettings.txt
http://www.manageengine.com/products/desktop-central/WMIPortSetup.txt
When I push the installation package (EXE package from a network share, with correct/valid network share credentials provided - The account I am using has read/execute/list permissions to the directory, it just does not have write/delete permissions) I can see setup.exe execute on the client machine, it runs for 2-5 minutes, then it closes (I am doing a silent install via the Office Config Utility from Microsoft). I get an error on the Desktop Central console:
This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package.
It seems really odd, because setup.exe obviously begins executing on the client, but the installation never finishes. This has happened with every version of Office 2010 I've tried lately. Tried with Standard/Pro, VLK/VAR, x86/x64 and various combinations of these. Happens on Windows XP and Windows 7 platforms, both with latest Windows Updates/service packs. I can't find anything online explaining why this would be happening.
Additionally, if I execute the exact same command I'm using on Desktop Central from the client computer's command prompt, it works without any issues:
\\servername\SoftwareDistribution\Microsoft Office\Office 2010\Professional\VAR\x86\setup.exe /adminfile "Office 2010 - Professional - VAR - x86.MSP"
So it's clearly not the network share, admin file, executable, or any other part of the Office software. I would think it's Desktop Central not using proper credentials, but that's eliminated by the fact that setup.exe successfully executes on the client machine, and then fails during the installation. I'm completely at a loss for what is causing this, especially when running the command manually works every time.
I've also attached the client logs, I'm not sure which holds information about this. I deleted the logs prior to an attempt, and then pushed the package. The logs, hopefully, only contain information about this deployment failing.
Tried with the client's Windows firewall on and off, and there's no third party AV or firewall installed yet.
I have ensured the Admin$ share is enabled, file and print sharing is turned on, and so on. Both sets of fixes from these two files have been applied as well:
http://www.manageengine.com/products/desktop-central/enableFirewallSettings.txt
http://www.manageengine.com/products/desktop-central/WMIPortSetup.txt
When I push the installation package (EXE package from a network share, with correct/valid network share credentials provided - The account I am using has read/execute/list permissions to the directory, it just does not have write/delete permissions) I can see setup.exe execute on the client machine, it runs for 2-5 minutes, then it closes (I am doing a silent install via the Office Config Utility from Microsoft). I get an error on the Desktop Central console:
This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package.
It seems really odd, because setup.exe obviously begins executing on the client, but the installation never finishes. This has happened with every version of Office 2010 I've tried lately. Tried with Standard/Pro, VLK/VAR, x86/x64 and various combinations of these. Happens on Windows XP and Windows 7 platforms, both with latest Windows Updates/service packs. I can't find anything online explaining why this would be happening.
Additionally, if I execute the exact same command I'm using on Desktop Central from the client computer's command prompt, it works without any issues:
\\servername\SoftwareDistribution\Microsoft Office\Office 2010\Professional\VAR\x86\setup.exe /adminfile "Office 2010 - Professional - VAR - x86.MSP"
So it's clearly not the network share, admin file, executable, or any other part of the Office software. I would think it's Desktop Central not using proper credentials, but that's eliminated by the fact that setup.exe successfully executes on the client machine, and then fails during the installation. I'm completely at a loss for what is causing this, especially when running the command manually works every time.
I've also attached the client logs, I'm not sure which holds information about this. I deleted the logs prior to an attempt, and then pushed the package. The logs, hopefully, only contain information about this deployment failing.