Supportworks V8 Technical Requirements: Difference between revisions
No edit summary |
|||
| (17 intermediate revisions by 2 users not shown) | |||
| Line 27: | Line 27: | ||
Microsoft Windows 2008 Server (64-bit) R2 | Microsoft Windows 2008 Server (64-bit) R2 | ||
Microsoft Windows 2008 Server (32-bit and 64-bit) | Microsoft Windows 2008 Server (32-bit and 64-bit) | ||
Microsoft Windows 2012 Server (64-bit) R2 | |||
Microsoft Windows 2016 Server (64-bit) | |||
===Supportworks Client=== | ===Supportworks Client=== | ||
| Line 32: | Line 34: | ||
Microsoft Windows 8 | Microsoft Windows 8 | ||
Microsoft Windows 7 | Microsoft Windows 7 | ||
=Separate Volume / Drive Installation= | |||
If your Supportworks Application is to be installed on a drive other than the C: drive | |||
Enable 8dot3name creation for the required drives prior to installation by running the following from the command prompt. To enable this on all drives on the server (recommended) | |||
fsutil 8dot3name set 0 | |||
You can also enable the 8dot3name for a specific drive . For example, ifSupportworks is to be installed on the D drive, run the following | |||
fsutil 8dot3name set d:0 | |||
=Firewall Configuration= | |||
Your firewall must be configured to allow connections to the server on the following TCP ports: | |||
5001- 5008 | |||
80 and 443 | |||
25 (SMTP with or without TLS) | |||
=Supported Web Browsers= | |||
*Internet Explorer 8.0 and above | |||
*Firefox 6.0 and above | |||
*Chrome 26.0 and above | |||
=Sizing Your Server – Minimum Memory and CPU Requirements= | |||
You will require a server with a minimum specification of | |||
4GB RAM | |||
1 Quad Core CPU | |||
The same amount of disk space on your existing Supportworks plus additional 2GB for the installation files | |||
Supportworks will be migrated to the same drive as your existing Supportworks application server. | |||
If a physical server is provided, we strongly recommend RAID 5 SCSI for resilience and performance | |||
=Databases= | |||
===Maria DB=== | |||
MariaDB is shipped as part of the Core Services that come with Supportworks ESP and is used as an embedded database. | |||
We pre-configure Supportworks ESP to use this embedded database for the application data | |||
===Microsoft SQL=== | |||
*SQL Server 2014 | |||
*SQL Server 2012 | |||
*SQL Server 2008 R2 | |||
===If Microsoft SQL Database is Used=== | |||
*Ensure that the client-side MSSQL components are installed on the main Supportworks server | |||
*Management Studio should be available on the Supportworks application server | |||
*Ensure that you can connect to the MSSQL database engine using SQL Server Authentication | |||
*Your MSSQL database administrator must be available during the migration | |||
=Other Requirements= | |||
'''Account for installation''' - | |||
This should have full local administrative rights on the new server | |||
'''System ID of new server''' - | |||
This can be obtained by running the utility available at | |||
https://public.hornbill.com/utils/SwSystemID.exe on the new server | |||
'''Test email credentials''' - | |||
Ensure access is verified via Telnet for SMTP, POP3 and IMAP protocols | |||
'''FTP client access''' - | |||
Enable FTP client access on the new server (where possible) to enable | |||
swift transfer of relevant files and folders required for the installation | |||
'''Windows updates''' - | |||
Ensure all windows updates are installed on the new server | |||
'''Download installation files from SFTP location provided''' - | |||
We will provide you with credentials for accessing the SFTP location | |||
Latest revision as of 12:40, 6 April 2018
| Status: | Published |
|---|---|
| Version: | 1.0 |
| Authors: | HTL QA |
| Applies to: | All Supportworks V8 ESP versions |
Installation Considerations – Physical / Virtual Server
- The migration will require a new Supportworks Server
- Supportworks can be installed on virtual or physical servers
- The Virtualization technology used is up to you
Supported Operating Systems
Supportworks Server
Microsoft Windows 2012 Server (64-bit) R2 Microsoft Windows 2012 Server (64-bit) Microsoft Windows 2008 Server (64-bit) R2 Microsoft Windows 2008 Server (32-bit and 64-bit) Microsoft Windows 2012 Server (64-bit) R2 Microsoft Windows 2016 Server (64-bit)
Supportworks Client
Microsoft Windows 10 Microsoft Windows 8 Microsoft Windows 7
Separate Volume / Drive Installation
If your Supportworks Application is to be installed on a drive other than the C: drive
Enable 8dot3name creation for the required drives prior to installation by running the following from the command prompt. To enable this on all drives on the server (recommended)
fsutil 8dot3name set 0
You can also enable the 8dot3name for a specific drive . For example, ifSupportworks is to be installed on the D drive, run the following
fsutil 8dot3name set d:0
Firewall Configuration
Your firewall must be configured to allow connections to the server on the following TCP ports:
5001- 5008 80 and 443 25 (SMTP with or without TLS)
Supported Web Browsers
- Internet Explorer 8.0 and above
- Firefox 6.0 and above
- Chrome 26.0 and above
Sizing Your Server – Minimum Memory and CPU Requirements
You will require a server with a minimum specification of
4GB RAM 1 Quad Core CPU The same amount of disk space on your existing Supportworks plus additional 2GB for the installation files Supportworks will be migrated to the same drive as your existing Supportworks application server.
If a physical server is provided, we strongly recommend RAID 5 SCSI for resilience and performance
Databases
Maria DB
MariaDB is shipped as part of the Core Services that come with Supportworks ESP and is used as an embedded database. We pre-configure Supportworks ESP to use this embedded database for the application data
Microsoft SQL
- SQL Server 2014
- SQL Server 2012
- SQL Server 2008 R2
If Microsoft SQL Database is Used
- Ensure that the client-side MSSQL components are installed on the main Supportworks server
- Management Studio should be available on the Supportworks application server
- Ensure that you can connect to the MSSQL database engine using SQL Server Authentication
- Your MSSQL database administrator must be available during the migration
Other Requirements
Account for installation - This should have full local administrative rights on the new server
System ID of new server - This can be obtained by running the utility available at https://public.hornbill.com/utils/SwSystemID.exe on the new server
Test email credentials - Ensure access is verified via Telnet for SMTP, POP3 and IMAP protocols
FTP client access - Enable FTP client access on the new server (where possible) to enable swift transfer of relevant files and folders required for the installation
Windows updates - Ensure all windows updates are installed on the new server
Download installation files from SFTP location provided - We will provide you with credentials for accessing the SFTP location