ODT (Office Deployment Tool) exe but be aware there's still a failure with latest one even MS updates it - look my post here an you'll find a working setup.exe. Latest can be downloaded from here and still not working.when making the configuration.xml from OCT , what should i put in the source path for local source?
Thanks!
Updated to latest OFFICE and still not working default from current folder.The SourcePath setting is optional, and not needed if you're following this guide's steps.
For downloading, it specifies a source folder if you have a local network share which keeps pre-downloaded files around, or where to find the files when installing. When undefined, ODT looks in the current folder path.
tosetup /configure configuration.xml
and run as administrator instead of dubble clicking the setup file, which worked earlier.@echo off
cd /d "%~dp0"
setup /configure configuration.xml
How can this be implemented? I have two before-logon steps in Post-Setup to handle installing Office.The problem with cleanup is knowing when the Office Setup process is actually finished, because it immediately backgrounds itself and isn't a blocking process. When it doesn't block, your wrapper script needs extra logic to watch for Setup to exit.
Are you able to share the cleanup BAT file please?Confirmed that shifting the cleanup command to after-logon got rid of the installation folder entirely.
It's just a command that I moved to the after-logon stage of Post-Setup.Are you able to share the cleanup BAT file please?
/c rmdir /S /Q "C:\office"
If you're not customizing the list of specific Office apps, this offline folder averages 3.1 GB. This gets worse when you consider the disk space temporarily involved during SFX setup:
- 1st instance when Post-Setup copies SFX file to local $$ or $1 folder- 2nd instance when it's self-extracted- 3rd instance when Office gets installed
Why not save time, and run setup.exe directly off the DVD/USB drive?
1. Exclude any unwanted Office apps from your config, before running setup.exe /download.
XML:<Configuration> <Add OfficeClientEdition="64"> <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> <ExcludeApp ID="Access" /> <ExcludeApp ID="Lync" /> <ExcludeApp ID="Publisher" /> </Product> </Add> <Updates Enabled="TRUE" /> <Display Level="None" AcceptEULA="TRUE" /> </Configuration>
2. Copy the entire folder (including setup.exe & the XML) to the mounted ISO's directory under new folder \Office365_Deploy.
3. Copy/paste this script as RunOfficeSetup.bat and run from Post-Setup (with no parameters).
Code:@echo off for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do ( if exist "%%i:\Office365_Deploy" ( set DRIVE=%%i goto :EXIT ) ) :EXIT cd /d %DRIVE%:\Office365_Deploy && .\setup.exe /configure configuration-Office365-x64.xml
View attachment 7781
What I do is to wait until you've created the USB install drive, then manually create a folder and copy the Office install files yourself.I use the bat file from garlin and I just add it to the ISO in Post Setup before logon machine right after the line where it should copy the contents of the Office offline folder to the %systemroot%\Office365_Deploy folder.
I have a bunch of other apps it installs but for some reason it gets stuck on a cmd window "Administrator: Post-Setup tasks", where I can see it installed Edge/Teams/... but then the cursor just stays blinking for a very long time.
If I use my xml and setup.exe when I log in for the first time, it installs just fine.
Any idea on how to troubleshoot this? Cause it used to work :-(
Maybe I'm confused on your second step in your guide, how to add the Office folder to the ISO? You just do that via NTLite itself right? Or do you copy the Office365_Deploy contents to the root of the iso manually?