Elecosoft UK Ltd Product Installation Guide

Transcription

1 Elecosoft UK Ltd Product Installation Guide Elecosoft UK Ltd Parkway House Pegasus Way Haddenham Business Park Haddenham Buckinghamshire HP17 8LJ United Kingdom Tel: +44 (0) Fax: +44 (0) Ast a Powerproject: the power behind successful projects Asta Powerproject: the power behind successful projects

2 Trademarks Powerproject is a registered trademark of Elecosoft UK Ltd in the UK, the European Union (Community Trademark Office), Norway, the USA and Australia. ios is a trademark or registered trademark of Cisco in the United States and other countries. Elecosoft and Elecosoft BIMCloud are registered trademarks of Elecosoft PLC. SQLite is a trademark of Hipp, Wyrick & Company, Inc. Microsoft, ActiveX, Active Directory, DirectX, Excel, Internet Explorer, SQL Server, Terminal Server, Windows and Windows PowerShell are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Oracle and SQL*Plus are either registered trademarks or trademarks of Oracle Corporation and/or its affiliates. Citrix is a registered trademark or trademark of Citrix Systems Inc in the United States and/or other countries. Wi-Fi is a registered trademark of Wi-Fi Alliance Elecosoft UK Ltd

3 Table of Contents 1 Overview of this document Notes on operating systems and database types Installing the Asta Powerproject Enterprise system Creating a Microsoft SQL Server database Creating a Microsoft SQL Server database user Specifying the Microsoft SQL Server authentication mode Installing Asta Powerproject Enterprise Installing the Asta Name Server and the Enterprise server to run as services Installing the Asta Name Server to run as a service Installing the Enterprise server to run as a service Configuring the Asta Name Server and Enterprise server services Configuring Asta Powerproject Enterprise registry settings Specifying whether baselines are pre-mounted completely Specifying whether projects are recalculated at mount time Specifying database timeout settings Installing an Oracle driver Creating a data source in Asta Serveradmin Configuring Asta Powerproject Enterprise using Asta Serveradmin Specifying the server location method in Asta Serveradmin Specifying the server temporary folder Specifying the audit logs folder and enabling audit logging Enabling users to log in automatically using Active Directory Configuring firewalls to work with Asta Powerproject Enterprise Setting firewall rules for the Asta Name Server and Enterprise server Setting firewall rules for specific ports Installing a licence server and Asta Licence Manager Choosing a computer on which to install an Asta licence server Installing the Asta Licence Manager application Obtaining your licences from Elecosoft UK Ltd Configuring Elecosoft UK Ltd licensing in a Windows domain environment Configuring Asta licensing in a Windows workgroup environment Configuring the Asta licence server machine Mirroring Windows user account details for each user Configuring firewalls to work with the Asta licence server Installing the Asta Powerproject client application Preliminary steps if installing onto a Terminal Server or Citrix server Elecosoft UK Ltd

4 4.2 Installing an Asta Powerproject Enterprise client Installing the licence server as a service Activating the Asta Powerproject client application Activating Asta Powerproject using a named user licence Activating Asta Powerproject using a concurrent licence Configuring file locations in the Asta Powerproject client Specifying the server location method in the Asta Powerproject client Checking that the client can connect to the Enterprise server Additional steps if you have an Asta Powerproject BIM licence Ensure that the computer has access to the Elecosoft BIMCloud Download and install Microsoft DirectX End-User Runtimes Additional steps if installing onto a Terminal Server or Citrix server Specifying that projects and their baselines should be pre-mounted Installing Asta Archive Manager Installing the latest version of Asta Powerproject Enterprise Configuring your Asta services to work with Asta Archive Manager Installing the Asta Archive Manager application Setting up proxy exceptions for the archiving web services Configuring Windows to enable the use of distributed transactions Configuring the distributed transaction timeout setting Installing Time Sheet for Asta Powerproject Installing and configuring Microsoft Internet Information Services Configuring Windows to allow ASP pages to run Installing necessary role services for the Web Server (IIS) Installing the Asta Developers Toolkit Creating a Microsoft SQL Server database for use with Time Sheet Creating a Microsoft SQL Server database user Installing Time Sheet Registering Time Sheet with Microsoft Internet Information Services Additional configuration in Internet Information Services version Creating an application pool for Time Sheet Specifying the server location method in the Asta Developers Toolkit Noting server and project information and mounting projects Creating tables in the Time Sheet database Granting the necessary users access to Time Sheet configuration files Enabling Time Sheet to connect to the database Registering the project(s) to be used with Time Sheet Updating Asta Powerproject with the Time Sheet connection string Configuring the Time Sheet mail agent service Elecosoft UK Ltd

5 6.19 Verifying that Time Sheet has been installed correctly Configuring Time Sheet s settings Accessing the Time Sheet login pages Notes on running Time Sheet Installing Web Access for Asta Powerproject Installing and configuring Microsoft Internet Information Services Configuring Windows to allow ASP pages to run Installing necessary role services for the Web Server (IIS) Installing the Asta Developers Toolkit Installing Web Access Additional configuration in Internet Information Services version Creating an application pool for Web Access Specifying the server location method in the Asta Developers Toolkit Noting server and project information and mounting projects Granting the necessary users full access to Web Access configuration files Registering the project(s) to be used with Web Access Verifying that Web Access has been installed correctly Configuring Web Access s settings Accessing the Web Access login page Installing Site Progress Mobile for Asta Powerproject Installing the Asta Developers Toolkit Installing the Site Progress Manager application Specifying the server location method in the Asta Developers Toolkit Ensuring that Site Progress Manager has access to Elecosoft UK Ltd s Cloud server Entering your company details into Site Progress Manager Configuring Site Progress Manager Configuring projects for use with Site Progress Mobile Configure tasks to make them appear in the Ticksheet screen Configure tasks to make them appear in the Turnaround screen Create user-defined fields to enable photographs to be associated with tasks and milestones Recording details of Site Progress Mobile users Recording details of your projects in Site Progress Manager Associating users with their tasks within projects Downloading Site Progress Mobile onto mobile devices Accessing the Site Progress Mobile web app Installing Business Intelligence for Asta Powerproject Installing the Asta Developers Toolkit Elecosoft UK Ltd

6 9.2 Specifying the server location method in the Asta Developers Toolkit Installing the Business Intelligence applications Creating the Business Intelligence database Configuring the Business Intelligence Controller application Installing Asta Project Viewer Installing the Asta Project Viewer application Additional steps if you are going to view projects that have associated IFC files Ensure that the computer has access to the Elecosoft BIMCloud Download and install Microsoft DirectX End-User Runtimes Installing Bidcon Installing Bidcon as a single-user application on one computer Additional steps if you have a Bidcon BIM licence Ensure that the computer has access to the Elecosoft BIMCloud Download and install Microsoft DirectX End-User Runtimes Installing Bidcon as a multi-user application with the database on a server Installing Bidcon on the server machine Creating Microsoft SQL Server users on the server Installing Bidcon on the client computers Configuring Bidcon clients to access the databases on the server Updating the Bidcon configuration file with the database location Installing Bidcon onto a Terminal Server or Citrix server Moving the Bidcon databases from one machine to another Upgrading an Asta Powerproject Enterprise installation to the latest version Stopping the Asta Name Server and Enterprise server services Installing the latest version of Asta Powerproject Enterprise Installing the latest version of Asta Developers Toolkit Creating a new database for the new version of the software Configuring a Microsoft SQL Server database user to be the database owner Creating a new data source that connects to the new database Converting data from the old data source into the new data source Specifying that the projects in the new data source should be premounted Unregistering the old data source Installing the latest version of the Asta Powerproject Enterprise client Upgrading an existing Asta Archive Manager installation to the latest version Elecosoft UK Ltd

7 13.1 Uninstalling the existing Asta Archive Components Installing the latest version of Asta Powerproject Enterprise Installing the latest version of the Asta Archive Manager application Upgrading an existing Time Sheet installation to the latest version Copying your existing Time Sheet configuration files Uninstalling the existing Time Sheet software Installing the latest version of Time Sheet Checking that the necessary users still have access to configuration files Merging existing configuration settings into the new version Upgrading the Time Sheet database Re-registering your Asta Powerproject project(s) in Time Sheet Upgrading an existing Web Access installation to the latest version Copying your existing Web Access configuration file Uninstalling the existing Web Access software Installing the latest version of Web Access Checking that the necessary users still have access to configuration files Implementing existing configuration settings in the new version Re-registering your Asta Powerproject project(s) in Web Access Moving Asta Powerproject Enterprise to a different server machine Installing Asta Powerproject Enterprise onto the new server machine Installing the Asta Name Server and the Enterprise server to run as services Configuring the Asta Name Server and Enterprise server services Configuring Asta Powerproject Enterprise registry settings Re-registering a data source in Asta Serveradmin Configuring Asta Powerproject Enterprise using Asta Serveradmin Configuring firewalls to work with Asta Powerproject Enterprise Elecosoft UK Ltd

8 1 Overview of this document This document describes how to install the Asta Powerproject Enterprise system and the following companion products: Asta Licence Manager. Asta Archive Manager. Time Sheet for Asta Powerproject. Web Access for Asta Powerproject. Site Progress Mobile for Asta Powerproject. Business Intelligence for Asta Powerproject. Asta Project Viewer. Bidcon. As well as describing the installation process for each product, this document describes any additional steps that you must take in order for the installation to be successful. For example, if you need to create a database to use with the product, this document describes the necessary steps. This document also describes how to upgrade existing installations of Elecosoft UK Ltd s software to the latest version and how to move an installation of Asta Powerproject Enterprise from one server machine to another. 1.1 Notes on operating systems and database types The instructions in this document assume that you are installing Asta Powerproject Enterprise and its companion products onto a server machine that is running the Microsoft Windows 2012 Server operating system and that you are using Microsoft SQL Server 2012 Express to create and manage your databases. It is possible to use other operating systems and other types of database. Where instructions differ between operating systems, this document outlines the different steps that you must take. If you choose to use a different type of database, you will need to identify and carry out the equivalent steps in the database management application that you are using. The instructions in this document that involve working with Microsoft SQL Server describe one possible way of working, not the only way of working. For example, the instructions in sections 2.1, Creating a Microsoft SQL Server database and 2.2, Creating a Microsoft SQL Server database user, describe one possible way of creating a database and a user to administer the database. It is important to note that while these instructions will achieve the desired result, the protocols in place in your own organisation may mean that you will need to follow slightly different procedures. For example, you may want to use an existing user to administer the database, or your Microsoft SQL Server password policies may necessitate a different approach to the one described here. Before carrying out the steps in this document to install an item of Elecosoft UK Ltd software, refer to the Elecosoft UK Ltd Product Overview and System Requirements Guide for details of the hardware and software that must be in place prior to installation. If any of the required software listed in that document is not already installed on the computer on which you want to install an item of Elecosoft UK Ltd software, install it before proceeding with the instructions in this guide Elecosoft UK Ltd

9 2 Installing the Asta Powerproject Enterprise system This section of the document describes how to install the Asta Powerproject Enterprise system, including the additional steps that you need to take in order to create a database for use with Asta Powerproject Enterprise. The installation of the Asta Powerproject Enterprise system comprises the following steps: Creating a Microsoft SQL Server database. Creating a Microsoft SQL Server database user. Specifying the Microsoft SQL Server authentication mode. Installing Asta Powerproject Enterprise. Installing the Asta Name Server and the Enterprise server to run as services. Configuring the Asta Name Server and Enterprise server services. Configuring Asta Powerproject Enterprise registry settings. Installing an Oracle driver. Creating a data source in Asta Serveradmin. Configuring Asta Powerproject Enterprise using Asta Serveradmin. Configuring firewalls to work with Asta Powerproject Enterprise. 2.1 Creating a Microsoft SQL Server database Before you install the Asta Powerproject Enterprise system, you must create a database in which to store the Asta Powerproject data. To create a Microsoft SQL Server database: 1. On the server machine on which Microsoft SQL Server is installed, launch the Microsoft SQL Server Management Studio and connect to your server. 2. Within the SQL Server Management Studio, right-click the Databases folder in the Object Explorer and select New Database: 3. The New Database dialog appears. 4. On the General page of the dialog, in the Database name field, enter a suitable name for the database, as illustrated below: 5. There is no need to change any of the default settings for this database; click OK to create it Elecosoft UK Ltd

10 All of your Asta Powerproject Enterprise data will be stored in this database. For this reason, you must ensure that the database is backed up regularly, preferably as part of an automatically-scheduled backup process. Some database backup mechanisms take the database offline temporarily while the backup is in process. If this is the case with your backup mechanism, you must stop the Enterprise server service before the database is taken offline, then restart it once the backup is complete. By default, Microsoft SQL Server 2012 Express places the database files that must be backed up in the following location: C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\ By default, it places backup files in the following location: C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\BACKUP\ Depending on the type and version of database that you are using, and the way in which the database software has been installed onto your server machine, these locations may be different for you. 2.2 Creating a Microsoft SQL Server database user Once you have created the Microsoft SQL Server database, you must create a new user to access it. To create a Microsoft SQL Server user: 1. Within the Microsoft SQL Server Management Studio Object Explorer, expand the Security folder, right-click the Logins folder and select New Login: The Login New dialog appears. 2. On the General page of the dialog, in the Login name field, enter a suitable name for the user, for example Asta. 3. Click the SQL Server authentication radio button. A number of fields below this radio button become available. 4. Enter a password for the user in the Password field, then re-enter it in the Confirm password field. 5. Clear the Enforce password policy check box: 6. In the Default database field, select the database that you have created: 2016 Elecosoft UK Ltd

11 7. In the Select a page section of the dialog, click Server Roles. 8. On the Server Roles page of the dialog, select the bulkadmin check box: 9. In the Select a page section of the dialog, click User Mapping. 10. On the User Mapping page of the dialog, in the Users mapped to this login group, select the check box to the left of the database that you have created: 11. The name of your database should now be appended to the title of the Database role membership role for group. In this group, select the db_owner check box: 12. Click OK. It is necessary to assign the bulkadmin server role to the database user in order to create data sources in Asta Serveradmin that use the optimise transaction data facility (see section 2.9, Creating a data source in Asta Serveradmin for details). If you are using an Oracle database rather than Microsoft SQL Server, you must ensure that you create a database user with sufficient privileges to use the SQL*LOADER database utility. This can be achieved by giving the user the role of CONNECT (Default) and DBA (Admin and default). 2.3 Specifying the Microsoft SQL Server authentication mode In order for Asta Powerproject Enterprise to work with Microsoft SQL Server, you must set the server authentication mode to SQL Server and Windows Authentication mode. To set the server authentication mode: 1. At the top of the Microsoft SQL Server Management Studio Object Explorer, right-click the SQL server and select Properties: 2016 Elecosoft UK Ltd

12 2. The Server Properties dialog appears. 3. In the Select a page section of the dialog, click Security. 4. On the Security page of the dialog, click the SQL Server and Windows Authentication mode radio button: 5. Click OK. 2.4 Installing Asta Powerproject Enterprise Now that you have created your database and a user in Microsoft SQL Server, you can install Asta Powerproject Enterprise. You can install Asta Powerproject Enterprise onto the server machine on which your database is located, or onto another server machine. The instructions in this document assume that you are installing it onto the server machine on which your database is located. The Asta Powerproject Enterprise installation routine installs the following applications: Asta Enterprise server an application that controls access to data sources (eg the database that you created earlier) and enables more than one user to access data sources simultaneously. Asta Name Server an application that holds details of all of the Enterprise servers that are currently running. The name server publishes details of these Enterprise servers to the Asta Powerproject client applications, without the clients having to connect to the servers individually. Asta Serveradmin a server administration utility. Controller an application that you use to operate the Enterprise server using a command prompt. All of these applications are available on the Windows Start screen once you have installed Asta Powerproject Enterprise. To install Asta Powerproject Enterprise: 1. Log into the server machine as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears Elecosoft UK Ltd

13 4. Follow the steps in the installation wizard to install Asta Powerproject Enterprise, clicking Next to move between the various screens of the wizard. If Microsoft.NET Framework 4 is not present on the server machine, the installation wizard will install it automatically. The installation of.net Framework 4 will take some time and may require you to reboot the server machine; if so, the Asta Powerproject installation wizard will carry on automatically after the reboot. Asta Powerproject Enterprise is installed into the following folder by default: C:\Program Files\Asta\Asta Powerproject enterprise\ (32-bit systems). C:\Program Files(x86)\Asta\Asta Powerproject enterprise\ (64-bit systems). 5. If you want to install Asta Powerproject Enterprise to a location other than the default, click the Custom radio button on the Setup Type screen, which will give you access to an additional page of the wizard in which you can specify an installation folder. 6. On the Setup Type screen, leave the Install server as a service check box cleared. Although you can use this check box to install the server as a service automatically, it is preferable to install the server as a service manually after the initial installation following the steps in the next section of this document as this gives you the ability to configure the name of the service, as well as a number of other variables. 7. Click Install on the final screen of the wizard to install Asta Powerproject Enterprise. 8. When the installation routine is complete, click Finish to exit the wizard. 9. Reboot the server machine on which you have installed Asta Powerproject Enterprise. 2.5 Installing the Asta Name Server and the Enterprise server to run as services Now that you have installed Asta Powerproject Enterprise, you can install the Enterprise server (AstaEnterprise.exe) and the Asta Name Server (AstaNameServer.exe) to run as services, so that they are loaded automatically when Windows starts and run in the background. You should install the Asta Name Server as a service first, followed by the Enterprise server Installing the Asta Name Server to run as a service To install the Asta Name Server to run as a service: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch a command prompt, ensuring that you run it as Administrator. A command prompt window appears: 2. In the command prompt window, change the directory location to the folder in which Asta Powerproject Enterprise has been installed, which is, by default: 2016 Elecosoft UK Ltd

14 C:\Program Files\Asta\Asta Powerproject enterprise\ (32-bit systems). C:\Program Files(x86)\Asta\Asta Powerproject enterprise\ (64-bit systems). 3. Type AstaNameServer.exe install and press ENTER. You see a confirmation that the service has been installed successfully: If you are planning to use Asta Archive Manager to archive historic data from your projects, instead of entering AstaNameServer.exe install, enter AstaNameServer.exe web install. This turns on web services that Asta Archive Manager requires to operate Installing the Enterprise server to run as a service You can install the Enterprise server to run as a service in a number of ways, each of which is described below. Choose the way that best fits the manner in which you want to use Asta Powerproject Enterprise and follow the instructions in that section. If you are not carrying on directly from the previous section, start by launching a command prompt on the server machine on which you have installed Asta Powerproject Enterprise, ensuring that you run it as Administrator, then change the directory location to the folder in which Asta Powerproject Enterprise has been installed (as described in the previous section). As with the installation of the Asta Name Server, if you are planning to use Asta Archive Manager to archive historic data from your projects, add web to whichever command you use to install the Enterprise server, to turn on web services that Asta Archive Manager requires to operate Installing the Enterprise server to run as a standard service If you install the Enterprise server to run as a standard service, it runs as a service with a name of <user name>_<machine name>, where <user name> is the name of the person who has logged onto the server machine and <machine name> is the name of the server machine itself. For example, if user JSMITH has logged onto a server machine called MAINSRV, the Enterprise server is run as a service on this machine with a name of JSMITH_MAINSRV. To install the Enterprise server to run as a standard service, enter the following at the command prompt: AstaEnterprise.exe install Installing the Enterprise server to run as a service with a specific name To install the Enterprise server to run as a service with a specific name, enter the following at the command prompt: AstaEnterprise.exe install <server name> Where <server name> is the name with which you want the service to run. The name must be a single word, with no spaces or punctuation. For example, to install the Enterprise server as a service so that it runs with the name AstaServer, enter: AstaEnterprise.exe install AstaServer 2016 Elecosoft UK Ltd

15 Installing the Enterprise server to run as a service with a specific identification number and name If you want to enable users to log in automatically using Active Directory, you must install the Enterprise server with a specific identification number and name. To install the Enterprise server to run as a service with a specific identification number and name, enter the following at the command prompt: AstaEnterprise.exe -server_id <server identification number> install <server name> Where <server identification number> is the number with which you want to identify the server and <server name> is the name with which you want the service to run. For example, to install the Enterprise server as a service so that it runs with the server identification number 1 and the name AstaProjectServer, enter: AstaEnterprise.exe -server_id 1 install AstaProjectServer Installing multiple Enterprise servers to run as services If you want to run more than one Enterprise server on a server machine, you must install each one with a specific identification number and name, as described in the previous section. For example, you could enter the following commands at the command prompt to install two Enterprise servers to run as services: AstaEnterprise.exe -server_id 1 install AstaServer1 AstaEnterprise.exe -server_id 2 install AstaServer Installing the Enterprise server to run as a service with specific dependencies Depending on which other services are installed on the server machine, you may experience problems in the following circumstances: If a service that is required for the Enterprise server or one of its components to operate does not run. If a service that prevents the Enterprise server or one of its components from operating does run. In particular, if you install the server to run as a service onto a server machine on which Oracle is installed, it is made dependent on all Oracle services (all services beginning with Ora ) by default. As well as potentially causing problems, this can degrade performance. You may want to install the Enterprise server to run as a service, while specifying the services on which it is dependent. To install the Enterprise server to run as a service and specify the services on which it is dependent, enter the following at the command prompt: AstaEnterprise.exe depend <dependencies> install Where <dependencies> is a comma-separated list of the services on which the service is dependent. For example, you could enter the following command at the command prompt to install the Enterprise server as a service that is dependent on the OracleServiceTEAMPLAN and MSSQLSERVER services: AstaEnterprise.exe depend OracleServiceTEAMPLAN,MSSQLSERVER install To incorporate a server identification number and server name into such a command, enter the following at the command prompt: AstaEnterprise.exe depend <dependencies> -server_id <server identification number> install <server name> 2016 Elecosoft UK Ltd

