v3.6.0 Install Guide

LGCSB GENERIC

INSTALLATION GUIDE

Software Version 3.6.0

This document contains all of the information you need to install version 3.6.0 of the Generic Intranet

LGCSB Generic Intranet – Version 3.6.0 - Installation

Table of

Table of ContentsTable of Contents ................................................................................................................................. 2Introduction .......................................................................................................................................... 4

Intended Audience ........................................................................................................................... 4Document Conventions .................................................................................................................... 4Related Information ......................................................................................................................... 4

Prerequisites ......................................................................................................................................... 5Installation Types ................................................................................................................................. 6

Update Install ................................................................................................................................... 6Full Install ........................................................................................................................................ 6Advanced Installations ..................................................................................................................... 6

Update Mode........................................................................................................................................ 7Preparation ....................................................................................................................................... 7Installation........................................................................................................................................ 8

INTRANETGROUP in SQL SERVER ....................................................................................... 9To check the name of the IntranetGroup visible in the users area of the laintranet1 and master databases .................................................................................................................................... 10

Starting the Update ........................................................................................................................ 11Installation Failure ......................................................................................................................... 20Post Installation.............................................................................................................................. 20

Full Install Mode ................................................................................................................................ 21

Preparation ..................................................................................................................................... 21Create IntranetGroup Group ...................................................................................................... 21Create Blank Database ............................................................................................................... 21Permissions for IntranetGroup Group........................................................................................ 21

Installation...................................................................................................................................... 22Starting the Installation .................................................................................................................. 23Installation Failure ......................................................................................................................... 31Post Installation.............................................................................................................................. 31

Configure your Intranet.............................................................................................................. 31Import Agresso Data .................................................................................................................. 31Configuring the Meetings Application ...................................................................................... 31Configure SQL Mail .................................................................................................................. 31Set up Staff Members................................................................................................................. 31

Advanced Installations ....................................................................................................................... 32

Upgrading and moving............................................................................................................... 32Moving Only ..............................................................................................................................

of

LGCSB Generic Intranet – Version 3.6.0 - Installation

Table of

Create an Application Pool for the Generic Intranet.................................................................. 39Create a virtual directory for the Generic Intranet within the _layouts folder of Sharepoint .... 41Configure your new virtual directory......................................................................................... 43Configure ASP.NET in the _layouts folder. .............................................................................. 45Restart IIS. ................................................................................................................................. 47

Setting up Web Parts to access the Generic Intranet with Sharepoint 2003 .................................. 48Using the Generic Intranet without Sharepoint.............................................................................. 52Definitions of Web Parts/Access Points ........................................................................................ 53

Name .......................................................................................................................................... 53Leave Web Part .......................................................................................................................... 53Expenses Web Part..................................................................................................................... 53Headlines Web Part.................................................................................................................... 54Meetings Web Part..................................................................................................................... 54Simple Phonebook Web Part ..................................................................................................... 54Advanced Phonebook Web Part ................................................................................................ 55Phonebook Update Web Part ..................................................................................................... 55Site Phonebook Update Web Part .............................................................................................. 56Arrears Web Part........................................................................................................................ 56Administration Web Part ........................................................................................................... 56

Web Parts for use with Sharepoint 2001 Only............................................................................... 57Phonebook Simple Search (SPS 2001) ...................................................................................... 57Phonebook Advanced Search (SPS2001) .................................................................................. 57Phonebook Results (SPS2001) .................................................................................................. 58

Setting up the Agresso Import ........................................................................................................... 59Introduction .................................................................................................................................... 59Preparation ..................................................................................................................................... 59Creating the import package .......................................................................................................... 60

Setting up the meetings application ................................................................................................... 70Step 1: Publishing the Outlook form on Microsoft Exchange. ...................................................... 71

Using Exchange 2003 ................................................................................................................ 71Using Exchange 2000 ................................................................................................................ 72

Step 2 Connect the user’s computer to the Generic Intranet database. .......................................... 74Step 3: Configuring Microsoft Outlook .........................................................................................

of

LGCSB Generic Intranet – Version 3.6.0 Update – Installation

Introductio

IntroductionThis document is intended to assist with the installation of the Generic Intranet version 3.6.0.It is distributed as part of a CD or update package distributed in compressed format.

Note: This installation guide covers full installation, with detailed descriptions of the post-installation procedures. If you only want to do an update installation, you need only read as far as page 21.

Intended Audience

This document is written for IT professionals.

It is expected that readers of this document know enough about Windows administrations to do the following tasks

Create and configure users Create Windows Nt/2000 or Active Directory groups Create SQL Server databases Create SQL Server users

Docum e nt Conventions

Text in this form gives instructions that the administrator is expected to perform

There can be more than one instruction

Occasionally explanatory notes will be added to an instruction

Notes: Text in this form gives additional warnings, or notes that may be important in unusualcircumstances.

Related Information

You can access detailed information on the LGCSB and its activities at the following URL:htt p : //www.lgcsb.ie/ .

of

LGCSB Generic Intranet – January ’05 Update - Installation

Prerequisites

PrerequisitesThe following software needs to be installed on your server in order to use this update of theGeneric Intranet

Windows 2000 Server, with the latest services packs (Service Pack 4), or Windows 2003Server

SQL Server 2000, with the latest service packso This can be run on a different server, if desired.o The server running SQL Server 2000 must have Microsoft Outlook installed

A Microsoft Exchange Server on your networko Please contact the LGCSB at ge n e ricintr a n e t@l g csb.ie if you need to run this

software without MS Exchange Sharepoint 2001 or Sharepoint 2003, with the latest service packs (Service Pack 3) .NET Framework, Version 1.1, with the latest service packs

o This version of the Generic Intranet has been recompiled and tested with this newer version of the .NET framework.

Internet Explorer Version 6.0o Please note that we have upgraded the basic requirement on browsers using the

Generic Intranet from IE 5.0 to IE 6.0.o We have been unable to test this update with versions of Internet Explorer less than

6.0. Generic Intranet

o If you want to upgrade an existing version of the Generic Intranet, You must have installed up to and including the January ’05 update of the Generic Intranet before attempting this update.

o If you want to create a fresh installation (see Installation Types below) of theGeneric Intranet, you will need an empty database for the Generic Intranet to installinto(See Preparation on Page 21)o It is also possible to use the installer to help with moving an existing version of the

Generic Intranet between servers, if the existing version has been upgraded to either the January ’05 version, or version 3.6.0 (i.e. this version). See Advanced Installation

below for more details.

of


