Mamut Guide for Add on for Client Manager

Mamut Business Software

Introduction

Mamut Enterprise Client Manager

Documentation for the Extensions of Mamut Enterprise System

Mamut Client Manager

Version: 12

II

Table of Contents

CLIENT MANAGER ..................................................................................................................... 1 Client Start ................................................................................................................................................................................2 Client Update............................................................................................................................................................................3

ADMINISTRATION OF THE DATABASE ............................................................................. 5 The Database............................................................................................................................................................................5 How to move a Company Database between two System Databases ................................................................6 How to Create a new system database with Client Manager ................................................................................7 Installed Files ...........................................................................................................................................................................7

LAYOUT OF MAMUT BUSINESS SOFTWARE .................................................................. 10 Setup of Mamut Business Software with Mamut Bureau .................................................................................... 10 Set Up in an ASP Environmentin an ASP Environment ........................................................................................ 10

UPDATING TO VERSION 12 ................................................................................................. 14 How to update from Version 11 to 12.1 in an environment that uses Client Manager ........................... 14

ACCESS TO ADDITIONAL PRODUCTS AND ENTERPRISE EXTENSIONS ................ 16

© 2008 Mamut. All rights reserved. Right reserved to change the product. Mamut and the Mamut logo are registered

trademarks for Mamut. All other trademarks are registered trademarks of their respective companies

CLIENT MANAGER

1

CLIENT MANAGER Client Manager consists of the programs Client Start and Client Update.

Client Manager is included in certain program versions and is used to manage several system

databases. A system database, or, one "installation", can contain several company databases

(companies, clients, sets of accounting). Users in need of several system databases are usually

accountancy firms with a large number of clients.

Client Start

Client Start gives users the opportunity start different Mamut databases from the same place. The

typical user may be an accountant, alternating between different databases at different locations.

Via Client Start you can launch Import/Export as well as other installed Mamut programs.

In addition, ClientStart lets you launch DataTools for different system databases and create backup

copies and perform administrative tasks in the databases.

Client Update

Client Update gives users the opportunity to update several databases at once. It is also possible to

update company databases within a system database. A typical user may be a system administrator,

who is responsible for managing several databases.

Note! You can update from Mamut Business Software version 12.1 to a newer versions of Mamut

Business Software with Client Update. See below to see how you can update from version 11 in an

environment which uses Client manager.

Launching the Applications

You can launch the programs by clicking on one of two shortcuts. These can be found in the same

location to where you installed Mamut Business Software, in the ClientManager folder.

The installation/update programs do not create shortcuts to these additional programs. Therefore, it

is recommended that you create a shortcut yourself, for example by right clicking on one of the

.exe files and selecting Create shortcut.

Installation

The applications are installed together with your Mamut program.

One Client Manager licence is required for each system database that will use the program. The

licences must be available in each one of the Data folders.

The Client Manager documentation can be downloaded from the Internet: www.mamut.ie

www.mamut.ie

MAMUT CLIENT MANAGER

2

Client Start Client Start gives users the opportunity to start different Mamut databases from the same place,

create new system databases and to have multiple databases open at the same time. The typical

user may be an accountant, alternating between different databases at different locations. Client

Start also offers an option to reindex a database or to run Import/Export and eventually start other

programs from Mamut that you have installed.

Start the program by double-clicking on the program file ClientStart.exe located in the

ClientManager folder. By default Mamut is selected in the Start Program drop-down list at the

bottom of the window. From this drop-down list you can also select to reindex the database, to

start Import/Export as well as to take backups of your database.

You can also create new system databases via Client Start. Read more below under

"Administration of databases".

DataTools/Backup

From Client Start you can also open the program DataTools for the different system databases, and

export backup of other administration tasks in the databases. You can open DataTools from Client

Start by selecting Backup from the drop-down list at the bottom of the window and clicking Start.

Import/Export

Mamut Import/Export is a program that simplifies the communication between Mamut Business

Software and other programs. Mamut Import/Export contains multiple predefined formats for

import and export of among other things, customers, suppliers, orders, invoice information and

much more. You can open Import/Export from the drop-down list at the bottom of the window.

CLIENT MANAGER

3