16 For example, to install the Enterprise server as a service that is dependent on the MSSQLSERVER service and so that it runs with the server identification number 1 and the name AstaProjectServer, enter: AstaEnterprise.exe depend MSSQLSERVER -server_id 1 install AstaProjectServer 2.6 Configuring the Asta Name Server and Enterprise server services Once you have installed the Asta Name Server and Enterprise server to run as services, they appear in the list of services in Windows Control Panel. Initially, both services are set to be started manually. You must configure the services to start automatically. To configure the Asta Name Server and Enterprise server services: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Control Panel. 2. Within Control Panel, select System and Security, then Administrative Tools. The Administrative Tools window appears. 3. Double-click the Services administrative tool. The Services window appears: 4. Locate the Asta Name Server and Asta Powerproject Enterprise Server services in the list (highlighted in the above illustration). If you have installed more than one Enterprise server to run as a service, a separate service will appear in the list for each Enterprise server. 5. Double-click one of the Asta services. The service s Properties dialog appears. 6. On the General tab of the dialog, select Automatic in the Startup type field: 2016 Elecosoft UK Ltd

17 7. Click OK to close the dialog. 8. Double-click the next Asta service in the list of services and repeat steps 6 and 7 to configure this service in the same way as the first. 9. If there are further Asta services in the list, configure these in the same way. 2.7 Configuring Asta Powerproject Enterprise registry settings There are a number of registry settings that affect the way in which Asta Powerproject Enterprise operates. Follow the instructions in this section to configure the registry settings in a way that suits your preferences Specifying whether baselines are pre-mounted completely Once you have created one or more projects in the Asta Powerproject Enterprise system, it is recommended that you specify that the projects and their baselines should be pre-mounted each time the Enterprise server starts (see section 4.9, Specifying that projects and their baselines should be pre-mounted, for more details). This is in order to speed up the mounting of projects and baselines, to reduce the usage of memory when projects are mounted and to prevent projects from being dismounted automatically when all users have finished working with them. However, some users prefer to maintain a slightly longer mounting process, as this can mean that the runtime performance of the Enterprise server is improved. You can use a registry key to specify whether baselines are pre-mounted completely when the Enterprise server starts, or whether only key (index) fields are mounted into memory, thereby reducing the amount of time taken to pre-mount baselines. To specify whether baselines should be pre-mounted completely when the Enterprise server starts: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Registry Editor. 2. In the left pane of Registry Editor, expand the registry to the following branch: HKEY_LOCAL_MACHINE\SOFTWARE\ASTA\PowerProject Teamplan\1.0\ DataSourceMount\ (32-bit systems). HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Asta\PowerProject Teamplan\1.0\DataSourceMount\ (64-bit systems). 3. In the right pane of Registry Editor, locate the KeyFieldsOnly registry key. This key determines whether or not baselines that are set to be premounted are mounted completely, or whether only key (index) fields are mounted into memory, thereby reducing the amount of time taken to mount baselines. The default, recommended value for this key is 2, which means that only key fields are mounted. 4. If you want to specify that baselines should be pre-mounted completely, edit the properties of this key and set its value to 0: 2016 Elecosoft UK Ltd

18 Although changing the behaviour in this way results in longer mounting times and greater memory usage, it also results in faster baseline updates, as baseline data does not have to be read into memory as and when it is required Specifying whether projects are recalculated at mount time If you experience a server problem or crash that prevents associated objects from being updated in line with each other, associated values can become mismatched. For example, a link may become detached from one of the tasks it is supposed to link. You can use a registry key to specify whether or not the Enterprise server recalculates projects and baselines at mount time, to check that all associated values match up with each other. Recalculating projects and baselines as they are mounted solves any such problems, but it also results in longer mounting times. To specify whether projects and baselines are recalculated at mount time: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Registry Editor. 2. In the left pane of Registry Editor, expand the registry to the following branch: HKEY_LOCAL_MACHINE\SOFTWARE\ASTA\PowerProject Teamplan\1.0\ DataSourceMount\ (32-bit systems). HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Asta\PowerProject Teamplan\1.0\DataSourceMount\ (64-bit systems). 3. In the right pane of Registry Editor, locate the RecalcOnMount registry key. This key determines whether or not projects and baselines are recalculated at mount time. The default value for this key is 1, which means that projects and baselines are recalculated at mount time. 4. To specify that projects and baselines should not be recalculated at mount time, edit the properties of this key and set its value to 1. Although changing the behaviour in this way results in shorter mounting times, it may lead to problems that result from mismatched associated values Elecosoft UK Ltd

19 2.7.3 Specifying database timeout settings You can use the following registry keys to specify how long the Enterprise server should wait for responses from your database: Use the ConnectionTimeout key to specify how long the Enterprise server should wait for a response from the database when connecting to it initially. If the value (in seconds) is exceeded, the Enterprise server assumes that the database is not available. Use the CommandTimeout key to specify how long the Enterprise server should wait for confirmation that a command that has been submitted to the database has been completed successfully. If the value (in seconds) is exceeded, the Enterprise server assumes that the command has failed. To specify database timeout settings: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Registry Editor. 2. In the left pane of Registry Editor, expand the registry to the following branch: HKEY_LOCAL_MACHINE\SOFTWARE\ASTA\PowerProject Teamplan\1.0\ EntSrv\ (32-bit systems). HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Asta\PowerProject Teamplan\1.0\EntSrv\ (64-bit systems). 3. In the right pane of Registry Editor, locate the ConnectionTimeout and CommandTimeout registry keys. 4. To specify different timeout settings, edit the properties of the keys and set their values to the required number of seconds. You may find that longer timeout values work better if you are working with extremely large volumes of data. 2.8 Installing an Oracle driver If you are using an Oracle database rather than Microsoft SQL Server, you must install a contemporary version of the Oracle Data Access Components for Oracle Client (ODAC) driver onto the server machine on which you have installed the Enterprise server. This driver must be installed in addition to the standard Oracle client software that is required in order to connect an Enterprise server to an Oracle data source. The earliest version of the driver that you must install is ODAC 11.2 Release 3 and Oracle Developer Tools for Visual Studio ( ) ; you can install a later version of this driver. The driver is freely available, with installation instructions, on Oracle s website. 2.9 Creating a data source in Asta Serveradmin You created a database when following the steps in section 2.1, Creating a Microsoft SQL Server database. You now need to create a corresponding data source in Asta Serveradmin, the application that you use to administer the Enterprises server. To create a data source in Asta Serveradmin: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Asta Serveradmin. 2. Select the New command from the Datasource menu. The New Datasource wizard appears Elecosoft UK Ltd

20 3. On the first screen of the wizard, enter a suitable name and description for the data source in the Name and Description fields; it is a good idea to give the data source a description that describes the projects that it will contain. 4. If you have installed more than one Enterprise server on the server machine or if you want to enable users to log in automatically via Active Directory, enter a positive integer that links the data source to a particular server in the Server identification number field: If you only use a single server and you are not using Active Directory to enable automatic login, you can leave this number set to 1. You can make a data source inaccessible to all servers (ie take it offline), by setting this number to zero. 5. Click Next. 6. On the next screen of the wizard, click Build to access the Connection String Generation wizard, which you can use to create the ActiveX Data Objects (ADO) connection string that specifies the database provider and the data source to which the Enterprise server should connect. 7. On the first screen of the wizard, click the Microsoft SQL Server database radio button: 8. Click Next. 9. On the second screen of the wizard, enter the name of the server machine on which you created the Microsoft SQL Server database in the Please enter the name of the machine that is running SQL Server field, noting the following points: If you are using Microsoft SQL Server 2012 Express, enter <server machine name>\sqlexpress, where <server machine name> is the name of the server machine. For example, if the server machine is called Server1, enter Server1\SQLExpress Elecosoft UK Ltd

21 If you are using Microsoft SQL Server 2012 Express and you have installed Asta Powerproject Enterprise onto the server machine on which your database is located, enter.\sqlexpress. If you are using a version of Microsoft SQL Server 2012 other than Express, simply enter the name of the server machine. For example, if the server machine is called Server1, enter Server Enter the name that you applied to the Microsoft SQL Server database when you created it in section 2.1, Creating a Microsoft SQL Server database, in the Please enter the catalog (database) to use field: 11. Click Next. 12. On the third screen of the wizard, enter the user name and password of the Microsoft SQL Server user that you created in section 2.2, Creating a Microsoft SQL Server database user and leave the Use SSPI integrated security check box cleared; if you use Windows authentication (in which Microsoft SQL Server interrogates Windows and grants access only to user accounts that are specified by the database administrator), do not enter a user name and password, but select the Use SSPI integrated security check box: 13. Click Finish to close the Connection String Generation wizard and return to the New Datasource wizard, where a connection string containing the information you have provided appears in the Connection string field: 14. Leaving the Optimise transaction data check box selected, select or clear the Server/database on same machine check box as appropriate depending on whether you have installed Asta Powerproject Enterprise on the server machine on which Microsoft SQL Server is installed Elecosoft UK Ltd

22 15. If you have installed Asta Powerproject Enterprise onto a different server machine, create a folder on the server machine on which Microsoft SQL Server is installed and give the user account that is being used to run the Asta Powerproject Enterprise server Full Control access rights to the folder. Temporary files will be stored in this folder. You must then specify the location of the folder in the Server/database shared folder field, in the format \\<server name\<path and folder name>. For example, if the server machine is called Server1 and the folder is on the root of the server and called AstaTemp, enter \\Server1\AstaTemp. 16. Click Test to test that the connection to the database works correctly. A message appears informing you whether or not the connection string is valid. 17. If the connection string is not valid, double-check the details of the database and user that you created, then create the connection string again. 18. Click Finish to close the New Datasource wizard. The new data source is created and appears in Asta Serveradmin: 2.10 Configuring Asta Powerproject Enterprise using Asta Serveradmin Once you have created a data source, you must follow the instructions in this section to use Asta Serveradmin to configure Asta Powerproject Enterprise. If the Enterprise server service is currently running, stop it before carrying out the steps described in this section, then restart it once you have finished configuring Asta Powerproject Enterprise using Asta Serveradmin Specifying the server location method in Asta Serveradmin You must specify the way in which you want the Asta Powerproject clients to locate the Enterprise server(s) that you have installed. To specify the server location method: 1. Within Asta Serveradmin, select the Set Locator command from the Server menu. The Server Location Method dialog appears. 2. Select the Asta Name Server check box, then enter either the IP address or the server name of the server machine on which you have installed the Asta Name Server. 3. Enter the number of seconds after which you want the Enterprise server to time out when it tries to connect to the Asta Name Server in the Asta Name Server timeout field. 4. The Asta Name Server pings for Enterprise servers every 20 seconds to determine which are available. Enter the number of minutes after which an unavailable Enterprise server should be removed from the Asta Name Server s list of servers in the Contact server timeout field. As servers may be unavailable temporarily as a result of network problems, for example entering a suitable timeout such as 5 minutes means that a server that is only unavailable temporarily is not removed unnecessarily from the Asta Name Server s list Elecosoft UK Ltd

23 5. Click OK Specifying the server temporary folder You must specify a folder on the server machine on which you have installed Asta Powerproject Enterprise into which the Enterprise server can store temporary files as it works. The server stores work-in-progress for the Asta Powerproject clients in order to be able to restore a client s work if the client crashes. As you can have more than one Enterprise server running on a server machine, the temporary files for each Enterprise server are stored in subfolders, each one unique to an Enterprise server, within the temporary folder you that you specify here. To specify the server temporary folder: 1. Within Asta Serveradmin, select the Set Temporary Folder command from the Server menu. The Browse For Folder dialog appears. 2. Select a folder on the server machine on which you have installed Asta Powerproject Enterprise in which to store temporary files; click Make New Folder to create a new folder at this point in time if a suitable folder does not already exist. 3. Click OK Specifying the audit logs folder and enabling audit logging You must specify a folder on the server machine on which you have installed Asta Powerproject Enterprise into which the Enterprise server can store audit logs as it works. The audit logs record which users perform which actions, the date and time on which the actions are performed, the applications that perform each action and the dates and times at which users log into and log out of projects. You can display audit logs from within Asta Serveradmin Elecosoft UK Ltd

24 If you have more than one data source, you can enable or disable audit logging for each one individually. Asta Serveradmin creates a subfolder for each data source for which audit logging is enabled. Every project in a data source has its own audit log file, <project name>.log, and its own usage log file, <project ID>_USAGE.LOG (where <project name> and <project ID> are the name and ID of the project respectively). Project audit logs continue to grow indefinitely, so if you edit a project regularly, you should delete the audit log files occasionally so that they do not take up too much disk space. To specify the audit logs folder: 1. Within Asta Serveradmin, select the Set Folder For Audit Logs command from the Server menu. The Browse For Folder dialog appears. 2. Select a folder on the server machine on which you have installed Asta Powerproject Enterprise in which to store audit logs; click Make New Folder to create a new folder at this point in time if a suitable folder does not already exist. 3. Click OK. To enable audit logging for a data source: 1. Within Asta Serveradmin, select the data source for which you want to enable audit logging. 2. Select the Properties command from the Datasource menu. The Datasource Properties dialog appears. 3. Click the Auditing tab. 4. Select the Generate auditing log for datasource check box: 5. Click OK. 6. Repeat the above steps to enable audit logging for each data source Elecosoft UK Ltd

25 Enabling users to log in automatically using Active Directory By default, users may have to enter their usernames and passwords once or twice to log in to a project in Asta Powerproject: Once to log in to the server (if there are server-level users defined). Once to log in to the project (if there are project-level users defined, and if the project-level username does not match the server-level username). Asta Powerproject Enterprise supports the Active Directory service, which catalogues information about all the objects on a network, including people, computers, and printers, and distributes that information throughout the network. Security is integrated with Active Directory through login authentication and access control. If you use Active Directory to manage the users on your network, you can configure Asta Powerproject Enterprise to allow users to log into servers and projects automatically, using the security and access control provided by Active Directory. This means that users do not have to enter user names and passwords when they log into their projects. To enable users to log in automatically using Active Directory: 1. Structure your users within Active Directory so that they belong to security groups which can be associated with specific Enterprise servers. For example, if you want one set of users (A) to have access to the data sources associated with server 1 and another set of users (B) to have access to the data sources associated with server 2, structure your Active Directory security groups so that the users belonging to set A are in one security group and the users belonging to set B are in another. 2. Associate each data source in Asta Serveradmin with a server identification number, so that when you link an Active Directory security group with a server identification number, the users within that security group will have access to the projects within the data sources that are associated with a particular server. Note that when using Active Directory to enable users to log in automatically, you must always start each Enterprise server with a unique name and identification number that corresponds to the server identification numbers you apply to your data sources. 3. Within Asta Serveradmin, select the Set Auto Login Information command from the Server menu. The List of Auto Login Information dialog appears: You use this dialog to specify the Active Directory security groups whose users you want to be able to log in automatically to each Enterprise server. 4. Click Add. The Add Active Directory Group dialog appears Elecosoft UK Ltd

26 5. Select the domain on which the security group is located in the Domain field. The Active Directory security groups within the domain appear in the Group field, listed within their hierarchy. 6. Select the security group whose users you want to be able to log in automatically in the Group field. 7. Enter the identification number of the server to which you want the users of the selected security group to be able to log into automatically in the Server ID field. 8. Click OK to confirm your selection and return to the List of Auto Login Information dialog. 9. If you have more than one Enterprise server, follow steps 4 to 8 for each server. 10. Click OK to close the dialog. 11. Create projects within Asta Powerproject within the appropriate data sources. Within each of the projects, create project-level users that correspond precisely to the users that are defined within Active Directory. The user names of the users you create within your projects must be identical to the names of the corresponding user in Active Directory. 12. Within your Asta Powerproject projects, apply a unique password to each project-level user. The passwords, which do not have to correspond with anything within Active Directory, prevent users within the same security group from accessing projects using the user name of another user within the same security group. 13. Within your Asta Powerproject projects, select the Active Directory Filtering check box on the General tab of the Options dialog. 14. Within Asta Serveradmin, specify that the Asta Powerproject projects should be mounted each time the Enterprise server(s) starts (see section 4.9, Specifying that projects and their baselines should be pre-mounted, for details of how to do this). Users within the selected security group can now log in automatically to the projects within the data sources that are associated with the specified Enterprise server. Note that you can select up to four separate security groups per server identification number, enabling their users to log in automatically. Although Asta Serveradmin contains additional configuration options, you have now completed the basic tasks that are required to configure Asta Powerproject Enterprise. Restart the Enterprise server service before continuing. Refer to the Asta Serveradmin Help for details of further configuration steps that you can carry out, for details of how to create user-defined fields in which to store your own information and for details of how to operate the Enterprise server using the Controller application, which is installed alongside the Enterprise server Configuring firewalls to work with Asta Powerproject Enterprise If you have installed Asta Powerproject Enterprise onto a server machine that is running Microsoft Windows 2008 Server R2 or later, you may find that your Asta Powerproject clients are unable to access your data sources and projects. This is a result of the Windows Firewall s default settings blocking communications to and from the Asta Name Server and the Enterprise server. You may notice similar problems if you use a firewall other than the Windows Firewall Elecosoft UK Ltd

27 If this is the case, follow the instructions in this section to configure your firewall to enable your Asta Powerproject clients, the Asta Name Server and the Enterprise server to communicate with each other. You do this by adding a number of inbound and outbound rules on the firewall on the server machine on which Asta Powerproject Enterprise has been installed. These instructions show how to configure the Windows Firewall, as this is the firewall that is used by default. If you use a different firewall, you should still follow the instructions in this section, adapting them as required to suit the firewall that you use Setting firewall rules for the Asta Name Server and Enterprise server To set up new inbound and outbound rules to enable communication with the Asta Name Server: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Windows Firewall. 2. In the left pane of the Windows Firewall, click Inbound Rules. The existing inbound rules are displayed in the middle pane. 3. Right-click Inbound Rules in the left pane and select New Rule. The New Inbound Rule wizard appears. 4. On the first screen of the wizard, click the Program radio button, then click Next: 5. On the second screen of the wizard, click the This program path radio button, then click Browse and locate the Asta Name Server application (AstaNameServer.exe) in the dialog that appears; it is located in the folder in which Asta Powerproject Enterprise has been installed. Select this and click Open to return to the second screen of the wizard, then click Next: 6. On the third screen of the wizard, click the Allow the connection radio button, then click Next: 2016 Elecosoft UK Ltd

28 7. On the fourth screen of the wizard, select the Domain check box, clear the Private and Public check boxes, then click Next: 8. On the fifth screen of the wizard, enter a name and description that will enable you to identify the new rule, then click Finish: 9. Right-click Outbound Rules in the left pane and select New Rule. The New Outbound Rule wizard appears. 10. Follow steps 4 to 8 above to create a new outbound rule in the same way that you created the inbound rule. You now need to set up similar inbound and outbound rules to enable communication with the Enterprise server. To do this, follow the steps above, but rather than specifying the Asta Name Server application on the second screen of the wizard, specify the Enterprise server (AstaEnterprise.exe, again located in the folder in which Asta Powerproject Enterprise has been installed) Setting firewall rules for specific ports If you have followed the instructions in the previous section to set up firewall rules for the Asta Name Server and the Enterprise server, but your Asta Powerproject clients are still unable to access your data sources and projects, follow the instructions in this section to set up firewall rules for specific ports. You must set up an inbound rule and an outbound rule for each of the following ports: 2016 Elecosoft UK Ltd

29 This port is used for communication between the Enterprise server and the Asta Name Server. 4199, 4200, 4201, These ports are used for communication between the Enterprise server and the Asta Powerproject clients. If you have a single Enterprise server service running on a server machine, you need only create rules for port 4199; if you have two Enterprise server services running, you need to create rules for ports 4199 and 4200; if you have three Enterprise server services running, you need to create rules for ports 4199, 4200 and 4201; and so on These ports are used for communication relating to notifications. The number of ports used depends on the number of client instances accessing the Enterprise server at any one time from a single computer (either from a client computer or from a Time Sheet or Web Access server). Port 4299 is used by all clients for notifications, but in some instances, multiple instances of a client can access the Enterprise server at the same time, resulting in more ports being used. As a result of this, you may need to create rules for the entire range of ports from 4299 to Follow the instructions below to set up new inbound and outbound rules for each of the above ports (or ranges of ports): 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Windows Firewall. 2. In the left pane of the Windows Firewall, click Inbound Rules. The existing inbound rules are displayed in the middle pane. 3. Right-click Inbound Rules in the left pane and select New Rule. The New Inbound Rule wizard appears. 4. On the first screen of the wizard, click the Port radio button, then click Next. 5. On the second screen of the wizard, click the TCP radio button. 6. Click the Specific local ports radio button and enter the port, or range of ports, to which the rule applies in the field to the right, then click Next: 7. On the third screen of the wizard, click the Allow the connection radio button, then click Next. 8. On the fourth screen of the wizard, select the Domain check box, clear the Private and Public check boxes, then click Next. 9. On the fifth screen of the wizard, enter a name and description that will enable you to identify the new rule, then click Finish. 10. Right-click Outbound Rules in the left pane and select New Rule. The New Outbound Rule wizard appears. 11. Follow steps 4 to 9 above to create a new outbound rule in the same way that you created the inbound rule, noting that the radio button mentioned in step 6 above is called Specific remote ports rather than Specific local ports in the New Outbound Rule wizard Elecosoft UK Ltd

30 3 Installing a licence server and Asta Licence Manager This section of the document describes how to install a licence server, on which are located the licences for your Elecosoft UK Ltd software applications, and the Asta Licence Manager application that enables you to manage the licences. It also describes how to obtain your licences from Elecosoft UK Ltd. The installation of Asta Licence Manager comprises the following steps: Choosing a server machine on which to install a licence server. Installing the Asta Licence Manager application. Obtaining your licences from Elecosoft UK Ltd. Configuring Elecosoft UK Ltd licensing in a Windows domain environment. Configuring Elecosoft UK Ltd licensing in a Windows workgroup environment. Configuring firewalls to work with the licence server. 3.1 Choosing a computer on which to install an Asta licence server When you install the Asta Licence Manager application, a licence server is installed automatically onto the same computer. However, you may want to install a licence server onto a different computer to the Asta Licence Manager, as this enables you to manage the licences contained within the licence server remotely, for example from the system administrator s computer. You do this by running the separate licence server installer which is available in the downloaded installation files. In normal practice, you will probably only want to install and use a single licence server, containing all of your licences. Ensure that you install the licence server onto a computer to which all of your Asta Powerproject clients can connect. Install the Asta Licence Manager onto any suitable computer that can connect to the computer on which you have installed the licence server, for example the system administrator s computer. Although one licence server is normally sufficient, you can install and use more than one, each on a different computer. You may want to install more than one licence server in the following circumstances: If you have an extremely large number of licences and want to spread the load over a number of different computers. If you want to set up different licence servers to serve different communities within your network. If you want to set up different licence servers to serve different product types. For example, you could have one licence server containing your normal licences, and another containing your read-only licences. If you want to set up a second licence server as a backup, containing a number of spare licences for use in the event of the failure of your main licence server (this would of course cost more in terms of the additional spare licences). The computer on which you install Asta Licence Manager will ideally be a physical machine, although it is possible to install it onto a virtual machine. If you choose to install Asta Licence Manager onto a virtual machine, the following restrictions apply: 2016 Elecosoft UK Ltd

