Possible Issues when Installing Altium NEXUS Server

The following is a list of possible issues that could be encountered when installing the Altium NEXUS Server. This list will be expanded as any further potential issues are identified.

• The Altium NEXUS Server cannot be installed on a PC running Windows Server 2008, or a 32-bit OS. If you intend to use a non-server variant of the Windows Operating System (Windows 10, Windows 8), you will only be able to have up to 10 concurrent connections to the NEXUS Server (10 with Ultimate and Professional versions). For more than 10 concurrent connections to the NEXUS Server, you will need to use a Windows Server variant of OS (Windows Server 2016 Standard Edition, 64-bit (Recommended), or Windows Server 2012 R2, 64-bit (Minimum)). These are the officially supported operating systems. You will also be unable to install if your version of Windows Operating System does not support Windows Authentication, including: Core, Home, Starter, and Base editions.
• Due to the observed unpredictable behavior of antivirus software, it is recommended to disable such software during the installation of the Altium NEXUS Server.
• The Altium NEXUS Server relies on a number of Microsoft runtime components for successful operation and access, in some situations these may not be present on the target machine. If you receive an error message about a missing library (DLL) when you attempt to sign into an Altium NEXUS Server, it indicates that there are missing Microsoft runtime components. To-date, this is only known to occur on Windows Server 2008 R2 x64 Datacenter. Use this link to download and install these missing components: http://www.microsoft.com/en-us/download/confirmation.aspx?id=29 
• If the computer is also running Microsoft Exchange Server, you might receive an HTTP Error 503 error when you first attempt to log in. The installation of the Exchange Server can change the Internet Information Services (IIS) configuration in a way that conflicts with the NEXUS Server. To resolve this, the following changes must be made to the applicationHost.config file:

<handlers accessPolicy="Read, Script">
...

<add name="kerbauth" image="C:\Program Files\Microsoft\Exchange Server\V15\Bin\kerbauth.dll" preCondition="bitness64" />
<add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" preCondition="bitness64" />
<add name="exppw" image="C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\auth\exppw.dll" preCondition="bitness64" />
<add name="cafe_exppw" image="C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\bin\exppw.dll"  preCondition="bitness64" />

...
</handlers>