Installation Types

Installation TypesThis package of the Generic Intranet can install in several different modes.

Update Install

This updates your Generic Intranet installation from the version shipped in January ‘05 to this mostrecent version. The following actions will be taken.

The Escalation Service will be updated to the latest version In the Generic Intranet Database (generally laintranet)

o some tables will be modifiedo some tables will be addedo some relationships will be addedo some views will be modifiedo some triggers will be addedo some stored procedures will be addedo some stored procedures will be modified

Most Generic Intranet web files will be replaced (i.e. the contents of C:\LocalIntranet)o The file web.config will not be replaced.

Full Install

This creates the Generic Intranet as if you do not have a previous installation on the target machine.The following actions will be taken.

The Escalation Service will be installed and registered as a service In the Generic Intranet Database, all tables will be created and populated with default data All Generic Intranet web files will be installed. The virtual directory for the local Generic Intranet will be configured.

Advanc e d Installations

You can choose during installation to omit or include the following installation steps Database installation Escalation service registration Web folder configuration

These options are useful for situations where you need to move an existing version of the GenericIntranet from one server to another.

If you want to update an existing version of Generic Intranet, turn to page 7.

If you want to create a new version of Generic Intranet, turn to page 21.

If you want more information about Advanced Installation options, turn to page 32.

of


Update

Update Mode

Pr e p a r ation

It is highly recommended that you do a full backup of your server and data before installing thisupdate. In particular, you must back up the following areas, which will be changed during installation.

The database "laintranet1" in SQL ServerThis installation will add new tables to this database, as well as modifying existing tables, views and stored procedures.Should installation fail, you may want to restore the database to the pre-installation condition

The contents of the C:\LocalIntranet folder on the serverMost files in this area will be overwritten during installation of this update.If you have locally modified any functionality, then you will need to implement these modifications once this update is complete.Take a copy of your changed files and make those changes again on the new versionof the software, if desired.

Permissions: The user installing this software must have full privileges to write to C:\LocalIntranet

of


Update

Installation

To install the Generic Intranet Update, you will require the following information The name of the server you will be installing onto.

Generally, this is “lanet-coco”, where “coco” is the name of your local authority. The location where the previous version of the Generic Intranet was installed.

By default, this is C:\LocalIntranet. The SQL Server where the data for the Generic Intranet is stored.

By default this is the same as the web server. The virtual directory mapped to C:\LocalIntranet

Normally this is /laintranet)

of


Update

INTRANETGROUP in SQL SERVER

In SQL the user “IntranetGroup” must exist with the same name in the following two places1) The Users section of the database “Laintranet1”2) The Users section of the “master” database.

Check the login name in these two places

NOTE: If the name under the “users” section of the two databases is different, the product will notinstall. The name visible under this section is the same text you will enter in the installation wizard.

of


Update

To check the name of the IntranetGroup visible in the users area of thelaintranet1 and master databases

Open the Security group

Open the “Logins” area of the Security Group

Right click on properties of IntranetGroup (or Domain\IntranetGroup)

Click on the “Database Access” Tab

Examine the access to the laintranet1 database

If the permit checkbox is not checked

Check the “permit” checkbox

If the user column does not show the domain name before IntranetGroup:

Click on User column and insert Domain Name before IntranetGroup

Examine the access to the master database

If the permit checkbox is not checked

Check the “permit” checkbox

If the user column does not show the domain name before IntranetGroup

Click on User column and insert Domain Name before IntranetGroup

of


Update

St a r ti n g t h e U p date From the CD or update package folder, run setup.exe. A setup process will begin.

First Screen

Click “Next >”

of


Update

Second Screen

Leave “Update the database” checked

Click Next >

Full Install: If you want to install a new database, you are reading the wrong instructions. Pleaseturn to Page 21 for details on preparing for and running a full installation)

Advanced Installation: You can also choose not to install the database. This would be part of an advanced installation, used only in special circumstances such as migrating to a new server. Please turn to Page 32 for more details on advanced installations.

of


Update

Third Screen

Leave “No, don’t register the escalation service checked”

Click “Next”

of


Update

Fourth Screen

Leave “Yes, configure the virtual directory” unchecked.

Click “Next”

of


Update

Fifth Screen

Unless you have a non-standard implementation, click “Next >”

of


Update

Sixth Screen

Unless you have a non-standard implementation, click “Next >”

Non-Standard Installations: If your database is installed on a different server, please change thedomain name and database name settings as appropriate.

SQL Server Agent Name: For an update installation, you can safely ignore the “SQL Server AgentService Name” setting.

(this setting is relevant only if you are registering the escalation service)

Permissions: You will need to ensure that the logged in user has sufficient permissions to be ableto update the database you are deploying to.

of


Update

Seventh Screen

Enter the domain name in the area provided, for example LGCSB_DUBLIN

Enter the Domain Name before IntranetGroup, for example LGCSB_DUBLIN\IntranetGroup

INTRANET GROUP: Depending on your configuration, you may need to enter the group namewithout the domain name before it. This will be as with previous updates of the Generic Intranet.

If your installation fails with an error message explaining that it could not find a group, you can re- try the installation: Simply enter IntranetGroup in this area

Click “Next >”

There will be a short pause before the final screen appears.

of


Update

Final Screen

Check “Everyone”

Click “Next >”

On receiving the message “Installed successfully” click “Finish”

If you are prompted to do so, click “Yes” to restart the server

of


Update

Installation Failure

If you receive an error message during the update click ‘OK’ on the message.

The install will automatically roll back to the start of step 2.While it is rolling back it may want to delete tables that were added during installation.

Allow it to do this - Click “Yes” to allow removal of these tables

Before attempting to rerun the install check that you have the correct required settings, in particularcheck the setting for the IntranetGroup as detailed on page 4.

Ensure that all users are logged out of the SQL database ‘Laintranet1’ and then rerun the install.

Post Installation

You should re-boot the machine after installing this update

Once you have completed the installation, the following information should be reviewed to ensurethat the expenses module will work correctly.

The approval procedure for expenses The Agresso company in use File paths for the Agresso export folders.

If you have recently completed an Agresso upgrade, you may need to re-create the Agresso Import folder. See page 59 for details on configuring your SQL Server for the Agresso Import.

of


Full Install

Full Install Mode

Pr e p a r ation

Create IntranetGroup Group

The Generic Intranet controls access to the database using a domain user group called“IntranetGroup”. Only members of this group will be able to use the Generic Intranet.

Create a user group called “IntranetGroup” on your domain.

