Access 365 run time deployment best practices

%3CLINGO-SUB%20id%3D%22lingo-sub-3010823%22%20slang%3D%22en-US%22%3EAccess%20365%20run%20time%20deployment%20best%20practices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3010823%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20an%20application%20that%20works%20with%20Excel%20and%20Access%20files%20via%20Access%20Database%20Engine%20(ACE).%20We%20need%20to%20provide%20a%20possibility%20to%20install%20the%20application%20at%20machines%20having%20no%20connection%20to%20Web%20(usual%20case%20for%20Windows%20Servers).%20We%20embedded%26nbsp%3B%20into%20the%20setup%20package%20of%20our%20application%20an%20ACE%20Redistributable%20(2010%2C%202016).%20We%20want%20to%20embed%20now%20Access%20365%20redistributable%20but%20get%20folder%20of%20size%202.8%20GB%20(our%20application%20setup%20has%20size%20of%20200%20MB).%20We%20are%20a%20bit%20shocked%20with%20the%20size.%20We%20used%20Office%20Deployment%20Tool%20and%20the%20following%20configuration%20for%20download%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E%3CCONFIGURATION%20id%3D%22ea1d01e6-1db1-4294-a72b-0af4360617e5%22%3E%0A%20%20%3CADD%20officeclientedition%3D%2264%22%20channel%3D%22SemiAnnual%22%3E%0A%20%20%20%20%3CPRODUCT%20id%3D%22AccessRuntimeRetail%22%3E%0A%20%20%20%20%20%20%3CLANGUAGE%20id%3D%22en-us%22%3E%3C%2FLANGUAGE%3E%0A%20%20%20%20%3C%2FPRODUCT%3E%0A%20%20%3C%2FADD%3E%0A%20%20%3CUPDATES%20enabled%3D%22TRUE%22%3E%3C%2FUPDATES%3E%0A%20%20%3CREMOVEMSI%3E%3C%2FREMOVEMSI%3E%0A%3C%2FCONFIGURATION%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3EWe%20used%26nbsp%3BOfficeCustomizationTool%26nbsp%3B%20in%20Microsoft%20365%20Apps%20admin%20center%20to%20generate%20the%20configuration.%3C%2FP%3E%3CP%3EDo%20we%20make%20some%20error%3F%20Or%26nbsp%3BAccess%20365%20runtime%20is%20really%20so%20huge%3F%3C%2FP%3E%3CP%3EWe%20have%20observed%20that%20if%20we%20install%20Access%20365%20runtime%20via%20Online%20installer%20available%20here%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Foffice%2Fdownload-and-install-microsoft-365-access-runtime-185c5a32-8ba9-491e-ac76-91cbe3ea09c9%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Foffice%2Fdownload-and-install-microsoft-365-access-runtime-185c5a32-8ba9-491e-ac76-91cbe3ea09c9%3C%2FA%3E%3C%2FP%3E%3CP%3Ethen%20the%20download%20takes%20much%20less%20time.%20So%2C%20it%20probably%20downloads%20much%20less%20data.%20But%20we%20cannot%20use%20Onliner%20installer%20as%20described%20above.%20From%20the%20other%20side%20we%20don't%20want%20to%20redistribute%20the%203%20GB%20heavy%20package.%20Please%2C%20help%20with%20your%20ideas%2Fadvices.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%20Alexander.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3013335%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20365%20run%20time%20deployment%20best%20practices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3013335%22%20slang%3D%22en-US%22%3EThe%20answer%20to%20both%20your%20questions%20(Do%20we%20make%20some%20error%3F%20Or%20Access%20365%20runtime%20is%20really%20so%20huge%3F)%20is%20'No'%20both%20times.%20Your%20XML%20is%20legit%20and%20the%20Access%20Runtime%20should%20be%20in%20the%20ballpark%20of%20less%20than%20200%20MB.%20But%2C%20here%20is%20the%20catch%3A%20All%20products%20M365Apps-related%20products%20use%20a%20unified%20installation%20source.%20So%20ODT%20pulls%20down%20this%20unified%20installation%20source%20which%20contains%20products%20like%20M365Apps%2C%20Visio%2C%20Project%20and%20the%20Access%20Runtime%20and%20is%20roughly%203GB%20in%20size.%20When%20running%20an%20installation%20(setp%20%2Fconfigure)%20the%20setup%20engine%20only%20pulls%20the%20data%20it%20needs%20to%20install%20the%20specified%20product%2C%20that's%20why%20the%20Access%20Runtime%20Online%20Install%20is%20much%20faster%20as%20it%20only%20pulls%20down%20what%20it%20needs.%20Even%20during%20an%20offline%20install%20it%20pulls%20only%20the%20data%20out%20of%20the%20source%20files%20it%20requires%20and%20not%20all%20of%20the%203GB.%20But%20this%20does%20not%20apply%20to%20the%20download%2C%20it%20always%20downloads%20the%20whole%20unified%20installation%20source.%20That's%20why%20you%20have%20the%203GB%20on%20disk.%20I'm%20not%20aware%20of%20any%20way%20to%20circumvent%20this%20behavior%20other%20than%20allowing%20online%20installs.%3C%2FLINGO-BODY%3E
Visitor

We have an application that works with Excel and Access files via Access Database Engine (ACE). We need to provide a possibility to install the application at machines having no connection to Web (usual case for Windows Servers). We embedded  into the setup package of our application an ACE Redistributable (2010, 2016). We want to embed now Access 365 redistributable but get folder of size 2.8 GB (our application setup has size of 200 MB). We are a bit shocked with the size. We used Office Deployment Tool and the following configuration for download:

<Configuration ID="ea1d01e6-1db1-4294-a72b-0af4360617e5">
  <Add OfficeClientEdition="64" Channel="SemiAnnual">
    <Product ID="AccessRuntimeRetail">
      <Language ID="en-us" />
    </Product>
  </Add>
  <Updates Enabled="TRUE" />
  <RemoveMSI />
</Configuration>

We used OfficeCustomizationTool  in Microsoft 365 Apps admin center to generate the configuration.

Do we make some error? Or Access 365 runtime is really so huge?

We have observed that if we install Access 365 runtime via Online installer available here https://support.microsoft.com/en-us/office/download-and-install-microsoft-365-access-runtime-185c5a3...

then the download takes much less time. So, it probably downloads much less data. But we cannot use Onliner installer as described above. From the other side we don't want to redistribute the 3 GB heavy package. Please, help with your ideas/advices.

 

Regards, Alexander.

2 Replies

The answer to both your questions (Do we make some error? Or Access 365 runtime is really so huge?) is 'No'. Your XML is legit, and the Access Runtime should be in the ballpark of less than 200 MB. But, here is the catch: All products M365Apps-related products use a unified installation source. So ODT pulls down this unified installation source which contains all products like M365Apps, Visio, Project and the Access Runtime and is roughly 3GB in size. When running an installation (setup /configure) the setup engine only pulls the data it needs to install the specified product. That's why the Access Runtime Online Install is much faster as, it only pulls down what it needs. But with the /download switch, it always downloads the whole unified installation source. That's why you have the 3GB on disk. I'm not aware of any way to circumvent this behavior other than allowing online installs.

Hello Martin!

Thank you very much for your prompt advice. We will follow the idea to propose online install during setup of our product. Additionally we will provide instructions for offline install that should be performed by hand.

Regards, Alexander.