Need assistance to deploy Office proplus.
I have download Office 2016 version of the Office Deployment Tool to a network shared (\\server01\office)
I have modified the configuration.xml file to include the source path
<Configuration>
<Add SourcePath="\\server01\off
<Product ID="O365ProPlusRetail" >
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
I then login to a workstation as domain user which has local admin right to the workstation and issue this command:
\\server01\office\setup.ex
I am getting a message about couldn't install. Not able to download a require file.
Am I missing any step here?
Also, is the download file(s) will be saved to the network shared or the workstation?
Please advise.
Thanks.
I have modified the configuration.xml file to include the source path
<Configuration>
<Add SourcePath="\\server01\off
<Product ID="O365ProPlusRetail" >
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
I then login to a workstation as domain user which has local admin right to the workstation and issue this command:
\\server01\office\setup.ex
I am getting a message about couldn't install. Not able to download a require file.
Am I missing any step here?
Also, is the download file(s) will be saved to the network shared or the workstation?
Please advise.
Thanks.
Mdlinnett
I believe you have to map a drive to the location. I don't think you can use the UNC (network share) path.
ASKER
I am using local path. Same issue.
screenshot2.png
screenshot2.png
What is the source path in the configuration.xml or deploy-office.xml file now? This should be a mapped drive, not a network share.
Also, one other thing I've noticed you didn't mention... Did you run 'setup.exe /download configuration.xml'?
The /download switch downloads the installation files, this needs to be ran once on the source Server before you can run 'setup.exe /configure configuration.xml'. When ran, the files are, I believe, downloaded to the directory containing the setup.exe.
As your clients will be pointing to a local source for the installation files, you will need (as it appears you have already done) separate configuration.xml files. One for the download and one for the configuration.
I have deployed Office 3 times using this method (I've just done the 3rd). The lack of clarity on office deployment really frustrated the hell out of me when I was trying to work it out.
This is my 'instructions' text file that I keep to hand :)
Download
CMD
cd c:\office16
setup.exe /download configuration.xml
Installation
CMD
cd c:\office16
setup.exe /configure configuration.xml
Also, one other thing I've noticed you didn't mention... Did you run 'setup.exe /download configuration.xml'?
The /download switch downloads the installation files, this needs to be ran once on the source Server before you can run 'setup.exe /configure configuration.xml'. When ran, the files are, I believe, downloaded to the directory containing the setup.exe.
As your clients will be pointing to a local source for the installation files, you will need (as it appears you have already done) separate configuration.xml files. One for the download and one for the configuration.
I have deployed Office 3 times using this method (I've just done the 3rd). The lack of clarity on office deployment really frustrated the hell out of me when I was trying to work it out.
This is my 'instructions' text file that I keep to hand :)
Download
CMD
cd c:\office16
setup.exe /download configuration.xml
Installation
CMD
cd c:\office16
setup.exe /configure configuration.xml
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.