Ensure any staff members who will use the Generic Intranet are in this group.

Create Blank Database

The Generic Intranet requires a database to install into. This database can be created on anyinstance of SQL Server.

Choose the instance of SQL Server that will run the Generic Intranet database

Create a new, blank database called “laintranet1”

Permissions for IntranetGroup Group

Ensure that the IntranetGroup Group you have created has access to the database you have created.

Ensure that the IntranetGroup Group you have created has access to the master database

Ensure that the name of the IntranetGroup under both databases is the same (see page 10 forassistance with this)

Installation Paths: By default, the product will copy web files into the folder C:\LocalIntranet.Please ensure this folder is not in use or the installation may fail. The administrator must have full privileges to write to this folder

Virtual Directory Paths: By default the product will install a new virtual directory on your server. This virtual directory is \laintranet. Please ensure that this virtual directory name is not in usealready, or the installation may fail.

of


Full Install

Installation

To install the Generic Intranet Update, you will require the following information The name of the domain you are installing in. The location where you plan to install the Generic Intranet.

By default, this is C:\LocalIntranet. The SQL Server where the data for the Generic Intranet will is stored.

By default this data is on the web server machine, so “localhost” will be enough. The name of the database where the Generic Intranet data will be stored

You will have created this blank database on this server during the “Preparation”step above.Normally, it should be called “laintranet1”

The virtual directory which will be mapped to C:\LocalIntranetNormally this is /laintranet

of


Full Install

Sta r ting the Installation

From the CD or downloaded package, run setup.exe. A setup process will begin.

First Screen

Click “NEXT >”

of


Full Install

Second Screen

Click on “Install a new database”

Click Next >

Upgrade: If you want to do an upgrade installation, you are reading the wrong instructions. Pleaseturn to Page 7 for details on preparing for and running an upgrade)

Advanced Installations: In some circumstances, you may wish to do an installation withoutinstalling a database. This is most likely if you are moving a copy of the Generic Intranet from one server to another. See page 32 for more information about advanced installations.

of


Full Install

Third Screen

Click “Yes, register the escalation service.

Click “Next”

of


Full Install

Fourth Screen

Check “Yes, configure the virtual directory”

Click “Next”

of


Full Install

Fifth Screen

Unless you wish to install to a non-standard location, click “Next >”

of


Full Install

Sixth Screen

SQL Server N a m e:

Enter the name of the SQL Server where you are running the Local Intranet Database

D a t a b a s e Na m e:

Enter the name of the blank database you created during the preparation step. (The recommendedname is laintranet1)

SQL Server Agent Service N a m e:

If your database is running on the default SQL Server instance on the local machine, you shouldleave the “SQL Server Agent” field as it is.

If your database is running on a named instance of SQL Server on the local machine you shouldreplace “SQLServerAgent” with “SQLAgent$InstanceName”

If you are running the database on a different server, you should clear this field completely.

Click Next >

of


Full Install

Seventh Screen

Enter the domain name of your local domain in the area provided, for example LGCSB_DUBLIN

Enter the Domain Name before IntranetGroup, for example LGCSB_DUBLIN\IntranetGroup

Click “Next >”

There will be a short pause before the final screen appears.

of


Full Install

Final Screen

Click on the “Everyone” option

Click “Next >”

The installation will run, and a message should say that the installation was successful. If the installation fails, see the instructions on the following page.

If the installation succeeds click “Finish”

Restart the server

of


Full Install

Installation Failure

If you receive an error message during the update click ‘OK’ on the message.

The install will automatically roll back to the start of step 2.While it is rolling back it may want to delete tables that were added during installation. Allow it to do this –

Click “Yes” to allow removal of these tables

Before attempting to rerun the install

Check that you have the correct required settings, in particular check the setting for theIntranetGroup as detailed above.

Ensure that all users are logged out of the SQL database ‘Laintranet1’ and then rerun the install.

Post Installation

Configure your Intranet

Once you have successfully installed the product, you will need to provide links to this productfrom your intranet. Please see the section “Intranet Configuration” on page 31 below for details on how you can use this product within your Intranet.

Import Agresso Data

In order to use the Expenses module, you will need to import Agresso data to the Generic IntranetDatabase. Please see the section entitled “Setting up the Agresso Import” on page 59 for more details

Configuring the Meetings Application

If you wish to use the Outlook Form that integrates with the Meetings Web Part, you will need toinstall the Outlook Form on your version of exchange. Please see the section “Configuring theMeetings Application” on Page 70 for more details.

Configure SQL Mail

In order to send e-mail notifications, the SQL Server Mail services need to be set up. See Page 80for more details.

Set up Staff Members

You will then need to configure your staff, departments, holidays and other business details withinthe product. Please see the “Administration Guide” for guidance on administrating this product.

of


Advanced

Advanced InstallationsIn cases where you need to move the Generic Intranet from one server to another, you can usevarieties of the installations described above to accommodate your situation.

Be Prepared - We recommend that you read the instructions above for BOTH the full install andthe upgrade install before attempting installation under these circumstances.

The following three scenarios are the most common.

Upgrading and moving

Scenario: I have an existing database from the January ’05 which is currently running the GenericIntranet. However, this version of the software will be hosted from a new server.Solution

Ensure that the database from January ’05 is available to the new server.

During installation:

On page 2, select “Upgrade The Database”

On page 3, select “Register the Escalation Service”

On page 4, check “Configure Virtual Directory”

You may have some files that were attached to expenses claims and meetings that also need to becopied. See Page 33 below for assistance on how to do this.

Moving Only

Scenario: I have an existing database which is currently running this version (v3.6.0) of thesoftware. However, I need to host the software on a new server.Solution

Ensure that the database from v3.6.0 is available to the new server

During installation:

On page 2, select “Don’t install a database”

On page 3, select “Register the Escalation Service”

On page 4, check “Configure Virtual Directory”

You may have some files that were attached to expenses claims and meetings that also need to becopied. See Page 33 below for assistance on how to do this.

Distant Upgrades

Scenario: I have an existing database which is currently running an older version than January ’05of the Generic Intranet. However, I need to install the latest version.Solution 1 (preferred)

If necessary, upgrade your installed version to the August ’04 release, available for download from

of


Advanced

h t tp ://e xtran e t .lg cs b.ie/ sp i nte r ne t / Do c um ents/Busi n e ss %20Applications / Local%20Authority%20Ge ne r ic%20Intranet/A ugus t %200 4 % 2 0Release/

