Office365 Package and Silent Install

brinnington said:
HI francis11,

I have done as you suggested and searched for setup.exe 16.0.17830.20162 from august 12 without success.

If you have it, please upload it so that I may download it.

Thank you.
Click to expand...
Official MS download url in first post here
 
HI francis11,

Thank you very much. setup.exe 16.0.17830.20162 did the trick. It was able to install Office LTSC 2024 just fine.

I also discovered another solution to the problem I was having trying to install Office LTSC 2024.

I had been getting this error message: "Couldn't install. We couldn't find the specified configuration file. Check the file path and file name." Error Code: 0-2048(0)

This had meant that I was unable to install Office LTSC 2024.

I was getting that error message when using the latest version of setup.exe from ODT. This was because I was not using an elevated command prompt when running this command: setup /configure configuration.xml

Once I used an elevated command prompt, that error message disappeared and I was able to install Office LTSC 2024.
 
It's a shame that the ODT is not as complete as the installation options present in the MSI installer of an Office 2016 for example
Certainly, the MSI installers are for the VL versions, and not Retail if I remember correctly
 
This can be useful to check your download choices before adding to NTLite:

Office Tool Plus -snip1.png
Office Tool Plus -snip2.png
Office Tool Plus -snip3.png
Office Tool Plus -snip4.png
Office Tool Plus -snip5.png
Office Tool Plus -snip6.png
 

Attachments

  • Office Tool Plus -snip6.png
    Office Tool Plus -snip6.png
    121.7 KB
Office Tool Plus looks like a similar implementation of MS's Office Customization Tool, but as a standalone app.

This app does require you to install .NET 8 Runtime. Making it more of tool for experts who are doing Office setup all the time, and less for casual or one-time users. But useful if you need finer control over the deployment settings.
 
when making the configuration.xml from OCT , what should i put in the source path for local source?
Thanks!
 
avi said:
when making the configuration.xml from OCT , what should i put in the source path for local source?
Thanks!
Click to expand...
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.
 
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.
 
garlin said:
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.
Click to expand...
Updated to latest OFFICE and still not working default from current folder.
 
After some testing find out how to solve the errorcode "0-2048-0" when try install Office with the latest updated ODT.
After updating to latest ODT of march 7. and unpacked the setup file into install folder i changed the cmd code for setup from
setup /configure configuration.xml
Click to expand...
to
@echo off
cd /d "%~dp0"
setup /configure configuration.xml
Click to expand...
and run as administrator instead of dubble clicking the setup file, which worked earlier.
And it's working. Finally.
 
Last edited:
Just tested both SFX and Setup methods and they work. May be useful to recommend a cleanup command to get rid of the install files.
 
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.
 
garlin said:
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.
Click to expand...
How can this be implemented? I have two before-logon steps in Post-Setup to handle installing Office.
  1. The BAT file you recommended for use
  2. [ /c rmdir /S /Q "C:\office" ] command right afterwards
Upon reaching the desktop I confirmed that Office was indeed installed and that the "office" folder exists on the root of the drive, but is empty.
Is it possible to add a /wait command to your script?

Or should I shift the cleanup commands to after-logon?

Edit: Cleanup and clarification
 
Last edited:
Confirmed that shifting the cleanup command to after-logon got rid of the installation folder entirely.
 
You must log in or register to reply here.
Back
Top