Installing signature

Transcription

1 Installing signature Installation Guide signature Support Team January 2010 Manual version 7.1 A guide on how to install signature and to get started using it. Covers all platforms. Copyright by Branded Mails. All rights reserved.

2 CONTENTS What is signature?... 3 Installing signature... 3 Installation Steps... 3 Additional Installation Steps for Windows 2003 Server Edition... 6 Additional Steps for Windows 2008 Server Edition... 8 Adjusting the Settings Database... 8 Using Microsoft Access as The Settings Database... 9 Using Microsoft SQL Server for The Settings Database... 9 SQL Server SQL Server Connecting the Cockpit to The Settings Database Running signature for Other Users Upgrading from version 5.x Upgrading the Settings Database: Microsoft SQL Server Upgrade the Settings Database: MS Access database Learn more and Contact Information Page 2

3 WHAT IS SIGNATURE? signature enables you to centrally control all signatures used in s sent through Microsoft Outlook. signature consists of the following parts: Cockpit Settings database A small executable file sign.exe Administration tool for controlling settings, signatures, campaigns, users, etc. Database connected to the Cockpit, which contains all information controlled by the Cockpit and user specific information, such as log files, last run times, signatures. The settings database must be accessible for all users who use signature. File that is run on each user computer (usually during logon) and that creates and controls signatures for this user. signature works with all Microsoft Office Outlook versions and with OWA for Exchange 2003 and signature is not a server product, but the Cockpit can be installed on a server, so that remote access and possibility for administration is ensured. Exchange is not needed for signature to work, nor is anything needed installed on any Exchange Servers. In the default installation package, for the settings database a Microsoft Access database is used. We also recommend using SQL Server for the settings database, if it is necessary. The necessary script for this scenario is available on our web site Note: You should only install signature once. You can also install the Cockpit on your super users' PCs. You do not need to install anything on any other PCs; however, all users must run the sign.exe executable file. INSTALLATION STEPS These installation steps are applied for all Windows versions. If the installation is performed on Windows 2003 Server (including SBS) and Windows 2008, additional steps might be necessary depending on your security settings. The necessary steps are also described later in this guide. Note: In order for the installation the process to complete, you need sufficient rights to install software on the PC that will host signature. To install signature, proceed as follows: 1. Download the software installation file signature.msi from and save this file on your computer. Page 3

4 2. Double-click the signature.msi file to start the installation wizard. The following window appears: 3. Click Next to proceed. In the End-user License Agreement window that appears, read and accept the term of the License Agreement. Page 4

5 4. Click Next to proceed. In the Destination Folder window, choose the installation path. The default path is C:\program files\ signature. 5. Click Next to proceed. Now you are ready to install the application. Click Install. If you are installing on Windows P, Vista or 7, select the launching application, Page 5

6 6. When the installation completes, double-click the signature Cockpit shortcut that has been added to your Desktop during the installation. The Cockpit opens and you are ready to get started using your new software. Note: If you are installing signature on Windows 2003 or Windows 2008 server platforms, the following warning message appears. Please follow the steps further in this guide on how to perform the installation on these Windows versions. Also, end the Cockpit.exe process in the Task Manager, as most probably it will remain running after an unsuccessful launching. ADDITIONAL INSTALLATION STEPS FOR WINDOWS 2003 SERVER EDITION The Data Execution Prevention on Windows 2003 Server prohibits the Cockpit from being able to run automatically. To allow the Cockpit to be run, proceed as follows: 1. Right-click My computer and select Properties. 2. Open the Advanced tab, and in the Performance section click Settings. Page 6

7 3. In the Performance Options window that appears open Data Execution Prevention tab, click Add and browse to the installation directory of signature. Unless you have changed it during the installation, it is c:\program files\ signature. 4. Once the Cockpit is added, it appears in the programs list. To finish the additional installation steps for the Windows 2003 Server, click OK. You are now ready to launch the Cockpit. Page 7

