Guide for Highstage domain and migration setup

Rationale

This document aims to help as guidance for setting up the Highstage server in various setups in relation to Windows Domain

Introduction

This document describes the procedure required when migrating Highstage LDAP replication to a new domain/AD.

Supported Setups

The following section explain various configuration for running Highstage and users in domains.

Running the Highstage server and users in the same domain

This is the basic setup and require minimal configuration.

Highstage Server in one domain and users in another

It is possible to run Highstage in one domain and users in another by specifying a different domain for LDAP replication in the parameter table. Please see section about LDAP Replication settings.

Highstage Server in one domain and users in various domains

By default, this is not a supported configuration. The Highstage application cannot facilitate different domains without the infrastructure to support it. The case where this scenario is possible, is that of a single domain for Highstage to use, with a established trust relationship to the other ones.

As this is a complex setup, please do not hesitate to contact the Highstage support team for more details.

Guide for changing domain configurations

Moving The Highstage server from one domain to another, and leaving the users behind

• Change Hostname First change the Hostname of the server, a guide for this can be found in Changing Hostname for Highstage.
• Check and Set LDAP properties In this case the queried domain have to be changed for LDAP replication because this don't follow the ones specified for the server. Please see LDAP Replication settings.
• Distribute new BAT-file The Bat file eases setup for users running Highstage from Windows computers. By default security policies in Windows are set so that users are prompted for credentials or rejected when connecting to an unknown remote folder. This can be easily changed by changing a registry key in windows. In order to distribute this change, the Highstage server can produce a BAT-file that makes this change. By centrally distributing it, IT-departments can lower time used by all users of the system. Please refer to Generating setup .BAT File for a guide for generating the BAT file.

Moving Highstage users from one domain to another

• Update User properties After ensuring that the parameters are defined correctly regarding LDAP lookup for the new domain, the ts_role table needs an update before replicating in order to update it with the new domain’s information. Where the logon name should have the form of ‘domain\obj’

The following snippet can be used to prepare the user table for migration

1
Update ts_role Set objectguid='',domain='',ldappath='',logonname='DOMAIN\'+obj;

• Check and Set LDAP properties Set the new Replication setting. See LDAP Replication settings for more info about this.

Guide for changing settings in Highstage

When changing domain for the Highstage server the following elements should be taken into consideration:

• Hostname
• Certificate
• LDAP settings

Changing Hostname for Highstage

When changing hostname for Highstage, the following places should be considered:

• Webrootclient parameter The parameter can be set in the parameter table under [System] -> [Security Parameters] and should reflect the actual URL of the Highstage web application. For instance: https://www.turbostage.net/ts/

  Important! Remember to use the specify HTTP or HTTPS in front of the hostname and end with /

   

• StorageURL parameter The parameter can be set in the parameter table under [System] -> [Security Parameters]

Use the URL of the WebDAV server specified in IIS. Example: https://www.turbostage.net/files

Tip! Files is the standard configuration, however other names can be used as well.

• Hosting.config

Ensure the hostname in the hosting.config.xml file in the root of the webapp folder (Usually found $HighstageInstallation/TurboStage/TS_WebApp/hosting.config.xml ). If this is wrong the jobs and refine tasks will never to executed. Confirmation and eventual errors can be found in the Windows Event Viewer, under Application Logs, reported by the TurbostageService.

• Web.config Check the web.config file in the root of the webapp for overwrites of parameters from database and other definition which uses the hostname.

Changing LDAP Replication settings

The following parameters should be taken into consideration when changing LDAP properties:

• Domain
• LdapUserID
• LdapPassword
• LdapUserGroups
• DefaultTrustees

By default if no 'LdapUserID' is set, the identity of the application pool is used to query the directory service with the Domain specified in the 'Domain'-parameter. If another identity should be used use the parameter 'LdapUserID' and 'LdapPassword'.

When changing domain make sure that if a group is specified in the 'DefaultTrustees' this group is also present in the new domain.

Generating setup .BAT File

On any Highstage server, a page called winclientsetup can generate the .BAT file for setting up clients fast. It can be found here: *Hostname*/ts/ts/setup/winclient/setup.aspx