Multi-user installations

If you have installed Mamut on several computers, you can still use Client Start from all of them,

limited only by your regular Mamut licence. A licence is required for Client manager in every

system databases where the functionality shall be used.

The settings are individual for each installation/computer. This means that a person regularly

working with certain database can add these to 'his/her' Client Start, while another user can have a

different setup for their installation.

Client Update Client update: Client Update enables you to update several databases simultaneously. It is also

possible to choose to update company databases within a system database.

Note! This procedure applies to updating from version 12.1 of Mamut Business Software, to

newer versions of Mamut Business Software. Below you can read about how you can update one

or multiple system databases from version 11.

How to update databases

Updating can take some time with large amounts of data. It is important that you allow the update

to complete. Once the update has been executed a status window will appear that informs you that

the wizard is complete.

1. Double-click the ClientUpdate.exe program file to start Client Update. The program file is located

in the ClientManager folder.

The files used for updating should be the newest available files. The program will check whether

there are databases that are not updated compared to the databases you have registered in Client

Start.

Click Next.

2. Mark the system databases you wish to update.


4

Tip! You can identify the system database under View - Settings - Other Programs in Mamut

Business Software.

3. Click Next.

Note! Updating can take some time for large amounts of data. It is important that you allow the

update to complete. Once the update has been executed a status window will appear that informs

you that the wizard is complete.

4. Click Complete.

Updating is now complete. The status window will be displayed if some of the system

databases did not permit the update.

ADMINISTRATION OF THE DATABASE

5


The Database

Microsoft® SQL Server® Database

Version 12.1 of Mamut Business Software is based on the Microsoft® SQL Server 2005 database.

The Mamut Business Software installer will detect any previous Microsoft SQL Server

installations automatically. Microsoft SQL Server will be installed if no previous installations are

detected.

If you choose the default single-user installation, the program will only be used on one computer,

this computer will act as the database server.

If you choose a multi-user installation, one of the computers within the network will act as the

database server. If no previous installation can be detected on this server, the Microsoft SQL

Server will be installed.

If you choose a client installation - through which you connect to a database server already

available within the network - you will not be required to install Microsoft SQL Server when

installing the Mamut Business Software program files.

Instance

A database server can have several different instances. When installing Mamut Business Software,

MAMUT will be suggested as the default instance name. You can enter a different instance name

if you, already have access to an existing instance for example. In order to get a full overview of

the systems, it is recommended that you create your own instance for the Mamut Business

Software database.

The database server name will often consist of the server name + the instance name. An example

of a database server can be: SERVERNAME\MAMUT.

Note! Instance name is only required if you will be running several SQL Servers on the same

computer.

An instance can contain one or several databases. The Mamut Business Software database consists

of one system database and one or several company databases.

System Database

The program's database consists of company database files and system files. The company

database files contain data relevant to the various company databases, while the system files

contain data which is shared by all company databases. Shared information can, for example,

include information about users and access information.

Tip! The server name, instance and system database are stored in the settings under View -

Settings - Other Settings - Other Programs.

Company Database

A company database represents one set of accounting records. Where book-keeping agencies refer

to "clients", other users handling several companies may view one company database as one

company/organisation. It is possible to manage several company databases in a single program

installation. The maximum number of company databases is determined by your licence.


6

Client Manager

Some program versions include Client Manager, which is a tool for managing several system

databases. One system database - or one "installation" - can contain several company databases

(companies/clients/sets of accounting records). For instance, accounting agencies, which handle a

large number of clients, are the kind of users who require several system databases.

Database Maintenance

Maintenance tasks such as repairing, re-indexing, or compressing the database are performed using

a separate application called DataTools. DataTools is a tool for database administration, and

supports the most common administrative tools for the SQL Server-based databases. The

application is automatically installed with the installation of Mamut Business Software and it can

be launched by double-clicking the file MDataTools.exe. This is located in the DataTools folder,

where the Mamut Business Software program files were installed. Example: C:\Program

Files\Mamut\DataTools.

In addition to maintenance tasks, you are also able to create and restore backup copies using

DataTools. More information can be found within the DataTools help files.

How to move a Company Database between two System Databases

