- This topic has 3 replies, 2 voices, and was last updated 6 years, 8 months ago by .
-
Posts
-
Hello All
I am working on scripting out a batch patch installation but i am getting hung up on the installer portion. Please see the scripting that i am running for the uninstalls and then the installs.
Office 2010 Uninstall – Working Fine
“C:Program Files (x86)Common FilesMicrosoft SharedOFFICE14Office Setup Controllersetup.exe” /uninstall ProPlus /config c:utilsOffice2010Removalconfig.xml
Office Pro Plus Bits
c:utilsodtsetup.exe /configure installOfficeProPlus32.xml
Here is my XML file for the installation
<Configuration>
<Add OfficeClientEdition=”32″>
<Product ID=”O365ProPlusRetail”>
<Language ID=”en-us” />
</Product>
</Add>
<AcceptEULA=”TRUE” />
<Property Name=”AUTOACTIVATE” Value=”1″ />
</Configuration>
Here is the step it keeps just sitting at
Sat-10:58:48> Remote Command: Executing \win10-office2016 -s c:utilsodtsetup.exe /configure installOfficeProPlus32.xml
If I go to a client and Run the same command it will prompt with UAC and then install will complete with no issue so I cannot figure out why it is not running and how to get around UAC.
Any help would be greatly appreciated
This might just need some quotes. Or it might need the -w to specify the working directory. If no -w then you might need to specify the full path to the .xml file instead of just the .xml file with no path. Or instead of manually pre-copying the files to the the target computer and then executing a ‘remote command’ you could instead just use a BP ‘deployment’ instead, in which case the entire thing would be handled for you by BP. See here: Deploying exe file fails but runs ok manually
You said “when I run it manually there is a UAC prompt.” Does “run it manually” mean as a BP deployment? Or Does that mean running it without BP just by executing the command at the prompt?
If you’re running it inside of BP, what makes you say that there is a UAC prompt? How do you know there is a UAC prompt? Where you do see this?
Generally speaking if you are running a deployment in BP, you will not ever experience a UAC prompt. If a deployment is hanging indefinitely, it’s generally because the parameter/switch used is not correct for a “silent” or “quiet” installation, and so the installer is popping up some type of prompt or window, but since it’s a remote deployment, that prompt/window cannot be seen and therefore cannot be clicked on to proceed with the installation.
Let’s go over a couple things…
1. Is the account that you are using to execute the deployment in the local admins group on the target computer?
2. Are you using alternate credentials in BP or are you launching BP with the same account that has local admin permissions on the target computer?
3. Is the account a domain account or is it a local account?
4. Can you confirm that you can successfully execute/complete BatchPatch ‘Actions > Windows Updates > Check for available updates’ on this target? Let’s make sure this works properly before trying a deployment. That way we can confirm that permissions are all what they need to be first.
5. In your deployment, can you confirm that your installofficeproplus32.xml file is in the same directory as the setup.exe on the BP computer? Can you also confirm that all of the other setup files that go along with the setup.exe are also in that same directory? If all of the files required for the installation are in the ODT folder, then when ‘copy entire directory’ is checked, they will all be copied to the target computer so that when the setup.exe is executed, it will be able to find all of the files that it needs, including the installofficeproplus32.xml file.
6. If everything is truly setup properly (this feels unlikely at the moment… it feels like there might be something simple that we’re missing) one thing to try is changing the remote execution context under ‘Tools > Settings > Remote’ to ‘Elevated token’.
-Doug
- You must be logged in to reply to this topic.