8 ADDITIONAL STEPS FOR WINDOWS 2008 SERVER EDITION The Data Execution Prevention on Windows 2008 Server prohibits the Cockpit from being able to run automatically. To allow the Cockpit to be run, proceed as follows: 1. Right-click Computer and select Properties. Click on Advanced System Settings. 2. Open the Advanced tab and then in the DEP form, click Settings. 3. In the Performance Options window that appears open the Data Execution Prevention tab, click Add and browse to the installation directory of signature. Unless you have changed it during the installation, it is c:\program files\ signature. 4. Once the Cockpit is added, it appears in the programs list. To finish the additional installation steps for the Windows 2008 Server, click OK. You are now ready to launch the Cockpit. ADJUSTING THE SETTINGS DATABASE The Cockpit controls the data in the settings database, but to be used by other users, the settings database must be available or shared via standard network sharing. Page 8

9 USING MICROSOFT ACCESS AS THE SETTINGS DATABASE The default option for the settings database is using Microsoft Access. The settings.mdb file is located in the installation directory. To make the default settings database available to other users, copy the settings.mdb file to a network share. If for performance and security reasons, you choose to use SQL server, perform the steps described in the following sections. USING MICROSOFT SQL SERVER FOR THE SETTINGS DATABASE Both SQL Server 2000 or 2005 can be used. SQL SERVER 2005 To set up a settings database on an SQL Server 2005, proceed as follows: 1. Download the script signature_sql2005.sql from the support section. 2. Open SQL Management Studio on the SQL Server you want to use. The script performs the following necessary tasks: Creates a database called signature Creates necessary tables Inserts content into tables Creates login and standard user and super user access Grants correct access to both users. 3. The script creates two database users called signature_superuser with password changemenow, and signature_standarduser with password changemealso. Change the passwords. You can also change the database user names, but then you need to make sure to replace them in all respective places. 4. Run the script from Management Studio by clicking New Query, open the SQL file and execute the script. The settings database is now prepared. SQL SERVER 2000 To set up a settings database on an SQL Server 2000, proceed as follows: 1. Download the script signature_sql2000.sql from the support section. 2. Open Enterprise Manager on the SQL Server you want to use. The script performs the following necessary tasks: Creates a database called signature Creates necessary tables Inserts content 3. A database must be created. To do so, enter the Enterprise Manager, right-click Database and create a database called signature. Page 9

10 4. Select the newly created database, open the SQL script and run it from Query Analyzer. 5. Create two database users: a super user login and a standard user login for everybody. 6. Grant the following rights for tables for the super user: Table Select Insert Update Delete Campaign Categories General Disclaimer License LicenseGroups OWA Settings Stationery lgdacampaigngroups lgdausers lgdanousers lgdagroups livemessage Pictures Preview rootcontext SettingsLegal Users lgdaowa lgdacollected lgdadefault Page 10

11 7. Grant the following rights for tables for the standard user: Table Select Insert Update Delete Campaign Categories General Disclaimer License LicenseGroups OWA Settings Stationery lgdacampaigngroups lgdausers lgdanousers lgdagroups livemessage Pictures Preview rootcontext SettingsLegal Users lgdaowa lgdacollected lgdadefault For more detailed information, see articles on The settings database is now prepared. CONNECTING THE COCKPIT TO THE SETTINGS DATABASE To connect the Cockpit to another settings database than the default, proceed as follows: 1. Open the Cockpit and open the Setup tab. Click Change database. Page 11

12 The Settings Database Location window with the current database connection appears. 2. Enter the credentials of your SQL Server and click Test. Once the test is successful, save the connection. 3. For changes to take effect, restart the Cockpit. Note: You must make sure that the database is set up for being used also with SQL users and not only Microsoft Windows users. If you only use Integrated Windows Authentication, you need to set the permissions manually according to the instructions above. If you have not set up security level appropriately, the following error message will appear when trying to connect to the database: If that is the case, make sure that either permissions for Integrated Authentication are set up, or allow SQL users. It is not within the scope of this manual to describe these actions in detail. Page 12