If you have previously had a large number of company databases (clients) in your database, you

may want to separate these out so that the company database is saved to a separate location, which

will increase the speed and security.

Moving a company database between two system databases

1. Start the program and select the database containing the company database that is to be separated.

2. Make a backup copy without system files in Mamut Business Software of the company database

that is to be separated. Place this backup copy in an easily accessible place.

3. Close Mamut Business Software.

4. Start the program via Client Start and select the system database you wish to move the company

database to.

5. Restore the backup copy from point 2.

6. If you like, you can now open the original database the company database was extracted from and

delete that company database there.

All of the company’s data is now in the previously empty database. Add the customer licence

and create the users that are required.


7

How to Create a new system database with Client Manager

The steps involved in creating a new system database

1. Start Client Manager by double clicking on the program file CientStart.exe from the folder

ClientManager, which is in the folder where you have installed the program files for Mamut

Business Software.

2. Click New in the toolbar in the overview window.

Note! You must have a licence for each system database that you use. You can create a new

system database with an evaluation licence in order to register an adequate licence in the usual

manner later.

3. Click Yes to start the wizard for the first time startup.

The program is checking if there is a database in the file path you provided to the document

area. Instead of writing in the path to the document area, it is easier if you click on Browse, and

navigate to the database. In a multi-user installation you must provide a network path to the

document area, for example: \\servername\mamut\data.

Installed Files

Division of Files

The program's database consists of company database files and system files. The company

database files contain data relevant for the various company databases, while the system files

contain data which is shared by all company databases. Shared information can, for example,

include information about user and access information.

The program files are divided so that files created or changed, when installing and updating the

system, are saved to a separate location. In Windows Vista®, files saved to C:\Program Files can

only be created or changed by using Windows® Installer.

Files which are meant to be created or changed by the user are saved to a location to which the

user(s) have access. Managing user access is the responsibility of the system administrator,

externally to the program, which means that it is the system administrator's responsibility to

allocate the relevant user access when installing a multi-user version of the program.

Default File Location when Installing

You can install the program files anywhere you like, the default file path is:

Program files: C:\Program Files\Mamut.

Document files and mamut.ini: C:\Documents and settings\All Users\Public Mamut\Mamut. In

Windows Vista® C:\Users\Public\Public Mamut\Mamut. Each system database gets its own area,

system001, system002 etc. In a multi-user installation the user must provide a network path under

installation/updating.

System and Client Databases: C:\Documents and settings\All Users\Public Mamut\Databases.

Vista® C:\Users\Public\Public Mamut\Databases.

C:\ represents your computer's hard drive.


8

Registry

The Registry settings are identical, regardless of your operating system. All Registry values are

located at the file path HKEY_LOCAL_MACHINE\SOFTWARE\Mamut\Mamut.

The Following values are Installed in the Registry: The values in the table contain examples for illustration.

Key Value in XP and prior versions

Values in Vista

AppName Mamut Business Software Mamut Business Software

AppPath C:\Program Files\Mamut\ C:\Program Files\Mamut\

DataPath C:\Documents and settings\All

Users\Public Mamut\Mamut\Data C:\Users\Public\Public

Mamut\Mamut\Data\

IniFile

C:\Documents and settings\All

Users \Public

Mamut\Mamut\Mamut.ini

C:\Users\Public\Public

Mamut\Mamut\Mamut.ini

InstallLanguage EN (for IE) EN (for IE)

InstallRoot C:\XP11.1.5165 C:\Vista12.0.6465

Language 1 (for IE) 1 (for IE)

MCode

Partner Mamut Mamut

Serverpath .\Mamut .\Mamut

Version 11.1.5165 12.0.6465

VersionType

Installation

New installation: When installing for the first time, the program will suggest C:\Program Files as

the location for the program files. The suggested location of the Library folder and the mamut.ini

file is described above in the section "Default File Location when Installing".

If you choose to install the program files to another location, the structure of the data area will

mirror the structure of the program files.

Updating: When updating, the new program files are installed to the file path you specified during

installation. The Library folder is installed to C:\Documents and settings\All Users\Public Mamut\

or Vista: C:\Users\Public\Public Mamut\.

