Specify exactly which edition of Office 2010 you tested (Standard, Pro, etc.). This is crucial--bugs that affect one edition may not affect others.
Specify exactly what type of install you tested (Typical, Custom, Minimal, etc.)
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.
Office 2010 has been installable in 32 bit Wine beginning with 1.3.9; however, versions prior to 1.3.35 suffered from bug 25476. This bug was fixed as of 1.3.35; if you are using an older version of Wine, upgrade.
Beginning with Wine 1.5.6, wine-mono is required for supported configurations. If your distro does not provide a wine-mono package, follow the instructions on http://wiki.winehq.org/Mono to install it.
If installing Office Professional Plus in a Wine version older than 1.5.6, see the note below for additional steps that must be taken prior to running the installer. These steps should not be needed for 1.5.6 and later provided wine-mono is installed on your system.
Make sure all dependencies of Wine are installed on your system, including winbind.
Install Office 2010 to a clean wineprefix--no winetricks or other tweaks, and no other applications installed. Do not change the Windows version in winecfg; it should remain at the default setting of XP.
Note: If you have 64 bit Wine installed on your system, you must create a 32 bit wineprefix for Office 2010 using the WINEARCH=win32 environment variable.
Follow the instructions in http://wiki.winehq.org/FAQ for creating a 32 bit wineprefix, running an installer, and using wineprefixes.
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, and the one installed by winetricks is insufficient. 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
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:
machine.config file from a native Mono install to the
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.
There are known regressions affecting the Office 2010 installer in the versions of Wine listed below. Do not attempt to install in them.
In addition, Office 2010 is not installable in any version prior to 1.3.9; this includes all 1.2.x versions.