Target Platforms
The following server systems are tested and supported:
- Windows Server 2000 (x32 only)
- Windows Server 2003 (x32/x64)
- Windows Server 2008 R2 (x64 only)
- Windows Server 2012 (x64 only)
- Windows Server 2012 R2 (x64 only)
- Windows 10 Server Technical Preview (x64)
IIS 7 is also available with Windows 7 and later and it is known that ScriptX works in these scenarios but they are not specifically supported; Windows 7 and later are client operating systems.
For Windows Server 2000 and 2003 both classic ASP and .NET based solutions are tested.
From Windows 2008 R2 onwards, only .NET based solutions are tested. However, it is known that classic ASP (and PHP) solutions work in these scenarios.
ScriptX Remote Printing is known to work - at the simplest interactive level - 'out of the box' on 'out of the box' configurations of Windows 7/8/10, Windows Server 2003, Windows Server 2008 and Windows Server 2012.
When working with Windows 2012 and later you must install the 'desktop experience' that includes Internet Explorer. ScriptX will not work with a 'core' install.
Configuration requirements
The successful implementation of ScriptX Remote Printing will require correct configuration of DCOM security on the server system; this will require a good understanding both of DCOM configuration, and the security policies in place on the server.
On all systems, Distributed COM must be enabled. Customers experience success with "Default Authentication Level" of CONNECT and "Default Impersonation Level" of IDENTIFY; these are the default settings.
Whilst we can provide general support on trouble-shooting problems, the vast array of configuration parameters available mean that it is impossible to provide guaranteed recipes for a working installation. A solid familiarity with enabling logging of security events is also recommended.
NOTE: Use of ScriptX Server side printing hosted in IIS will require Component services configuration on Windows Server 2003 and later.
Edition requirements
It is important to deploy the correct edition of ScriptX for the server system in use, in other words:
- Deploy ScriptX 32-bit Edition on x32 systems.
- Deploy ScriptX 64-bit Edition on x64 editions of Windows Server 2003 and later.
Notes
- For Windows Server 2008/IIS 7 and later, you may configure the Application Pool worker process to use 32bit -- this will not work with ScriptX, you must use 64bit worker processes (please check the default for your system).
- The 64-bit Edition cannot be installed on x32 based operating systems, however the 32-bit Edition can be installed on x64 based systems. IA64 based systems are not supported.
- We recommend avoiding installng both x86 and x64 editions on the same server as it significantly increases the risk of incorrect configuration. The scenarios where it might be required to install both are hightly specialised - if you believe you might need to do this please contact our support services to discuss your requirements.
Our advice on the use of x64/x86 has changed due to a change in the implementation of Internet Explorer 9 and later on x64 systems such that ScriptX x86 Edition will no longer work on x64 systems when the MeadCo TriPrint Server object is configured to run under a named identity (i.e. a non-interactive account).
::> A simple example