If you have updated from version 11, the Data folder will be moved to the new location the next

time you start the program.

When updating from version 11 the document area moves to this file path. If you have selected a

different file path than C:\Program Files, the document area (data folder) will not be moved.


9

First Start-Up

After new installation: When launching the program after having performed a new installation,

no files or values in the Registry are changed. In the mean time, you can change the location of the

document area.

When updating from version 11.x: If you have completed an update, the file path to the

Document area (Data folder) is amended according to the following logic:

If the data folder is located at C:\Program Files

Not Vista: It is moved to C:\Documents and settings\All Users\Public Mamut\Mamut

Vista: It is moved to C:\Users\Public\Public Mamut\Mamut.

If the data folder is located somewhere else:

The Data remains where it is while the Library folder and the mamut.ini file are moved. You

will thereby end up with 3 different file paths.


10

LAYOUT OF MAMUT BUSINESS SOFTWARE

Setup of Mamut Business Software with Mamut Bureau

Client Manager is a part of the program Mamut Bureau.

With Mamut Enterprise Bureau ASP, you will find many positive reasons to offer your clients

access to your applications, numbers and reports 24 hours a day. At the same time that you as the

accountant, have the possibility to log in to the Mamut system, from for example your home

office. The solution provides your accounting bureau the best premise to be able to manage and

update the clients applications and data areas.

Below you can read more about Setup in a ASP environment.

Set Up in an ASP Environmentin an ASP Environment

In a typical ASP-environment, the customer’s database is managed by and located at the

Application Service Provider. Customers log on remotely using "thin" clients. Many accountants

opt for a solution where each client is separated into a different database so that it is possible for

them to work within the database at the same time as the client.

It is recommended that you install 2 separate ERROR: Variable (Vendor2) is undefined -

installations on the ASP-server.

The reason for installing 2 versions of Mamut is that the program path to Mamut’s database is

changed in Mamut.ini when using Mamut’s ASP program. Since Mamut.ini is located together

with the program files, any user, who does not start Mamut using the ASP-program, will get he

same database. If you have two installations of the program files, you can use one installation

together with the ASP program and let external clients use the other one. External users will then

connect to the database via a network station, which is automatically linked up to a login script.

This way they will not be able to see which other clients and databases are located in the system.

On the Mamut installation CD, you will find both a regular set of installation files and a set of

installation files called Setup2. These are installed in separate folders. Please refer to the section

Setup for Application Service Providers below for more details.

Installation 1: (For customers, who log in via the Terminal Server client)

D:\Setup\Install\setup.exe

Installation 2: (For administrators and accountants – it is this installation the administrative tool is

linked up to). D:\Setup\Install\setup2\setup.exe

Preparations before installing in an ASP-environment

1. The server for ASP must be properly set up and accessible for the users.


11

2. Mamut is properly installed and if relevant, updated according to the Installation/Setup of Mamut

with Windows 2000 Terminal Server instructions below.

3. Please read the section Setup for Application Service Providers below.

You are now ready to install in a ASP-environment.

Installation/Setup of Mamut with Windows 2000 Terminal Server

When you are installing Mamut for running on the Windows 2000 Terminal Server, there are

several aspects you need to consider.

Please consider the following when installing Mamut on the Windows 2000 Terminal Server:

Install the Terminal Server service on the Windows 2000 server in Application Server mode.

Install Mamut as a multi-user installation with the database locally. Do not set up the database

on a Network station, even if this is actually located locally on the server. However, this does

not apply to ASP- suppliers.

Installation

1. Log into the Terminal Server as Administrator. It is recommended that you sit locally at the

server during the installation.

2. If you have Mamut installed prior to this, check where the program files and database files for the

program are saved on your system. The default location for the program files is located under C:

Program Files\Mamut (for example) and the document area and Mamut.ini are located under

C:\Documents and Settings\All Users\Public Mamut\Mamut. Check where the program files

are saved by right-clicking on the Mamut shortcut and selecting Properties. The path should be

displayed under the Shortcut tab. Write down the path to the database files.

Read more regarding the structure in the program above.

3. Insert the CD with the new edition of Mamut.

4. Go to [Start] and select Settings - Control Panel.

5. Double-click Add or Remove Programs.

