Limit
your report to the installer only. Reports on the performance of
individual apps should be filed under their respective AppDB entries.
Problems with running any of the apps should only be mentioned if it is
clear that it is due to a problem with the installer.

If you used any overrides during the install,
please list them and explain exactly what problem each override was
needed to solve.

Test reports that do not follow these guidelines will be rejected. ­

­­

HOWTO

­(2017-04-10)

These instructions assume you are familiar with the basics of using
Wine and Linux, including running apps from the command line. If you are
new to Wine and/or Linux, before proceeding further please familiarize
yourself with the information in the FAQ, particularly the sections on creating a 32 bit wineprefix, running an installer, and using wineprefixes.

Make sure all dependencies of Wine are installed on your system, including wine-mono and winbind.

If installing a volume-licensed copy of Office 2010that requires MAK activation, please read the note below for the workaround for bug 30033.

For Wine 2.2 and later, set the Windows version to XP. (For older versions, the default was XP, and should not be changed.)

Install Office 2010 to the newly-created wineprefix simply by running the installer.

After installing, set riched20 to native, builtin in winecfg to enable Powerpoint to start and selection boxes to display correctly.

Do not use winetricks; Office installs its own riched20 to a private directory.

This override may be set globally if Office is installed to a separate wineprefix (recommended).

If other applications are installed to the wineprefix (strongly discouraged), either set the override individually for each Office application, or set riched20 to builtin individually for the non-Office applications, as non-Office applications will not be able to find the riched20 installed by Office.

HOWTO: Office Professional Plus Workarounds for Wine versions without wine-mono

(2012-06-04)

Office Professional Plus does not require .NET to be installed, but if it detects that it is installed, it will look for a machine.config file. This will fail on Wine versions without wine-mono installed (i.e., versions prior to 1.5.6).

The recommended solution is to install wine-mono. The instructions below are provided solely for those who are unable to upgrade to a version of Wine supporting wine-mono.

There are two ways to work around this without installing wine-mono:

Copy a
machine.config file from a native Mono install to the
wineprefix's drive_c/windows/Microsoft.NET/Framework/v2.0.50727/CONFIG
directory.

Delete all .NET-related registry keys.

Installing winetricks dotnet20 will also work around the bug; however, because that will install native dlls that may cause other problems, it is not recommended.

The above workarounds must be done before running the installer. If you do not, and the installer fails, you must delete that wineprefix and start fresh, as the rollback process leaves behind something that prevents subsequent attempts from succeeding, even with one of the workarounds applied. Note also that a rolled-back install leaves running processes that must be killed manually.

Known regressions

(2018-01-07)

There are known regressions affecting the Office 2010 installer in the versions of Wine listed below. Do not attempt to install in them.

Each of the above lines in the config.xml file should be between angled brackets, which unfortunately can't be shown here because the AppDB will not display anything between angled brackets. If you are unsure how it should look, see bug 30033 for an example with the brackets.

5) Save the config.xml file and run the installer..

Guidelines for Submitting Test Reports

Test in a clean wineprefix, using plain Wine.

Specify exactly which edition of Office you tested (Standard, Pro, etc.). This is crucial--bugs that affect one edition may not affect others.

Limit
your report to the installer only. Reports on the performance of
individual apps should be filed under their respective AppDB entries.
Problems with running any of the apps should only be mentioned if it is
clear that it is due to a problem with the installer.

If you used any overrides during the install,
please list them and explain exactly what problem each override was
needed to solve.

* Wine 1.8 backports got activation working, 1.6 bitched about network errors
* Winbind to be installed
* Winetricks to install dotnet2, corefonts
* So for winetricks the code is: apt-get install winetricks -y;winetricks corefonts dotnet20
* Winecfg to set windows version to XP. Setting wine to windows 7 would make excel go about not enough memory errors
* Winecfg to set msxml6 to built-in, then native. Otherwise it seems word bitches about some xml templates being wrong
* There was a dropdown menu in Word that wouldn't appear on the phone activation screen. This prevented me from finding out the phone number plus entering a confirmation number.
* Winecfg to set riched20 and gdiplus to native. Setting these and restarting word let me select the country for phone activation and the confirmation entry field became OK.
* I had to call +44 1290 211 388 which is MSFT Toll free activation number.
* Went through a couple of options, then selected mobile
* Got an SMS with a bitly link
* Had to click through a couple of options then enter the installation I

Yeah sorry, I didn't add the command- sudo apt install winbind samba. I recently tried installing it again and followed my own tutorial and couldn't do it. After reading the error. I understood the error. Sorry for any inconvenience.