Upgrade your installed version to the January ’05 update, available for download fromh t tp ://e xtran e t .lg cs b.ie/ sp i nte r ne t / Do c um ents/Busi n e ss %20Applications / Local%20Authority%20Ge ne r ic%20Intranet/G eneric%20 U pdate%20Ja n %2020 0 5/

Follow the instructions for the “Upgrade Install” above.

Solution 2 (difficult)

Follow the instructions for the “Full Install” above

Copy the data from the old database to a new database.

Use DTS (Data Transformation Services) to copy data from your old database to your new database.

If you have difficulty transferring the data with DTS, there are some SQL scripts in “contrib.” folder of therelease package that you may find of assistance – these scripts are untested and unsupported

Alternatively, you can use a copy of SQL Data compare from Red Gate software (ht tp :/ / www . red - gate . com ) toassist with data migration

My scenario isn’t covered by the above descriptions.There are a total of 12 different ways of installing the Generic Intranet, depending on what has beeninstalled previously on your server.If you need advice on how best to install the Generic Intranet, please contact LGCSB GenericIntranet support at g e n e r i c i ntr a n e t @lg cs b . ie

Cop y ing files from one server to another

The following features of the Generic Intranet create files that are stored on the file system of theweb server.

Attachment of documents to meeting bookings Attachment of documents to expenses claims Archival of expenses claims Logging of Agresso Exports Images of staff members

If you have been using these features of the Generic Intranet, you will need to copy the files for each of these features from your old server to your new server once installation is complete.

Process

In each case, the process is the same

Determine where on your old server the files are stored

Determine where on your new server the files should be stored

Copy the files from one server to the other.

Settings

In each case, there are settings that the Generic Intranet can use to determine which folder thesefiles are stored in.

of


Advanced

You may need to review these settings on the old and new server to determine where you can findthe files. See the Administration Guide for help in using and changing settings for the Generic Intranet. If any of these settings is not listed on your server, the files will be stored in the default location.

File Groups

The following table lists groups of files that the Generic Intranet creates and stores on your behalf

Check each file group, and where necessary, copy files..

File Group,Description

SettingSection

SettingName

Default Location

Staff ImagesPictures of staff membersExpenses Attachments Documents that are attached to expenses claimsExpenses Archives Expenses that have been savedto file and deleted from the databaseExpenses Export Information Export files and export logs from Agresso ExportsMeetings Attachments Documents that are attached to meeting bookings

Global StaffImageFolder

Expenses Approval Document Folder

Expenses ArchiveFolder

Expenses Agresso Export Folder

Meetings Meetings Upload Folder

C:\LocalIntranet\ExpensesAdministration\StaffImages\

C:\LocalIntranet\ClaimingExpenses\docs\

C:\LocalIntranet\ExpensesAdministration\archive

C:\LocalIntranet\ExpensesAdministration\agresso\

C:\GenericIntranet\DotNetWebParts\docs\

of


Intranet

Intranet Configuration

Introduction

You will need to configure your intranet in order to access the functionality provided by thisproduct. While it has been installed, there is no direct means for your users to access the functionality.

There are a number of different facets to the user interface of this product. Each area provides different functionality, and to different types of users.

In this document, we call these areas “Access Points”. Under Sharepoint, you will set up these areas as web parts on the Sharepoint Dashboards you consider most appropriate.

These access points are detailed on Page 53. The primary web parts are as follows

Leave Web Part (Page 53)Used to access the functionality of the leave system

Expenses Web Part (Page 53)Used to access the function of the Travel & Subsistence system

Headlines Web Part (Page 54)Used to access the functionality of the Generic Intranet tickertapes

Meetings Web Part (Page 54)Used to view room bookings

Simple Phonebook Web Part (Page 54) Used to search the list of staff

Advanced Phonebook Web Part (Page 55) Used to search the list of staff

Phonebook Update Web Part (Page 55)Used by front office staff to update staff phone numbers

Administration Web Part (Page 56)Used to configure the Generic Intranet

First, however, we provide instructions on how to set up these access points in Sharepoint 2001, andhow to configure Sharepoint 2003 for the Generic Intranet.

of


Intranet

Setting up Web Parts to access the p r oduct with Sharepoint 2001

To add any one of these locations as a web part to a Dashboard within Sharepoint 2001, use thefollowing steps:

Ensure you have administrative privileges for the Dashboard within Sharepoint.

Click on the “Content” link on the top right corner of the page.

No Content Link? If the content link does not appear, you do not have administrative privileges forthis page.

A screen for the content of the dashboard appears.

Click on “Create New Web Part”

of


Intranet

A screen to configure a new web part appears

of


Intranet

Various configuration properties are available.

Set the configuration settings as appropriate to your intranet environment.

The most important two properties are as follows:

In the “Advanced Settings” area, click on “Get Content from the following link”

Enter the URL in the box provided

In most cases, you will also want the web part to run inside a frame.

Check the “Isolate this Web Part’s content from the other web parts” box.

of


Intranet

Using the Generic Intranet under Sharepoint 2003There are some extra configuration steps required to get the Generic Intranet working withSharepoint 2003, as follows

Create and configure an Application Pool for the Generic Intranet Create and configure a virtual directory within the _layouts folder, for use with Sharepoint

2003 Restart IIS

Create an Application Pool for the Generic Intranet

Open the IIS Manager.

Open the local server

Click with the right mouse button on the “Application Pools” folder icon

Choose “New/Application Pool…”

The “Add New Application Pool” dialog will appear.

of


Intranet

Give your Application Pool the name “Generic Intranet”

Base your new pool on the MS SharePoint Portal App Pool

Press OK

of


Intranet

Create a virtual directory for the Generic Intranet within the _layouts folder ofSharepoint

Stay within IIS Manager

Open the Default Web Site

Open the _layouts folder within the Default Web Site

Click with the right mouse button on the cog icon for the _layouts folder

Choose “New/Virtual Directory…”

The Virtual Directory wizard appears.

Click Next

Give the new virtual directory the alias “laintranet”

Click Next

Give the new virtual directory the path C:\LocalIntranet.

Non-Standard Installations: If you have installed the Generic Intranet in a non-default location,enter that instead)

Click Next

Set Permissions: Read, Write and Script.

Click Next

of


Intranet

Click Finish

of


Intranet

Configure your new virtual directory

Click the right mouse button on the new virtual directory within the _layouts folder, and choose“Properties”

A properties window for this virtual directory appears

Within the Application Pool dropdown, choose “Generic Intranet”

Click on the “Directory Security” tab

of


Intranet