6. Click the Add New Programs button.

7. Click the CD or Floppy button and Browse (in NT 4.0 just click on Browse once).

8. Browse to the folder X:\Setup\Install\ (X is the CD drive on your system).

9. Double-click on the Setup.exe file.

10. Click OK.

11. Click Next.

12. The installation program for Mamut will start.

13. Select Server installation and follow the installation wizard.

14. When Mamut has finished installing click on Finish. If the program asks you to restart, select to

do this later. The installation of Mamut is finished and you are back in the installation setup for the

Terminal Server. Click Next and then Finish.

15. The program is now installed at the server. If you received a message during installation asking

you to restart, you need to do so before you start up Mamut. If you, in addition, has machines that

are logged on to the program via a regular client installation, the program files for these

installations need to be installed/updated as described in the regular installation documentation.


12

16. Start up Mamut for the first time and select to create a new multi-user installation with this

computer as the server. Make sure to install the database files in a different place from where the

program files are installed.

You have now successfully installed the program.

Note! It is important to give all users access to the folder where Mamuts program files are located.

Set up for Application Service Providers

Application Service Providers, or others using similar installation environments, need to take into

consideration certain aspects regarding printer setup and databases.

Database

When setting up a Terminal Server, you may optimise the speed by installing the Mamut database

on the same server. This offers maximum speed when working toward the database. However, for

an Application Service Provider this is usually not as practical.

This is usually solved using a logon script, connecting the user to a network station (i.e. H: ). This

network station may be individual for each user/customer/client, but the same for all users at a

client’s. Example: Client AB has user A, B and C, who all connect to the same place via station H.

Client BC has users D and E, who connect to another area with their station H.

When starting up Mamut for the first time, you can choose to create a multi-user installation, with

the server located at a different computer. Point to a folder at the connected network station (i.e.

H:\Mamut) The H: station will get a new empty database in the H.\Mamut folder. This database

may be copied to new areas for other customers, so they can start using Mamut and create their

own databases.

User access

In order for users to run Mamut as trouble-free as possible, they need to be granted access to the

following locations to run Mamut:

Access to the database: This is controlled via user rights within the program, and eventually

directly through the administration tools for SQL Server.

Data Folder: All users for this database need to have Full access to this folder.

Program files: All users need access to this folder to create and delete temp files.

Default temporary folder for each user: All users need Full access here.

Read more about the data structure above.

Printers

Mamut has printer settings at 3 levels. Most modules also offer to select printer.

First level: If no printer settings are defined in Mamut, the Windows default printer will be

used. (Terminal/Citrix-session).

Second level: Printer settings can be defined in Mamut, and saved in Mamut.ini. (Mamut.ini

is also used to find the database, and is located in the same folder as the Mamut database.)

Application Service Providers will rarely find this practical, since these settings are shared by

all users running these program files.

Third level: Printer settings may be defined for each report. Name, driver, drawer, driver

settings etc. is saved for the report. If you make settings for the Contact list report, these can

be copied to other reports that are being used. Since the settings are saved in the database,

they are individual for each customer. This may still not be an optimal setup for installation

using client-printers from the customers, since these may have different names for different

users.


13

Finally, you can also enable the printer settings window to open when printing in most modules.

When printing you will then see a box, where you select which printer should be used for the

current printing job.

The most practical solution for Application Service Providers may be not to use printer settings in

Mamut. This way, the default printer for the current user session is used as the default printer for

Mamut. This is because more users will link local printers and the names for these printers will

always differ depending on which user is logged on and from which machine.

Additionally, you can go into the setup for users in Mamut and determine that they always need to

select a printer when printing. To do this, go to View – Settings – Security – User

administration and go into a user and the connected user profile. Under Settings per Module –

Reports and the Reports tab you choose to Select printer. These users will then get up a box in

which they select the printer for printing to in those Mamut modules, where you can choose a

printer. Where you cannot choose a printer (transfer of journal entries to the Nominal ledger, for

example), the user session default printer is used.

External users (Clients/Customers) setup

This section explains how to set up access to the server for users who connect via the Terminal

server.

The installation for external users needs to be set up so that it connects to a database via a network

