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/14 02:37] – rodolico | microsoft_windows:officefails [2022/11/14 03:36] (current) – rodolico | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| 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. | 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. | ||
| + | |||
| + | **Note**: It appears that saving the ODT directory described below to a safe backup location is equivalent to saving an installation ISO in that it allows you to do a reinstall if necessary. | ||
| ===== Summary ===== | ===== Summary ===== | ||
| Line 138: | Line 140: | ||
| 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. | 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.1668415046.txt.gz · Last modified: 2022/11/14 02:37 by rodolico