Click on the “Edit” button within the “Authentication and Access Control Area on the tab.

The “Authentication Methods” dialog box will appear

Ensure that the “Enable Anonymous Access” box is unchecked

Click OK to close this dialog box

Click OK to close the properties window for the virtual server.

of


Intranet

Configure ASP.NET in the _layouts folder.

Open the folder that the Sharepoint _layouts directory is associated with.

Note: By default this will be as follows:

C:\Program Files\Common Files\Microsoft Shared\Web ServerExtensions\60\template\layouts

However, you may need to examine the properties of the _layouts virtual directory to find out the location on your serer.

Using a text editor such as Notepad, open the file web.config in this folder.

Look for a line which looks like this:

<add verb="*" path="*.aspx"type="System.Web.UI.PageHandlerFactory, System.Web,Version=1.0.5000.0, Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" />

It should be around line 6 of the file. It is easiest to find by searching for the text<httpHandlers>

You will need to add a configuration line after this line that allows web services to run correctly.

With version 1.1.4322 of the .NET framework, the text you need to add looks like this:

of


Intranet

<add verb="*" path="*.asmx"type="System.Web.Services.Protocols.WebServiceHandlerFactory,System.Web.Services, Version=1.0.5000.0, Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>

If you have a different version of the framework, you may require different syntax. In this case you will need to follow these steps

Locate your machine.config file This should be in the folder C:\Windows\Microsoft.NET\Framework\version\CONFIG\ Search for the text <httpHandlers> Find an <add> tag with the path attribute “*.asmx” Copy that line

Your web.config should look as follows after you have added the line:

Save and close the file.

of


Intranet

Restart IIS.Return to Internet Information Services Manager

Click with the right mouse button on your server

Choose “All Tasks/Restart IIS…”

A Stop/Start/Restart Dialog will appear

Click OK

of


Intranet

Setting up Web Parts to access the Gene r ic Intranet with Sha r epoint 2003

To set up a given access point as a web part in Sharepoint 2003, use the following steps.

Ensure you have the permissions to administrate the area you will add the web part to.

Go to the area where you want to create the web part

Click on “Edit Page”

No Edit Page link? If you have no “Edit Page” link, you may not have permissions to edit thepage.

The “Modify Shared Page” link will now be available on the right of your screen.

of


Intranet

Click on “Modify Shared Page”

Click on “Add Web Parts”

Click on “Browse”

A frame appears on the right of the screen with a list of web parts.

of


Intranet

Press “Next” until you see the Page Viewer Web Part

Drag and Drop the Page Viewer Web Part to your dashboard using the left mouse button.

The page viewer web part will appear in your chosen zone.

of


Intranet

Click on “Open the tool pane” to configure the web part

A window appears on the right of your screen to configure the web part.

of


Intranet

Various configuration options are available to you.The important one is “Link” –

Type the location of the access point into the “Link” area

Click on “Apply” to make these changes to your page viewer web part.

Using the Generic Intranet without SharepointThis product has been built to be integrated with Microsoft Office Sharepoint.

However, you do not require Sharepoint to use this product. Most access points listed below will also work without outside of Sharepoint.

You can create a link from your intranet to the access point URL directly, or create frames on your intranet that are linked to each access point, as appropriate for the architecture of your intranet.

of


Intranet

Definitions of Web Parts/Access Points

This document provides the following information about each access point.

Name

Purpose What this access point is used forComments Any additional comments on how might be used.URL The location on your server that the Access Point is available atURL (SPS 2003) The location on your server that the Access Point is available at under

Sharepoint 2003

Non-Standard Locations: If you are using a non-standard installation, youwill need to change these locations as appropriate.

Users The type of users that use this access pointSharepoint 2001? Whether this access point works as a Sharepoint 2001 web partSharepoint 2003? Whether this access point works as a Sharepoint 2003 web partFree Standing? Whether this access point works outside of SharepointSetup Notes Any additional details about how this access point should be configured.

Leave Web Part

Purpose Shows the amount of leave remaining to the userAllows users to apply for, enter, approve and report on leaveShows the amount of leave waiting for approval by the user.

Comments Different users see different levels of information as appropriateURL htt p ://l o c a l h o s t /la i nt r ane t /N e wLeave/LeaveWeb P art.aspx URL (SPS 2003) /_ l a yout s /l aintr a net/NewLeave/Le a veWebPart. a spx

Users AllSharepoint 2001? YesSharepoint 2003? YesFree Standing? YesSetup Notes You can control whether the “Use Outlook” link (only appropriate to certain

Sharepoint 2001 installations) appears through leave settings.

Expenses Web Part

Purpose Allows users to enter, approve and report on expensesShows the amount of expenses that are waiting for approval by the user

Comments Different users see different levels of information as appropriateURL htt p ://l o c a l h o s t /la i nt r ane t / C l a i m ingExpenses/Expenses W ebPart.aspx URL (SPS 2003) /_ l a you t s/ l aintr a net/Clai mi n gE xp en s es/E xp en s e s We bPart. a spx Users AllSharepoint 2001? YesSharepoint 2003? YesFree Standing? YesSetup Notes You can control whether the “Use Outlook” link (only appropriate to certain

Sharepoint 2001 installations) appears through expenses leave settings.

of


Intranet

Headlines Web Part

Name Headlines Web PartPurpose Show the current headlines.

These headlines can be drawn from a variety of sources.CommentsURL htt p ://l o c a l h o s t /la i nt r ane t /Headlin e s/Tick erTa p eWebPart. a spx URL (SPS 2003) /_la y ou t s/ l aintr a net/Head l in es/ T ic k erTapeWeb P art . aspx Users AllSharepoint 2001? YesSharepoint 2003? YesFree Standing? YesSetup Notes Headlines can come from web pages, RSS, a database table or WebDAV.

You configure headline sources through the web.config file inC:\LocalIntranet

The scrolling mode of the headlines can be controlled through the headlinessettings.

Meetings Web Part

Purpose Show the meetings that currently bookedProvide links to Meetings Search functionality

CommentsURL htt p ://l o c a l h o s t /la i nt r ane t /Do t Ne tWebParts/Mee t in g sWe bPart. a spx URL (SPS 2003) /_ l a you t s/ l aintr a net/DotNetW e bParts/MeetingsWeb P art.as p x Users AllSharepoint 2001? YesSharepoint 2003? YesFree Standing? YesSetup Notes You will need to install Outlook Form to allow people to book meeting

rooms through this web part.

Simple Phonebook Web Part