31 If you copy, clone or upgrade a virtual machine image on which Asta Licence Manager is installed, the licences are unavailable in the copied, cloned or upgraded virtual machine and you are unable to add any licences to the copy, clone or upgrade. You cannot move a licence from a licence server that has been installed onto a virtual machine. A warning message appears if you attempt to do so. If you attempt to move a licence from a licence server that has been installed onto a physical computer to an Asta software client or to a licence server that has been installed onto a virtual machine, you are warned that the move cannot be reversed and asked if you wish to continue. You are able to loan an Asta Powerproject licence from a licence server that has been installed onto a virtual machine, but that loan will be subject to a maximum of 30 days. 3.2 Installing the Asta Licence Manager application To install Asta Licence Manager: 1. Log into the computer on which you are going to install Asta Licence Manager as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears. 4. Follow the steps in the installation wizard to install Asta Licence Manager, clicking Next to move between the various screens of the wizard. 5. Click Install on the final screen of the wizard to install Asta Licence Manager. 6. When the installation routine is complete, click Finish to exit the wizard. If you want to install an Asta licence server onto a separate computer, you can now do so by running the separate licence server installer, which is available in the downloaded installation files, on the other computer. 3.3 Obtaining your licences from Elecosoft UK Ltd Once you have installed Asta Licence Manager, you can use the application to obtain the licences that you need for your Elecosoft UK Ltd software. To obtain your licences from Elecosoft UK Ltd: 1. Launch Asta Licence Manager on the computer on which you have installed it. 2. Click the Request tab: 2016 Elecosoft UK Ltd

32 3. Enter the name of the computer on which the licence server for which you want to request licences is installed in the Server name field. Alternatively, click Browse to search the network for a licence server. 4. Select the product for which you want to request a licence in the Product field. 5. Select the Read only client check box if you want to request a licence for a read-only version of Asta Powerproject, or select the Educational client check box if you want to request a licence for an educational version. Leave both check boxes clear to request a standard licence. 6. Click Generate. 7. Asta Licence Manager generates a licence request key, which is displayed in the Licence request key field. You must transfer the licence request key to Elecosoft UK Ltd s Technical Support department. 8. Click Copy to copy the licence request key to the Windows Clipboard. 9. Paste the licence request key into an , entitled NEW LICENCE REQUEST, and send it to support@elecosoft.com. 10. Once you have transferred the licence request key to Elecosoft UK Ltd, the Technical Support department will send you a licence code. Copy the licence code that you have received to the Windows Clipboard. 11. Within Asta Licence Manager, click the Add tab: 12. Click Paste to paste the licence code into the Licence key field. 13. Click Add. A licence or licences of the type you requested is added to the selected licence server Elecosoft UK Ltd

33 3.4 Configuring Elecosoft UK Ltd licensing in a Windows domain environment The instructions in this section assume that you are working in a Windows domain environment. If you are working in a Windows workgroup environment, ignore the instructions in this section and refer to section 3.5, Configuring Asta licensing in a Windows workgroup environment. The absence of a Domain users group (referred to below) indicates that you are working in a Windows workgroup environment. If you are not sure whether you are working in a domain environment or in a workgroup environment, consult with your IT staff. After you have obtained your licences from Elecosoft UK Ltd, you need to configure the computer on which your licence server is located to enable users to access the licences. Note that domain administrators have access to the licences by default, so you should use a non-administrator user to test access to the licences. Before you configure the licence server machine, you should choose an Active Directory group with which to control access to licences. Which group you use will depend on whether you want to allow or deny access to the licences by default. Two common choices are as follows: The Distributed COM users group. Users would not be a member of this group by default and would be denied access to the licences unless they were added to this group. The Domain users group. Users would be a member of this group by default and the licences would be freely accessible to anybody who is logged into the domain. To configure the licence server machine: 1. On the computer on which you have installed the licence server, launch Control Panel. 2. Within Control Panel, select System and Security, then Administrative Tools. The Administrative Tools window appears. 3. Double-click the Component Services administrative tool. The Component Services window appears: 4. Double-click the Computers folder in the middle pane of the Component Services window. The My Computer icon appears. 5. Right-click My Computer and select Properties. The My Computer Properties dialog appears. 6. On the Default Properties tab of the dialog, ensure that the Enable Distributed COM on this computer check box is selected: 2016 Elecosoft UK Ltd

34 7. On the COM Security tab of the dialog, click Edit Limits in the Launch and Activation Permissions group: The Launch and Activation Permission dialog appears: 8. Click Add. The Select Users, Computers, Service Accounts, or Groups dialog appears: 9. In the Enter the object names to select field, enter the name(s) of the individual users or the name of the Active Directory group that contains the users who are to use the licences. 10. Click Check Names to ensure that you have entered the user or group name correctly. 11. Click OK to return to the Launch and Activation Permission dialog. 12. With the new group selected in the Group or user names field, select all four Allow check boxes in the Permissions for field, then click OK. 13. Click OK to close the My Computer Properties dialog Elecosoft UK Ltd

35 14. In the left pane of the Component Services window, navigate through the folders to view the DCOM Config folder (Console Root Component Services Computers My Computer DCOM Config), then double-click the folder to open it: 15. Right-click the Asta Licence Server entry within the folder and select Properties. The Asta Licence Server Properties dialog appears. 16. On the Security tab, in the Launch and Activation Permissions group, click the Customize radio button: 17. In the same group of fields, click Edit. The Launch and Activation Permission dialog appears. 18. As you did before, use this dialog to enter the name(s) of the individual users or the name of the Active Directory group that contains the users who are to use the licences and select all four Allow check boxes in the Permissions for field, then click OK. 19. Repeat steps for the Access Permissions and Configuration Permissions groups of fields in the Asta Licence Server Properties dialog. 20. On the Endpoints tab, click Add. The Select DCOM Protocol and Endpoint dialog appears: 21. Select Connection-oriented TCP/IP in the Protocol sequence field, then click OK to close the dialog. Connection-oriented TCP/IP now appears in the DCOM protocols and endpoints field on the Security tab of the Asta Licence Server Properties dialog. 22. Click OK to close the Asta Licence Server Properties dialog. 23. Close the Component Services window. Your licences are now ready for use Elecosoft UK Ltd

36 3.5 Configuring Asta licensing in a Windows workgroup environment The instructions in this section assume that you are working in a Windows workgroup environment. If you are working in a Windows domain environment, ignore the instructions in this section and refer to section 3.4, Configuring Elecosoft UK Ltd licensing in a Windows domain environment. If you are not sure whether you are working in a domain environment or in a workgroup environment, consult with your IT staff. Asta Licence Manager is intended primarily for use in a Windows domain environment. Despite this, it is possible to use it in a Windows workgroup environment, although as Windows workgroup is not the intended environment, the procedure for configuring Elecosoft UK Ltd licensing in this environment is somewhat cumbersome. If you are working in a Windows workgroup environment, you should direct the member of your organisation s IT staff who is responsible for your network infrastructure towards the information in this section, as it is likely that they will need to assist with configuring the network; they will also need to confirm that they are happy to carry out the configuration steps as described below, as there are implications to the security of the network. Configuring Elecosoft UK Ltd licensing in a Windows workgroup environment comprises two steps: Configuring the licence server machine. Mirroring Windows user account details for each user. These two steps are described below Configuring the Asta licence server machine After you have obtained your licences from Elecosoft UK Ltd, you need to configure the computer on which your licence server is located to enable users to access the licences. When working in a Windows workgroup environment, you need to use the Everyone Active Directory group to control access to licences. This means that licences will be freely accessible to everyone in the Windows workgroup. To configure the licence server machine: 1. On the computer on which you have installed the licence server, launch Control Panel. 2. Within Control Panel, select System and Security, then Administrative Tools. The Administrative Tools window appears. 3. Double-click the Component Services administrative tool. The Component Services window appears: 4. Double-click the Computers folder in the middle pane of the Component Services window. The My Computer icon appears. 5. Right-click My Computer and select Properties. The My Computer Properties dialog appears Elecosoft UK Ltd

37 6. On the Default Properties tab of the dialog, ensure that the Enable Distributed COM on this computer check box is selected: 7. On the COM Security tab of the dialog, click Edit Limits in the Access Permissions group: The Access Permission dialog appears: 8. If Everyone does not appear in the Group or user names field, Click Add. The Select Users, Computers, Service Accounts, or Groups dialog appears (if Everyone already appears in this field, move onto step 12): 9. In the Enter the object names to select field, enter Everyone. 10. Click Check Names to ensure that you have entered the group name correctly. 11. Click OK to return to the Access Permission dialog Elecosoft UK Ltd

38 12. With Everyone selected in the Group or user names field, select all of the Allow check boxes in the Permissions for field, then click OK. 13. On the COM Security tab of the My Computer Properties dialog, click Edit Default in the Access Permissions group, then follow steps 8 to 12 above. 14. On the COM Security tab of the My Computer Properties dialog, click Edit Limits in the Launch and Activation Permissions group, then follow steps 8 to 12 above. 15. On the COM Security tab of the My Computer Properties dialog, click Edit Default in the Launch and Activation Permissions group, then follow steps 8 to 12 above. 16. Click OK to close the My Computer Properties dialog. A warning appears to inform you that you are about to modify machine-wide DCOM settings and that some applications may not work correctly as a result. Taking heed of the warning, click Yes to continue. 17. In the left pane of the Component Services window, navigate through the folders to view the DCOM Config folder (Console Root Component Services Computers My Computer DCOM Config), then double-click the folder to open it: 18. Right-click the Asta Licence Server entry within the folder and select Properties. The Asta Licence Server Properties dialog appears. 19. On the Security tab, click the Use default radio buttons in the Launch and Activation Permissions and Access Permissions groups: 20. Click OK to close the Asta Licence Server Properties dialog Mirroring Windows user account details for each user Once you have configured the computer on which your licence server is located, you must mirror the Windows users account details for each of your Asta Powerproject users on that computer (this is handled automatically when working in a Windows domain environment, but not when working in a Windows workgroup environment) Elecosoft UK Ltd

39 To do this, you need to add each user s Windows account (ie their Windows user name and password) to the licence server machine. Each user name and password must be entered precisely as it is used on the appropriate user s workstation. Take particular care over any capitalisation and punctuation that is used in the user names and passwords, as the slightest error (for example, entering a user name as Jennifer_Smith rather than as Jennifer.Smith ) would mean that the user would be unable to use their Elecosoft UK Ltd licence. If a user changes their workstation password at a later date, note that you must update the user s account manually on the licence server machine in order for the user to carry on using their Elecosoft UK Ltd licence. There are a number of ways of adding Windows accounts to a Windows computer. Your IT staff should be able to do this; for your convenience, a brief overview of the procedure is given below: 1. On the computer on which you have installed the licence server, launch a command prompt, ensuring that you run it as Administrator. A command prompt window appears: 2. Type lusrmgr.msc and press ENTER. The lusrmgr window appears: 3. Select the New User command from the Action menu. The New User dialog appears: 2016 Elecosoft UK Ltd

40 4. Enter details of the Windows user account of one of your Asta Powerproject users, ensuring that the user name and password are entered precisely as they are used on the appropriate user s workstation. Ensure that the User must change password at next logon check box is not selected. You may also like to select the Password never expires check box, to cut down on future password maintenance work on the Asta licence server machine. 5. Click OK to close the dialog and create the new user. 6. Repeat steps 3 to 5 above to add details of the Windows user accounts for each Asta Powerproject user. 7. In the left pane of the window, double-click the Users folder. 3.6 Configuring firewalls to work with the Asta licence server If you use a firewall for example, the Windows Firewall you must configure the firewall to enable your Asta Powerproject clients to connect to your licence server. You do this by adding a number of inbound and outbound rules on the following computers: The computer on which the licence server has been installed. The computer on which Asta Licence Manager has been installed. The computers on which the Asta Powerproject client applications are installed. Both the Asta Powerproject clients and the Asta Licence Manager application use the astalicenceserver.exe application, which is located in C:\Program Files\Common Files\Asta\ (or C:\Program Files (x86)\common Files\Asta\ for 64-bit operating systems) for communication across the network, using port 135. It is recommended that you create firewall rules for the astalicenceserver.exe executable rather than for port 135, as this allows only the Asta Powerproject clients and the Asta Licence Manager application to access the port. These instructions show how to configure the Windows Firewall, as this is the firewall that is used by default. If you use a different firewall, you should still follow the instructions in this section, adapting them as required to suit the firewall that you use. To set up new inbound and outbound rules to enable Asta Powerproject clients to communicate with the licence server: 1. On the computer on which you have installed the licence server, launch Windows Firewall. 2. In the left pane of the Windows Firewall, click Inbound Rules. The existing inbound rules are displayed in the middle pane. 3. Right-click Inbound Rules in the left pane and select New Rule. The New Inbound Rule wizard appears. 4. On the first screen of the wizard, click the Program radio button, then click Next. 5. On the second screen of the wizard, click the This program path radio button, then click Browse and locate astalicenceserver.exe in the dialog that appears; it is located in C:\Program Files\Common Files\Asta\ (or C:\Program Files (x86)\common Files\Asta\ for 64-bit operating systems). Select this and click Open to return to the second screen of the wizard, then click Next. 6. On the third screen of the wizard, click the Allow the connection radio button, then click Next Elecosoft UK Ltd

41 7. On the fourth screen of the wizard, select the Domain check box, clear the Private and Public check boxes, then click Next. 8. On the fifth screen of the wizard, enter a name and description that will enable you to identify the new rule, then click Finish. 9. Right-click Outbound Rules in the left pane and select New Rule. The New Outbound Rule wizard appears. 10. Follow steps 4 to 8 above to create a new outbound rule in the same way that you created the inbound rule. 11. Repeat the above steps to create new inbound and outbound rules on the computer on which Asta Licence Manager has been installed (if this is a different computer) and on each computer on which an Asta Powerproject client application is installed Elecosoft UK Ltd

42 4 Installing the Asta Powerproject client application This section of the document describes how to install the Asta Powerproject client application. You should carry out the instructions in this section to install the Asta Powerproject client on each computer that is going to access the Enterprise server. The installation of the Asta Powerproject client comprises the following steps: Preliminary steps if installing onto a Terminal Server or Citrix server. Installing an Asta Powerproject Enterprise client. Activating the Asta Powerproject client application. Configuring file locations in the Asta Powerproject client. Setting the server location method in the Asta Powerproject client. Checking that the client can connect to the Enterprise server. Additional steps if you have an Asta Powerproject BIM licence. Additional steps if installing onto a Terminal Server or Citrix server. Specifying that projects and their baselines should be pre-mounted. 4.1 Preliminary steps if installing onto a Terminal Server or Citrix server If you are installing an Asta Powerproject Enterprise client onto a Terminal Server or a Citrix server, you must first carry out a number of preliminary steps, as described below. If you are installing onto a standard computer, ignore the instructions in this section and move onto the next section. To prepare the Terminal Server or Citrix server for installation: 1. Log into the Terminal Server or a Citrix server machine as a user with Administrator privileges. 2. Launch a command prompt. 3. In the command prompt window, type change logon /disable and press ENTER in order to disable logins to sessions and to ensure that no users are currently connected. You see a confirmation that logins are now disabled. 4. Type change user /install and press ENTER in order to set the Terminal Server or Citrix server into install mode. You see a confirmation that the server machine is now ready to install applications. 4.2 Installing an Asta Powerproject Enterprise client If you currently have a non-enterprise version of Asta Powerproject installed on a computer and are moving to Asta Powerproject Enterprise, you cannot upgrade to an Asta Powerproject Enterprise client by simply installing the Enterprise client over the top of your existing client. In this situation, you must uninstall your existing Asta Powerproject client, then install the Enterprise client in its place. To install an Asta Powerproject Enterprise client: 1. Log into the computer on which you are going to install the Asta Powerproject Enterprise client as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears Elecosoft UK Ltd

43 4. Follow the steps in the installation wizard to install the Asta Powerproject Enterprise client, clicking Next to move between the various screens of the wizard. The Asta Powerproject Enterprise client is installed into the following folder by default: C:\Program Files\Asta\Asta Powerproject\ (32-bit systems). C:\Program Files(x86)\Asta\Asta Powerproject\ (64-bit systems). 5. If you want to install the Asta Powerproject Enterprise client to a location other than the default, click the Custom radio button on the Setup Type screen, which will give you access to an additional page of the wizard in which you can specify an installation folder. 6. If you are installing the Asta Powerproject Enterprise client onto a Terminal Server or a Citrix server, select the Install licence server as a service check box on the Setup Type screen of the wizard. This installs the licence server as a service, which is required for Terminal Server and Citrix installations. If you forget to select this check box during the installation of the client, follow the instructions in section 4.2.1, Installing the licence server as a service, to install the licence server as a service after you have completed the Asta Powerproject Enterprise client installation. 7. Click Install on the final screen of the wizard to install the Asta Powerproject Enterprise client. 8. When the installation routine is complete, click Finish to exit the wizard. 9. Reboot the computer on which you have installed the Asta Powerproject Enterprise client, if you are requested to do so Installing the licence server as a service If you have installed an Asta Powerproject Enterprise client onto a Terminal Server or a Citrix server and you did not select the Install licence server as a service check box on the Setup Type screen of the installation wizard, you must follow the instructions in this section to install the licence server as a service after you have completed the Asta Powerproject Enterprise client installation. If you have installed the Asta Powerproject Enterprise client onto a standard computer, or if you selected the Install licence server as a service check box, ignore the instructions in this section. To install the licence server as a service: 1. Launch Windows Task Manager and verify that AstaLicenceServer.exe does not appear in the list on the Processes tab. If it does appear, select it and click End Process to terminate it. 2. Close Windows Task Manager. 3. Launch a command prompt, ensuring that you run it as Administrator. A command prompt window appears: 2016 Elecosoft UK Ltd

44 4. In the command prompt window, change the directory location to the following folder: C:\Program Files\Common Files\Asta\ (32-bit systems). C:\Program Files(x86)\Common Files\Asta\ (64-bit systems). 5. Type astalicenceserver.exe /unregserver and press ENTER. 6. Type astalicenceserver.exe /install and press ENTER. 7. Within Control Panel, select System and Security, then Administrative Tools. The Administrative Tools window appears. 8. Double-click the Services administrative tool. The Services window appears. 9. Locate the Asta Licence Server service in the list. 10. Double-click the service. The service s Properties dialog appears. 11. On the General tab of the dialog, select Automatic in the Startup type field, then click Start to start the service. 12. Click OK to close the dialog. If a message appears informing you that the service could not start, launch Windows Task Manager again and check whether a copy of the AstaLicenceServer.exe process appears in the list on the Processes tab. If a copy does appear, terminate the copy then try to start the service again. Instead of following the steps above, you can download and run the following utility, which automates the above steps: Activating the Asta Powerproject client application Once you have installed an Asta Powerproject client, you can use it for a trial period without activating it. You must activate the Asta Powerproject client by the end of this period in order to continue using it once the trial period is over. You can activate the Asta Powerproject client at any time during this period. Until you activate the Asta Powerproject client, an activation reminder appears each time you start the software. Depending on your installation of Asta Powerproject Enterprise, you may have either of the two following types of licence: A named user licence. A concurrent licence, which is located on a licence server. If you have an internet connection, you can activate Asta Powerproject automatically over the internet. If you do not have an internet connection, you can activate Asta Powerproject manually with the aid of Elecosoft UK Ltd s Technical Support department. Activating Asta Powerproject over the internet is quicker and easier than activating it via the Technical Support department. If you activate the Windows firewall on a computer on which an Asta Powerproject client is installed, you must define astalicenceserver.exe and Port 135 as exceptions in the firewall before attempting to activate Asta Powerproject. See section 3.6, Configuring firewalls to work with the Asta licence server, for more details. If you install Asta Powerproject onto a virtual machine and activate the software, you are warned that the activation cannot be undone. This means that you will be unable to subsequently install and activate Asta Powerproject on a different computer Elecosoft UK Ltd

45 4.3.1 Activating Asta Powerproject using a named user licence To activate an Asta Powerproject client using a named user licence: 1. Ensure that you have an active internet connection on the computer on which you have installed the Asta Powerproject client. 2. On the computer on which you have installed the Asta Powerproject client, launch Asta Powerproject. A message appears informing you that you can use Asta Powerproject for a trial period and that you must activate it at some point during the trial period. 3. Click Activate. The Product Activation dialog appears. 4. Enter details into the fields on the dialog you must complete all of the fields and you must enter a valid address in the address field then click OK. Asta Powerproject attempts to activate itself automatically over the internet. If your serial number is associated with a named user licence, a dialog appears to inform you that the activation was successful when the activation is complete. You can now continue to use Asta Powerproject. 5. If your serial number is associated with a concurrent licence one that is contained within a licence server the Locate Licence Server dialog appears. Enter the name of the computer on which the licence server is located and click OK. Asta Powerproject attempts to contact the licence server on the specified computer and, if a successful connection is made, a dialog appears to inform you that Asta Powerproject is now configured to obtain its licence from the specified licence server. You can now continue to use Asta Powerproject. In some cases, automatic activation may not be successful. Automatic activation will not work in the following circumstances: If you do not have a connection to the internet, or if your connection to the internet is not currently active. If Elecosoft UK Ltd s automatic activation service is currently unavailable. If you have installed and are attempting to activate a single copy of Asta Powerproject on more than one computer. If you are reinstalling Asta Powerproject on a computer whose hardware has been altered significantly. If automatic activation fails, a dialog that informs you of the problem will appear and you will either be asked to activate Asta Powerproject manually or to contact Elecosoft UK Ltd s Technical Support department for assistance Activating Asta Powerproject using a concurrent licence To activate an Asta Powerproject client using a concurrent licence that is located on a licence server: 1. On the computer on which you have installed the Asta Powerproject client, launch Asta Powerproject. A message appears informing you that you can use Asta Powerproject for a trial period and that you must activate it at some point during the trial period. 2. Click either Continue Trial or Activate Later (depending on whether the trial period has ended). The main Asta Powerproject window appears. 3. Click File, then click Activation. The Activation tab of the Backstage view appears Elecosoft UK Ltd

