Jump to content

CUSTOMIZED UN-INSTALLATION OF OFFICE APPS USING OFFICE DEPLOYMENT TOOL (ODT)


The AchieVer

Recommended Posts

1 hour ago, Akaneharuka said:

@DR_ADHAM If I want to install Office 365 ProPlus which HTML code should I use ?

 

Only replace 

<Product ID="ProPlus2019Retail">

 

with:

<Product ID="O365ProPlusRetail">

Of course if you mean office 365 proplus retail

apEv6TK.png

Link to comment
Share on other sites


  • Replies 88
  • Views 9.1k
  • Created
  • Last Reply

For O365 , just use the Product ID O365ProPlusRetail  in the config file

Link to comment
Share on other sites


2 minutes ago, Akaneharuka said:

 

@DR_ADHAM Can you sent that set up html files to me please :)

 

Thanks in advance

 

Akane.

 

Could you please show me the .img file you're intending to install ?

So it would be easier to guide you in the right path.

Link to comment
Share on other sites


@Akaneharuka

PM sent

 

You didn't add the source path in your config file as I described.

As a consequence, the program tried to download the files online but as I see you disabled your network connection.

To install offline, you've to use the config file I provided here:

 

Link to comment
Share on other sites


@Akaneharuka

 

I was just wondering, Is your issue with regards to the installation of O365 been resolved?🙂

Link to comment
Share on other sites


On ‎12‎/‎1‎/‎2018 at 2:28 PM, DR_ADHAM said:

<Configuration> <Add SourcePath="F:\" OfficeClientEdition="64" Channel="Monthly" ForceUpgrade="TRUE"> <Product ID="ProPlus2019Retail"> <Language ID="en-us"/> <ExcludeApp ID="OneNote"/>

@ DR_ADHAM

to have the same language as someone's own OS, the line
<Language ID = "en-us" />

could be replaced with
<Language ID = "MatchOS" />

right?

(as read on internet)

 

thx

Link to comment
Share on other sites


@tigerjack

 

To automatically install the same languages as the operating system, use "MatchOS" as the Language ID,MatchOS cannot install the operating system languages if Office doesn't support that language or if the ODT cannot find the correct language pack in the local source files. To help address this issue, I recommend that you specify a backup language and a backup source location for the language pack. To do so, use the Fallback attribute and AllowCdnFallBack attribute.

 

 

<Language ID="MatchOS" Fallback="en-us" /> </Product>

 

 

Link to comment
Share on other sites


On 12/1/2018 at 7:07 PM, Akaneharuka said:

@DR_ADHAM If I want to install Office 365 ProPlus which HTML code should I use ?

 

 

Akane

 

Use below code:

 

<Configuration>
  <Add OfficeClientEdition="64" Channel="Insiders" AllowCdnFallback="TRUE" ForceUpgrade="TRUE">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="0" />
  <Property Name="PinIconsToTaskbar" Value="TRUE" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Updates Enabled="TRUE" />
  <RemoveMSI All="TRUE" />
  <Display Level="Full" AcceptEULA="TRUE" />
</Configuration>

 

The above code install Office 365 ProPlus from the latest version from CDN network with all applications.

 

If you want to exclude some apps you can modify it as per your requirement.

Link to comment
Share on other sites


The channel ID in config file should be “monthly “

Link to comment
Share on other sites


4 hours ago, xhartom said:

 

Use below code:

The above code install Office 365 ProPlus from the latest version from CDN network with all applications.

 

If you want to exclude some apps you can modify it as per your requirement.

 

This's online not offline install, then her lang as I see will be "ja-jp".

She can use Language ID = "MatchOS" and Language ID = "en-us" to install both English and any matching languages.

 

Link to comment
Share on other sites


You cannot use two language attributes in one config file, instead Fallback attribute had to be used with MatchOS for language ID.

 

When using the ODT, you can automatically install the Office language that matches the display language of your operating system. To do so, use Language ID="MatchOS" in the configuration file.

 

However,After installing Office, you can use the ODT to install additional language packs for Office. To do so, follow the steps for installing Office with the ODT, but use a new configuration file that uses “LanguagePack” as the Product ID and that indicates which languages to add.

 

To Install office in any language, we just have to change the corresponding Language ID in the config file.

 

 

 

Link to comment
Share on other sites


odt.png

 

EXAMPLE:

<Add SourcePath="\\Server\Share" 
     OfficeClientEdition="32"
     Channel="Broad" 
     AllowCdnFallback="True">
  <Product ID="O365ProPlusRetail">
     <Language ID="MatchOS" Fallback="en-us" />
  </Product>