Purpose Provide an area for users to run a simple search on the staff listDisplay results in the same area

CommentsURL htt p ://l o c a l h o s t /la i nt r ane t /N e wPhonebook/ S i mpleSear c hSt a nd alo n e. h t ml URL (SPS 2003) /_la y ou t s/ l aintr a net/New P honebook/Si m ple S ea r chStandalo n e. h t m l Users AllSharepoint 2001? Yes (but see note)Sharepoint 2003? YesFree Standing? YesSetup Notes For Sharepoint 2001, there is an alternative way of setting up the phone

book

of


Intranet

Advanced Phonebook Web Part

Purpose Provide an area where users can run a more complete search of the staff listDisplays results in the same area

CommentsURL

ht t p:/ / localhost/laintranet/New P honebook/AdvancedOptions S tan dalone.ht m l URL (SPS 2003) /_la y ou t s/ l aintr a net/New P honebook/AdvancedOptions S tandalon e. h t ml Users AllSharepoint 2001? Yes (But see note)Sharepoint 2003? YesFree Standing? YesSetup Notes For Sharepoint 2001, there is an alternative way of setting up the phone

book

Purpose Provide an area where users can see organizational chart web part.Comments The chart is determined by the relationships between the departments and

sections that you have configured through the staff administration section.URL ht t p:/ /l ocalhost/laintranet/NewL e a ve/Or g Char t W ebPart . aspx URL (SPS 2003) /_la y ou t s/ l aintr a net/NewLeave/OrgChartWeb P a rt.aspx Users AllSharepoint 2001? Yes (But see note)Sharepoint 2003? YesFree Standing? YesSetup Notes For Sharepoint 2001, there is an alternative way of setting up the phone

book

Phonebook Update Web Part

Purpose Provide an area where front desk personnel can easily update phonenumbers within the organisation

Comments This web part was written at the request of some local authorities: The purpose is so that certain personnel can update staff members’ phone contact details without updating other details.

URL htt p ://l o c a l h o s t /la i nt r ane t /Expens es A d m i nis trati o n/ A d m i nPhonebook.aspx URL (SPS 2003) /_la y ou t s/ l aintr a net/Exp ensesA d m inistration/Ad m in P honebook.aspx Users All (But see note)Sharepoint 2001? YesSharepoint 2003? YesFree Standing? YesSetup Notes By default, this URL is UNSECURED – any Generic Intranet Staff member

can use it.

It is expected that I.T. in local authorities will secure access to this page.

You can do this using any or all of the following techniques1. Place the web part on a dashboard that only the correct personnel

can access using security in Sharepoint2. Use ASP.NET authorization with the <authorization> tag tp

of


Intranet

web.config to secure access to the page.3. Use NTFS file security to secure access to the .aspx file.4. Use IIS to secure access to the page with IP numbers.

Site Phonebook Update Web Part

Purpose Provide an area where front desk personnel can easily update anorganisational phonebook for frequently used numbers

Comments The site phonebook feature must be enabled using web.config for this web part to be useful. See page 105 of the administration guide for help on howto enable the site phonebook.

URL htt p ://l o c a l h o s t /la i nt r ane t /N e wPhonebook/Organization P honebook.aspx URL (SPS 2003) /_la y ou t s/ l aintr a net/New P honebook/Organiz a tionPhon e book.aspx Users All (But see note)Sharepoint 2001? YesSharepoint 2003? YesFree Standing? YesSetup Notes By default, this URL is UNSECURED – any Generic Intranet Staff member

can use it.

It is expected that I.T. in local authorities ill use IIS security and/orASP.NET security (through web.config) to ensure that only those staff who should access this URL can.

Arrears Web Part

You can do this using any or all of the following techniques1. Place the web part on a dashboard that only the correct personnel

can access using security in Sharepoint2. Use ASP.NET authorization with the <authorization> tag tp

web.config to secure access to the page.3. Use NTFS file security to secure access to the .aspx file.4. Use IIS to secure access to the page with IP numbers.

Purpose Provide an area where finance personnel can run arrears and report onarrears runs

Comments Only users configured as Expenses Administrators can use these facilities.URL htt p ://l o c a l h o s t /la i nt r ane t /Expens es A rre a r s/ArrearsWebPart.aspx URL (SPS 2003) /_ l a yout s /l aintr a net/Exp en s eArrears /Arr e ars Web P art.a s px Users Expenses AdministratorsSharepoint 2001? YesSharepoint 2003? YesFree Standing? YesSetup Notes This web part should be placed on a dashboard not visible to most users.

Administration Web Part

Purpose Allow administrators to configure aspects of the Generic Intranet

of


Intranet

Comments Access control is through the “Applications” configuration area within theadministration applicationAdministrators of the Web Server machine always have full access toGeneric Intranet administration

URL htt p ://l o c a l h o s t /la i nt r ane t /Expens es A d m i nis tra t i o n/ A d m i nWeb P art.aspx URL (SPS 2003) /_la y ou t s/ l ocalhost/ l ai ntr a net/Exp e n sesA d m inistration/A d m inWebPart.a s px Users Administrators OnlySharepoint 2001? YesSharepoint 2003? YesFree Standing? YesSetup Notes Ideally, this would be placed in a dashboard or area that is inaccessible to

most users.

Web Parts for use with Sharepoint 2001 OnlyPhonebook Simple Search (SPS 2001)Purpose Provides simple search area

However, results are displayed in a different web partComments There are three web parts that can combine to provide phonebook

functionality in SPS 2001: Simple Search (SPS2001), Advanced Search(SPS2001) and Phonebook Results (SPS2001)This uses facilities in SPS 2001 to communicate between the three web parts on the HTML page. These facilities are not available in SPS 2003.

URL htt p ://l o c a l h o s t /la i nt r ane t /N e wPhonebook/ S i mpleEntr yFor m.a s p URL (SPS 2003) n/aUsers AllSharepoint 2001? YesSharepoint 2003? NOFree Standing? NOSetup Notes Must be placed on the same page as the Advanced Search (SPS2001) and

Phonebook Results (2001) web parts.

Phonebook Advanced Search (SPS2001)

Purpose Provides advanced search areaResults are displayed in a different web part

Comments There are three web parts that can combine to provide phonebook functionality in SPS 2001: Simple Search (SPS2001), Advanced Search(SPS2001) and Phonebook Results (SPS2001)This uses facilities in SPS 2001 to communicate between the three web parts on the HTML page. These facilities are not available in SPS 2003.

