- Some disk space to download Office 365 and to prepare the package ( 3 GB should be enough)
- A target machine where to try the software deployment
- The Office 2013 Deployment Tool for Click-to-Run
- Some time to make your tests :-)
- Download the Office 2013 Deployment Tool for Click-to-Run and run it: it will ask you a directory where to place the extracted files (less than 1MB)
- Create an empty local directory to store the installation sources of Office 365 ( c:\TempOffice in this example )
- Amend the configuration.xml provided by default to point to that directory. Your configuration should look like the following one:
<Configuration>
<Add SourcePath="c:\TempOffice" OfficeClientEdition="32" >
<Product ID="O365ProPlusRetail">
<Language ID="nl-nl" />
</Product>
</Add>
</Configuration>
4. Now from the command line issue the command setup.exe /download configuration.xml and wait until the download is complete (~1 GB)
5. Browse to the target directory ( c:\TempOffice in this example ) and move all the content in the directory where you have the setup.exe and configuration.xml files
At this point you need a batch that will kick in the installation. The batch needs t create a temporary directory, copy all the files and folders of the current directory there and launch the setup.exe this time with the /configure option.
This step is required because the SourcePath parameter is not able to handle relative paths (e.g.: ..\myfiles OR .\) but only absolute paths (e.g.: c:\tempOffice\)
Do not worry! I wrote the script for you:
@ECHO OFF
REM Script written by Marco S. Zuppone for DELL.
REM Try it before to use in production !!
IF NOT EXIST "C:\TempOffice" (MKDIR "C:\TempOffice") ELSE (DEL "C:\TempOffice\*.*" /F /S /Q)
XCOPY /E *.* "C:\TempOffice"
PUSHD %cd%
CD "C:\TempOffice"
setup.exe /configure configuration.xml
POPD
RMDIR /S /Q "c:\Tempoffice"
At the end your directory with all the content should look like this:
6. Copy the folder on a test machine, open the DOS command line, change to that directory and run the batch (I called it, in my example installOffice.bat)
Verify that the installation is correct and all is fine. Force the inventory of the test machine after the installation has been successfully performed.
7. Select all the files in the folder (Office subfolder and all the content) and create a ZIP file of the content.
8.Look for the Inventory of the test machine, open it and look for the Office 365 in the Installed Programs section.
9. Click on the Office 365 record and associate to it the ZIP file that you created at the point 7
10. Create now the Managed Installation under the Deployments menu: the only focal point here is to use Override Default and put in the Parameters field the name of the batch that will perform the installation.
Job Done. I'd suggest, as usal, to test the managed distribution against one or more test clients before to go in production.
You can create a configuration.xml file with the script current directory like this :
ECHO ^<Configuration^> > "%~dp0configuration.xml"
ECHO ^<Add SourcePath="%~dp0" OfficeClientEdition="32" ^> >> "%~dp0configuration.xml"
ECHO ^<Product ID="O365ProPlusRetail"^> >> "%~dp0configuration.xml"
ECHO ^<Language ID="fr-fr" /^> >> "%~dp0configuration.xml"
ECHO ^</Product^> >> "%~dp0configuration.xml"
ECHO ^</Add^> >> "%~dp0configuration.xml"
ECHO ^</Configuration^> >> "%~dp0configuration.xml"
The ^ are escape character for < and >
With that, you don't have to copy all files and folders to a temporary directory. - gwir 8 years ago
So you associate the 32 bit edition to Office 365 and the 64 edition to Office 365 x64.
Kind regards,
MArco - StockTrader - StockTrader 8 years ago
Anyone know of a good verify step you could do? i was thinking maybe on the directories
"test" - brucegoose03 7 years ago