</Add>

 

Link to comment
Share on other sites


To Add languages to existing installations of Office 365 ProPlus, use the following config file:

 

<Configuration>

 <Add OfficeClientEdition="32">

  <Product ID="LanguagePack">

     <Language ID="fr-fr" />

      <Language ID="ja-jp" />

  </Product>

 </Add>

</Configuration>

 

the configuration file installs the French and Japanese language packs.

 

 

 

Link to comment
Share on other sites


First of all, thank you all for your suggestions

I tried this method to download the files needed for an offline installation and it seems to have worked

 

-create a folder in C:\  named Office365  (or OfficeProPlus)
-put in the same folder setup.exe, eula and configuration.xml files from ODT (i don't know if eula is necessary)
-modify (edit) configuration.xml (the example is in my case)

 

<Configuration>
<Add SourcePath="C:\Office365" OfficeClientEdition="32" Channel="Monthly">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Updates Enabled="TRUE" Channel="Monthly" />
<Display Level="None" AcceptEULA="TRUE" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

 

note, according to your needs... : you can modify   -version 32 or 64 (line 2)
                                                                                          -product "O365ProPlusRetail" or "ProPlus2019Retail" (line 3)
                                                                                          -language (line 4)

naturally in C:\ if you create the folder OfficeProPlus you have to change the second line of configuration.xml (where in my example there is <Add SourcePath="C:\Office365") in C:\OfficeProPlus

 

Once everything is done, open command prompt and run the below command to begin the downloading process:
First, you have to navigate to the created folder by typing the command
cd c:\Office365 (or OfficeProPlus)
Then
setup.exe /download configuration.xml

 

at the end of process I have found a new folder (in the same folder) with the installation files

 

 

 

 

 

 

Link to comment
Share on other sites


To download the files for offline installation you just have to Run the ODT executable in download mode :

 

setup.exe /download downloadconfig.xml

 

After running the command, go to the download location you defined in the configuration file and look for an Office folder with the appropriate files in it.

 

Further, the source path attribute is used in the config file if you intend to 

Download the installation files for Office 365 ProPlus from a local source .

 

Now , to download from a local source, follow the steps for downloading Office with the ODT, but include in your configuration file the download path, which defines where the installation files are downloaded from. 

 

i don't know if eula is necessary)

 

Its not necessary 

 

 

 

 

 

 

Link to comment
Share on other sites


I followed the steps but I'm not able to uninstall the products I want to remove.

 

When I use the command 

setup /configure config.xml

Nothing happens!

U00.jpg

 

Here is the config file I used

2A3B.jpg

 

What could be wrong? Please help me!

 

Link to comment
Share on other sites


@AbdoZaghloul

 

Did you run the ODT exe ?

 

Is the version installed 32 bit as mentioned in the config file?

 

Was the setup.exe and config file in the same folder?

 

Answer these , accordingly I will assist you 

Link to comment
Share on other sites


4 minutes ago, The AchieVer said:

@AbdoZaghloul

 

Did you run the ODT exe ?

 

Is the version installed 32 bit as mentioned in the config file?

 

Was the setup.exe and config file in the same folder?

 

Answer these , accordingly I will assist you 

You mean by ODT, the exe file from Microsoft?, if yes then yes.

 

Yes 32 bit.

 

Yes both in the same folder.

Link to comment
Share on other sites


@AbdoZaghloul

 

Ok.

 

Run the ODT < you will have 2 files < delete the sample config files < now create a folder on the desktop , name it office2019 < now transfer the setup.exe and your config file in it.

 

Run the CMD as administrator < type the following command to change the directory:

 

cd \Users\UserName\Desktop\Office2019

 

where UserName has to be replaced with your device name 

 

Now run the configure command:

 

setup /configure config.xml

 

The removal of selective apps should start now.

 

Tell me how it goes.

 

 

Link to comment
Share on other sites


59 minutes ago, The AchieVer said:

@AbdoZaghloul

 

Ok.

 

Run the ODT < you will have 2 files < delete the sample config files < now create a folder on the desktop , name it office2019 < now transfer the setup.exe and your config file in it.

 

Run the CMD as administrator < type the following command to change the directory:

 

cd \Users\UserName\Desktop\Office2019

  

where UserName has to be replaced with your device name 

 

Now run the configure command:

 

setup /configure config.xml

  

The removal of selective apps should start now.

 

Tell me how it goes.

 

 

Thank you. That worked very well!

 

But I wonder why it didn't work first when I had the folder in D drive, I didn't change anything just moved the folder to the desktop!

 

Thanks once more for your help, really appreciated.

Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...