URL htt p ://l o c a l h o s t /la i nt r ane t /N e wPhonebook/AdvancedOp tion s. aspx URL (SPS 2003) n/aUsers AllSharepoint 2001? YesSharepoint 2003? NOFree Standing? NO

of


Intranet

Setup Notes You must isolate the content of this web part from the others through theSharepoint Web Part Properties

Phonebook Results (SPS2001)

Purpose Displays results of phonebook searches.Comments There are three web parts that can combine to provide phonebook

functionality in SPS 2001: Simple Search (SPS2001), Advanced Search(SPS2001) and Phonebook Results (SPS2001)This uses facilities in SPS 2001 to communicate between the three web parts on the HTML page. These facilities are not available in SPS 2003.

URL htt p ://l o c a l h o s t /la i nt r ane t / W ebParts/PhonebookR e sul t s. a sp URL (SPS 2003) n/aUsers AllSharepoint 2001? YesSharepoint 2003? NOFree Standing? NOSetup Notes You must ensure that the content of this web part is NOT ISOLATED

through the Sharepoint web part properties.

of


Setting up the Agresso

Setting up the Agresso Import

Introduction

In order to use the Expenses Module, you need to set up a link between the Agresso database andthe database associated with the Generic Intranet. This information is used so that the Expenses module can create information.

This import process needs to be automated so that the expenses system is always synchronised withAgresso.

We use an import process driven by a SQL Server Data Transformation Services (DTS) package to manage this link.

The following instructions explain how to set up this import process.

Pr e p a r ation

You must have an NT login that has administrative privileges on the Intranet server to create theDTS package.

You must know which server is used to store the Agresso data

You must know which database on this server is used to store the Agresso data

of



Creating the impo r t package

Log on to the server that stores the Generic Intranet database.

Start the SQL Server Enterprise Manager

Within SQL Server Enterprise manager, click on the Generic Intranet database (normallylaintranet1)

Click on the Tools menu, choosing the sub-menu “Data Transformation Services” and the menuoption “Import Data…”

A Data Transformation Services Wizard will appear

of



Introductory Screen

Press “Next”

of



“Choose a Data Source” ScreenWe will be choosing the Agresso database as our source.

The source database type is “Microsoft OLE DB Provider for SQL Server”

Select the server that is used to store the Agresso database from the “Server:” drop-down list

Select either NT authentication or SQL Server Authentication.

If you choose SQL Server Authentication, you will be required to enter a username and password

Select the database that is used to store the Agresso data from the “Database:” dropdown list

Click “Next”

of



“Choose a destination” screenOn this screen, we will be choosing the Generic Intranet database

The destination database type is “Microsoft OLE DB Provider for SQL Server”

Select the server that is used to store the Generic Intranet from the “Server:” drop-down list

In most cases, this will be “localhost”, as the DTS package is being created on the destination server.

Select either NT authentication or SQL Server Authentication.If you choose SQL Server Authentication, you will be required to enter a username and password

Select the database that is used to store the Generic Intranet data from the “Database:” dropdownlist

Normally, this will be a database called “laintranet1”

Click “Next”

of



“Specify Table Copy or Query” screenWe will be copying tables

Ensure “Copy table(s) and view(s) from the source database is chosen.

Click “Next”

of



“Select Source Tables and Views” screenThere are five tables that we want to copy from the Agresso database:

acruserinfo agldimension agldimvalue aglrelation aglrelvalue

We will repeat the following two steps 5 times, once for each table.

Step 1: S e l e ct a t a ble for cop y ing

On the page entitled “Select Source Tables and Views”

Scroll down to the table “acruserinfo” and check it.

Scroll across to the “Transform” column.

Step 2: Configure how t he table is copied

Click on the button with three dots (…) on it.

A dialog box will appear

of



“C o l u mn Mappings and Trans f o r m ation” dialog

Ensure that the “Delete Rows in destination table” checkbox is checked.

Click OK.

You have now successfully selected the table acruserinfo for import.

Repeat this process to select the following four additional tables for import

agldimension

agldimvalue

aglrelation

aglrelvalue

Once all five tables have been selected and configured, you should be back on the screen “SelectSource Tables and Views”

Select “Next”

of



“Save, schedule and replicate package” screen

We want to schedule a weekly run, and save the package on the Generic Intranet Server.

Check the box entitled “Schedule DTS package for later execution”

Click on the button beside this checkbox with the three dots (…) on it.

A dialog box will appear.

of



“Edit recurring Job S che d u l e” dialog

In the “Occurs” area, click on “Weekly”

In the “Weekly” area, click on the “Sat” checkbox

In the “Daily Frequency” area, click on “Occurs once at:” option

Enter a time for the run in the area provided

Click OK

You will return to the “Save, schedule and replicate package” screen.

Click Next >

of



“Save Data Package” screen

Enter “Agresso Data Import” in the Name field provided

Enter a description for this import data

Select the server where the Generic Intranet database is stored from the “Server Name” drop downlist

Click “Next”

The following screen shows a summary of the import package you are creating

Click “Finish”

The job will run immediately, allowing you to check your workOnce the job has been completed, a dialog box will appear to tell you so.

Click on OK

of


Setting up the meetings

Setting up the meetings applicationThe meetings application consists of three components

1) A room booking application2) A web part that displays room bookings3) Administration screens to control the rooms available.

This room booking application is written as a Microsoft Outlook Form that runs on each user’s computer. It replaces the standard Outlook calendar, providing an extra screen that staff can use in order to book a room.

There are three steps you must take in order to provide this functionality to your users.

1) Install the room booking form on your Microsoft Exchange server

Two of these steps need to be repeated on each user’s computer2) Set up a connection between the user’s computer and the database server3) Configure the user’s Microsoft Outlook installation so that they will use the room booking

form instead of their standard calendar form

Facilities Manager Some local authorities have centralised management of room booking with onestaff member. In this case you just need to run steps 2 and 3 on that staff member’s computer.

The following instructions cover these three steps

of



Step 1: Publishing the Outlo ok f o rm on Mi c r o s o ft Exc h a n ge.

The Outlook Form required for the Meeting and Agendas application needs to be published to theOrganization Forms Library.

Forms that are installed into the Organization Forms Library are available to the entireOrganization.

Using Exchange 2003

The procedure for publishing a form in Exchange 2003 differs from earlier versions. If you areusing an earlier version of Exchange go to the section ‘Using Exchange 2000’.

Note: If you are using Outlook 2003, you must turn off caching mode before publishing a form andthen you can turn it back on when the form is published

1. Hold down the shift key and double click on the Meeting.oft file