13 RUNNING SIGNATURE FOR OTHER USERS The sign.exe file retrieves settings and template information from the settings database, collects user contact details, and generates ready signatures. The sign.exe file also sends log information to the settings database each time a user runs the sign.exe file. The log information for an individual user can be seen in the Cockpit s Diagnostics section, Open Log file. The log information for all users can be seen in the Cockpit s Diagnostics section, Status Monitor. When the Cockpit has been installed and the settings database adjusted, to run signature for other users, it must be ensured that the sign.exe file is run on every user s computer. The sign.exe file can be simply shared and users may run it manually each time they need an update from the settings database, however, most common way is to run the sign.exe automatically during logon. Note: If you have installed Microsoft Outlook on a server platform, you also need to enable DEP for sign.exe in the same way as for the Cockpit. To make the sign.exe file accessible to all users for running it manually, copy the sign.exe file from the installation directory c:\program Files\ Signature\ to a network share. The sign.exe file is digitally signed by Branded Mails for your security and performance. To set running the sign.exe file automatically during logon, proceed as follows: 1. From the installation directory c:\program Files\ Signature\ copy the sign.exe file to the NETLOGON share or another share, where files for running automatically during logon, are located. 2. Use one of the following scripts as example for adjusting the current logon script. Bat file: START \\server\netlogon\sign.exe Provider=sqloledb;Data Source=SQLKSERVER01;Initial Catalog= Signature;User Id= Signature_Superuser;Password=changemenow; VB Script: Set oshell = CreateObject("WScript.Shell") oshell.run \\server\netlogon\sign.exe Provider=sqloledb;Data Source=SQLKSERVER01;Initial Catalog= Signature;User Id= Signature_Superuser;Password=changemenow;", 0, True Information in the example is fictive; it must be replaced with your own. Copy the connection to the settings database from the Cockpit s Change Database section. Page 13

14 UPGRADING FROM VERSION 5. To upgrade from version 5., proceed as follows: 1. Obtain a valid license key for version 7.. Ask for your new license key from your account manager or to info@brandedmails.com stating your customer name and providing the existing license key in the . Note that maintenance subscribers can have only a new key. UPGRADING THE SETTINGS DATABASE: MICROSOFT SQL SERVER 1. Download the upgrade script from the support section. Choose MS SQL 2000 or MS SQL 2005 according to your server. 2. Download and install the latest version of the Cockpit as described in Installing signature. 3. Reconnect to the new settings database as described in Connecting the Cockpit to The Settings Database. 4. Restart the Cockpit. 5. Download and replace the existing sign.exe file with the new version. The sign.exe file is located in the installation directory c:\program Files\ Signature\, or downloadable from UPGRADE THE SETTINGS DATABASE: MS ACCESS DATABASE 1. For security reasons make a copy of the existing settings database. 2. Download the latest version of the settings.mdb from the support section. 3. Open both databases: the existing and the new blank database. 4. From the new blank database copy or drag the following tables to the existing settings database: lgdaowa SettingsLegal Users lgdacollected 5. To the lgdausers table, add the following columns manually: custom_num6 (Number / Long integer) custom_num7 (Number / Long integer) custom_num8 (Number / Long integer) custom_num9 (Number / Long integer) custum_num10 (Number / Long integer) custom_str6 (text size 250) custom_str7 (text size 250) custom_str8 (text size 250) custom_str9(text size 250) custom_str10 (text size 250) owa_error (text size 250) owa_lastrun (text size 50) 6. To the Preview table, add the following columns manually: custom_str1 (memo) custom_str2 (memo) custom_str3 (text size 50) custom_str4(text size 50) custom_str5 (text size 50) Page 14

15 7. Download and install the latest version of the Cockpit as described in Installing signature. 8. Reconnect to the new settings database as described in Connecting the Cockpit to The Settings Database. 9. Restart the Cockpit. 10. Download and replace the existing sign.exe file with the new version. The sign.exe file is located in the installation directory c:\program Files\ Signature\, or downloadable from Page 15

16 LEARN MORE AND CONTACT INFORMATION You can find useful information about using signature, administration, modules, etc. on our web site : Guides Support forum Video demonstrations and guides. Rued Langgaards Vej 7, 5 DK-2300 Copenhagen Denmark 823 Salisbury House 29 Finsbury Circus London, EC2M 5QQ United Kingdom Tel: Tel: +44 (0) Fax: Fax: +44 (0) support@brandedmails.com Page 16