station. There are two ways in which to connect this network station:

Home area

Logon script

Home area

When a user has been created in the Active Directory, the user will have a tab called Profile. This

tab contains a setting for the Home folder. Under this tab it is possible to specify a particular

station letter that will be mapped to a particular address when logging on. The same letter must

always be used for all users, but it should be mapped to different folders depending on the location

of the current user’s database.

Log on script

The tab mentioned above also has a setting for User profile. One of the lines is called Logon

script. Here, the user can enter the name of a file which contains a script enabling station letters to

be mapped to areas. These files will be located in a folder that is separated from the server, called

Netlogon. The files may have the extension .bat or .cmd and contain scripts that are run when the

user logs on. The file names must be entered without the full path, just the file name.

Here are some examples of text that this type of script may contain:

@echo off

@net use H: \\server\customer1\mamut

@net use I: \\server\customer1\common

This script will give the user two stations when logging on. One, which is mapped to the area

where Mamut’s database may be located, and one which, for example, is for common files for the

user’s company.

Strictly speaking, it is only necessary to map a station with access to Mamut’s database.


14

UPDATING TO VERSION 12

How to update from Version 11 to 12.1 in an environment that uses Client Manager

With Client update you can update one or multiple system databases at the same time from version

12.1. It is also possible to choose to update by company database inside a system database.

Below you are able to read how you can update from one or multiple system databases from

version 11.

How to update from Version 11 to 12.1 in an environment which uses Client Manager

1. Install version 12.1 to the same place as version 11.

2. Start the program Mamut Business Software (Mamut.exe). This starts the updating. The system

database that is stated in mamut.ini is updated to version 12.1.

3. Relocate mamut.ini file which has been created under C:\Documents and settings\All users\Public

Mamut\Mamut.

4. Open mamut.ini which is located under C:\Program Files\Mamut - or, if the program files are

installed to another file path, in the folder where mamut.exe program files have been installed.

Change the file path in mamut.ini at <Datalocation> so that it points to the file path for another of

the system databases you shall update.

UPDATING TO VERSION 12

15

5. Start the program Mamut Business Software (mamut.exe) This starts the updating of the system

database that was stated above.

6. Eventually, repeat points 3-5 for all system databases that shall be updated.

The database in then updated. When later updating from version 12.1, it will be possible to

update multiple system databases in one simple operation.


16

ACCESS TO ADDITIONAL PRODUCTS AND ENTERPRISE EXTENSIONS

So that you can use additional products, you need to register the licence number you receive after

you ordered the product, and you also have to set up which users or which company database

should have access to the extra features. Once you have done this, the additional product is ready

for use.

When you buy additional products, you will be sent a licence number for each of the additional

products you have purchased.

If you receive several licence numbers, you will first need to register the licence for the program

itself. After that, you can continue with registering the licence number for the service agreement or

other additional products.

Note! When you register a licence number it is important to enter the licence number correctly in

the same way as it appears in the letter/e-mail you received. Be especially careful with the

difference between the letter "O" and number "0". Our licence numbers do not contain the letter

"O", only the number "0".

How to register an additional licence

1. Go to Help - About and click on Register Licence Number.

2. Enter your licence number and click OK.

The additional licence is now registered.

Some of the Mamut Enterprise add-on products have to be registered for your company database

or for certain users, who will be given access to the new functionality.

After you have registered the licence for your additional product and restarted your Mamut

Enterprise system, you will have access to the licence administration area. To get there, go to Help

- About - Manage licence Information.

Find out whether the additional product is for a number of users, company database or All users

and company databases.

How to manage access to additional products

1. Go to Help - About.

2. Select Manage Licence Information.

ACCESS TO ADDITIONAL PRODUCTS AND ENTERPRISE EXTENSIONS

17

3. You will now see a list of the additional products you have access to. Select the additional product

you want to manage from the left and click on Add.

4. Select a company database or user and click OK.

5. Close the program and restart it.

All functionality is now available.

Note: At the bottom of the page you can see how many licences you have for the additional

product. You can add as many users/company databases as you have licences for.

Mamut Guide for Add on for Client Manager

Documents

Transcript of Mamut Guide for Add on for Client Manager