Customer Data Inquiry

Background

The purpose of this data inquiry is to ensure that all data is available before new Highstage server setup.

If a test server is required in addition to a production server then data for both servers should be made available before installation.

MS-SQL Server and Databases

The Highstage database may reside at a local SQL server (standard or express), or at a central server.

If located at a central SQL server, the databases must be created before setup starts. Database names could be Highstage for production database and HighstageTest for test database.

The account used by Highstage must be created and the user account used by Highstage for data access must have owner permissions to database. The account could be SQL accounts (SQL mixed mode authentication), or domain users accounts. Account names could be Highstage for production access and HighstageTest for test access. Two accounts provide better isolation between production and test.

Notice

In case of using a central SQL server, information about SQL server name (and instance name), credentials and database names must be available. In case SQL server is located locally, SQL server must be installed locally before Highstage installation.

Format URL's

The server requires a formal URL for web access to the Highstage web site. The URL should be fully qualified for future flexibility, and it should be long term durable since references to Highstage may be done from various places like documents, intranet and mails. The URL could be highstage.company.com or hs.company.net, or whatever fits the organization.

Requirement

The formal URL must be defined, and the routing must be established in DNS

SSL Certificate

Information between server and user must be encrypted, both for authentication/data security, but also for basic functionality to work in OS and applications like MS Office.

Requirement

A SSL certificate valid for the formal URL must be available

SMTP server

Highstage must be able to send mails through a SMTP server.

If external users (e.g. consultants etc.) will have access to Highstage server then relaying must be allowed. Also Highstage is able to send mail if system errors occur for proactive support by the Highstage team, this feature also requires relaying.

Requirement

Information about SMTP server name and possible port and credentials is required.

User group for Highstage access

Highstage users must be imported from one or more security groups In Active Directory. Only users imported from Active Directory to Highstage will have access to Highstage.

Highstage reuses standard Microsoft security (e.g. for file system etc.). The group(s) must therefore be a security group, and cannot be a mail group or organizational unit (OU). Hieratical security groups (groups in groups) are accepted.

Requirement

the name(s) of the security group(s) is required.

Windows client setup (For Windows users)

Refer to document DOCU13247 for requirements on Windows client setup.\ The specified .bat file or deployment of Group Policies (GPO) are required for usability and good user experience.