46 4. Click Configure. The Product Activation Configuration wizard appears: 5. Enter the name or IP address of the computer on which the licence server is located in the field on the next screen of the wizard, then click Next. 6. Click Finish on the final screen of the wizard. If a licence is available on the licence server on the named computer, you can now continue to use Asta Powerproject. 4.4 Configuring file locations in the Asta Powerproject client Before you start using Asta Powerproject, it is a good idea to check that the file locations are set correctly in the client. You can specify the locations in which the Asta Powerproject client should expect to find a variety of different file types. To configure file locations in the Asta Powerproject client application: 1. Launch the Asta Powerproject client. 2. Click File, then click Options. The Options dialog appears. 3. Click the File Locations tab: 4. Select a file location in the list and click Modify to change the location if required Elecosoft UK Ltd

47 5. You may want to select the Only use the given file locations check box to prevent additional templates and borders from being presented to you when you create new projects and print. If you clear this check box, templates and borders in other locations for example, the folder in which Asta Powerproject has been installed may be presented to you in addition to the templates and borders that are stored in the folders specified on this dialog. 6. Click OK. 4.5 Specifying the server location method in the Asta Powerproject client You must specify the way in which you want the Asta Powerproject client to locate the Enterprise server(s) that you have installed. The server location details that you specify in the client must match those that you specified in section , Specifying the server location method in Asta Serveradmin. To specify the server location method in the Asta Powerproject client application: 1. Within the Asta Powerproject client, click File, then click Info. The Info tab of the Backstage view appears. 2. Click Server Locator. The Client/Server Communication Details dialog appears. 3. Select the Asta Name Server check box, then enter either the IP address or the server name of the server machine on which you have installed the Asta Name Server: 4. Click OK. 4.6 Checking that the client can connect to the Enterprise server The Asta Powerproject client should now be able to locate the Enterprise server and access the data source that you created. To check that the client can connect to the Enterprise server and access the data source: 1. Within the Asta Powerproject client, click File, then click New. The New tab of the Backstage view appears: 2016 Elecosoft UK Ltd

48 2. Click Browse. The New dialog appears: 3. In the bar on the left of the dialog, click Server Projects. The server and data source that you created should appear in the dialog, and you should be able to create a project in the data source. If the server and/or data source do not appear in the New dialog, try the following steps to track down the problem: Install an Asta Powerproject client on the server machine on which you have installed the Enterprise server and check whether this client can access the server and data source. If it can, but a client that is installed on another computer cannot, it is possible that the problem is a firewall, network or access rights issue. See section 2.11, Configuring firewalls to work with Asta Powerproject Enterprise, for details of how to configure your firewall to allow your Asta Powerproject clients to connect to the Enterprise server. Stop the Enterprise server service and run the Enterprise server as an application (AstaEnterprise.exe, located in the folder in which Asta Powerproject Enterprise was installed). After this, launch the client again and attempt to connect. If the client can see the Enterprise server when it is running as an application but not when it is running as a service, try editing the properties of the Enterprise server and Asta Name Server services and change the login accounts under which they run Elecosoft UK Ltd

49 If you are not configuring Asta Powerproject Enterprise to allow users to log into servers and projects automatically via Active Directory (as described in section , Enabling users to log in automatically using Active Directory), click File, then click Options to access the Options dialog. On the General tab, clear the Active Directory server filtering check box, then click OK: If you are using a single data source only, on the server machine on which you have installed Asta Powerproject Enterprise, launch Asta Serveradmin and check whether the server ID of the data source is set to 1. This is visible in the data source details that are displayed on the main Asta Serveradmin screen: If the server ID of the data source is set to anything other than 1, edit the properties of the data source and correct this. Check that the same server location method details have been specified both in Asta Serveradmin and in the Asta Powerproject client. See sections , Specifying the server location method in Asta Serveradmin and 4.5, Specifying the server location method in the Asta Powerproject client, for details of how to do this. If and only if the server machine on which you have installed Asta Powerproject Enterprise has multiple network cards, you must associate Asta Powerproject Enterprise with a single IP address. To do this, launch Asta Serveradmin and select the Set Listener Endpoint command from the Server menu to access the Set Listener Endpoint dialog: Click the Always use the following IP address for the endpoint radio button, enter the IP address of the listener endpoint that you want Asta Powerproject Enterprise to use, then click OK. Note that if you make any changes in Asta Serveradmin, you will need to restart the Asta services afterwards in order for the changes to take effect. Restart the Asta Name Server service first, followed by the Enterprise server service Elecosoft UK Ltd

50 4.7 Additional steps if you have an Asta Powerproject BIM licence If you have a licence for Asta Powerproject BIM, you must carry out two additional steps, as described below, once you have installed the Asta Powerproject client application. If you do not have a licence for Asta Powerproject BIM, ignore the instructions in this section Ensure that the computer has access to the Elecosoft BIMCloud Once you have installed the Asta Powerproject client application onto a computer, you must ensure that all user accounts that need to access the Elecosoft BIMCloud on that computer are able to do so via HTTP, using the following URL: You may need to allow access to the URL if your IT configuration applies restrictions to HTTP traffic. If you use locally-stored IFC files only with Asta Powerproject BIM, you do not need to ensure access to the Elecosoft BIMCloud Download and install Microsoft DirectX End-User Runtimes The Microsoft DirectX End-User Runtimes must be installed on the computer on which Asta Powerproject BIM is installed. If you install Asta Powerproject BIM onto a computer that does not have the DirectX End-User Runtimes installed, a warning appears when you attempt to display the IFC Model pane. You can download and install the required DirectX End-User Runtimes from the following location: Additional steps if installing onto a Terminal Server or Citrix server If you are installing an Asta Powerproject Enterprise client onto a Terminal Server or a Citrix server, you must carry out an additional step, as described below, once you have installed the Asta Powerproject Enterprise client. If you are installing onto a standard computer, ignore the instructions in this section. To reset the Terminal Server or Citrix server after installation: 1. Log into the Terminal Server or a Citrix server machine as a user with Administrator privileges. 2. Launch a command prompt. 3. In the command prompt window, type change user /execute and press ENTER in order to set the Terminal Server or Citrix server back into execute mode. You see a confirmation that the server machine is now ready to execute applications. 4. Type change logon /enable and press ENTER in order to re-enable logins to sessions. You see a confirmation that logins are now enabled Elecosoft UK Ltd

51 4.9 Specifying that projects and their baselines should be premounted Once you have created one or more projects in the Asta Powerproject Enterprise system, it is recommended that you specify that the projects and their baselines should be pre-mounted each time the Enterprise server starts. This is in order to speed up the mounting of projects and baselines, to reduce the usage of memory when projects are mounted and to prevent projects from being dismounted automatically when all users have finished working with them. If you choose not to pre-mount a project, it is mounted when it is opened, and dismounted when all users have finished working with it. To specify that a project and its baselines should be pre-mounted when the Enterprise server starts: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Asta Serveradmin. 2. Select the Pre-Mount Settings command from the Server menu. The Pre- Mount Settings dialog appears. The dialog lists all projects that are currently configured to be pre-mounted. 3. Click Add. The Add Pre-Mount Project dialog appears: 4. Specify whether you want to pre-mount the project only, or the project and its baselines, in the Pre-mount type field. It is recommended that you premount both projects and their baselines. 5. Select the data source in which the project is located in the Datasource field. 6. Enter the ID of the project that you want to pre-mount in the Project ID field. 7. Click OK to return to the Pre-Mount Settings dialog. The project is added to the list. 8. Repeat steps 3 to 7 to specify that any additional projects should be premounted. 9. Click OK to confirm your changes and close the Pre-Mount Settings dialog. If you want to pre-mount two projects in different data sources that share the same project ID, you must not enter their details into the Pre-Mount Settings dialog during the same dialog session; if you do this, only one of the projects that shares the project ID will be pre-mounted. In this situation, you must access the Pre- Mount Settings dialog, specify one of the projects and close the dialog, then reenter the dialog and specify the second project Elecosoft UK Ltd

52 5 Installing Asta Archive Manager This section of the document describes how to install Asta Archive Manager, which enables users to archive historic data from live projects into archive files, then restore them as required. Asta Archive Manager comprises the following elements: The Asta Archive Manager application. This is an application that enables the archiving and restoration of data from your Asta Powerproject projects. This application should be installed either onto the same machine as the Enterprise server or onto another computer on the network. Asta Archive Components. The Asta Archive Components, which have no user interface, are installed automatically onto the server machine on which your Enterprise server is located when you carry out an Asta Powerproject Enterprise installation. The installation of Asta Archive Manager comprises the following steps: Installing the latest version of Asta Powerproject Enterprise. Configuring your Asta services to work with Asta Archive Manager. Installing the Asta Archive Manager application. Setting up proxy exceptions for the archiving web services. Configuring Windows to enable the use of distributed transactions. Configuring the distributed transaction timeout setting. 5.1 Installing the latest version of Asta Powerproject Enterprise Before you install Asta Archive Manager, you must ensure that you have installed, or upgraded to, the latest version of Asta Powerproject Enterprise. This is to ensure that the Asta Archive Components are installed onto the server machine on which the Enterprise server is located. Follow the instructions in section 12, Upgrading an Asta Powerproject Enterprise installation to the latest version, in order to upgrade to the latest version of Asta Powerproject Enterprise. 5.2 Configuring your Asta services to work with Asta Archive Manager If you have been working with Asta Powerproject Enterprise for some time and you have not installed Asta Archive Manager before, you must configure the Enterprise server and Asta Name Server services to work with Asta Archive Manager. This involves stopping and removing the services, then reinstalling them configuring them to work with Asta Archive Manager and to start automatically, as they did before. To configure your Asta services to work with Asta Archive Manager: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Control Panel. 2. Within Control Panel, select System and Security, then Administrative Tools. The Administrative Tools window appears. 3. Double-click the Services administrative tool. The Services window appears: 2016 Elecosoft UK Ltd

53 4. Locate the Asta Name Server and Asta Powerproject Enterprise Server services in the list (highlighted in the above illustration). If you have installed more than one Enterprise server to run as a service, a separate service will appear in the list for each Enterprise server. 5. Double-click one of the Asta services. The service s Properties dialog appears. 6. On the General tab of the dialog, select Manual in the Startup type field: 7. Click OK to close the dialog. 8. Double-click the next Asta service in the list of services and repeat steps 6 and 7 to configure this service in the same way as the first. 9. If there are further Asta services in the list, configure these in the same way. 10. Reboot the server machine on which you have installed Asta Powerproject Enterprise. When it restarts, the Asta services will not start automatically. 11. Launch a command prompt, ensuring that you run it as Administrator. A command prompt window appears: 2016 Elecosoft UK Ltd

54 12. In the command prompt window, change the directory location to the folder in which Asta Powerproject Enterprise has been installed, which is, by default: C:\Program Files\Asta\Asta Powerproject enterprise\ (32-bit systems). C:\Program Files(x86)\Asta\Asta Powerproject enterprise\ (64-bit systems). 13. Type AstaNameServer.exe remove and press ENTER. The Asta Name Server service is removed. 14. Type AstaEnterprise.exe remove and press ENTER. The Asta Enterprise server service is removed. Note that if you installed the server to run as a service with a specific name, you will need to type AstaEnterprise.exe remove <server name>, for example AstaEnterprise.exe remove AstaServer. 15. You must now reinstall the Asta Name Server and Enterprise server to run as services again. Follow the instructions in section 2.5, Installing the Asta Name Server and the Enterprise server to run as services, in order to do this, ensuring that you include the -web appendage when you do so. 16. You must now configure the Asta Name Server and Enterprise server services to start automatically. Follow the instructions in section 2.6, Configuring the Asta Name Server and Enterprise server services, in order to do this. 5.3 Installing the Asta Archive Manager application Now that you have configured your Asta services to work with Asta Archive Manager, you can install the Asta Archive Manager application. The instructions in this document assume that you are installing the Asta Archive Manager onto the server machine on which your Asta Powerproject Enterprise server is located, although you can install it onto another computer on the same network. To install the Asta Archive Manager application: 1. Log into the server machine as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears. 4. Follow the steps in the installation wizard to install Asta Archive Manager, clicking Next to move between the various screens of the wizard. 5. Asta Archive Manager is installed into the following folder by default: C:\Program Files\Asta\Asta Archive Manager\ (32-bit systems). C:\Program Files(x86)\Asta\Asta Archive Manager\ (64-bit systems). 6. If you want to install Asta Archive Manager to a location other than the default, click the Custom radio button on the Setup Type screen, which will give you access to an additional page of the wizard in which you can specify an installation folder. 7. Click Install on the final screen of the wizard to install Asta Archive Manager. 8. When the installation routine is complete, click Finish to exit the wizard Elecosoft UK Ltd

55 5.4 Setting up proxy exceptions for the archiving web services If you use a proxy server and if you have installed Asta Archive Manager onto a computer other than the server machine on which your Asta Powerproject Enterprise server is located, you must set up proxy exceptions for the IP address and TCP/IP port number of the archiving web services in Microsoft Internet Explorer. If you do not use a proxy server or if you have installed Asta Archive Manager onto the server machine in which your Enterprise server is located, ignore the instructions in this section and move onto the next section. To set up proxy exceptions for the archiving web services: 1. On the computer on which you have installed Asta Archive Manager, launch Microsoft Internet Explorer. 2. Select the Internet Options command from the Tools menu. The Internet Options dialog appears. 3. Click the Connections tab. 4. Click LAN Settings. The Local Area Network (LAN Settings) dialog appears. 5. In the Proxy server group of fields, ensure that the Use a proxy server for your LAN check box is selected and enter details of the proxy server in the Address and Port fields: 6. In the same group of fields, click Advanced. The Proxy Settings dialog appears. 7. Enter enterprise server IP address:1910;enterprise server IP address:1950 in the Do not use proxy server for addresses beginning with field: 8. Click OK to save the settings and close the dialog, then click OK to close the remaining dialogs that are open. 5.5 Configuring Windows to enable the use of distributed transactions Asta Archive Manager makes use of distributed transactions. In order to use distributed transactions, you may need to change some Windows settings on the computer on which you have installed Asta Archive Manager. To configure Windows to enable the use of distributed transactions: 1. On the computer on which you have installed the Asta Archive Manager, launch Control Panel. 2. Within Control Panel, select System and Security, then Administrative Tools. The Administrative Tools window appears. 3. Double-click the Component Services administrative tool. The Component Services window appears: 2016 Elecosoft UK Ltd

56 4. Double-click the Computers folder in the middle pane of the Component Services window. The My Computer icon appears. 5. Double-click the My Computer icon in the middle pane. A number of folders appear. 6. Double-click the Distributed Transaction Coordinator folder in the middle pane. 7. Right-click Local DTC in the middle pane and select Properties. The Local DTC Properties dialog appears. 8. Click the Security tab: 9. Select the Network DTC Access check box. 10. In the Client and Administration group of fields, select the Allow Remote Administration check box. 11. In the Transaction Manager Communication group of fields, select the Allow Inbound and Allow Outbound check boxes. 12. Select the Enable XA Transactions check box. 13. Click OK to close the Local DTC Properties dialog. 14. Close the Component Services window. If you have installed Asta Archive Manager onto a computer that is running Windows 2003 Server, follow the instructions above but in step 5, right-click the My Computer icon and select Properties, then click Security Configuration on the MSDTC tab of the My Computer Properties dialog to access the check boxes that you need to select. 5.6 Configuring the distributed transaction timeout setting Distributed transactions have a default timeout setting of 10 seconds, which needs to be changed in order for Asta Archive Manager to work correctly. You do this by editing a file (two files, if you are running a 64-bit operating system) on the computer on which you have installed Asta Archive Manager. If you have installed Asta Archive Manager onto a computer other than the server machine on which your Asta Powerproject Enterprise server is located, you must also edit this file on the server machine on which the Enterprise server is located Elecosoft UK Ltd

57 To configure the distributed transaction timeout setting: 1. On the computer on which you have installed the Asta Archive Manager, launch Windows Explorer and navigate to the following folder: C:\Windows\Microsoft.NET\Framework\v \Config\ 2. Within this folder, locate the machine.config file and open it in a text editor such as Notepad. The last line of the file should read as follows: </configuration> 3. Enter the following into the file, immediately before the last line: <system.transactions> <machinesettings maxtimeout= 10:00:00 /> </system.transactions> 4. Save and close the file. The timeout has now been changed from 10 seconds to 10 hours. 5. If you are running a 64-bit operating system, navigate to the following folder and make the same changes to the machine.config file in that folder: C:\Windows\Microsoft.NET\Framework64\v \Config\ (64-bit systems). 6. If you have installed Asta Archive Manager onto a computer other than the server machine on which your Enterprise server is located, follow the above steps to change the timeout on the server machine on which your Enterprise server is located Elecosoft UK Ltd

58 6 Installing Time Sheet for Asta Powerproject This section of the document describes how to install Time Sheet for Asta Powerproject, which enables users to record, submit and update time spent on project and non-project work using web-based timesheets, without the need for a full Asta Powerproject licence. Time Sheet comprises a number of Active Server Pages (ASP) scripts that run within Microsoft Internet Information Services. Time Sheet uses the Asta Developers Toolkit to read and update Asta Powerproject projects, and updates a separate Time Sheet database. Time Sheet comprises the following elements: The Time Sheet application. This is an application, installed on a server machine that acts as a web server. You can install Time Sheet onto the same server machine as the Enterprise server provided that the server machine can operate as both an application server and a web server or you can install it onto a separate server machine. If you use both Time Sheet and Web Access, you can install both onto the same server machine (note that each must run in its own application pool). Asta Developers Toolkit. This is an application that enables communication between Time Sheet and your Asta Powerproject Enterprise server. It must be installed onto the web server, alongside the Time Sheet application. The Time Sheet database. This is a Microsoft SQL Server or Oracle database. The Time Sheet database can be located anywhere; you may want to locate it in the same place as your Asta Powerproject Enterprise data sources. The installation of Time Sheet for Asta Powerproject comprises the following steps: Installing and configuring Microsoft Internet Information Services. Configuring Windows to allow ASP pages to run. Installing necessary role services for the Web Server (IIS). Installing the Asta Developers Toolkit. Creating a Microsoft SQL Server database for use with Time Sheet. Creating a Microsoft SQL Server database user. Installing Time Sheet. Registering Time Sheet with Microsoft Internet Information Services. Additional configuration in Internet Information Services version 6. Creating an application pool for Time Sheet. Specifying the server location method in the Asta Developers Toolkit. Noting server and project information and mounting projects. Creating tables in the Time Sheet database. Granting the necessary users access to Time Sheet configuration files. Enabling Time Sheet to connect to the database. Registering the project(s) to be used with Time Sheet. Updating Asta Powerproject with the Time Sheet connection string. Configuring the Time Sheet mail agent service. Verifying that Time Sheet has been installed correctly. Configuring Time Sheet s settings. Accessing the Time Sheet login pages. Notes on running Time Sheet Elecosoft UK Ltd

59 6.1 Installing and configuring Microsoft Internet Information Services You must ensure that Microsoft Internet Information Services version 6 or later is installed on the server machine on which you are going to install Time Sheet. If it is not already installed, install the latest version of Microsoft Internet Information Services before you proceed any further. If Microsoft Internet Information Services version 7 or later is installed on the server machine, carry out the following instructions to ensure that a number of components are installed: 1. On the server machine on which you are going to install Time Sheet, launch Control Panel. 2. Within Control Panel, select System and Security, then Administrative Tools. The Administrative Tools window appears. 3. Double-click the Server Manager administrative tool. The Server Manager window appears: 4. In the left pane of the Server Manager window, click IIS. 5. Scroll down in the right pane of the window until you see the Roles and Features information: 6. To the right of the Roles and Features heading, click Tasks and select Add Roles and Features from the menu that appears: 2016 Elecosoft UK Ltd

60 The Add Roles and Features wizard appears. 7. Click Next to skip past the introductory page of the wizard. 8. On the Select installation type page of the wizard, click the Role-based or feature-based installation radio button, then click Next. 9. On the Select destination server page of the wizard, select the server on which you are going to install Time Sheet, then click Next. 10. On the Select server roles page of the wizard, expand Web Server (IIS); within that, expand Management Tools, then within that, expand IIS 6 Management Compatibility. 11. If they are not already selected, select the IIS 6 Metabase Compatibility, IIS 6 Management Console and IIS 6 WMI Compatibility check boxes, then click Next: 12. On the Select features page of the wizard, click Next. 13. On the Confirm installation selections page of the wizard, click Install. 14. Close the wizard when the installation is complete. 6.2 Configuring Windows to allow ASP pages to run If you are going to install Time Sheet onto a server machine that is running Microsoft Windows 2003 Server, you must configure Windows to allow ASP pages to run. If you are installing Time Sheet onto a server machine that is running an operating system other than Microsoft Windows 2003 Server, ignore the instructions in this section and move onto the next section. To configure Windows to allow ASP pages to run: 1. On the server machine on which you are going to install Time Sheet, launch Control Panel. 2. Within Control Panel, select Programs, then Add or Remove Programs. The Add or Remove Programs window appears. 3. In the Add or Remove Programs window, click Add/Remove Windows Components. The Windows Components wizard appears Elecosoft UK Ltd

