microsoft_windows:officefails
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
microsoft_windows:officefails [2022/11/13 23:30] – rodolico | microsoft_windows:officefails [2022/11/14 03:36] (current) – rodolico | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Installation of Microsoft Office Fails ====== | ====== Installation of Microsoft Office Fails ====== | ||
- | We purchased and tried to install Microsoft Office LTSC Standard on a Windows Terminal Server 2019 for a client. It failed with an error 0-2054, which is a general purpose error message that doesn' | + | We purchased and tried to install Microsoft Office LTSC Standard on a Windows Terminal Server 2019 for a client. It failed with an error 0-2054, which is a general purpose error message that doesn' |
- | Searching the Internet | + | Searching the Internet |
- | The client really needed this installed as soon as possible, so, after a couple of days of searching, I realized it was likely the new installation system Microsoft has set up that was causing the issue. Looking at the download from Microsoft, I realized it was a compressed file that, when uncompressed, | + | The client really needed this installed as soon as possible, so, after a couple of days of searching, I realized it was likely the new installation system Microsoft has set up that was causing the issue. |
- | ===== Unpacking | + | In the past, you would get a CD or download an ISO from Microsoft and install from there. However, to install Microsoft Office now, you download a small executable which, when run, creates a subdirectory with a binary file (setup.exe) and one or more XML files. It appears the same setup.exe is used for all Microsoft Office installs after 2016, with the XML file configuring which product you are installing. |
- | Download | + | **Note**: It appears that saving |
+ | ===== Summary ===== | ||
+ | A lot of time, the new setup just works. However, if it does not, and you're comfortable on the command line, it is less prone to error to do the install from the command line. | ||
- | ===== Manual Run (installer | + | - Visit https:// |
+ | - Export that configuration to a file on your computer | ||
+ | - While there, download the latest copy of the Offline Deployment Tool | ||
+ | - Follow instructions at https:// | ||
- | Microsoft has something called the Offline Deployment Tool. It appears to me to be the exact same thing as the installer above. You can see the instructions at https:// | + | ===== Details and Story ===== |
- | Now, all you need is the XML file that defines the installation. If your original installer left things laying around, just grab the correct one of those. I found out much later that all the product id's are listed at https:// | + | ==== What happened ==== |
- | It would have been much easier if I had used the Office | + | We purchased Microsoft Office LTSC Standard 2021 for the client. Going to Microsoft' |
+ | |||
+ | The offline deployment tool (ODT) works well, but the instructions are fairly difficult to locate. Most of the instructions assume everything is working in the GUI, not assuming you are having problems which are being hidden. | ||
+ | |||
+ | ==== First Try ==== | ||
+ | |||
+ | When the installer failed, it left some files laying around. | ||
+ | |||
+ | I opened the command prompt as administrator and went into the directory. From there, I ran <code bash> | ||
+ | |||
+ | However, there was a /download option which said it needed a configuration file as the lone parameter (after the option), so I ran <code bash> | ||
+ | |||
+ | I played with other parameters, then finally discovered | ||
+ | |||
+ | ==== Failure ==== | ||
+ | |||
+ | Assuming I was done, I patted myself on the back and opened Excel, so I could put in the license key and activate. It would not accept my license key, telling me something like | ||
+ | < | ||
+ | |||
+ | I looked and saw that we had installed the Professional version. I had used the configuration file downloaded from Microsoft' | ||
+ | |||
+ | ==== Solution ==== | ||
+ | |||
+ | This was very perplexing. I opened the XML file | ||
+ | |||
+ | Finally, I looked at the XML file in question. | ||
+ | <code xml original.xml> | ||
+ | <!-- Office 2021 enterprise client configuration file sample. To be used for Office 2021 | ||
+ | | ||
+ | Visio 2021, and Project 2021. | ||
+ | |||
+ | Do not use this sample to install Office 365 products. | ||
+ | |||
+ | For detailed information regarding configuration options visit: http:// | ||
+ | To use the configuration file be sure to remove the comments | ||
+ | |||
+ | The following sample allows you to download and install Office 2021 Professional Plus, | ||
+ | Visio 2021 Professional, | ||
+ | |||
+ | This configuration file will remove all other Click-to-Run products in order to avoid | ||
+ | | ||
+ | | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
- | <code xml configuration.xml> | ||
- | < | ||
<Add OfficeClientEdition=" | <Add OfficeClientEdition=" | ||
- | <Product ID="Standard2021Volume" | + | <Product ID="ProPlus2021Volume"> |
< | < | ||
- | < | + | < |
- | < | + | |
</ | </ | ||
- | <Product ID="VisioStd2019Volume" | + | <Product ID="VisioPro2021Volume"> |
< | < | ||
- | < | ||
- | < | ||
</ | </ | ||
- | <Product ID="ProjectStdXVolume" | + | <Product ID="ProjectPro2021Volume"> |
< | < | ||
- | < | ||
- | < | ||
</ | </ | ||
</ | </ | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | <Updates Enabled=" | ||
- | < | ||
- | < | ||
- | <User Key=" | ||
- | <User Key=" | ||
- | <User Key=" | ||
- | </ | ||
- | </ | ||
- | </ | ||
- | Now, open a command prompt. I used administrator privileges, but I'm not sure it was necessary. Move to the ODT directory. | + | |
- | <code bash>cd \ODT</ | + | |
- | Begin the download. The syntax is //setup /download configurationFileName// | + | |
- | <code bash> | + | |
- | Finally, do the installation. For some reason, it is called configure, not install, but hey... | + | |
- | < | + | |
- | You should soon see the standard installation process happen in the GUI. | + | |
- | ===== Additional Problems ===== | + | < |
- | When I tried this the first 10 or 15 times, it failed because I was installing Office 2021 Professional, | + | < |
- | Finally, I looked at the XML file in question | + | < |
+ | |||
+ | </ | ||
+ | </ | ||
+ | |||
+ | Note that this is for // | ||
+ | |||
+ | Finally, after playing a little, I tried various names to change | ||
<code xml manual.xml> | <code xml manual.xml> | ||
Line 107: | Line 137: | ||
</ | </ | ||
</ | </ | ||
+ | |||
+ | When I ran /download followed by /configure, I was able to install the standard version which accepted the product key I had, so my clients were able to use their system, finally. | ||
+ | |||
+ | Obviously, someone at Microsoft put the wrong configuration file in the Standard version download. | ||
+ | |||
+ | ===== Easy way to do it ===== | ||
+ | |||
+ | After we were able to do this, I did a little more research and found that Microsoft has a very nice configuration tool for the new installation program. It is located at https:// | ||
+ | |||
+ | Finally, when you are exporting the file, it gives you a link to download the latest version of the Office Deployment Tool to ensure you are up to date on that. | ||
+ | |||
+ | I'd recommend the following procedure: | ||
+ | - Fill out the form at https:// | ||
+ | - Export the form | ||
+ | - Grab a fresh copy of the Office Deployment tool | ||
+ | - Save the xml file created to a convenient location. Following instructions assume it is named // | ||
+ | - Create a directory. Recommended by Microsoft is c:\ODT | ||
+ | - Run the new copy of the Office Deployment Tool and point the installer to c:\ODT | ||
+ | - Copy the XML file you downloaded into that directory | ||
+ | - Open a command prompt as administrator | ||
+ | - Move to the created directory< | ||
+ | - Download installation files< | ||
+ | - Get a cup of coffee while it finishes (takes a while, especially on a slow connection) | ||
+ | - Start the installation< | ||
+ | - Done. | ||
+ | |||
+ | Following is an example of configuration.xml created by the web site. Note that it has a lot more options than I even knew were needed. | ||
+ | |||
+ | <code xml configuration.xml> | ||
+ | < | ||
+ | <Add OfficeClientEdition=" | ||
+ | <Product ID=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | <Product ID=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | <Product ID=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | <Updates Enabled=" | ||
+ | < | ||
+ | < | ||
+ | <User Key=" | ||
+ | <User Key=" | ||
+ | <User Key=" | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | ===== Links ===== | ||
+ | * https:// | ||
+ | * https:// | ||
+ | * https:// | ||
+ | |||
+ | These are a couple of the sites I visited that did not help solve the problem, but do show some other issues and solutions. | ||
+ | * https:// | ||
+ | * https:// | ||
+ |
microsoft_windows/officefails.1668403801.txt.gz · Last modified: 2022/11/13 23:30 by rodolico