2. When the form is open, go to the Tools menu Forms Publish Forms As…

of



3. Choose Organisational Forms Library in the “Look In” field and type in “Meeting” in the“Display Name” field

4. Then Click Publish

Using Exchange 2000

The following steps summarize how to setup the Organization Forms Library for forms to beinstalled.

Set-up the Organization Forms library1. In the Exchange Administrator program open the Tools menu and click Forms

Administration.

Note: If the Organization Forms library is not defined, click New to create the Organization Formslibrary, and set the proper language.

2. Expand Folders, System Folders, EForms Registry.

3. In the details window Double-click on the Organization Forms object to open the propertiesand click ‘Client Permissions’

of



4. Give a person or a group the Owner role to allow the user or group to install forms in theorganization forms library. Remember who this is - You will log on as this person shortly.

Note: If there is another form with a similar name such as Organizational Forms (2343) then repeatsteps 4 and 5 for this object also.

Use Outlook to publish the form1. Log onto the exchange server as the person you set up at stage 4 above and open Outlook.

2. Select the form to publish by going to Tools > Forms > Choose Form > User Templates inFile System.

3. Browse to the installation package folder or CD.

4. Browse to the “Meetings” sub-folder

5. Open the form called “Meeting”.

6. In the Outlook Form publish the form

a. Go to Tools > Forms > Publish Form

b. Look in > Organisational Forms Library.

c. Enter Display name ‘Meeting’ and

d. Click ‘Publish’

7. Close Outlook

The next two steps must be repeated on each user’s computer.

of



Step 2 Connect the use r ’s computer to the Generic Intranet database.

Login Scripts Some local authorities have written “login” scripts that make it possible to automateall or part of this process. We have provided copies of these scripts in your install package, in the/contrib. folder. The LGCSB has not written these scripts, nor do we support them. For more help with any of these scripts, please contact the writers of the software.

In order for the Microsoft Outlook form to connect to the Generic Intranet database, a Data SourceName (DSN) must be created on each user’s computer.

This DSN is a configuration file that helps the Outlook form connect to the correct database.

DSN’s are configured through the ODBC Data Sources administration tool.

Open the ODBC Data Source Administrator

Click on “Start” and select the “Programs” menu.

Choose the “Administrative Tools” menu.

Choose the “Data Sources (ODBC)” menu.

The ODBC Data Source Administrator will start

Click on the “System DSN” tab

Click “Add”

Specify the SQL Server driver and click “Finish”.

The Microsoft SQL Server DNS Configuration page will appear

of



Type Laintranet1 in the Name field.

Set Server to the name of the server where the Generic Intranet Database is stored

Click Next

A page entitled “Create a new Data Source to SQL Server” will appear

Select With Windows NT Authentication

Select “Client Configuration” and within “Network Libraries” select “TCP/IP”

of



Select OK

Click on “NEXT >”

A new page will appear

Check the “Change the default database” checkbox

Select the default database to the name of the Generic Intranet Database

Normally, this will be Laintranet1

Click on “NEXT >”

Another screen will appear to complete the DSN configuration

of



Check the checkbox marked “Change the language of SQL Server system messages to:”

Select “British English” from the drop down box provided.

Click “Finish”

A new screen appears to allow you to test the connection.

of



Click on “Test Data Source…” to ensure your connection is correct.

The test screen will appear.

of



Click on OK to close the test window

Click on OK to complete configuration of the DSN

Click on OK to close the ODBC Data Source Administrator

Step 3: Configuring Microsoft Outlook

Configure your user’s Microsoft Outlook installation so that they will use the room booking forminstead of their standard calendar form

This section describes how the Meeting form is installed on the client machines.Outlook must be installed on the client.

Open Outlook and right click on the calendar folder. Select properties.

Under the ‘General’ tab beside the ‘When posting to this folder’ instruction, choose forms.

Choose ‘Organizational forms library’

Select ‘meeting’ and click ‘open’

of


Configuring SQL

Configuring SQL MailIn order to send e-mail, the SQL Server Mail service must be properly configured on the databaseserver that runs the Generic Intranet database. The SQL Server Mail service uses the Microsoft Exchange client services to send e-mail over a Microsoft Exchange server. Essentially you need to create and configure a Microsoft Outlook profile on the database server

Set up the S QL Mail user profile

Set up a Windows 2000/NT User account on the Domain Server, with ‘SQLServerMail’ as the username.

Set up an Exchange mailbox on Exchange server for the same user with the same name‘SQLServerMail’.

Configure the S Q L Mail user on the Generic In t ranet database se r ver

Add this user to the administrators group on the server:

Select Administration Tools, Computer Management, Local Users and Groups,

Click Groups

Click Administrators

Click Add.

Select ‘SQLServerMail’ user.

Active Directory: This procedure may need to be carried out in Active Directory Local Users andGroups if that is how users are set up on the server.

Install Outlook on the database server.

This application is part of the MS Office installation.

Log out of windows and Log on as the new user – ‘SQLServerMail’.

Set up a mail profile in Outlook to view the SQL

Right click on Outlook Icon on the desktop

Select Properties, ADD

Click MS Exchange Server, Enter name ‘SQLServerMail’

Enter in the name of the Exchange Server and Mailbox ‘SQLServerMail’

Configure SQL Services to use this user profile

Log off and login as Administrator.

Go into Administration Tools and Services.

Double click on MSSQLServer to open properties and click the Logon Tab.

Click on the ‘This Account’ radio button

Enter ‘Servername\SQLServerMail’ in the account window

of


Configuring SQL

Enter the password

Enter confirmation password.

Click Apply and OK.

Click on SQLServer Agent under services and do same as above for it.

Configure SQL Server to use the correct mail profile

Log off and Log on as SQLServerMail

Stop and Restart both the SQLServer and SQLServer Agent Services:

Select ‘SQL Server’ in the Services window

Click the stop button,

The ‘SQL Server Agent’ will automatically stop also.

Select “SQL Server” in the Services window and click the Start/Continue button.

Select “SQL Server Agent” in the Services window and click the Start/Continue button

Open up SQL Server Enterprise Manager.

Open the “Support Services” areaExpand SQLServer group

Expand SQLServer

Open folder ‘Support Services’,

Select the mail profileRight click on SQL mail

Select properties

Select MS Exchange settings from profile name menu.

Stop and Restart both the SQLServer and SQLServer Agent Services

You should restart the server at this stage.

of

v3.6.0 Install Guide

Documents

Transcript of v3.6.0 Install Guide