61 4. In the Windows Components wizard, click Application Server, then click Details. The Internet Information Services (IIS) dialog appears. 5. In the Internet Information Services (IIS) dialog, click World Wide Web Service, then click Details. The World Wide Web Service dialog appears. 6. In the World Wide Web Service dialog, click the Active Server Pages check box, then click OK. 7. Click OK or Finish as appropriate to close the open windows and dialogs. 6.3 Installing necessary role services for the Web Server (IIS) If you are going to install Time Sheet onto a computer that is running Microsoft Windows 2008 Server R2 or Microsoft Windows 2012 Server, you must use Server Manager to ensure that a number of role services are installed for the Web Server (IIS). If you are installing Time Sheet onto a server machine that is running an operating system other than Microsoft Windows 2008 Server R2 or Microsoft Windows 2012 Server, ignore the instructions in this section and move onto the next section. To install necessary role services for the Web Server (IIS): 1. On the server machine on which you are going to install Time Sheet, launch Control Panel. 2. Within Control Panel, select System and Security, then Administrative Tools. The Administrative Tools window appears. 3. Double-click the Server Manager administrative tool. The Server Manager window appears: 4. In the left pane of the Server Manager window, click IIS. 5. Scroll down in the right pane of the window until you see the Roles and Features information: 2016 Elecosoft UK Ltd

62 6. To the right of the Roles and Features heading, click Tasks and select Add Roles and Features from the menu that appears: The Add Roles and Features wizard appears. 7. Click Next to skip past the introductory page of the wizard. 8. On the Select installation type page of the wizard, click the Role-based or feature-based installation radio button, then click Next. 9. On the Select destination server page of the wizard, select the server on which you are going to install Time Sheet, then click Next. 10. On the Select server roles page of the wizard, expand Web Server (IIS); within that, expand Web Server, then within that, expand Common HTTP Features. 11. If they are not already selected, select the Static content, Default Document, Directory Browsing and HTTP Errors check boxes. 12. Within Web Server (IIS) Web Server, expand Health and Diagnostics. 13. If they are not already selected, select the HTTP Logging and Request Monitor check boxes. 14. Within Web Server (IIS) Web Server, expand Application Development. 15. If they are not already selected, select the ASP and ISAPI Extensions check boxes, then click Next Elecosoft UK Ltd

63 16. On the Select features page of the wizard, click Next. 17. On the Confirm installation selections page of the wizard, click Install. 18. Close the wizard when the installation is complete. 6.4 Installing the Asta Developers Toolkit Before you install Time Sheet, you must install the Asta Developers Toolkit also known as the OCX onto the server machine onto which you are going to install Time Sheet. To install the Asta Developers Toolkit: 1. Log into the server machine as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears. 4. Follow the steps in the installation wizard to install the Asta Developers Toolkit, clicking Next to move between the various screens of the wizard. The Asta Developers Toolkit is installed into the following folder by default: C:\Program Files\Asta\Asta Developers Toolkit\ (32-bit systems). C:\Program Files(x86)\Asta\Asta Developers Toolkit\ (64-bit systems). 5. If you want to install the Asta Developers Toolkit to a location other than the default, click the Custom radio button on the Setup Type screen, which will give you access to an additional page of the wizard in which you can specify an installation folder. 6. Click Install on the final screen of the wizard to install the Asta Developers Toolkit. 7. When the installation routine is complete, click Finish to exit the wizard. 6.5 Creating a Microsoft SQL Server database for use with Time Sheet Before you install Time Sheet, you must create a database in which to store the Time Sheet data on the server machine on which you are going to install Time Sheet or onto a machine to which the server machine has access. The steps involved in creating a Microsoft SQL Server database for use with Time Sheet are exactly the same as those involved in creating one for use with Asta Powerproject Enterprise. Follow the instructions in section 2.1, Creating a Microsoft SQL Server database, in order to create a database for use with Time Sheet. 6.6 Creating a Microsoft SQL Server database user Once you have created the Microsoft SQL Server database, you must create a new user to access it. The steps involved in creating a Microsoft SQL Server database user for use with Time Sheet are exactly the same as those involved in creating one for use with Asta Powerproject Enterprise. Follow the instructions in section 2.2, Creating a Microsoft SQL Server database user, in order to create a database for use with Time Sheet Elecosoft UK Ltd

64 6.7 Installing Time Sheet Now that you have created your database and a user in Microsoft SQL Server, you can install Time Sheet. The instructions in this document assume that you are installing Time Sheet onto the server machine on which your database is located and that this is the same server machine on which your Asta Powerproject Enterprise server is located. To install Time Sheet for Asta Powerproject: 1. Log into the server machine as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears. 4. Follow the steps in the installation wizard to install Time Sheet, clicking Next to move between the various screens of the wizard. Time Sheet is installed into the following folder by default: C:\Inetpub\wwwroot\AstaTimesheet\ 5. If you want to install Time Sheet to a location other than the default, click Change on the Destination Folder screen, which will give you access to an additional page of the wizard in which you can specify an installation folder. 6. The installation wizard can register Time Sheet with Microsoft Internet Information Services automatically. Alternatively, you can register it yourself, as described in section 6.8, Registering Time Sheet with Microsoft Internet Information Services. Click the appropriate radio button on the Configure Internet Information Services screen to indicate whether or not you want to carry out the registration yourself. If you allow the installation wizard to register Time Sheet with Microsoft Internet Information Services, the default URL with which Time Sheet can be accessed is set to name>/astatimesheet/), where <server name> is the name of the server machine on which Time Sheet is installed. 7. Click Install on the final screen of the wizard to install Time Sheet. 8. When the installation routine is complete, click Finish to exit the wizard. 9. Reboot the server machine on which you have installed Time Sheet. 6.8 Registering Time Sheet with Microsoft Internet Information Services If, when installing Time Sheet (as described in section 6.7, Installing Time Sheet), you chose to register Time Sheet with Microsoft Internet Information Services yourself, you now need to perform this task. If you allowed the Time Sheet installation wizard to register Time Sheet with Microsoft Internet Information Services automatically, you can ignore this section and move onto the following section. To register Time Sheet with Microsoft Internet Information Services: 1. On the server machine on which Microsoft Internet Information Services is installed, launch the Internet Information Services Manager. 2. Within Internet Information Services Manager, create a new virtual directory. 3. When prompted for an alias, enter the name that you want to apply to the Time Sheet website, for example AstaTimesheet Elecosoft UK Ltd

65 4. When prompted for a directory, specify the folder in which you installed Time Sheet, for example C:\Inetpub\wwwroot\AstaTimesheet\. 5. Set permissions for the virtual directory to Read/Run Scripts and set the execute permission to Scripts Only. 6.9 Additional configuration in Internet Information Services version 6 If you have Microsoft Internet Information Services version 6 installed, you need to carry out the following steps: If you are installing Time Sheet onto a server machine that has Microsoft Internet Information Services version 7 or later installed, ignore the instructions in this section and move onto the next section. 1. On the server machine on which Microsoft Internet Information Services is installed, launch the Internet Information Services Manager. 2. In the left pane of Internet Information Services Manager, expand the hierarchy until you see AstaTimesheet, then right-click it and select Properties. The AstaTimeSheet Properties dialog appears. 3. Click the Virtual Directory tab. 4. Select Scripts and Executables in the Execute permissions field and select High (Isolated) in the Application protection field: 5. Click OK Creating an application pool for Time Sheet Time Sheet must run in its own application pool. If Time Sheet is the only web application running on Microsoft Internet Information Services, it can run in the default application pool, DefaultAppPool; if there is more than one web application running, follow the instructions below to create a new application pool for Time Sheet and configure Time Sheet to run within it: 1. On the server machine on which Microsoft Internet Information Services is installed, launch the Internet Information Services Manager. 2. In the left pane of Internet Information Services Manager, right-click Application Pools and select Add Application Pool. The Add Application Pool dialog appears: 2016 Elecosoft UK Ltd

66 3. In the Name field, enter a descriptive name such as Asta Time Sheet. 4. In the.net Framework version field, select No Managed Code. 5. In the Managed pipeline mode field, select Classic. 6. Select the Start application pool immediately check box. 7. Click OK. 8. Right-click the new application pool and select Advanced Settings. The Advanced Settings dialog appears: 9. In the Enable 32-Bit applications field, select True (64-bit operating systems only). 10. In the Idle time-out (minutes) field, enter In the Regular time interval (minutes) field, enter Click OK. 13. In the left pane of Internet Information Services Manager, expand the hierarchy until you see AstaTimesheet, then right-click it and select Convert to Application. The Add Application dialog appears: 2016 Elecosoft UK Ltd

67 14. Click Select. The Select Application Pool dialog appears. 15. In the Application pool field, select the application pool that you have created: 16. Click OK in both dialogs to close them. 17. Restart Microsoft Internet Information Services Specifying the server location method in the Asta Developers Toolkit You must specify the way in which you want the Asta Developers Toolkit to locate the Enterprise server(s) that you have installed. The server location details that you specify in the client must match those that you specified in section , Specifying the server location method in Asta Serveradmin. To specify the server location method in the Asta Developers Toolkit: 1. In the folder into which you installed the Asta Developers Toolkit, launch the ServerLocator.exe file. The Asta Server Locator Utility dialog appears. 2. Select the Asta Name Server check box, then enter either the IP address or the server name of the server machine on which you have installed the Asta Name Server: 3. Click OK Elecosoft UK Ltd

68 6.12 Noting server and project information and mounting projects You must note down information about the server and project(s) that you will use in conjunction with Time Sheet. You will use this information in section 6.16, Registering the project(s) to be used with Time Sheet, when you register the projects in Time Sheet. Once you have done this, (if they are not configured to be premounted, as described in section 4.9, Specifying that projects and their baselines should be pre-mounted) you must mount the project(s) that are to be used with Time Sheet. If you are going to use Time Sheet to record time against more than one project, you must mount each project individually. Your Enterprise servers should be configured to run as services, meaning that they are loaded automatically when Windows starts and run in the background, with no user interface. You use the Controller application, which is installed alongside the Enterprise server, to display a window in which you can enter Enterprise server commands. To note server and project information and mount the Asta Powerproject project: 1. On the computer on which you have installed the Enterprise server(s), launch the Controller application from the Windows Start screen. The Controller application window appears: 2. Press ENTER to view a list of the Enterprise servers that are currently running: 3. Make a note of the name of the Enterprise server(s). 4. Type the name of the Enterprise server on which the projects that you will use with Time Sheet are located and press ENTER. You see a confirmation that you have connected to the server. 5. Type projects and press ENTER. You see a list of the projects on the server: 6. Make a note of the DSID (data source ID), PID (project ID) and name of each project that you will use with Time Sheet Elecosoft UK Ltd

69 7. It is recommended that you pre-mount the projects that are to be used with Time Sheet (as described in section 4.9, Specifying that projects and their baselines should be pre-mounted). If your projects are not configured to be pre-mounted, type mount <data source ID>:<project ID> and press ENTER in the Controller application to mount each project that will be used with Time Sheet, where <data source ID> is the ID of the data source and <project ID> is the ID of the project Creating tables in the Time Sheet database In section 6.5, Creating a Microsoft SQL Server database for use with Time Sheet, you created a database for use with Time Sheet. You now need to populate the database with tables. You do this by executing a SQL file that is installed alongside Time Sheet. To populate your Time Sheet database with tables: 1. On the server machine on which you installed Time Sheet, launch SQL Server Management Studio. 2. Click the File menu, then select Open File. The Open File window appears. 3. Navigate to the folder into which you installed Time Sheet (which is C:\Inetpub\wwwroot\AstaTimesheet\ by default). 4. Select the create_tables_sqlsrv.sql file and click Open. The file opens in SQL Server Management Studio. 5. Ensure that the Time Sheet database that you created is selected in the Available Databases control on the SQL Editor toolbar, then click Execute in the same toolbar: The SQL file creates the tables in the Time Sheet database Granting the necessary users access to Time Sheet configuration files Time Sheet s configuration settings are stored in the following two files, which are located in the folder in which Time Sheet is installed: Config.xml. Columns.xml. Before you begin configuring Time Sheet, you must grant two user accounts access to the folder in which Time Sheet is installed and to all of the files and subfolders that it contains. The IIS_IUSRS account requires full control over the folder and the Users account requires Modify and Write access. To do this: 1. On the server machine on which you installed Time Sheet, launch Windows Explorer and navigate to the folder that contains the folder into which you installed Time Sheet (which is C:\Inetpub\wwwroot\AstaTimesheet\ by default) Elecosoft UK Ltd

70 2. Right-click the Time Sheet installation folder ( AstaTimesheet in the above example) and select Properties. The folder s Properties dialog appears. 3. On the Security tab of the dialog, click Edit. The folder s Permissions dialog appears: 4. Select the IIS_IUSRS user in the Group or user names field. 5. Select the Allow check box against Full control in the Permissions for IIS_IUSRS group. 6. Select the Users user in the Group or user names field. 7. Select the Allow check boxes against Modify and Write in the Permissions for Users group. 8. Click OK to close the folder s Permissions dialog, then click OK to close the folder s Properties dialog Enabling Time Sheet to connect to the database Once you have populated the Time Sheet database with tables, you must specify the ActiveX Data Objects (ADO) connection string that individual instances of Time Sheet use to connect to the database. To enable Time Sheet to connect to the database: 1. Launch a web browser and load the following page to access Time Sheet Configuration: name>/<web site name>/config.asp Where <server name> is the name of the server machine on which Time Sheet is installed and <web site name> is the name that you specified when installing Time Sheet. By default, the URL will be: name>/astatimesheet/config.asp 2. The Time Sheet Configuration Login screen appears: 2016 Elecosoft UK Ltd

