System requirements and instructions for the installation of OneOffixx client components are presented here.
The OneOffixx client can be installed on the following operating systems:
Supported Microsoft Office Versions
OneOffixx supports all Microsoft Office versions later than Office 2010, 32-bit as well as 64-bit versions. __OneOffixx supports earlier versions of Microsoft Windows and Microsoft Office until they are no longer supported by Microsoft (“extended support period by an API Service”).
NEU ab 3.0 The OneOffixx client with Release 2019 requires at least .NET Framework 4.7.2 .
The OneOffixx client with version 3.0 requires at least .NET Framework 4.5.2.
Hard disk space
The software itself needs approximately 200 MB of hard disk space. In addition, log files and settings are stored by the OneOffixx client. A local cache for offline usage is also created. Cache size varies with number and size of templates.
The server applications and the OneOffixx client need to be located in the same domain or in a domain authorized by system trusts.
The OneOffixx installer is available in a 32-bit and a 64-bit version. The required version depends on the installed Microsoft Office version.
The 64-bit OneOffixx version needs to be installed if a 64-bit version of Microsoft office is used.
The OneOffixx client communicates exclusively by HTTP/HTTPS with the OneOffixx server. Therefore, only port 80 or port 443 is required.
The OneOffixx MSI package contains the OneOffixx client and various Microsoft Office add-ins.
OneOffixx’ specific parameters:
The following parameters are only necessary for certain installation versions (e.g. installation on Terminal Servers) and are therefore optional:
Apart from this, common MSIEXEC command-line options apply.
msiexec /qb /i "OneOffixx.Install(x86).msi" APPLICATIONFOLDER="C:\Program Files (x86)\OneOffixx" SERVICEENDPOINTURL="http://appurl/OneOffixxService.svc" INSTALLDESKTOPSHORTCUT=1 AUTOSTART=1 /l*v OneOffixxInstall.log AddLocal=WordAddInFeature,OutlookAddInFeature
ServiceEndpointUrl via Registry:
OneOffixx searches the registry for a string value “ServiceAddress” with the keys (HKCU &HKLM):
[HKEY_CURRENT_USER\Software\Sevitec Informatik AG\OneOffixx] "ServiceAddress"="http..."
[HKEY_LOCAL_MACHINE\Software\Sevitec Informatik AG\OneOffixx] "ServiceAddress"="http..."
or (suitable for group policies)
[HKEY_CURRENT_USER\Software\Policies\Sevitec Informatik AG\OneOffixx] "ServiceAddress"="http..."
This value will be used instead of ServiceAddress from the OneOffixx.exe.config file, if found.
OneOffixx ADMX templates are available to control these settings via group policies.
OneOffixx installer’s default settings are aiming for a “normal” installation on a system that can be started by one or multiple Windows users. Here, cache and settings are stored in %AppData%.
Every OneOffixx client entity needs to have exclusive access to ensure full functionality. A new cache location needs to be declared, if this is not the case (e.g. for some Citrix/Terminal Server configurations).
No further parameters are necessary. Cache and settings are stored in %AppData%.
☑ No roaming profiles stored on server side
Cache as well as settings can be stored in %AppDataLocal%, if the following parameter is set:
DATAINLOCALAPPDATAFOLDER = True
☑ Roaming profiles stored on server side
☑ %AppDataLocal% folder is not being deleted
☑ User is always logged in on the same machine
The following setting can specify the cache location, if %AppData% as well as %AppDataLocal% is not an option, or it is possible that multiple OneOffixx entities are open for one user.
CACHEFOLDER = Path e.g. //Share/... (with Placeholders like %username% etc.)
☑ Terminal server installation with multiple open sessions per user
☑ Specified network drive is present and always available
It is also possible to store the settings in a dedicated folder:
SETTINGFOLDER = Path e.g. //Share/... (with Placeholders like %username% etc.)
OneOffixx add-ins cannot be started, i.e. no Office icon is visible in the Office ribbon. This may have several causes:
Slowly starting Office can be caused by an incomplete execution of the “Native Image Generator (ngen)” process. This process is triggered automatically after the installation and is part of the .NET framework. Executing “Native Image Generator” (ngen):
The process ngen.exe is located in the following path: c:\windows\microsoft.net\framework\v4.0.30319\ngen.exe. The current status can be checked with “display”. This should look like this:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe display "C:\Program Files (x86)\OneOffixx\OneOffixx.exe" Microsoft (R) CLR Native Image Generator - Version 4.6.1087.0 Copyright (c) Microsoft Corporation. All rights reserved. NGEN Roots: C:\Program Files (x86)\OneOffixx\OneOffixx.exe NGEN Roots that depend on "c:\Program Files (x86)\OneOffixx\OneOffixx.exe C:\Program Files (x86)\OneOffixx\OneOffixx.exe Native Images: OneOffixx, Version=2.3.40190.0, Culture=neutral, PublicKeyToken=null
The compilation process should be re-started by “update”, if OneOffixx is displayed as “pending”.
This should significantly accelerate the loading process for add-ins.