71 3. Enter the Time Sheet Configuration password (this is set to asta by default and click Login. The initial Time Sheet Configuration screen appears. 4. Click Settings. The Main Configuration Settings screen appears. 5. Click Database Options: 6. Enter the ActiveX Data Objects (ADO) connection string that individual instances of Time Sheet use to connect to the database (for full details of the connection string syntax, click Help). 7. Click Apply to save the details of the connection string Registering the project(s) to be used with Time Sheet Once you have specified the ActiveX Data Objects (ADO) connection string that individual instances of Time Sheet use to connect to the database, you must register each project that will be used in conjunction with Time Sheet. You made a note of the details of the projects in section 6.12, Noting server and project information and mounting projects. To register the project(s) that are to be used with Time Sheet: 1. Within Time Sheet Configuration, on the Main Configuration Settings screen, click Asta Powerproject Options: 2. Enter a unique ID to assign to the first project s data set within the Time Sheet database in the Project ID field. To keep things simple, you can enter the same ID as the ID of the Asta Powerproject project itself which you will enter in the Proj ID field. 3. Enter the name of the Enterprise server (not the name of the server machine itself) on which the first project is located in the Server name field. Note that the server name is case-sensitive. 4. Enter the name of the first project in the Project name field. This name is displayed to Time Sheet users when they log in Elecosoft UK Ltd

72 5. Enter the ID of the data source in which the first project is located in the DS ID field. 6. Enter the ID of the first Asta Powerproject project in the Proj ID field. 7. If you have set up a server-level user in Asta Serveradmin and given the user a password, enter the server-level username and password in the Server user and Server password fields; otherwise, leave these fields blank. 8. Click Apply to save the details of the project. A second column appears: 9. Follow steps 2 to 8 to enter details of other projects that you want to use with Time Sheet, entering details of each project into a different column Updating Asta Powerproject with the Time Sheet connection string You must now update Asta Powerproject with information on the Time Sheet database. The Time Sheet connection string is stored against project summary objects in Asta Powerproject, which enables you to write macros that refer to Time Sheet data. Updating Asta Powerproject with the connection string also enables a number of Time Sheet-specific fields in Asta Powerproject. To update Asta Powerproject with the Time Sheet connection string: 1. Within Time Sheet Configuration, on the Main Configuration Settings screen, click Return to return to the initial Time Sheet Configuration screen. 2. Click Update. The Update Asta Powerproject with Configuration Data screen appears. Details of the projects that you have registered appear on the screen, with a separate column for each: 3. Enter the username of the top-level user in each project in the Asta Powerproject user fields. 4. Enter the password of the top-level user in each project in the Asta Powerproject password fields. 5. Click Apply to update the project with the Time Sheet connection string Elecosoft UK Ltd

73 6.18 Configuring the Time Sheet mail agent service Time Sheet sends s using a mail agent an application that is installed alongside Time Sheet that runs as a service and manages the sending of s. The mail agent a system service called TSAPPMailAgent is installed automatically when you install Time Sheet. Once you have installed Time Sheet, you must use Time Sheet Configuration to specify the details of your SMTP mail server. You must then start the mail agent service and configure it to start automatically, via Control Panel. The service is not configured to start automatically at first, as it would not make sense to do so until you have specified the details of the mail server. To specify the details of your SMTP mail server: 1. On the initial Time Sheet Configuration screen, click Settings. The Main Configuration Settings screen appears. 2. Click Mail Options: 3. Enter the IP address or the WINS/NetBIOS name of the SMTP mail server through which Time Sheet should route s in the SMTP mail server field. 4. Enter the number of the server s port to which Time Sheet should initiate a connection in the SMTP mail server port (25 usually) field. 5. Enter the number of seconds for which the Time Sheet mail agent should wait before attempting to send failed s those with a status of pending to the SMTP mail server again in the SMTP retry interval field. The default is 120, ie two minutes. 6. Enter the number of times that the Time Sheet mail agent should attempt to send failed s to the SMTP mail server before giving up and marking the s with a status of failed in the SMTP retry limit field. The default is Click Apply to save your settings. To start the Time Sheet mail agent service and configure it to start automatically: 1. On the server machine on which you installed Time Sheet, launch Control Panel. 2. Within Control Panel, select System and Security, then Administrative Tools. The Administrative Tools window appears. 3. Double-click the Services administrative tool. The Services window appears: 2016 Elecosoft UK Ltd

74 4. Locate the Timesheet for Asta Powerproject Mail Agent service in the list (highlighted in the above illustration). 5. Double-click the service. The service s Properties dialog appears. 6. On the General tab of the dialog, select Automatic in the Startup type field. 7. Click OK to close the dialog. Note that if you change the values in the SMTP retry interval or SMTP retry limit fields when the Time Sheet mail agent service is running, you will need to restart the service in order for your changes to take effect Verifying that Time Sheet has been installed correctly You can run a script to verify that the Time Sheet database has been configured correctly. To do this: 1. On the server machine on which you installed Time Sheet, launch a command prompt. A command prompt window appears. 2. In the command prompt window, change the directory location to the folder in which Time Sheet has been installed, which is, by default: C:\Inetpub\wwwroot\AstaTimesheet\ 3. Type cscript verify1.js and press ENTER to run a check using the Windows Scripting Host, which informs you of any problems with the Time Sheet database. If any problems are identified, fix them before proceeding. You can access a web page to verify that you have completed the Time Sheet installation successfully. To do this: 1. Launch a web browser and load the following page: name>/<web site name>/verify2.asp Where <server name> is the name of the server machine on which Time Sheet is installed and <web site name> is the name that you specified when installing Time Sheet. By default, the URL will be: name>/astatimesheet/verify2.asp. 2. The script outputs server variables to ensure that the virtual directory is configured correctly and launches the Asta Developers Toolkit and Time Sheet to ensure that they can be loaded via the internet or intranet. If any problems are identified, fix them before proceeding Elecosoft UK Ltd

75 6.20 Configuring Time Sheet s settings You can now configure the way in which Time Sheet runs, using Time Sheet Configuration. Refer to the Time Sheet Configuration Help for full details of how to configure Time Sheet s settings Accessing the Time Sheet login pages The different types of Time Sheet user launch Time Sheet using the following URLs (in each case, <server name> is the name of the server machine on which Time Sheet is installed and <web site name> is the name that you specified when installing Time Sheet): Time Reporters: name>/<web site name>/default.asp Resource Managers: name>/<web site name>/resman.asp Project Managers: name>/<web site name>/projman.asp Project Effort Reporters: name>/<web site name>/per.asp Finance Officers: name>/<web site name>/expman.asp 6.22 Notes on running Time Sheet It is essential to mount the projects on the Enterprise server before Time Sheet clients start to connect. You can speed up access times to projects by pre-mounting them each time the Enterprise server starts. Pre-mounting a project also prevents it from being dismounted automatically when all users have finished working with it. See section 4.9, Specifying that projects and their baselines should be pre-mounted, for details of how to pre-mount projects. All of the text that is displayed to the user by Time Sheet is stored in the resources.txt file, located in the folder in which Time Sheet is installed. You can edit or translate this if required. If you do change any of the text, you must restart Microsoft Internet Information Services and Time Sheet for the changes to take effect. It is recommended that you make use of the security facilities within Asta Powerproject, based on project users and security groups. Time Sheet users should log into Time Sheet with a specific Asta Powerproject username and password. You can configure Time Sheet to enable users to log in automatically, via either the Cosign authentication system or Windows Authentication. When automatic logging in is enabled, users of all types are able to access Time Sheet without having to enter a username and password. Refer to Setting up Time Sheet users in the Time Sheet Configuration Help for details of how to set up different types of user Elecosoft UK Ltd

76 7 Installing Web Access for Asta Powerproject This section of the document describes how to install Web Access for Asta Powerproject, which enables users to view, edit and share project data over an intranet, without the need for a full Asta Powerproject licence. Like Time Sheet, Web Access comprises a number of Active Server Pages (ASP) scripts that run within Microsoft Internet Information Services. Web Access uses the Asta Developers Toolkit to read and update Asta Powerproject projects. Web Access comprises the following elements: The Web Access application. This is an application, installed on a server machine that acts as a web server. You can install Web Access onto the same server machine as the Enterprise server provided that the server machine can operate as both an application server and a web server or you can install it onto a separate server machine. If you use both Time Sheet and Web Access, you can install both onto the same server machine (note that each must run in its own application pool). Asta Developers Toolkit. This is an application that enables communication between Web Access and your Asta Powerproject Enterprise server. It must be installed onto the web server, alongside the Web Access application. The installation of Web Access for Asta Powerproject comprises the following steps: Installing and configuring Microsoft Internet Information Services. Configuring Windows to allow ASP pages to run. Installing necessary role services for the Web Server (IIS). Installing the Asta Developers Toolkit. Installing Web Access. Additional configuration in Internet Information Services version 6. Creating an application pool for Web Access. Specifying the server location method in the Asta Developers Toolkit. Noting server and project information and mounting projects. Granting the necessary users access to Web Access configuration files. Registering the project(s) to be used with Web Access. Verifying that Web Access has been installed correctly. Configuring Web Access s settings. Accessing the Web Access login pages. 7.1 Installing and configuring Microsoft Internet Information Services You must ensure that Microsoft Internet Information Services version 6 or later is installed on the server machine on which you are going to install Web Access. If it is not already installed, install the latest version of Microsoft Internet Information Services before you proceed any further. If Microsoft Internet Information Services version 7 or later is installed on the server machine, you must ensure that a number of components are installed. The steps involved are exactly the same as those given for configuring Microsoft Internet Information Services during the installation of Time Sheet. Follow the instructions in section 6.1, Installing and configuring Microsoft Internet Information Services, in order to configure Microsoft Internet Information Services for use with Web Access Elecosoft UK Ltd

77 If you are installing Web Access onto a server machine onto which Time Sheet has already been installed, ignore the instructions in this section and move onto section 7.5, Installing Web Access. 7.2 Configuring Windows to allow ASP pages to run If you are going to install Web Access onto a server machine that is running Microsoft Windows 2003 Server, you must configure Windows to allow ASP pages to run. The steps involved are exactly the same as those given for configuring Windows during the installation of Time Sheet. Follow the instructions in section 6.2, Configuring Windows to allow ASP pages to run, in order to configure Windows for use with Web Access. If you are installing Web Access onto a server machine onto which Time Sheet has already been installed, ignore the instructions in this section and move onto section 7.5, Installing Web Access. 7.3 Installing necessary role services for the Web Server (IIS) If you are going to install Web Access onto a computer that is running Microsoft Windows 2008 Server R2 or Microsoft Windows 2012 Server, you must use Server Manager to ensure that a number of role services are installed for the Web Server (IIS). The steps involved are exactly the same as those given for installing role services during the installation of Time Sheet. Follow the instructions in section 6.3, Installing necessary role services for the Web Server (IIS), in order to install role services for use with Web Access. If you are installing Web Access onto a server machine onto which Time Sheet has already been installed, ignore the instructions in this section and move onto section 7.5, Installing Web Access. 7.4 Installing the Asta Developers Toolkit Before you install Web Access, you must install the Asta Developers Toolkit also known as the OCX onto the server machine onto which you are going to install Web Access. The steps involved are exactly the same as those given for installing the Asta Developers Toolkit during the installation of Time Sheet. Follow the instructions in section 6.4, Installing the Asta Developers Toolkit, in order to install the Asta Developers Toolkit for use with Web Access. If you are installing Web Access onto a server machine onto which the Asta Developers Toolkit has already been installed, ignore the instructions in this section and move onto the next section. 7.5 Installing Web Access The instructions in this document assume that you are installing Web Access onto the server machine on which your Asta Powerproject Enterprise server is located. To install Web Access for Asta Powerproject: 1. Log into the server machine as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears. 4. Follow the steps in the installation wizard to install Web Access, clicking Next to move between the various screens of the wizard Elecosoft UK Ltd

78 Web Access is installed into the following folder by default: C:\Inetpub\wwwroot\AstaWebAccess\ 5. If you want to install Web Access to a location other than the default, click Change on the Destination Folder screen, which will give you access to an additional page of the wizard in which you can specify an installation folder. 6. Click Install on the final screen of the wizard to install Web Access. 7. When the installation routine is complete, click Finish to exit the wizard. 8. Reboot the server machine on which you have installed Web Access. 7.6 Additional configuration in Internet Information Services version 6 If you have Microsoft Internet Information Services version 6 installed, you need to configure a number of settings in Internet Information Services Manager. The steps involved are exactly the same as those given for configuring Microsoft Internet Information Services during the installation of Time Sheet. Follow the instructions in section 6.9, Additional configuration in Internet Information Services version 6, in order to configure Microsoft Internet Information Services for use with Web Access. Configure the settings for AstaWebAccess rather than for AstaTimesheet. 7.7 Creating an application pool for Web Access Web Access must run in its own application pool. If Web Access is the only web application running on Microsoft Internet Information Services, it can run in the default application pool, DefaultAppPool; if there is more than one web application running, follow the instructions below to create a new application pool for Web Access and configure Web Access to run within it. The steps involved are exactly the same as those given for creating an application pool during the installation of Time Sheet. Follow the instructions in section 6.10, Creating an application pool for Time Sheet, in order to create an application pool and configure Web Access to run within it. Configure AstaWebAccess to run in the new application pool that you create rather than AstaTimesheet. 7.8 Specifying the server location method in the Asta Developers Toolkit You must specify the way in which you want the Asta Developers Toolkit to locate the Enterprise server(s) that you have installed. The server location details that you specify must match those that you specified in section , Specifying the server location method in Asta Serveradmin. The steps involved are exactly the same as those given for configuring the Asta Developers Toolkit during the installation of Time Sheet. Follow the instructions in section 6.11, Specifying the server location method in the Asta Developers Toolkit, in order to specify the server location method in the Asta Developers Toolkit. If you are installing Web Access onto a server machine onto which the Asta Developers Toolkit has already been installed, ignore the instructions in this section and move onto the next section Elecosoft UK Ltd

79 7.9 Noting server and project information and mounting projects You must note down information about the server and project(s) that you will use in conjunction with Web Access. You will use this information in section 7.11, Registering the project(s) to be used with Web Access, when you register the projects in Web Access. Once you have done this, you must mount the project(s) that are to be used with Web Access. If you are going to use Web Access in conjunction with more than one project, you must mount each project individually. The steps involved are exactly the same as those given for noting server and project information during the installation of Time Sheet Follow the instructions in section, 7.9, Noting server and project information and mounting projects, in order to note server and project information and mount projects for use with Web Access Granting the necessary users full access to Web Access configuration files Web Access s configuration settings are stored in the rw_config.xml file, which is located in the folder in which Web Access is installed (which is C:\Inetpub\wwwroot\AstaWebAccess\ by default). Before you begin configuring Web Access, you must grant two user accounts access to the folder in which Web Access is installed and to all of the files and subfolders that it contains. The steps involved are exactly the same as those given for granting full control over Time Sheet configuration files during the installation of Time Sheet. Follow the instructions in section 6.14, Granting the necessary users access to Time Sheet configuration files, in order to grant the users access to the folder in which Web Access is installed Registering the project(s) to be used with Web Access You must register each project that will be used in conjunction with Web Access. You made a note of the details of the projects in section 7.9, Noting server and project information and mounting projects. To register the project(s) that are to be used with Web Access: 1. Launch a web browser and load the following page to access Web Access Configuration: name>/<web site name>/config.asp Where <server name> is the name of the server machine on which Web Access is installed and <web site name> is the name with which Web Access has been installed. By default, the URL will be: name>/astawebaccess/config.asp. 2. The Web Access Configuration Login screen appears: 2016 Elecosoft UK Ltd

80 3. Enter the Web Access Configuration password (this is set to asta by default and click Login. The initial Web Access Configuration screen appears. 4. Click Settings. The Main Configuration Settings screen appears. 5. Click Asta Powerproject Options: 6. If you want to make your Time Sheet projects available in Web Access, select the Use Time Sheet for Asta Powerproject projects check box, enter the ADO connection string that individual instances of Web Access use to connect to the Time Sheet database in the Connection string field and click Apply (for full details of the connection string syntax, click Help). If you want to make other projects available in Web Access, follow the instructions below. If you are using Web Access to view and edit a single project, enter details of the project into the first column the leftmost column leaving the other columns blank. 7. Enter the name of the Enterprise server (not the name of the server machine itself) on which the first project is located in the Server name field. Note that the server name is case-sensitive. 8. Enter the name of the first project in the Project name field. This name is displayed to Web Access users when they log in. 9. Enter the ID of the data source in which the first project is located in the DS ID field. 10. Enter the ID of the first Asta Powerproject project in the Proj ID field. 11. If you have set up a server-level user in Asta Serveradmin and given the user a password, enter the server-level username and password in the Server user and Server password fields; otherwise, leave these fields blank. 12. Click Apply to save the details of the project. 13. Follow steps 7 to 12 to enter details of other projects that you want to use with Web Access, entering details of each project into a different column Elecosoft UK Ltd

81 7.12 Verifying that Web Access has been installed correctly You can access a web page to verify that you have completed the Web Access installation successfully. To do this: 1. Launch a web browser and load the following page: name>/<web site name>/verify2.asp Where <server name> is the name of the server machine on which Web Access is installed and <web site name> is the name with which Web Access has been installed. By default, the URL will be: name>/astawebaccess/verify2.asp. 2. The script outputs server variables to ensure that the virtual directory is configured correctly and launches the Asta Developers Toolkit and Web Access to ensure that they can be loaded via the internet or intranet. If any problems are identified, fix them before proceeding Configuring Web Access s settings You can now configure the way in which Web Access runs, using Web Access Configuration. Refer to the Web Access Configuration Help for full details of how to configure Web Access s settings Accessing the Web Access login page Web Access users launch Web Access using the following URL (<server name> is the name of the server machine on which Web Access is installed and <web site name> is the name with which Web Access has been installed): name>/<web site name>/default.asp 2016 Elecosoft UK Ltd

82 8 Installing Site Progress Mobile for Asta Powerproject This section of the document describes how to install Site Progress Mobile for Asta Powerproject, which enables on-site reporting of progress against tasks and build stages in Asta Powerproject projects, using a mobile app and a web app. Site Progress Mobile can be used either with Asta Powerproject Enterprise, or with a non-enterprise Asta Powerproject client. Site Progress Mobile comprises the following elements: The Site Progress Manager application. This is an application that is used by administrators to export information from your Asta Powerproject projects to Site Progress Mobile, and to import information back into the Asta Powerproject projects once progress has been recorded and submitted. Site Progress Manager is also used to configure the way in which Site Progress Mobile operates. The Site Progress Manager application passes project information between Asta Powerproject and Site Progress Mobile via the internet, so you must have a valid internet connection in order to use Site Progress Manager. You can install Site Progress Manager onto more than one computer; for example, you may want to install it onto one computer for use by the overall administrator, who sets up users and configures their access rights, and onto several other computers for use by publisher users, who assign Site Progress Mobile users to the appropriate tasks in your projects and export and import project information. The Site Progress Mobile app. This freely-downloadable app is used by onsite progress reporters to record the progress of tasks and build stages from a remote location using a mobile device. Although the mobile devices must have a valid internet connection (either via a cellular network or via Wi-Fi ) in order to receive and submit project information at the start and end of each working period, Site Progress Mobile does not require an internet connection to be available all the time, which enables it to be used in locations with little or no network coverage or Wi-Fi availability. There are three versions of the Site Progress Mobile app: one suitable for use with Android mobile devices, one suitable for use with ios mobile devices and one suitable for Windows Mobile devices. The Site Progress Mobile web app. This app, which can be accessed via a URL by any web-enabled device using a web browser, can be used as an alternative to the Site Progress Mobile app. A valid internet connection is required at all times that the Site Progress Mobile web app is in use. Asta Developers Toolkit. This is an application that enables Site Progress Mobile to read Asta Powerproject files that have a.pp extension. If you install Site Progress Manager on a machine on which an Asta Powerproject client is installed, the Asta Developers Toolkit will already be installed Elecosoft UK Ltd

83 The installation of Site Progress Mobile for Asta Powerproject comprises the following steps: Installing the Asta Developers Toolkit. Installing the Site Progress Manager application. Specifying the server location method in the Asta Developers Toolkit. Ensuring that Site Progress Manager has access to Elecosoft UK Ltd s Cloud server. Entering your company details into Site Progress Manager. Configuring Site Progress Manager. Configuring projects for use with Site Progress Mobile. Recording details of Site Progress Mobile users. Recording details of your projects in Site Progress Manager. Associating users with their tasks within projects. Downloading Site Progress Mobile onto mobile devices. Accessing the Site Progress Mobile web app. 8.1 Installing the Asta Developers Toolkit Before you install the Site Progress Manager application, you must install the Asta Developers Toolkit also known as the OCX onto the computer(s) onto which you are going to install Site Progress Manager. The steps involved are exactly the same as those given for installing the Asta Developers Toolkit during the installation of Time Sheet. Follow the instructions in section 6.4, Installing the Asta Developers Toolkit, in order to install the Asta Developers Toolkit for use with Site Progress Manager. If you are going to install Site Progress Manager onto a machine on which an Asta Powerproject client is installed, the Asta Developers Toolkit will already be present; in this case, move onto the next section. 8.2 Installing the Site Progress Manager application You can install Site Progress Manager onto more than one computer. For example, you may want to install it onto one computer for use by the overall Site Progress administrator, who sets up users and configures their access rights, and onto several other computers for use by publisher users, who assign Site Progress Mobile users to the appropriate tasks in your projects and export and import project information. There are two versions of Site Progress Manager: a 32 bit version and a 64 bit version. You must install the version that corresponds to the Asta Powerproject client that you use: if you install the 64 bit version of the Asta Powerproject client you must install the 64 bit version of Site Progress Manager; otherwise, you must install the 32 bit version. To install the Site Progress Manager application: 1. Log into the computer on which you are going to install the Site Progress Manager application as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears Elecosoft UK Ltd

84 4. Follow the steps in the installation wizard to install the Site Progress Manager application, clicking Next to move between the various screens of the wizard. The Site Progress Manager application is installed into the following folder by default: C:\Program Files\Asta\Asta Site Progress Manager\ (32-bit systems). C:\Program Files(x86)\Asta\Asta Site Progress Manager\ (64-bit systems). 5. If you want to install the Site Progress Manager application to a location other than the default, click the Custom radio button on the Setup Type screen, which will give you access to an additional page of the wizard in which you can specify an installation folder. 6. Click Install on the final screen of the wizard to install the Site Progress Manager application. 7. When the installation routine is complete, click Finish to exit the wizard. 8.3 Specifying the server location method in the Asta Developers Toolkit If you use Asta Powerproject Enterprise rather than a non-enterprise Asta Powerproject client, you must specify the way in which you want the Asta Developers Toolkit to locate the Enterprise server(s) that you have installed. The server location details that you specify must match those that you specified in section , Specifying the server location method in Asta Serveradmin. The steps involved are exactly the same as those given for configuring the Asta Developers Toolkit during the installation of Time Sheet. Follow the instructions in section 6.11, Specifying the server location method in the Asta Developers Toolkit, in order to specify the server location method in the Asta Developers Toolkit. If you use a non-enterprise Asta Powerproject client, or if you are installing the Site Progress Manager application onto a machine onto which the Asta Developers Toolkit has already been installed, ignore the instructions in this section and move onto the next section. 8.4 Ensuring that Site Progress Manager has access to Elecosoft UK Ltd s Cloud server Once you have installed the Site Progress Manager application onto a computer, you must ensure that all user accounts that are to use Site Progress Manager on that computer are able to access Elecosoft UK Ltd s Cloud server via HTTP, using the following URL: You may need to allow access to the URL if your IT configuration applies restrictions to HTTP traffic. At the same time, you should ensure that each computer on which Site Progress Manager is installed has access to the location in which the Asta Powerproject project files are located and to the location in which any photographs that are to be taken using Site Progress Mobile are to be downloaded Elecosoft UK Ltd

85 8.5 Entering your company details into Site Progress Manager Once you have installed Site Progress Manager onto a computer, you need to enter your company details into the application the first time you launch it. These details, which will have been provided to you by Elecosoft UK Ltd, enable Site Progress Manager to connect to Elecosoft UK Ltd s Site Progress database, via the internet. To enter your company details into Site Progress Manager: 1. Launch Site Progress Manager on the computer on which you have installed it. The Asta Site Progress Manager Login dialog appears: 2. Enter the name and ID of your company into the Company name and Company ID fields and enter the user name and password of the administrator user into the User name and Password fields. This information will have been given to you by Elecosoft UK Ltd. You must enter these details precisely as they have been given to you, as if you enter the details incorrectly, you will not be able to access Site Progress Manager. 3. Click OK. Site Progress Manager connects to Elecosoft UK Ltd s Site Progress database via the internet. If you have entered the details correctly, you access Site Progress Manager. 8.6 Configuring Site Progress Manager You can now use the Settings screen in Site Progress Manager to configure the way in which Site Progress Mobile runs. Refer to the Site Progress Manager Help for full details of how to configure Site Progress Manager s settings. 8.7 Configuring projects for use with Site Progress Mobile You must open each project that you want to use with Site Progress Mobile in Asta Powerproject and configure it as described below Configure tasks to make them appear in the Ticksheet screen In order for a task to appear as a build stage in the Site Progress Mobile Ticksheet screen, you must carry out the following steps: 1. Create a bar-level user-defined field with an object type of Bar, a user field type of String and a user field name of Plot_No. 2. Display the Plot_No user-defined field in the spreadsheet. 3. For each bar in the project that represents an individual plot, enter a text string to identify the plot into the user-defined field. For example, you might enter Plot 1, Plot 2, Plot 3, etc into the user-defined field Elecosoft UK Ltd

86 4. Within Library Explorer, create a code library in which to store the code library entries that relate to different build stages. You can give this code library any name, but if you are using more than one Asta Powerproject project, the name of the code library must be the same within each project. 5. Specify the name of the code library in the Build stage code library name field on the Ticksheet Settings screen within Site Progress Manager: 6. Within the code library, create a code library entry for each build stage. Give each code library entry a name that accurately describes the build stage. 7. Assign the relevant build stage code library entries to the tasks in the project that represent build stages. 8. Use the Site Progress Manager Assign Access screen to associate the appropriate Site Progress Mobile user with the chart or summary group in which the task is located. In summary, a task appears as a build stage on the Ticksheet screen if: It is located on a bar against which text has been entered into the Plot_No user-defined field. A code library entry from the build stage code library has been assigned to the task. The name of the build stage code library has been specified in the Build stage code library name field on the Ticksheet Settings screen within Site Progress Manager. The appropriate Site Progress Mobile user has been associated with the chart or summary group in which the task is located Configure tasks to make them appear in the Turnaround screen In order for a task to appear in the Site Progress Mobile Turnaround screen, you must carry out the following steps: 1. Use the Site Progress Manager Assign Access screen to associate the appropriate Site Progress Mobile user with the chart or summary task in which the task is located. 2. Ensure that nothing has been entered into the Plot_No user-defined field against the bar on which the task is located. In summary, a task appears on the Turnaround screen if: The appropriate Site Progress Mobile user has been associated with the chart or summary group in which the task is located. Nothing has been entered into the Plot_No user-defined field against the bar on which the task is located Elecosoft UK Ltd

87 8.7.3 Create user-defined fields to enable photographs to be associated with tasks and milestones If you are using Site Progress Mobile in conjunction with Asta Powerproject Enterprise, you need to create two user-defined fields in Asta Serveradmin to enable photographs to be associated with tasks and milestones. The user-defined fields must have the following attributes: User-defined field 1 Object type: Task. User field type: URL. User field name: Attachments. User-defined field 2 Object type: Milestone. User field type: URL. User field name: Attachments. 8.8 Recording details of Site Progress Mobile users You must use Site Progress Manager to record details of each person who is to use Site Progress Mobile. There are three types of Site Progress Mobile user: Admin user one or more users who are able to use all of the functionality within Site Progress Manager. Admin users are able to configure Site Progress Manager, create, edit and delete other users, record details of projects, associate users with their tasks in a project, and export and import project information to and from Site Progress Mobile. Admin users can also be Site Progress Mobile users if required. Publisher user one or more users who are able to use Site Progress Manager to record details of projects, associate users with their tasks in a project, and export and import project information to and from Site Progress Mobile. Publisher users can also be Site Progress Mobile users if required. Publisher users cannot configure Site Progress Manager or create, edit and delete other users. Site Progress Mobile user one or more users who use Site Progress Mobile to record and submit progress information, using either a mobile device or a web browser. Site Progress Mobile users cannot use their user names and passwords to log into Site Progress Manager. The users that you create in Site Progress Manager are unrelated to users in Active Directory or Asta Powerproject: you do not have to create corresponding user records in either application. To record details of a Site Progress Mobile user: 1. On the main Site Progress Manager screen, click Users. The Users screen appears: 2016 Elecosoft UK Ltd

88 2. Click Add to create a new user. 3. Enter a name for the user in the Name field. This name is used to identify the user in Site Progress Mobile and a code library entry with this name is created within the Asta Powerproject project(s) within the ASPUsers code library when you associate the user with their tasks in a project; if the ASPUsers code library does not already exist, it is created automatically. 4. Select a colour to display next to the user on the Site Progress Manager Assign Access screen in the Assignment colour field. Assigning a different colour to each user makes it easier to identify users when you associate them with their tasks within a project. This colour is also assigned to the user s code library entry in the Asta Powerproject project(s). 5. Enter the user's address in the address field. 6. Either enter a password directly into the Password field, or click Generate to generate a password. Admin users and Publisher users use this password to log into Site Progress Manager; Site Progress Mobile users need to enter this password into Site Progress Mobile the first time they launch the app on a mobile device or when they access Site Progress Mobile using a web browser. 7. Use the User role check boxes to specify which elements of Site Progress Mobile the user is able to access (see above for details of the three different types of Site Progress user). 8. Click Apply. Once you have created a Site Progress Mobile user, you may like to them the details that they will need to log into Site Progress Mobile on their mobile device or using a web browser. They will need to know your company ID, their user name and their password. 8.9 Recording details of your projects in Site Progress Manager You must use Site Progress Manager to record details of your Asta Powerproject projects. You must record details of each project that you use in conjunction with Site Progress Mobile. To record details of an Asta Powerproject project: 1. On the main Site Progress Manager screen, click Projects. The Projects screen appears. 2. Click the Standalone radio button if you are using Site Progress Mobile in conjunction with a non-enterprise Asta Powerproject client, or click the Enterprise radio button if you are using it in conjunction with Asta Powerproject Enterprise Elecosoft UK Ltd

89 3. Click Add. A dialog appears in which you can browse for and select the project or database file that you want to add. 4. Select the project or database that you want to add. The Project Password dialog appears: 5. Click the Use the default username and password radio button if you want Site Progress Manager to access the project using its top-level user name and password, or click the Specify a particular username and password for this project radio button if you want Site Progress Manager to access the project using a different user name and password. If you have clicked the latter radio button, enter the user name and password that you want to use in the dialog. Note that this user name and password must exist in the selected project. 6. Click OK. Details of the selected project or database appear in the row. 7. Click Apply Associating users with their tasks within projects You must use Site Progress Manager to associate users with the charts or summary groups within your Asta Powerproject projects for which they are responsible. Users receive information about the tasks within the charts or summary groups for which they are responsible each time you export project information using Site Progress Manager. In order to associate a user with an area of a project, you must first have recorded details of the user and the project in Site Progress Manager. To associate users with their tasks within projects: 1. On the main Site Progress Manager screen, click Assign Access. The Assign Access screen appears. 2. Select the project with which you want to associate one or more users in the Projects field. The hierarchical structure of the project appears in the Assignment view field: 2016 Elecosoft UK Ltd

90 3. In the Assignment view field, navigate to and click a chart or summary group that contains the tasks for which a user is responsible. 4. Click and drag a user from the User list field onto the selected chart or summary group to associate them with that branch of the project. The chart or summary group changes colour to indicate that a user has been associated with it: When you apply your changes, the code library entry within the ASPUsers code library that relates to the user is assigned to the chart or summary group. If you want to assign a different user to a chart or summary group, click and drag the other user onto the chart or summary group to override any existing user association. If you want to unassign all users from a chart or summary group, click and drag the None user onto the chart or summary group. 5. Continue assigning users until all of the required areas of the project are associated with a user. 6. Click Apply Downloading Site Progress Mobile onto mobile devices Site Progress Mobile users can download the Site Progress Mobile app onto any Android, ios or Windows Mobile device from the following locations: Android: ios: Windows Mobile: available in the Windows app store. Search for Asta Site Progress or Siteprogress. Once a user has downloaded the Site Progress Mobile app onto their mobile device, they are prompted to enter your company ID and their user name and password the first time that they access the app. Site Progress Mobile remembers these details, so each user has only to enter them once Elecosoft UK Ltd

91 Note that each file that is exported to Site Progress Mobile can be exported only once. This means that if a Site Progress Mobile user has access to more than one mobile device, or to a mobile device and the web app, they can only access their project information each working period on one mobile device, or via the web app: they cannot access the same period s information on more than one device, or using a mobile device and the web app. For this reason, if a user upgrades their mobile device, they must ensure that they have submitted all of their project information on their old device before they discontinue using the old device, as they will not be able to access the same project information on their new device; they will only be able to access project information relating to new periods on their new device Accessing the Site Progress Mobile web app Site Progress Mobile users who are to record progress using the Site Progress Mobile web app can access it via the following URL: You may need to allow access to the URL if your IT configuration applies restrictions to HTTP traffic Elecosoft UK Ltd

92 9 Installing Business Intelligence for Asta Powerproject You can export Business Intelligence data from Asta Powerproject projects to an external spreadsheet or database, in a form that is optimised for convenient reporting using a reporting tool of your choice. Asta Powerproject includes a Business Intelligence export to Microsoft Excel as standard, which means that you can use Excel s reporting tools to create unique reports on your data. More advanced users can download and install the Business Intelligence Controller, an application that enables you to specify the way in which you want data to be exported to an external database. When you export Business Intelligence data, the data is exported according to a Business Intelligence export model, which defines the information that is included. You can set up as many Business Intelligence export models as you need, with each one defining a different set of information to be exported. When you export Business Intelligence data, only data that your security group s access rights allow you to view are exported. You can use the Business Intelligence Controller to export data from one or more standalone projects or from projects that are stored in a data source on an Enterprise server. Business Intelligence for Asta Powerproject comprises the following elements: The Business Intelligence Controller application. This is an application that enables the export of data from your Asta Powerproject projects into an external database. This application can be installed onto any machine that has access to your project data and to the external database to which you want to export information. Asta Developers Toolkit. This is an application that enables communication between Business Intelligence and your Asta Powerproject Enterprise server. It must be installed alongside the Business Intelligence Controller application; if you install the Business Intelligence Controller on a machine on which an Asta Powerproject client is installed, the Asta Developers Toolkit will already be installed. The Business Intelligence Model Compiler application. This is an application that enables you to compile Business Intelligence export models so that they can be used to export information to Microsoft Excel or to an external database. This application is installed automatically when alongside the Business Intelligence Controller application. The Business Intelligence database. This is a Microsoft SQL Server, Oracle or SQLite database. The Business Intelligence database can be located anywhere; you may want to locate it in the same place as your Asta Powerproject Enterprise data sources. A reporting tool of your choice with which to create reports using the data that has been exported to the Business Intelligence database. The installation of Business Intelligence for Asta Powerproject comprises the following steps: Installing the Asta Developers Toolkit. Specifying the server location method in the Asta Developers Toolkit. Installing the Business Intelligence applications. Creating the Business Intelligence database. Configuring the Business Intelligence Controller application Elecosoft UK Ltd

93 9.1 Installing the Asta Developers Toolkit You must install the Asta Developers Toolkit also known as the OCX onto the computer onto which you are going to install the Business Intelligence applications. The steps involved are exactly the same as those given for installing the Asta Developers Toolkit during the installation of Time Sheet. Follow the instructions in section 6.4, Installing the Asta Developers Toolkit, in order to install the Asta Developers Toolkit for use with the Business Intelligence applications. If you are going to install the Business Intelligence applications onto a machine on which an Asta Powerproject client is installed, the Asta Developers Toolkit will already be present. In this case, move onto section 9.3, Installing the Business Intelligence applications. 9.2 Specifying the server location method in the Asta Developers Toolkit. If you have installed the Asta Developers Toolkit onto the machine on which you are going to install the Business Intelligence applications, you must specify the way in which you want the Asta Developers Toolkit to locate the Enterprise server(s) that you have installed. The server location details that you specify must match those that you specified in section , Specifying the server location method in Asta Serveradmin. The steps involved are exactly the same as those given for installing the Asta Developers Toolkit during the installation of Time Sheet. Follow the instructions in section 6.11, Specifying the server location method in the Asta Developers Toolkit, in order to specify the server location method in the Asta Developers Toolkit. If you are going to install the Business Intelligence applications onto a machine onto which the Asta Developers Toolkit has already been installed and configured, ignore the instructions in this section and move onto section 9.3, Installing the Business Intelligence applications. 9.3 Installing the Business Intelligence applications You install the Business Intelligence Controller application and the Business Intelligence Model Compiler application using the same installation file. There are two versions of the Business Intelligence applications: a 32 bit version and a 64 bit version. You must install the version that corresponds to the Asta Powerproject client that you use: if you install the 64 bit version of the Asta Powerproject client you must install the 64 bit version of the applications; otherwise, you must install the 32 bit version. To install the Business Intelligence applications: 1. Log into the machine on which you want to install the Business Intelligence applications as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears. 4. Follow the steps in the installation wizard to install the Business Intelligence applications, clicking Next to move between the various screens of the wizard Elecosoft UK Ltd

94 The Business Intelligence applications are installed into the following folder by default: C:\Program Files\Asta\BI Applications\ (32-bit systems). C:\Program Files(x86)\Asta\BI Applications\ (64-bit systems). 5. When the installation routine is complete, click Close to exit the wizard. 9.4 Creating the Business Intelligence database You should create the Business Intelligence database using a suitable database management tool: For Microsoft SQL Server, use SQL Server Management Studio. For Oracle databases, use Oracle SQL Developer or SQL*Plus. For SQLite databases, use one of the many SQLite database creation tools that are freely-available. 9.5 Configuring the Business Intelligence Controller application You must specify a connection string in the Business Intelligence Controller application to enable it, or the Asta Powerproject Enterprise server, to communicate with the external Business Intelligence database. Refer to the Sample database connection strings topic in the Business Intelligence Controller Help for details of the connection string syntax Elecosoft UK Ltd

95 10 Installing Asta Project Viewer This section of the document describes how to install Asta Project Viewer, a readonly project viewing application which you can use to open and view projects that have been created in Asta Powerproject. If the project you open has been saved in Asta Powerproject BIM with its associated IFC model or IFC group model, the IFC model or IFC group model opens in Asta Project Viewer when you open the project and you can use Asta Project Viewer to view and navigate around the model. The installation of the Asta Project Viewer comprises the following steps: Installing the Asta Project Viewer application. Additional steps if you are going to view projects that have associated IFC files Installing the Asta Project Viewer application To install Asta Project Viewer: 1. Log into the computer on which you are going to install Asta Project Viewer as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears. 4. Follow the steps in the installation wizard to install the Asta Project Viewer, clicking Next to move between the various screens of the wizard. The Asta Powerproject Enterprise client is installed into the following folder by default: C:\Program Files\Asta\Asta Powerproject\ (32-bit systems). C:\Program Files(x86)\Asta\Asta Powerproject\ (64-bit systems). 5. If you want to install Asta Project Viewer to a location other than the default, click the Custom radio button on the Setup Type screen, which will give you access to an additional page of the wizard in which you can specify an installation folder. 6. Click Install on the final screen of the wizard to install Asta Project Viewer. 7. When the installation routine is complete, click Finish to exit the wizard. 8. Reboot the computer on which you have installed Asta Project Viewer, if you are requested to do so Additional steps if you are going to view projects that have associated IFC files If you are going to use Asta Project Viewer to view projects that have associated IFC files projects that have been created in Asta Powerproject BIM you must carry out two additional steps, as described below, once you have installed Asta Project Viewer. If you are not going to view projects that have associated IFC files, ignore the instructions in this section Elecosoft UK Ltd

96 Ensure that the computer has access to the Elecosoft BIMCloud If you are going to view projects that have associated IFC files which are located in the Elecosoft BIMCloud, you must ensure that all user accounts that need to access the Elecosoft BIMCloud on that computer are able to do so via HTTP, using the following URL: You may need to allow access to the URL if your IT configuration applies restrictions to HTTP traffic. If you are going to view projects that use locally-stored IFC files only with Asta Project Viewer, you do not need to ensure access to the Elecosoft BIMCloud Download and install Microsoft DirectX End-User Runtimes The Microsoft DirectX End-User Runtimes must be installed on the computer on which Asta Project Viewer is installed. If you install Asta Project Viewer onto a computer that does not have the DirectX End-User Runtimes installed, a warning appears when you attempt to display the IFC Model pane. You can download and install the required DirectX End-User Runtimes from the following location: Elecosoft UK Ltd

97 11 Installing Bidcon This section of the document describes how to install Bidcon, which can be used to produce detailed estimates for your projects. Bidcon can be installed as a singleuser application on one computer (a local installation), or as a multi-user application in which a database is installed on a server machine and individual client applications are installed on different computers (a server installation). Bidcon can be used in conjunction with IFC files that are located in the Elecosoft BIMCloud, to produce estimations based on IFC models. Bidcon comprises the following elements: The Bidcon client applications. Many users running the client application on different PCs on a network can access estimations that are stored in a central database. The Bidcon database. This is a Microsoft SQL Server database. The Bidcon database can be located anywhere. The following sections describe the different ways of installing Bidcon: Installing Bidcon as a single-user application on one computer. Installing Bidcon as a multi-user application with the database on a server. Installing Bidcon onto a Terminal Server or Citrix server Installing Bidcon as a single-user application on one computer As detailed in the Elecosoft UK Ltd Product Overview and System Requirements Guide, a version of Microsoft SQL Server and the Microsoft.NET Framework 4 must be installed on the computer on which you are installing Bidcon. If one or both of these items are not present on the computer, you can choose to install them as part of the Bidcon installation. To install the Bidcon application: 1. Log into the computer on which you are going to install the Bidcon application as a user with Administrator privileges. 2. Locate the Bidcon installation file that you have downloaded. 3. Right-click the Bidcon installation file and select Run as administrator from the menu that appears. 4. A dialog appears informing you that a number of temporary files will be placed in a particular folder and that these can be deleted after the installation is complete. Note the folder mentioned by the dialog and click OK to close this dialog. The installation files are unzipped. After a few moments, the following dialog appears: 2016 Elecosoft UK Ltd

98 This dialog displays the different steps that are involved in the installation of Bidcon. A red cross appears against each step that has not yet been completed; once a step has been completed, a green tick appears against it. 5. Carry out the steps listed on the dialog in the order in which they appear. You can carry out each step by clicking the icon that appears against it. For example, to install Bidcon, click and follow the steps in the installation wizard, clicking Next to move between the various screens of the wizard. When installing Bidcon, specify that you are carrying out a local installation. 6. Clicking launches the first screen of the Bidcon Database Setup wizard: 7. Leaving the information in the Server information fields unchanged, click Test Connection to check that the connection to Microsoft SQL Server is valid. If any problems are reported, ensure that Microsoft SQL Server has been installed correctly then test the connection again; once the connection has been validated, click Next to view the second screen of the wizard: 2016 Elecosoft UK Ltd

99 8. You can use this screen to specify the locations of the Bidcon databases that will be created (note that the names of the databases must be BidConSystem and BidConEstimation ). For most installations, simply leave the information in the fields unchanged and click Next to view the final screen of the wizard: 9. You use this screen to specify whether you want to log any errors that may occur when working with Bidcon. Click Finish to exit the wizard when you have done so. 10. Before clicking to install the drivers for the Bidcon hardware key, ensure that the Bidcon hardware key is not connected to the computer; you should reconnect it once the installation is complete. 11. Once you have completed all of the Bidcon installation steps, restart your computer before launching Bidcon Additional steps if you have a Bidcon BIM licence If you have a licence for Bidcon BIM, you must carry out two additional steps, as described below, once you have installed the Bidcon application. If you do not have a licence for Bidcon BIM, ignore the instructions in this section Ensure that the computer has access to the Elecosoft BIMCloud Once you have installed the Bidcon application onto a computer, you must ensure that all user accounts that are to use Bidcon BIM on that computer are able to access the Elecosoft BIMCloud via HTTP, using the following URL: You may need to allow access to the URL if your IT configuration applies restrictions to HTTP traffic Elecosoft UK Ltd

100 Download and install Microsoft DirectX End-User Runtimes The DirectX End-User Runtimes must be installed on the computer on which Bidcon BIM is installed. If you install Bidcon BIM onto a computer that does not have the DirectX End-User Runtimes installed, a warning appears when you attempt to display an IFC model. You can download and install the required DirectX End-User Runtimes from the following location: Installing Bidcon as a multi-user application with the database on a server Installing Bidcon as a multi-user application with the database on a server comprises the following steps: Installing Bidcon on the server machine. Creating Microsoft SQL Server users on the server. Installing Bidcon on the client computers. Configuring Bidcon clients to access the databases on the server. Updating the Bidcon configuration file with the database location Installing Bidcon on the server machine As detailed in the Elecosoft UK Ltd Product Overview and System Requirements Guide, a version of Microsoft SQL Server and the Microsoft.NET Framework 4 must be installed on the server machine onto which Bidcon is to be installed. If one or both of these items are not present on the computer, you can choose to install them as part of the Bidcon installation. To install the Bidcon application on the server machine, follow the instructions in section 11.1, Installing Bidcon as a single-user application on one computer, but in step 5, specify that you are carrying out a server installation rather than a local installation Creating Microsoft SQL Server users on the server You can either create new Microsoft SQL Server database users for use with Bidcon, or use one or more existing users. Note the following: You must give one user, to be used by the system administrator, sysadmin rights over the Bidcon databases, so that the user is able to connect to the databases and install updates to the contents or structure of the databases as required. If you want other Bidcon users to have more limited access rights, create Microsoft SQL Server users with the appropriate access rights. All Bidcon database users must have db_datareader and db_datawriter rights over the Bidcon databases Installing Bidcon on the client computers As detailed in the Elecosoft UK Ltd Product Overview and System Requirements Guide, the Microsoft.NET Framework 4 must be installed on the computers onto which the Bidcon client application is to be installed; a version of Microsoft SQL Server is not required on these computers Elecosoft UK Ltd

101 To install the Bidcon application on the client computers, follow the instructions in section 11.1, Installing Bidcon as a single-user application on one computer, with the following differences: In step 5, specify that you are carrying out a client installation rather than a local installation. Instead of carrying out steps 6 to 9, follow the instructions in section , Configuring Bidcon clients to access the databases on the server. You then need to update the Bidcon configuration file with the location of the databases. To do this, follow the instructions in section , Updating the Bidcon configuration file with the database location Configuring Bidcon clients to access the databases on the server To configure Bidcon clients to access the databases on the server: 1. Once you have installed the Bidcon application on a client computer, click to launch the first screen of the Bidcon Database Setup wizard: 2. Enter either the IP address or the server name of the server machine onto which you installed Bidcon in the Server name field. If you are using Microsoft SQL Server Express, prefix the IP address or server name with \CONSULTEC if you are using SQL Server 2012 or later, or with \BIDCON for earlier versions of Microsoft SQL Server Express. 3. Enter the user name and password of the system administrator Microsoft SQL Server user that you are using for Bidcon or of a user with fewer access rights if appropriate in the User name and Password fields. 4. Click Test Connection to check that the connection to Microsoft SQL Server is valid. If any problems are reported, ensure that Microsoft SQL Server has been installed correctly then test the connection again; once the connection has been validated, click Next to view the second screen of the wizard: 2016 Elecosoft UK Ltd

102 5. Leave the information in the fields unchanged and click Next to view the final screen of the wizard: 6. You use this screen to specify whether you want to log any errors that may occur when working with Bidcon. Click Finish to exit the wizard when you have done so Updating the Bidcon configuration file with the database location Once you have installed the Bidcon client on a computer and configured it to access the databases on the server, you need to update the Bidcon configuration file, BidCon.Settings.config, with the database location. The configuration file can be found in the following location: C:\Users\Public\Consultec\BidCon\ To update the configuration file with the database location: 1. Open the configuration file in Notepad and search for the following line within it: 2. <add key= NetAddress value= min_serveripaddress /> 3. If the line does not currently exist, add it to the configuration file; if the line does exist, but has additional characters at the beginning and end, remove these additional characters. 4. Replace serveripaddress with the IP address of the server on which your databases are located. 5. Save and close the configuration file. If you update this file on one of the client computers, you can copy it to a network location, then copy it to the other client computers replacing the existing configuration file on these computers which saves you from having to update the file on each computer individually Installing Bidcon onto a Terminal Server or Citrix server If you are installing Bidcon onto a Terminal Server or a Citrix server, note the following points: A version of Microsoft SQL Server and the Microsoft.NET Framework 4 must be installed on the server machine. Before you install Bidcon onto the server machine, you must prepare the server machine for installation, as described in 4.1, Preliminary steps if installing onto a Terminal Server or Citrix server. You install Bidcon onto the server machine as described in section 11.1, Installing Bidcon as a single-user application on one computer. If Bidcon s databases are in a different location, follow the instructions in section , Configuring Bidcon clients to access the databases on the server, to configure Bidcon to access the databases Elecosoft UK Ltd

103 The clients that are to use Bidcon should be assigned a shortcut to BidCon.exe, which is located in the folder on the Terminal Server or Citrix server into which Bidcon was installed. After you have installed Bidcon onto the server machine, you must set the Terminal Server or Citrix server back into execute mode, as described in section 4.8, Additional steps if installing onto a Terminal Server or Citrix server. The Terminal Server or Citrix server must be restarted after the installation of Bidcon Moving the Bidcon databases from one machine to another When you carry out a server installation of Bidcon, the following two databases are created on the server machine: C:\Users\Public\Consultec\BidCon\Database\BidConSystem.mdf. C:\Users\Public\Consultec\BidCon\Database\BidConEstimation.mdf. After the initial installation of Bidcon, it is possible to move the Bidcon databases from one machine to another. If you choose to do this, you must then update the Bidcon configuration file with the location of the databases, on each machine on which Bidcon is installed. To do this, follow the instructions in section , Updating the Bidcon configuration file with the database location Elecosoft UK Ltd

104 12 Upgrading an Asta Powerproject Enterprise installation to the latest version This section of the document describes how to upgrade an existing installation of Asta Powerproject Enterprise to the latest version. Upgrading Asta Powerproject Enterprise to the latest version comprises the following steps: Stopping the Asta Name Server and Enterprise server services. Installing the latest version of Asta Powerproject Enterprise. Installing the latest version of Asta Developers Toolkit. Creating a new database for the new version of the software. Configuring a Microsoft SQL Server database user to be the database owner. Creating a new data source that connects to the new database. Converting data from the old data source into the new data source. Specifying that the projects in the new data source should be pre-mounted. Unregistering the old data source. Installing the latest version of the Asta Powerproject Enterprise client Stopping the Asta Name Server and Enterprise server services The first step when upgrading Asta Powerproject Enterprise is to stop the Asta Name Server and Enterprise server services on the server machine on which Asta Powerproject Enterprise is installed. To stop the services: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Control Panel. 2. Within Control Panel, select System and Security, then Administrative Tools. The Administrative Tools window appears. 3. Double-click the Services administrative tool. The Services window appears: 4. Locate the Asta Name Server and Asta Powerproject Enterprise Server services in the list (highlighted in the above illustration). If you have installed more than one Enterprise server to run as a service, a separate service will appear in the list for each Enterprise server. 5. Right-click one of the Asta services and select Stop. The service is stopped Elecosoft UK Ltd

105 6. Stop the other Asta services in the same way. 7. If any other Elecosoft UK Ltd software for example, Asta Serveradmin is currently running on the server machine, close the software before continuing Installing the latest version of Asta Powerproject Enterprise Once you have stopped the Asta Name Server and Enterprise server services, you can install the new version of Asta Powerproject Enterprise. From version onwards, the Asta Archive Components that are used with Asta Archive Manager are installed automatically onto the server machine on which your Enterprise server is located when you carry out an Asta Powerproject Enterprise installation, so you no longer need to install them separately. For this reason, if you use Asta Archive Manager in addition to Asta Powerproject Enterprise and are intending to upgrade it from a version earlier than , you must uninstall the existing Asta Archive Components before going any further. To install the new version of Asta Powerproject Enterprise: 1. Log into the server machine on which you are going to upgrade Asta Powerproject Enterprise as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears. 4. A dialog appears informing you that you are about to upgrade Asta Powerproject Enterprise. Click Yes to continue. 5. Follow the steps in the installation wizard to upgrade Asta Powerproject Enterprise to the latest version, clicking Next to move between the various screens of the wizard. 6. When the installation routine is complete, click Finish to exit the wizard Installing the latest version of Asta Developers Toolkit Once you have installed the new version of Asta Powerproject Enterprise, you must install the new version of the Asta Developers Toolkit. To install the new version of the Asta Developers Toolkit: 1. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 2. Right-click the setup.exe file and select Run as administrator from the menu that appears. 3. A dialog appears informing you that you are about to upgrade the Asta Developers Toolkit. Click Yes to continue. 4. Follow the steps in the installation wizard to upgrade the Asta Developers Toolkit, clicking Next to move between the various screens of the wizard. 5. When the installation routine is complete, click Finish to exit the wizard Creating a new database for the new version of the software Once you have installed the new version of the Asta Developers Toolkit, you must create a new database to use with the upgraded version of Asta Powerproject Enterprise Elecosoft UK Ltd

106 Follow the instructions in section 2.1, Creating a Microsoft SQL Server database, in order to create a new database Configuring a Microsoft SQL Server database user to be the database owner Once you have created the new database, you must configure the appropriate Microsoft SQL Server user to be the database owner. To configure the user to be the database owner: 1. Within the Microsoft SQL Server Management Studio Object Explorer, expand the Security folder, expand the Logins folder, then right-click the user that you want to configure and select Properties: The Login Properties dialog appears. 2. On the User Mapping page of the dialog, in the Users mapped to this login group, select the check box to the left of the new database: 3. The name of your database should now be appended to the title of the Database role membership role for group. In this group, select the db_owner check box: 4. Click OK Elecosoft UK Ltd

107 12.6 Creating a new data source that connects to the new database Once you have created the new database, you must create a corresponding data source in Asta Serveradmin. Follow the instructions in section 2.9, Creating a data source in Asta Serveradmin, in order to create a new data source Converting data from the old data source into the new data source Once you have created the new database and its corresponding data source, you must convert the data from the old data source into the new data source. To convert data from the old data source into the new data source: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch the Enterprise server with which the database is associated from the Windows Start screen do not start it as a service. The Enterprise Server window appears: 2. Type datasources and press ENTER. You see a list of the data sources on the server. Make a note of the IDs of both the old and new data sources. 3. Type convert <old data source ID> <new data source ID> at the command prompt and press ENTER, where <old data source ID> is the ID of the data source you want to convert and <new data source ID> is the ID of the data source into which you want to transfer the converted data. The data from the old data source is converted into the latest format and copied into the new data source. Depending on the size of the data source, this may take a considerable length of time. If the data source that you need to convert contains a large number of projects, you may like to convert a range of projects at a time. You can do this by specifying the range of projects within the data source that you want to convert. The full syntax of the convert command is convert <old data source ID[:<project ID>[- <end project ID>]]> <new data source ID>, where <project ID> is the number of the first project that you want to convert and <end project ID> is the number of the last project that you want to convert Elecosoft UK Ltd

108 For example: convert AAAAAA:1000 BBBBBB would convert project 1000 and its baselines in data source AAAAAA into data source BBBBBB. convert AAAAAA: BBBBBB would convert project 1000 in data source AAAAAA into data source BBBBBB, but would not convert its baselines. convert AAAAAA: BBBBBB would convert projects 1000, 1001, 1002 and 1003 in data source AAAAAA into data source BBBBBB, but would only convert the projects' baselines if the baseline project IDs were included in the range specified Specifying that the projects in the new data source should be pre-mounted Once you have converted the data from the old data source into the new data source, you should specify that the projects and baselines within the new data source should be pre-mounted each time the Enterprise server starts. Follow the instructions in section 4.9, Specifying that projects and their baselines should be pre-mounted, in order to specify that the projects and baselines within the new data source should be pre-mounted Unregistering the old data source You can now unregister the old data source. Unregistering a data source does not delete it; it merely ensures that the data source does not appear whenever data sources or projects are listed in Asta Powerproject Enterprise. To unregister the old data source: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Asta Serveradmin. 2. Select the old data source in the left-hand pane. 3. Select the Unregister command from the Datasource menu Installing the latest version of the Asta Powerproject Enterprise client You can now install the new version of the Asta Powerproject Enterprise client application. To install the new version of the Asta Powerproject Enterprise client application: 1. Log into the computer on which you are going to install the Asta Powerproject Enterprise client as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears. 4. A dialog appears informing you that you are about to upgrade the Asta Powerproject application. Click Yes to continue. 5. Follow the steps in the installation wizard to upgrade the Asta Powerproject Enterprise client to the latest version, clicking Next to move between the various screens of the wizard. 6. When the installation routine is complete, click Finish to exit the wizard Elecosoft UK Ltd

109 13 Upgrading an existing Asta Archive Manager installation to the latest version This section of the document describes how to upgrade an existing installation of Asta Archive Manager to the latest version. Upgrading Asta Archive Manager to the latest version comprises the following steps: Uninstalling the existing Asta Archive Components. Installing the latest version of Asta Powerproject Enterprise. Installing the latest version of the Asta Archive Manager application Uninstalling the existing Asta Archive Components From version onwards, the Asta Archive Components are installed automatically onto the server machine on which your Enterprise server is located when you carry out an Asta Powerproject Enterprise installation, so you no longer need to install them separately. For this reason, if you are upgrading Asta Archive Manager from a version earlier than , you must uninstall the existing Asta Archive Components before going any further. To uninstall the existing Asta Archive Components: 1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Control Panel. 2. Within Control Panel, select Programs, then Uninstall a program. The Programs and Features window appears. 3. Select the Asta Archive Components program and click Uninstall. 4. Follow the prompts onscreen to uninstall the Asta Archive Components, rebooting the server machine afterwards if you are prompted to do so Installing the latest version of Asta Powerproject Enterprise Once you have uninstalled the existing Asta Archive Components, you must install, or upgrade to, the latest version of Asta Powerproject Enterprise. This is to ensure that the latest version of the Asta Archive Components are installed onto the server machine on which the Enterprise server is located. Follow the instructions in section 12, Upgrading an Asta Powerproject Enterprise installation to the latest version, in order to upgrade to the latest version of Asta Powerproject Enterprise Installing the latest version of the Asta Archive Manager application Once you have installed the latest version of Asta Powerproject Enterprise, you can install the latest version of the Asta Archive Manager application. To install the new version of the Asta Archive Manager application: 1. Log into the computer on which the existing version of Asta Archive Manager is installed as a user with Administrator privileges. 2. Locate the setup.exe file within the folder into which you unzipped the downloaded installation files. 3. Right-click the setup.exe file and select Run as administrator from the menu that appears Elecosoft UK Ltd

110 4. A dialog appears informing you that you are about to upgrade Asta Archive Manager. Click Yes to continue. 5. Follow the steps in the installation wizard to upgrade Asta Archive Manager to the latest version, clicking Next to move between the various screens of the wizard. 6. When the installation routine is complete, click Finish to exit the wizard Elecosoft UK Ltd

111 14 Upgrading an existing Time Sheet installation to the latest version This section of the document describes how to upgrade an existing installation of Time Sheet for Asta Powerproject to the latest version. If you are upgrading Time Sheet to a later version, you normally need to upgrade Asta Powerproject Enterprise to the latest version as well. If this is the case, you should upgrade Asta Powerproject before you upgrade Time Sheet. See section 12, Upgrading an Asta Powerproject Enterprise installation to the latest version, for details of how to do this. Upgrading Time Sheet for Asta Powerproject to the latest version comprises the following steps: Copying your existing Time Sheet configuration files. Uninstalling the existing Time Sheet software. Installing the latest version of Time Sheet. Checking that the necessary users still have access to configuration files. Merging existing configuration settings into the new version. Upgrading the Time Sheet database. Re-registering your Asta Powerproject project(s) in Time Sheet Copying your existing Time Sheet configuration files The first step when upgrading Time Sheet is to make a copy of the files in which Time Sheet s configuration settings are stored: config.xml and columns.xml. These files are located in the folder in which Time Sheet is installed. Copying these files means that you will be able to carry over your existing configuration settings into the new version of Time Sheet. To copy your existing Time Sheet configuration settings: 1. Log into the server machine on which Time Sheet is installed as a user with Administrator privileges. 2. Launch Windows Explorer and navigate to the folder in which Time Sheet is installed (which is C:\Inetpub\wwwroot\AstaTimesheet\ by default). 3. Select and copy config.xml and columns.xml, then paste them into a different folder, for example C:\Temp\ Uninstalling the existing Time Sheet software Once you have copied the Time Sheet configuration files, you can uninstall the existing installation of Time Sheet. 1. On the server machine on which Time Sheet is installed, launch Control Panel. 2. Within Control Panel, select Programs, then Uninstall a program. The Programs and Features window appears. 3. Select the Time Sheet for Asta Powerproject program and click Uninstall. 4. Follow the prompts onscreen to uninstall Time Sheet, rebooting the server machine afterwards if you are prompted to do so. 5. Launch Windows Explorer and navigate to the folder in which Time Sheet was installed, then delete the config.xml and columns.xml files from that folder Elecosoft UK Ltd

112 14.3 Installing the latest version of Time Sheet Once you have uninstalled the old version of Time Sheet, you can install the latest version. Follow the instructions in section 6.7, Installing Time Sheet, in order to install the latest version of Time Sheet. Once you have installed the latest version of Time Sheet, you must restart Microsoft Internet Information Services on the server machine on which Time Sheet is installed. If you rebooted the server machine at the end of the installation routine, Microsoft Internet Information Services will have been restarted automatically Checking that the necessary users still have access to configuration files Once you have installed the latest version of Time Sheet, you must check that two user accounts still have access to the folder in which Time Sheet is installed and over all of the files and subfolders that it contains. The IIS_IUSRS account requires full control over the folder and the Users account requires Modify and Write access. Follow the instructions in section 6.14, Granting the necessary users access to Time Sheet configuration files, in order to check that the users still have the necessary permissions Merging existing configuration settings into the new version Once you have checked that the IIS_IUSRS user still has full control over the Time Sheet configuration files, you must merge your configuration settings from the earlier version of Time Sheet into the latest version. To merge your existing configuration settings into the new version of Time Sheet: 1. On the server machine on which you have installed Time Sheet, launch a command prompt, ensuring that you run it as Administrator. A command prompt window appears: 2. In the command prompt window, change the directory location to the folder in which Time Sheet has been installed. 3. Type TimesheetFileMerger.exe <location of old config.xml> <location of new config.xml> and press ENTER. For example, if you pasted the copy of config.xml into C:\Temp and accepted the default installation folder for Time Sheet, enter: TimesheetFileMerger.exe C:\Temp C:\Inetpub\wwwroot\ AstaTimesheet If either of the file locations contains one or more spaces, you must enclose the pathnames in double quotation marks, as in the following example: TimesheetFileMerger.exe C:\Temporary Folder C:\Inetpub\wwwroot\AstaTimesheet You see a confirmation that the config.xml files have been merged successfully Elecosoft UK Ltd

113 4. Copy the old columns.xml file and paste it into the folder in which Time Sheet has been installed Upgrading the Time Sheet database Once you have installed the latest version of Time Sheet, you must upgrade the Time Sheet database to the latest format. You must backup your Time Sheet database before upgrading it to the latest format. You upgrade the Time Sheet database to the latest format by executing one or more SQL files, which are located in the folder in which Time Sheet is installed. The number of files that you must execute depends on the version of Time Sheet that you had installed prior to upgrading. For example, if the latest version of Time Sheet were and you were upgrading from version , you would have to execute the update_tablesv602.sql file; if you were upgrading from version , you would have to execute update_tablesv601.sql file, then the update_tablesv602.sql file. To upgrade the Time Sheet database: 1. On the server machine on which you installed Time Sheet, launch SQL Server Management Studio. 2. Click the File menu, then select Open File. The Open File window appears. 3. Navigate to the folder into which you installed Time Sheet (which is C:\Inetpub\wwwroot\AstaTimesheet\ by default). 4. Select the appropriate update_tables file and click Open. The file opens in SQL Server Management Studio. The first script that you need to run is the one that relates to the version of Time Sheet immediately after the version that you were using previously. 5. Ensure that the Time Sheet database is selected in the Available Databases control on the SQL Editor toolbar, then click Execute in the same toolbar: The SQL file updates the tables in the Time Sheet database. 6. Repeat steps 2 to 5 to execute any further files that are required in order to update the tables in the database to the latest version Re-registering your Asta Powerproject project(s) in Time Sheet If, as well as upgrading Time Sheet, you have had to upgrade your Asta Powerproject data source to a later version of Asta Powerproject, the ID of the data source that contains your projects will be different following the upgrade. If this is the case, you must update the ID of each project s data source in the DS ID field on the Asta Powerproject Options screen of Time Sheet Configuration. Follow the instructions in section 6.16, Registering the project(s) to be used with Time Sheet, in order to re-register your project(s) in Time Sheet Elecosoft UK Ltd

114 15 Upgrading an existing Web Access installation to the latest version This section of the document describes how to upgrade an existing installation of Web Access for Asta Powerproject to the latest version. If you are upgrading Web Access to a later version, you normally need to upgrade Asta Powerproject Enterprise to the latest version as well. If this is the case, you should upgrade Asta Powerproject before you upgrade Web Access. See section 12, Upgrading an Asta Powerproject Enterprise installation to the latest version, for details of how to do this. Upgrading Web Access for Asta Powerproject to the latest version comprises the following steps: Copying your existing Web Access configuration file. Uninstalling the existing Web Access software. Installing the latest version of Web Access. Checking that the necessary users still have access to configuration files. Implementing existing configuration settings in the new version. Re-registering your Asta Powerproject project(s) in Web Access Copying your existing Web Access configuration file The first step when upgrading Web Access is to make a copy of the file in which Web Access s configuration settings are stored: rw_config.xml. This files is located in the folder in which Web Access is installed. Copying this file means that you will be able to carry over your existing configuration settings into the new version of Web Access. To copy your existing Web Access configuration settings: 1. Log into the server machine on which Web Access is installed as a user with Administrator privileges. 2. Launch Windows Explorer and navigate to the folder in which Web Access is installed (which is C:\Inetpub\wwwroot\AstaWebAccess\ by default). 3. Select and copy rw_config.xml, then paste it into a different folder, for example C:\Temp\ Uninstalling the existing Web Access software Once you have copied the Web Access configuration file, you can uninstall the existing installation of Web Access. 1. On the server machine on which Web Access is installed, launch Control Panel. 2. Within Control Panel, select Programs, then Uninstall a program. The Programs and Features window appears. 3. Select the Web Access for Asta Powerproject program and click Uninstall. 4. Follow the prompts onscreen to uninstall Web Access, rebooting the server machine afterwards if you are prompted to do so. 5. Launch Windows Explorer and navigate to the folder in which Web Access was installed, then delete the rw_config.xml file from that folder Elecosoft UK Ltd

115 15.3 Installing the latest version of Web Access Once you have uninstalled the old version of Web Access, you can install the latest version. Follow the instructions in section 7.5, Installing Web Access, in order to install the latest version of Web Access. Once you have installed the latest version of Web Access, you must restart Microsoft Internet Information Services on the server machine on which Web Access is installed. If you rebooted the server machine at the end of the installation routine, Microsoft Internet Information Services will have been restarted automatically Checking that the necessary users still have access to configuration files Once you have installed the latest version of Web Access, you must check that two user accounts still have access to the folder in which Web Access is installed and over all of the files and subfolders that it contains. The IIS_IUSRS account requires full control over the folder and the Users account requires Modify and Write access.. Follow the instructions in section 7.10, Granting the necessary users full access to Web Access configuration files, in order to check that the users still have the necessary permissions Implementing existing configuration settings in the new version Once you have checked that the IIS_IUSRS user still has full control over the Web Access configuration files, you must replace the new version of rw_config.xml with the version that you copied earlier. To do this, on the server machine on which you have installed Web Access, copy the old rw_config.xml file and paste it into the folder in which Web Access has been installed, replacing the newer version of the file Re-registering your Asta Powerproject project(s) in Web Access If, as well as upgrading Web Access, you have had to upgrade your Asta Powerproject data source to a later version of Asta Powerproject, the ID of the data source that contains your projects will be different following the upgrade. If this is the case, you must update the ID of each project s data source in the DS ID field on the Asta Powerproject Options screen of Web Access Configuration. Follow the instructions in section 7.11, Registering the project(s) to be used with Web Access, in order to re-register your project(s) in Web Access Elecosoft UK Ltd

116 16 Moving Asta Powerproject Enterprise to a different server machine This section of the document describes how to move an installation of Asta Powerproject Enterprise from one server machine to another. You may need to do this if you are upgrading your hardware. If you are carrying out a general upgrade of hardware, you may also be moving your Microsoft SQL Server database from one server machine to another. This is not covered by these instructions; you should refer to your database software provider s documentation for details of how to do this. Moving an installation of Asta Powerproject Enterprise from one server machine to another comprises the following steps: Installing Asta Powerproject Enterprise onto the new server machine. Installing the Asta Name Server and the Enterprise server to run as services. Configuring the Asta Name Server and Enterprise server services. Configuring Asta Powerproject Enterprise registry settings. Re-registering a data source in Asta Serveradmin. Configuring Asta Powerproject Enterprise using Asta Serveradmin. Configuring firewalls to work with Asta Powerproject Enterprise Installing Asta Powerproject Enterprise onto the new server machine The first step is to install Asta Powerproject Enterprise onto the new server machine. Follow the instructions in section 2.4, Installing Asta Powerproject Enterprise, in order to install Asta Powerproject Enterprise onto the new server machine Installing the Asta Name Server and the Enterprise server to run as services The next step is to install the Asta Name Server and the Enterprise server to run as services on the new server machine, so that they are loaded automatically when Windows starts and run in the background. Follow the instructions in section 2.5, Installing the Asta Name Server and the Enterprise server to run as services, in order to install the Asta Name Server and the Enterprise server to run as services Configuring the Asta Name Server and Enterprise server services Once you have installed the Asta Name Server and Enterprise server to run as services, you must configure them to start automatically on the new server machine. Follow the instructions in section 2.6, Configuring the Asta Name Server and Enterprise server services, in order to configure the Asta Name Server and Enterprise server services Configuring Asta Powerproject Enterprise registry settings Once you have configured the Asta Name Server and Enterprise server services to start automatically, you must configure the registry settings on the new server machine Elecosoft UK Ltd

117 Follow the instructions in section 2.7, Configuring Asta Powerproject Enterprise registry settings, in order to configure the registry settings on the new server machine Re-registering a data source in Asta Serveradmin You now need to re-register a data source in Asta Serveradmin, to work with your database. The steps involved in re-registering a data source are very similar to those involved in creating a new data source, the difference being that when you reregister a data source, any existing information in your database is not overwritten. If you were to create a new data source in this situation, the data source creation process would overwrite any existing information in your database. To re-register a data source in Asta Serveradmin: 1. On the new server machine, launch Asta Serveradmin. 2. Select the Reregister command from the Datasource menu. The Register Datasource wizard appears. 3. On the first screen of the wizard, enter a suitable name and description for the data source in the Name and Description fields; it is a good idea to give the data source a description that describes the projects that it will contain. 4. If you have installed more than one Enterprise server on the server machine or if you want to enable users to log in automatically via Active Directory, enter a positive integer that links the data source to a particular server in the Server identification number field: If you only use a single server and you are not using Active Directory to enable automatic login, you can leave this number set to 1. You can make a data source inaccessible to all servers (ie take it offline), by setting this number to zero. 5. Click Next. 6. On the next screen of the wizard, click Build to access the Connection String Generation wizard, which you can use to create the ActiveX Data Objects (ADO) connection string that specifies the database provider and the data source to which the Enterprise server should connect. 7. On the first screen of the wizard, click the Microsoft SQL Server database radio button: 2016 Elecosoft UK Ltd

118 8. Click Next. 9. On the second screen of the wizard, enter the name of the server machine on which the Microsoft SQL Server database is located in the Please enter the name of the machine that is running SQL Server field, noting the following points: If you are using Microsoft SQL Server 2012 Express, enter <server machine name>\sqlexpress, where <server machine name> is the name of the server machine. For example, if the server machine is called Server1, enter Server1\SQLExpress. If you are using Microsoft SQL Server 2012 Express and you have installed Asta Powerproject Enterprise onto the server machine on which your database is located, enter.\sqlexpress. If you are using a version of Microsoft SQL Server 2012 other than Express, simply enter the name of the server machine. For example, if the server machine is called Server1, enter Server Enter the name that you applied to the Microsoft SQL Server database when you created it in 2.1, Creating a Microsoft SQL Server database, in the Please enter the catalog (database) to use field: 11. Click Next. 12. On the third screen of the wizard, enter the user name and password of the Microsoft SQL Server user that you created in section 2.2, Creating a Microsoft SQL Server database user: 13. Leaving the Use SSPI integraged security check box cleared, click Finish to close the Connection String Generation wizard and return to the Register Datasource wizard, where a connection string containing the information you have provided appears in the Connection string field: 2016 Elecosoft UK Ltd

119 14. Leaving the Optimise transaction data check box selected, select or clear the Server/database on same machine check box as appropriate depending on whether you have installed Asta Powerproject Enterprise on the server machine on which Microsoft SQL Server is installed. 15. If you have installed Asta Powerproject Enterprise onto a different server machine, create a folder on the server machine on which Microsoft SQL Server is installed and give the user account that is being used to run the Asta Powerproject Enterprise server Full Control access rights to the folder. Temporary files will be stored in this folder. You must then specify the location of the folder in the Server/database shared folder field, in the format \\<server name\<path and folder name>. For example, if the server machine is called Server1 and the folder is on the root of the server and called AstaTemp, enter \\Server1\AstaTemp. 16. Click Test to test that the connection to the database works correctly. A message appears informing you whether or not the connection string is valid. If the connection string is not valid, double-check the details of the database and user that you created, then create the connection string again. 17. Click Finish to close the New Datasource wizard. The new data source is created and appears in Asta Serveradmin: 16.6 Configuring Asta Powerproject Enterprise using Asta Serveradmin Once you have re-registered the data source, you must use Asta Serveradmin to configure Asta Powerproject Enterprise on the new server machine. Follow the instructions in section 2.10, Configuring Asta Powerproject Enterprise using Asta Serveradmin, in order to configure Asta Powerproject Enterprise Configuring firewalls to work with Asta Powerproject Enterprise If you have installed Asta Powerproject Enterprise onto a server machine that is running Microsoft Windows 2008 Server R2 or later, you must configure the firewall on the new server machine to enable your Asta Powerproject clients, the Asta Name Server and the Enterprise server to communicate with each other. Follow the instructions in section 2.11, Configuring firewalls to work with Asta Powerproject Enterprise, in order to configure the firewall on the new server machine to work with Asta Powerproject Enterprise Elecosoft UK Ltd