Linked-In_LSSe64 Master Guide for implementation and Use with Appendix

LSSe64 64-bit Law Office Management Software
Legal Software Systems, Inc.
1200 Executive Parkway, Suite 200
Eugene, OR 97401
http://lsse64.com
National Sales and Support (800) 331-4122
General Business (541) 342-5166
support@legalsoftwaresystems.com
http://lsse64.com/clients
1 | P a g e
l 7
CONTENT PAGE DESCRIPTION
CLIENT – SQL IMPLEMENTATION TASKS PERFORMED BY CLIENT
LSSe64 Platform Requirements - Client portal access 2 Windows Server and SQL Server supported platforms
Additional Downloads to install on the SQL Server - Links 3 .Net, MS Office iFilters, Adobe iFilters, Word Perfect iFilters
SQL iFilter installs and registration scripts 4 Install Full Text iFilter and run registration scripts
Windows Firewall 5 Add port rules if Windows Firewall is enabled on SQL Server
Implementation Plan - Record configuration details here 11 Planning your LSSe64 Implementation
Preparation Checklist - Remember your backup plan! 13 SQL Server Preparation - Downloads & Active Directory accounts
SQL Server Installation Tasks 15 SQL Install step by step - See NOTES for required Updates
Configuring the SQL Report Server 29 Web Service URL Folder Settings & Site Settings
Create SQL Linked Server Object - ADSI 35 Use LSSe64Proxy account for Active Directory authentication
Client Server Administration Task 38 Complete after LSS Support creates & configures the database
Gateway Install and Configuration 47 Install Gateway and Optional Configuration task
LSS SUPPORT - IMPLEMENTATION TASKS PERFORMED BY LSS SUPPORT
LSS SUPPORT SQL CONFIGURATION TASK 54 Review SQL Configuration and create LSSe64 database
LSSe64 APPLICATION TASK 54 Install LSSe64 Client and run utilities to build tables and scripts
TESTING LSSe64 CONFIGURATION PERFORMED BY LSS SUPPORT / CLIENT
Test LSSe64 Configuration 67 Detailed Configuration Testing
LSSe64 CLIENT INSTALL & USER SECURITY PERFORMED BY CLIENT
Adding Users to LSSe64 75 Security planning and user configuration
LSSe64 Client Installation – Current Version 86 For User workstations
Major or Minor Version Upgrade 92 First install to SQL Server and upgrade database
LSSe64 USER GUIDES HOW TO INSTRUCTIONS
LSSe64 Calendar Scheduling 96 Calendar Use instructions for the End Users
LSSe64 Document Management (DMS) 117 DMS Use instructions for the End Users
APPENDIX
Miscellaneous Documentation 142 General Issue, solution, troubleshooting information

Eugene, OR 97401
http://lsse64.com
2 | P a g e
LSSe64 Platform Requirements - Client Return to Content
REQUIREMENTS NOTE
Client Services - Downloads and Documentation http://www.lsse64.com/clients/
Username:
Password:
Supported Operating System versions:
− Microsoft Windows Server 2008 R2
− Windows Server 2012 R2
Microsoft lists the minimum system requirements for all SQL 2008 R2
versions and editions on their website at: http://msdn.microsoft.com/en-
us/library/ms143506.aspx Depending on your firm’s data processing
needs however, these minimum requirements may not be appropriate.
For new server purchases, LSS recommends a 64-bit server, Microsoft 64-
bit Windows Server 2008 R2 or Windows Server 2012 R2, and a minimum
of 8GB of RAM.
Supported SQL versions:
− Microsoft SQL Server 2008 R2
NOTE: With SQL 2008 R2, LSSe64 requires that SQL 2008 R2 SP2 and
hotfix CU13 for SP2 (version 10.50.4319.0 or later) be installed in order
for proper pagination and page numbering of billing statements and
other reports.
− SQL Server 2012
SQL EXPRESS NOTE: Optional but limited free Microsoft SQL ‘Express Database
with Advanced Services’ edition - no more than five users will access LSSe64 at any
given time, and the total size of your LSSe64 database is 5GB or less. SQL Express
also has hardware limitations such as
− Uses only single CPU even if more are available
− MAX memory usage of 1 GB
− Does not include native SQL maintenance backup utilities
(Most firms will reach the Express 10GB database limit very quickly so SQL Express
is not a recommended platform however can be useful for a test environment).
For Microsoft SQL Server 2008 R2, LSSe64 requires one of the following
editions:
− Express Database with Advanced Services (free, but not recommended)*
− Workgroup Edition
− Standard Edition (recommended for most firms)
− Enterprise Edition
For Microsoft SQL Server 2012, LSSe64 requires one of the following
editions:
− Express Database with Advanced Services (free, but not
recommended)*
− Standard Edition (recommended for most firms)
− Business Intelligence
− Enterprise Edition
* The free SQL Express edition is only suitable for very small firms and/or when the
licensed features of LSSe64 are limited to certain components. Use of LSSe64 with
the free SQL Express edition requires prior written approval from LSS. See our ‘SQL
Questions and Answers’ document for more information.

Eugene, OR 97401
http://lsse64.com
3 | P a g e
Additional Downloads to install on SQL Server - Client Return to Content
DOWNLOADS NOTE
1. Verify that most current .Net 4 platform has been installed.
NOTE: .Net is required by the LSSe64 client which you may not choose to load
on the SQL server however when LSS Support is working to implement the
system they will need to install the LSSe64 client to run the scripts that build
out the database tables and scripts; when installed on the SQL Server do not
select any Add-in options and do not select the Folder Monitor options these
will hook into your SQL CALs. We highly recommend that you leave this client
in place for future testing and troubleshooting.
.NET Downloads:
http://www.microsoft.com/net/downloads
2. Download and install iFilters for productivity applications such as
Microsoft Office, Adobe, and Word Perfect.
NOTE: Full text indexing of certain file types requires iFilter packages from
Microsoft, Adobe and/or Corel. These are available free of charge from their
respective vendor websites and get installed on your Microsoft SQL Server.
The Client is responsible for installing the iFilters and running registration
scripts to load iFilters into SQL.
Microsoft Office 2010 Filter Packs both 32-bit and 64-bit platforms:
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=17062
WordPerfect iFilter:
http://www.wordperfect.com/ca/pages/patches/300002.html?pgid=800161&ppid=300002
Adobe PDF iFilter for 64-bit platforms:
http://www.adobe.com/support/downloads/thankyou.jsp?ftpID=5542&fileID=5550
3. Add Adobe installed iFilter installation path to your Server ‘Path -
System Variables’ list and reboot the server to take effect.
“c:program filesadobeadobe PDF iFilter 9 for 64-bit platformsbin”
Select PATH from System
Variable list > click Edit
Add a semi-colon (;) and the
iFilter installation path.
Default installation Path:
C:Program filesAdobeAdobe
PDF iFilter 9 for 64-bitbin
- Control Panel
- Systems and
Security
- System
- Advanced
System Settings
- Click the
'Environment
Variables'

Eugene, OR 97401
http://lsse64.com
4 | P a g e
Additional Downloads to install on SQL Server - Client Return to Content
DOWNLOADS NOTE
4. SQL iFilter installs and registration scripts
Select ‘New Query’ > type the script text into the Query window
> click ‘Execute’
− iFilters packs should be listed in Control Panel once installed
− From SQL Management Studio Execute the following Query scripts
to:
1. Load the iFilters:
sp_fulltext_service ‘load_os_resources’, 1
2. Register the iFilters:
sp_fulltext_service ‘verify_signature’, 0
3. Restart the SQL Server service.
4. Verify the expected newer document extensions like docx, xslx,
msg, are listed:
select * from sys.fulltext_document_types
NOTE: Be sure to restart the
SQL Server service after
registering iFilters or you will
not see the expected
document type results.

Eugene, OR 97401
http://lsse64.com
5 | P a g e
When Windows Firewall is enabled add port rules - Client Return to Content
WINDOWS FIREWALL ENABLED CREATE PORT RULES - 1
If the Windows firewall needs to be running on your SQL server you will
need to add incoming port rules to allow client access to the SQL
Server.
If using a Named instance (other than the default instance
MSSQLSERVER) refer to the following link
http://msdn.microsoft.com/en-
us/library/ms177440(v=sql.105).aspx
RULES FOR SQL ACCESS:
1. UDP port 1434 for SQL administration
2. TCP port 1433 for SQL communications
3. TCP port 80 for http web access to SQL Reporting Services
Create New Inbound Rule Wizard named 'LSSe64 SQL Administration'
a. UDP port 1434 (used for SQL administration)
Control Panel > Windows Firewall > Advanced Settings > Inbound Rules >
New Rule > Select ‘Port’ option > click ‘Next’ > Select ‘UDP’ option and
‘Specific local port’ option entering port number 1434 > click ‘Next’
a. b.

Eugene, OR 97401
http://lsse64.com
6 | P a g e
When Windows Firewall is enabled add port rules - Client continued Return to Content
Create New Inbound Rule Wizard named 'LSSe64 SQL Administration'
1. UDP port 1434 (used for SQL administration) - continued
Leave the ‘Action’ Dialog set to ‘Allow the connection’ > click ‘Next’ > on the
‘Profile’ unselect the options for ‘Private’ and ‘Public’ > click ‘Next’
c. d.
In the ‘Name’ dialog enter the Name 'LSSe64 SQL Administration' and a
description for the Rule > click ‘Finish’
e.

Eugene, OR 97401
http://lsse64.com
7 | P a g e
Create New Inbound Rule Wizard named 'LSSe64 SQL Communications'
2. TCP port 1433 (SQL communications)
New Rule > Select ‘Port’ option > click ‘Next’ > Select ‘TCP’ option and
a. b.
Leave the ‘Action’ Dialog set to ‘Allow the connection’ > click ‘Next’ On the ‘Profile’ unselect the options for ‘Private’ and ‘Public’ > click ‘Next’
c. d.

Eugene, OR 97401
http://lsse64.com
8 | P a g e
Create New Inbound Rule Wizard named 'LSSe64 SQL Communications'
2. TCP port 1433 (SQL communications) - continued
In the ‘Name’ dialog enter the Name 'LSSe64 SQL Communications' and a
e.

Eugene, OR 97401
http://lsse64.com
9 | P a g e
Create New Inbound Rule Wizard named ‘LSSe64 SQL Report Server’
b. TCP port 80 (http web access for SQL Reporting Services)
New Rule > Select ‘Port’ option > click ‘Next’ > Select ‘TCP’ option and
a. b.
Leave the ‘Action’ Dialog set to ‘Allow the connection’ > click ‘Next’ On the ‘Profile’ unselect the options for ‘Private’ and ‘Public’ > click ‘Next’
c. d.

Eugene, OR 97401
http://lsse64.com
10 | P a g e
Create New Inbound Rule Wizard named ‘LSSe64 SQL Report Server’
c. TCP port 80 (http web access for SQL Reporting Services) -
continued
In the ‘Name’ dialog enter the Name 'LSSe64 SQL Report Server' and a
e.
You should now have 3 completed Inbound Firewall Rules:

Eugene, OR 97401
http://lsse64.com
11 | P a g e
Implementation Plan - Client - use this implementation plan to document important configuration points Return to Content
TASK DOCUMENT ACCESS CREDENTIALS
1. Configure Remote Access for Legal Software Systems for
Implementation and future support and troubleshooting
Set up Remote Access for LSS Support to log into the SQL Server for
configuration and a workstation for testing; provide remote access
details to support@legalsoftwaresystems.com.
NOTE: If possible you can leave this access configuration in place for LSS
Support to perform future support and troubleshooting.
2. Create Active Directory LSSe64 Administration user to Configure
SQL and for LSS Support troubleshooting.
Member of Domain Admins
Requires mailbox for outlook integration
SQL Sysadmin (set in SQL)
Notate username and password
Username: LSSe64Admin
Password:
3. Create Active Directory user for test workstation install and
training.
Member of Domain Users
Notate username and password
Username: LSSe64User
Password
4. Create Active Directory Proxy user for SQL reporting and ADSI
Server Object Execution Proxy account.
NOTE: Set as Execution Account in the SQL Reporting Services
Configuration Manager and any Active Directory password changes for
this account will need to be updated in Reporting Services Configuration
Manager. Also update the password In SQL Management Studio >
Server Objects > ADSI Server properties > Security
Member of Domain Users
No mailbox necessary
Use for Proxy authentication to LSSe64 database for
ADSI Server Object (active directory) security context
and LSSe64 reporting
Notate username and password.
NOTE: must be db_owner to LSSe64 database
otherwise reporting will fail.
Username: LSSe64Proxy
Password:
5. Create Active Directory user that will be used to update
Exchange user calendars.
Member of Domain users
Use for Calendar Gateway (log on & lock)
Username: LSSe64Gateway
Password:
6. In SQL you will create a SQL security account named LSSe64.
NOTE: It is a good idea to notate your SQL Sysadmin SA account
password here as well
SA SQL account password:___________________________
NOTE: must be db_owner to LSSe64 database to initialize or create tables
This is a SQL only account.
NOTE: Do not add to Active Directory; in SQL
Grant ‘View Server State’ Access to LSSe64
Master SQL Login.
Username: LSSe64
Password:
7. Create 32-bit ODBC System DNS connection to integrate to
Legacy LSS. Launch from C:WindowsSYSWOW64odbcad32.exe
Notate ODBC connection name and
password.
Name: LSS2LSSe64
Password:

Eugene, OR 97401
http://lsse64.com
12 | P a g e
Implementation Plan - Client continued Return to Content
TASK DOCUMENT ACCESS CREDENTIALS
8. Create a list of users who will be added to LSSe64, and note
which users require Administrative access.
LSSe64 is integrated with Active Directory accounts; therefore user
accounts must exist in Active Directory prior to adding to LSSe64
9. Delegate Access needs to be enabled to Users Outlook for all
users of the LSSe64 Calendar module.
The LSSe64Gateway account will be processing Calendar Events;
therefore the LSSe64 Gateway account will require Delegate Access to all
Calendar users Exchange mailboxes. Refer to your LSSe64 user list for
accounts requiring delegate access for LSSe64Gateway to be configured.
10. Document Management module requires physical storage where
Native file copies will be staged.
Create a Share where all LSS users will have full control access to
Native Document Storage where the Active Directory User
Group for LSSe64 (usually Domain Users) has FULL ACCESS.
NOTE: Storage requirements can grow considerably over time.
LSSe64 - Native Document Storage Location:
___________________________________________________________
For clients migrating from Legacy LSS DOCS - Legacy Storage location:
___________________________________________________________
11. Windows Server details SQL Servername:
___________________________________________________________
SQL Server Operating System:
___________________________________________________________
12. SQL Server details
NOTE: For a performance improvement create SQL data and log files on
an alternate local drive (not the then the primary C drive) if possible.
LSSe64 Data (.mdf) and transaction (.log) file location:
____________________________________________________
SQL Version:
___________________________________________________________
SQL instance name where LSSe64 (database) was created:
___________________________________________________________
13. SQL Reporting Services Configuration Manager
LSSe64 Report Server Folder name: LSSe64 Reports (suggested)
___________________________________________________
SQL Reporting Services Report Manager URL:
___________________________________________________________
SQL Reporting Services Web Service URL:
___________________________________________________________

Eugene, OR 97401
http://lsse64.com
13 | P a g e
Preparation Checklist - Client continued Return to Content
TASK NOTE
1. Client Responsible for
− Create Active Directory LSSe64 Administrative user to Configure SQL
and for LSS Support troubleshooting.
Member of Domain Admins: LSSe64Admin
SQL Sysadmin (set in SQL)
− Create Active Directory user for test workstation install and training.
Member of Domain Users: LSSe64User
− Create Active Directory Proxy user for SQL reporting.
Member of Domain Users: LSSe64Proxy
No mailbox necessary
Required for Document Management
− Create Active Directory Gateway user that will be used to update
Exchange user calendars.
Member of Domain Users: LSSe64Gateway
Requires full delegate access to each LSSe64 calendar user’s email profile
− Configure Inbound Port Access for SQL access - Only necessary if
Windows Firewall is enabled on the SQL Server.
1434 UDP - SQL administration
1433 TCP - SQL communications
80 TCP - http web access for SQL Reporting
− Installing SQL with Mixed Mode Authentication
− Adding accounts to Active Directory and SQL
− Configuring SQL Reporting Services
− Creating the Linked Server Object (ADSI) for Active Directory
integration.
SQL Server 2008 R2 or SQL 2012 R2
NOTE: With SQL 2008 R2, LSSe64 requires that SQL
2008 R2 SP2 and hotfix CU13 for SP2 be installed in order for proper pagination
and page numbering of billing statements and other reports.
7. Client responsible for
− Download & Install Productivity iFilter Packs on SQL Server.
a. Microsoft Office 2010 iFilter Pack for 64 bit
b. Adobe PDF iFilter for 64 bit
c. Word Perfect iFilter Pack
− Adobe iFilter path needs to be added to SQL Server Environment
Variables (make sure you enter your installed path if different).
C:Program FilesAdobeAdobe PDF iFilter 9 for 64-bit platformBin
− Create storage location for LSSe64 database and log files; if
possible create on alternate local drive, not your C drive.
i.e. D:LSSe64DB

Eugene, OR 97401
http://lsse64.com
14 | P a g e
Preparation Checklist - Client continued Return to Content
TASK NOTE
− Configure a Shared Storage Location for native copies of files saved to
Document Management; grant access to Domain Users and LSSe64 will
manage security as files are saved with restricted access
Native Document Storage path will need to be added to System Settings
and Defaults > LSS Docs tab > in 2 locations
a. Document and File Storage Location
b. Email Storage Location
− Prepare a SQL backup and recovery plan, create and test that
plan.
NOTE: You will see the last date your LSSe64 database has been
backed up when you have the Console open in the boxes at the
bottom of the console window.
Client is responsible for planning, configuration, and testing of the SQL
LSSe64 database backup plan.
You can schedule using SQL Backup or will need a Backup application with
a SQL Backup Agent.
Remember that a Server level backup will also need to be scheduled as
part of the backup plan.
12. Client responsible for (optional)
− To prevent unattended server reboots set your SQL Server and
Gateway machine to ‘not Update Automatically’.
Just in case the computer encounters an unattended reboot we have
instructions to configure your system to auto logon, launch the LSSe64
Gateway, and auto lock
− Be sure to note your configuration details in the implementation
Plan for future reference.
Server information, storage location, usernames and passwords for
LSSe64 accounts used in database configuration and to run the Gateway
machine.

Eugene, OR 97401
http://lsse64.com
15 | P a g e
SQL Server installation tasks - Client - list Return to Content
TASK PG NOTE
1. SQL Installation 16 SQL requires the latest service pack and cumulative update (CU) packages
2. Setup Support Rules & Product Key 16
3. Product Updates 16
4. Setup Support Rules 17
5. Product Key & License Terms 17
6. Setup Role 17
7. Feature Selection 18
8. Installation Rules 18
9. Instance Configuration - option 1 - Default Instance 19
10. Instance Configuration - option 2 - Named Instance 19
11. Disk Space Requirements 20
12. Server Configuration 20
13. Database Engine Configuration - Server Configuration tab 20
14. Database Engine Configuration - Data Directories tab 21
15. Analysis Services Configuration - Server configuration & Data Directories tabs 21
16. Reporting Services Configuration 22
17. Error Reporting 22
18. Installation and Configuration Rules 22
19. Ready to Install 23
20. Apply SQL Updates 23
21. Launch SQL Management Studio 24
22. Verify - In SQL Management Studio - operational 24
23. Verify - LSSe64 Admin - added and enable sysadmin in SQL 25
24. Add - LSSe64Proxy - Windows account to SQL Login Security 26
25. Add - LSSe64 - SQL - SA account to SQL Login Security 27
26. Set SQL Server properties - Grant ‘View Server State’ for LSSe64 28
27. Edit SQL Protocols - with SQL Configuration Manager 29

Eugene, OR 97401
http://lsse64.com
16 | P a g e
SQL Server installation tasks - Client continued - back to SQL task list Return to Content
TASK NOTE
1. SQL Installation - Log in as LSSe64Admin
NOTE: LSSe64Admin should be a member in the Domain Admin group. This
account will be used by LSS Support for SQL Server access, testing, and future
troubleshooting.
Launch the SQL installation package > Select Installation and option
for New SQL Server
Install supported Microsoft SQL version (screenshots are from SQL 2012)
2. Setup Support Rules
When you launch the SQL installation package it first performs
various system checks and you may need to resolve reported issues
to continue. Click on Show Details to review.
Click ‘OK’ to continue.
3. Product Updates
Available SQL updates will be listed > select ‘Include SQL Server
product updates’ to add these updates to your installation package.
NOTE: All SQL versions require the latest Service Pack and Cumulative
Update (CU) packages to be applied.
click ‘Next’ to Install Setup Files

Eugene, OR 97401
http://lsse64.com
17 | P a g e
TASK NOTE
4. Setup Support Rules
The results of several platform checks will be listed. If you see any
errors in this list you will need to resolve the errors before you can
continue.
NOTE: If you have ‘Windows Firewall’ enabled on your server; setup Support
Files will report a warning however you will be allowed to proceed and
can open the appropriate ports after completing the SQL installation.
Click on Show Details and review > Click ‘Next’ to continue or cancel
to resolve reported issues before continuing.
5. Product Key
You will be prompted for a ‘Product Key’ > select desired SQL edition
option:
a. ‘Specify a free edition:’ with the options to install SQL Server in
‘Evaluation’ mode (this will expire) or ‘Express’
b. ‘Enter the product key;’ to enter your purchased SQL licensed
product key.
Enter your Product key if needed > click ‘Next’
License Terms - Select ‘I accept license terms’ and click ‘Next’.
6. Setup Role
Options to install for LSSe64
Setup Role > Select ‘All Features with defaults’
NOTE: Both options allow you to edit selected options in the next step. ‘All
Features with Defaults’ will have options pre-selected which will include all
required options for LSSe64.

Eugene, OR 97401
http://lsse64.com
18 | P a g e
TASK NOTE
7. Feature Selection
All features needed by LSSe64 will be selected; however you will still
have an option to unselect in the next step.
NOTE: Reporting Services or Report Server features should be selected during
the installation of any supported SQL edition as it is necessary for LSSe64
reporting. We also recommend that you create your LSSe64 database mdf
and log files on an alternate (alternate to the drive where the SQL application
was installed) local drive on the same server.
a. Unselect Distributed Replay Controller and Distributed
Replay Client as this is not necessary for LSSe64.
What is Distributed Replay: http://msdn.microsoft.com/en-
us/library/ff878183.aspx
b. If you are not using SharePoint Server you can unselect
Reporting Services - SharePoint as well
c. Accept the remaining default options and click ‘Next’ to
continue.
8. Installation Rules
Platform checks will be performed and any errors will be reported. If
you encounter errors you need to resolve these to continue.
If there are no errors you can click ‘Next’ to continue.

Eugene, OR 97401
http://lsse64.com
19 | P a g e
TASK NOTE
9. Instance Configuration - option 1
Instance Configuration > Default Instance (MSSQLSERVER)
a. We recommend selecting the defaults if possible, unless you are
installing to an existing SQL Server that already has a proprietary
database using the default instance.
b. When using a default SQL Instance you can configure inbound port
access to standard SQL ports (noted in Window Firewall port rules).
10. Instance Configuration - option 2
Instance Configuration > Named Instance (i.e. SQL2012_LSSe64)
a. A named instance becomes part of the installation path; therefore using
a unique instance name causes the new SQL installation to install to a
separate location and allowing you to restart just a single instance
affecting only the LSSe64 database when needed.
c. When using a named SQL instance, port access will be dynamically
selected, unless within SQL you configure static ports for that named
instance:
http://msdn.microsoft.com/en-us/library/cc646023(v=sql.105).aspx
http://msdn.microsoft.com/en-us/library/ms177440(v=sql.105).aspx

Eugene, OR 97401
http://lsse64.com
20 | P a g e
TASK NOTE
11. Disk Space Requirements
Required and available space will be reported allowing you to go
back and change your installation path if you find this installation will
deplete the available space to an unacceptable level.
Click ‘Next’ to continue.
12. Server Configuration
We recommend that you accept the default service account and
collation configuration
Click ‘Next’ to continue.
NOTE: If installing SQL Server 2008 R2 you will need to select the desired
account for SQL Server Agent and SQL Analysis Service. We suggest using NT
AuthoritySystem.
Local System is a very high-privileged built-in account. It has extensive
privileges on the local computer system and acts as the computer on the
network. The actual name of the account is ‘NT AUTHORITYSYSTEM’.
13. Database Engine Configuration - Server Configuration tab
a. Set the SQL authentication mode to ‘Mixed Mode’
NOTE: You can change the Authentication mode manually after
installation as follows; Open the Microsoft SQL Server Management
Studio (usually found under Start > All Programs > Microsoft SQL Server
2008). In the left pane, at the very top of the list, right-click your SQL
server name and select Properties. In the left pane of the Server
Properties page, select Security. In the right pane, select ‘SQL Server and
Windows Authentication mode’ > Press OK to save these settings.
b. Remember to enter and document the SQL SA password
NOTE: SQL SysAdmin account is the Master SQL administration account; leaving
SA account password blank creates a point of vulnerability.

Eugene, OR 97401
http://lsse64.com
21 | P a g e
TASK NOTE
14. Database Engine Configuration - Server Configuration tab
a. Click ‘Add Current User’ to add LSSe64Admin
b. Also click ‘Add’ and select your network Administrator
account
- Data Directories tab NOTE: We recommend using the default path
15. Analysis Services Configuration - Server Configuration tab
Accept the defaults and consider adding your administrator account
as the Analysis Services administrator (LSSe64 Admin does not need
access).
- Data Directories tab NOTE: We recommend using the default path

Eugene, OR 97401
http://lsse64.com
22 | P a g e
TASK NOTE
16. Reporting Services Configuration - options
Accept the default options and click ‘Next’ to continue.
NOTE: If you failed on Reporting Services Catalog Database File Existence
and/or Reporting Services Catalog Temporary Database File Existence go Back
and select the Reporting Services Native Mode Install only option and try
again. This would be due to a previous SQL installation.
17. Error Reporting
18. Installation and Configuration Rules

Eugene, OR 97401
http://lsse64.com
23 | P a g e
TASK NOTE
19. Ready to Install
a. Review your installation features and install path
Click ‘Install’ to begin the file installation.
b. Installation Progress - Wait for the Installation Progress to
complete (this can take some time to finish).
c. Complete - When you reach the ‘Complete’ dialog installed
features should have a Green Checkmark being reported as
successfully installed
Click ‘Close’ and the SQL installer will close.
d. You should perform a Server reboot to make sure your new
SQL services all start successfully
20. Apply SQL Updates - After the server reboot run Windows Update to
see if there are any important SQL updates that need to be applied
and apply them.
We do recommend applying any available service packs or important
security updates for SQL and rebooting again when finished.
NOTE: With SQL 2008 R2, LSSe64 requires that SQL
2008 R2 SP2 and hotfix CU13 for SP2 be installed in order for proper
pagination and page numbering of billing statements and other reports.
All SQL versions require the latest Service Pack and Cumulative Update (CU)
packages be applied.

Eugene, OR 97401
http://lsse64.com
24 | P a g e
TASK NOTE
21. Launch SQL Management Studio
NOTE: If you used the default instance name of MSSQLSERVER all you need is
the server name entered into the ‘Connect to Server’ server name field. If you
created a custom instance name like SQL2012_LSSe64 you will need to enter
both the server name and instance name as follows:
<Servername><instance name>
i.e. Server4SQL2012_LSSe64
If you followed the install instructions exactly you should be able to log in as
LSSe64Admin or Administrator having full Sysadmin security privileges.
You can browse to select form active SQL instances
22. Verify - In SQL Management Studio that you can launch and see the
System Databases; master, model, msdb, and tempdb and a Report
Server and Report Server Temp database nested under the Database
node in SQL Management Studio.
SQL had a SQL Security node that when expanded opens a Logins
node. In addition each database will have a Security > Users node.
In the steps following you will add Windows Active Directory accounts
to the SQL Security > Logins node that are necessary for LSS Support
to complete the SQL LSSe64 database configuration.
If you followed the instructions exactly you should already see the
accounts LSSe64Admin and Administrator already added to the SQL
Security > Logins node.
The LSSe64Admin account is a member of the Active Directory
Domain Admins group and when added to SQL will require Sysadmin
SQL privilege to be granted. This will allow LSS Support to log into SQL
as a Sysadmin having access required for completing the configuration
and future support.

Eugene, OR 97401
http://lsse64.com
25 | P a g e
TASK NOTE
23. Verify - LSSe64Admin Windows account has been added to SQL
Security > Login; if not add it now as follows:
a. In SQL Management Studio > Object Explorer > Expand the SQL
Server ‘Security’ node.
NOTE: This Security Account should have been created if SQL was
installed while logged in as LSSe64Admin and you followed the SQL
installation steps described previously. LSSe64Admin is a member of the
Domain Admins group in Active Directory and requires SQL Sysadmin
security access.
b. Select the ‘Logins’ node > right click > select ‘New Login’.
c. On the ‘General’ page make sure the option for ‘Windows
authentication’ is selected.
d. Search for the <Domain>LSSe64Admin account in Active
Directory and select it.
e. Enable Sysadmin - on the ‘Server Role’ page add/select the
‘sysadmin’ role.
Keep the remaining default settings.
NOTE: LSS Support will complete the LSSe64Admin account configuration
after the LSSe64 database has been created.
Remember to document the account password.

Eugene, OR 97401
http://lsse64.com
26 | P a g e
TASK NOTE
24. Add - LSSe64Proxy Windows account to SQL Security > Login
Server ‘Security’ node
LSSe64Proxy is a member of the Domain Users group in Active Directory
and will be used as a Proxy Execution Account to Active Directory and
for rendering SQL Reports in LSSe64.
c. On the ‘General’ page make sure the option for ‘Windows
d. Search for the <Domain>LSSe64Proxy account in Active
Directory and select it.
e. Keep the remaining default settings.
NOTE: LSS Support will complete the LSSe64Proxy account configuration
after they create the LSSe64 database.

Eugene, OR 97401
http://lsse64.com
27 | P a g e
TASK NOTE
25. Add - LSSe64 SQL account to SQL Security > Login.
NOTE: This Security Account will be used for your database connection.
d. On the ‘General’ page make sure the option for ‘SQL Server
e. Unselect the option to ‘Enforce password policy’ which will
automatically unselect the other 2 password options below.
f. Keep the remaining default settings.
NOTE: LSS Support will complete the LSSe64Admin account
configuration after the LSSe64 database has been created.
g. Set SQL Server properties - Grant ‘View Server State’ for LSSe64
− In SQL Management Studio select your (top node) SQL Server Instance >
right-click and select Properties.
− In the ‘Server Properties’ dialog select ‘Permissions in the Left
navigation panel > in the ‘Logins or Roles’ panel select the SQL account
‘LSSe64’.
− In the ‘Permissions for LSSe64’ panel locate the ‘View Server State’
permission and select the ‘Grant’ option > click ‘OK’ to save.
Select image & press
‘ctrl+click’ to preview a
large copy of image on
page 56 > (‘ctrl+click on
large image to return

Eugene, OR 97401
http://lsse64.com
28 | P a g e
TASK NOTE
26. Edit SQL Protocols - Open SQL Configuration Manager
a. In the left panel expand the ‘SQL Server Network Configuration’
node and select your SQL Instance
b. In the right panel enable the following protocols:
Shared Memory
Named Pipes
TCP/IP
c. Select each protocol that needs to be enabled > Right click >
select ‘Enable’ > click the ‘OK’ button and you will be prompted
to restart SQL Services for changes to take effect.
d. In the left pane of SQL Configuration Manager select the ‘SQL
Server Services’ > In the right panel select ‘SQL
Server(<instance_name>)’ > right click and select ‘Restart’

Eugene, OR 97401
http://lsse64.com
29 | P a g e
SQL Report Server configuration - Client - list Return to Content
TASK PG NOTE
1. Set the Execution Account for SQL Reporting 30 Use SQL Reporting Services Configuration Manager
2. Configure Permissions for SQL Reporting 30 Web Services URL link to configure Site Settings and Folder Settings
3. Test SQL Reporting Web Service Security 31 Verify your SQL Report configuration
4. Configure SQL Report Services Site Settings Security 33 Limited security for Proxy access to reporting

Eugene, OR 97401
http://lsse64.com
30 | P a g e
SQL Report Server configuration - Client continued - back to Report Server configuration list Return to Content
TASK NOTE
1. Set the Execution Account for SQL Reporting
1. After completing your SQL installation open Start > All Programs
> the SQL Report Services Configuration Manager > enter the
new SQL Server name and the instance name (default is
MSSQLSERVER) that you created during installation in the
‘Reporting Services Configuration’ dialog > click ‘Connect’.
2. In the left pane, select ‘Execution Account’.
3. In the right pane, select ‘Specify an execution account’ > enter the
account name as <domain>LSSe64Proxy > Click ‘Apply’.
− Configure Reporting Services Permissions for users
− Note your Report Manager URL:
i.e. 'http://<server>:80/Reports’
− Note your Web Service URL:
i.e. ‘http://<server>:80/ReportServer’
Be sure to document these web paths in your Implementation Plan
(PG 11); the Web Service URL will be part of your Database Connection
Dialog in LSSe64.

Eugene, OR 97401
http://lsse64.com
31 | P a g e
TASK NOTE
− Test SQL Reporting Web Service Security
a. In the Reporting Configuration Manager left panel select ‘Web
Service URL’ > in the right panel click on the ‘Report Server Web
Service URL’ hyperlink.
NOTE: Internet Explorer (IE) does not pass the credential to the Report
Server automatically, therefore if you are prompted to login when
clicking the ‘Report Manager URL,’ configure your Internet Explorer
Browser Security Options for User Authentication: located in Tools >
Security tab > click the ‘Custom’ button > scroll to the bottom of the
settings list to find > User Authentication > Logon > select ‘Automatic
Logon with current user name and password’ > click the 'OK' button.
b. The hyperlink should open a browser. The result looks a bit
cryptic however if your browser opens without errors you can
continue, otherwise the error will need to be resolved first.
c. In the Reporting Configuration Manager left panel select ‘Report
Manager URL’ > in the right panel click on the ‘Virtual Directory
URL’ hyperlink.
NOTE: Internet Explorer (IE) does not pass the credential to the Report
Server automatically, therefore if you are prompted to login when
clicking the ‘Report Manager URL,’ configure your Internet Explorer
Browser Security Options for User Authentication: located in Tools >
Security tab > click the ‘Custom’ button > scroll to the bottom of the
settings list to find > User Authentication > Logon > select ‘Automatic
Logon with current user name and password’ > click the 'OK' button.

Eugene, OR 97401
http://lsse64.com
32 | P a g e
TASK NOTE
d. The hyperlink should open a browser to the Reporting Services
Virtual Directory. It looks a bit cryptic however what you are
looking for are errors being reported, if not you can continue,
otherwise the error will need to be resolved first.
e. On the ‘Home’ page of the Report Manager website, click the
'Folder Settings' tab.
f. Click ‘New Role Assignment’.
g. In the ‘Group or user name’ field, enter the security group
identified above (i.e. <domain>Domain Users).
h. In the role list below, select 'Browser' and click ‘OK’ to save the
changes.
i. Create a second Role for LSSe64Admin to support publishing of
reports (assuming you are logged in as LSSe64Admin) Click ‘New Role
Assignment’.
j. In the ‘Group or user name’ field, enter the security group
identified above (i.e. <domain>LSSe64Admin).
k. In the role list below, select all options' and click ‘OK’ to save the
changes.
l. On the Home page of the Report Manager website, in the top-
right corner, click the ‘Site Settings’ link.

Eugene, OR 97401
http://lsse64.com
33 | P a g e
TASK NOTE
m. You have completed adding Roles to Folder Setting Security.
4. Configure SQL Report Services Site Settings Security.
a. In the Reporting Configuration Manager select the blue menu
option ‘Site Settings’.
b. In the left Site Settings section select ‘Security’ and click the
‘New Role Assignment’ option.
c. In the Group or Username field enter ‘<domain>LSSe64Proxy’.
d. Select the ‘System User’ option and click ‘OK’.

Eugene, OR 97401
http://lsse64.com
34 | P a g e
TASK NOTE
e. Create a second Role Assignment for LSSe64Admin (account in
use for implementation) In the left ‘Site Settings’ page select
‘Security’ and click the ‘New Role Assignment’ option.
f. In the Group or Username field enter ‘<domain>LSSe64Admin’.
g. Select the ‘System Administrator’ option and click ‘OK.’
NOTE: When LSSe64 Reports are published to SQL Reporting Server you
need to be logged in as a SQL Reporting ‘System Administrator’.
NOTE: To support publishing of LSSe64 Complex Reports you need to edit
the SQL web.config file
See the Appendix for errom message if not edited and instructions to
correct this error: Resolve error publishing LSSe64 reports

Eugene, OR 97401
http://lsse64.com
35 | P a g e
Create SQL Linked Server Object - ADSI - Client - list Return to Content
TASK PG NOTE
1. Configure a SQL Linked Server object named ADSI 36 Proxy object for Windows Active Directory to auto log-in to LSSe64
2. Linked Server - General page 36 Settings for limited access
3. Linked Server - Security page 37 Settings for limited access

Eugene, OR 97401
http://lsse64.com
36 | P a g e
Create SQL Linked Server Object - ADSI - Client continued - return to Linked Server list Return to Content
TASK NOTE
1. Configure a SQL Linked Server object named ADSI to proxy login
authentication for users set up in LSSe64. Use the LSSe64Proxy
account that is a member of Domain Users as the Execution Account.
a. In SQL Management Studio Expand ‘Server Objects’ > select
‘Linked Servers’ and right-click > Select ‘New Linked Server’.
2. Linked Server - General page
a. In the New Linked Server dialog select the General page.
b. In the Linked server field, type ADSI.
c. In the Server type option, select ‘Other data source’.
d. For Provider, select ‘OLE DB Provider for 'Microsoft Directory
Services’.
e. For Product Name, type ‘LSSe64 Active Directory integration’.

Eugene, OR 97401
http://lsse64.com
37 | P a g e
Create SQL Linked Server Object - ADSI - Client continued - return to Linked Server list Return to Content
TASK NOTE
3. Linked Server - Security page
a. In the New Linked Server dialog select the ‘Security’ page.
b. Under the selection ‘For a login not defined In the list above,
connections will’, select ‘Be made using this security context:’
c. Enter ‘<domain>LSSe64Proxy’ account in the ‘Remote Login’
field and the account password in the ‘With password’ field.
d. Press OK to save the new ADSI Linked Server.

Eugene, OR 97401
http://lsse64.com
38 | P a g e
Client Server Administration Task - Client - list Return to Content
TASK PG NOTE
1. Configure Backup - plan, configure, and test 39 Clients responsible for LSSe64 database backup and recovery.
2. No Automatic Updates - suggested 39 Prevent unattended reboots.
3. Automated Console Login, application launch, and Lock
optional
40 In case of unattended reboots configure auto logon and console
lock.
4. Nightly Reboot configuration - optional 41 A daily reboot can help keep your server resources in optimal
health
5. Firm Defaults - System Settings and Defaults (SSD) 44 Client Administrator to review and complete their Firm Default
SSD configuration options.
Firm Defaults will be applied to new LSSe64 user accounts when
created so should be set prior to adding the user accounts.
6. Configure full Delegate Access for LSSe64 Gateway account
Performed by Client
45 Delegate access is necessary for Firms implementing LSSe64
Calendaring in order for the LSSe64Gateway to interface LSSe64
scheduled events to interface to user’s Outlook schedules.

Eugene, OR 97401
http://lsse64.com
39 | P a g e
Client Server Administration Task - Client continued - back to client admin task list Return to Content
TASK NOTE
These task are to be performed by the Client after LSS Support
completes their SQL Database create and SQL configuration task.
1. Client implementation task on pages 1-37
2. LSS Support implementation task on pages 54-66
3. Client Admin task 38-46
4. Gateway Configuration (calendaring or workflow) pages 47-53
1. Configure Backup - of LSSe64 Database and the SQL server for total
recovery - CLIENTS ARE RESPONSIBLE FOR BACKUP PLANNING,
BACKUP IMPLEMENTATION, AND RECOVERY.
In the LSSe64 Console footer we report that last LSSe64 database backup date
Consider the following:
a. Backup the server for quicker recovery.
b. Backup the LSSe64 database; this can be configured through SQL
Backup or using backup software with a SQL Agent.
c. Consider SQL point in time recovery using SQL transaction logs.
d. Be sure to test both your backup and recovery plans.
NOTE: We recommend that the LSSe64 database Recovery Model be set to Simple.
The ‘simple’ recovery model uses less disk space, and if you should ever need to
restore the database, it will be restored to the point in time where the backup took
place. The ‘simple’ recovery model is appropriate for most firms. The ‘full’ recovery
model uses much more disk space, and requires management of transaction logs,
but if you should ever need to restore the database, you may have the option to
restore it to any specific point in time. The ‘full’ recovery model is appropriate for
firms who employ an on-staff or contracted SQL expert to manage the SQL server.
2. No Automatic Updates - Verify or set the Server to NOT
automatically update software.
a. From Control Panel or the Start menu > All Programs > Windows
Update.
b. Select the 'Important Updates' dropdown options to 'download
updates but let me choose whether to install them'.
c. Change other options as appropriate for your organization.
Set you SQL server software update scheme to any setting that does NOT
allow automatic updates in order to prevent unattended reboots.

Eugene, OR 97401
http://lsse64.com
40 | P a g e
TASK NOTE
Automated Console Login, application launch, and Lock - optional In case of unattended reboots you can configure the SQL server to auto
logon and lock the console, launching LSSe64 Gateway to process LSSe64
Calendar events (Gateway could be installed on a different computer).
1. Create a batch file that will:
a. Launch outlook.
b. Launch (LSSe64) LSS.exe in Gateway mode.
c. Lock the Server console.
NOTE: This batch file will launch LSSe64 in Gateway mode; if you are setting
the Gateway up on separate computer you would configure this on that
machine rather than the SQL Server.
Startgw.bat Example:
timeout /T 5
start /d ‘c:program filesMicrosoft officeoffice12’ outlook.exe
timeout /T 5
start /d ‘c:program fileslegal software systems, inclsse64’ lss.exe
gateway
timeout /T 10
c:windowssystem32rundll32.exe user32.dll Lock Workstation
2. Add a shortcut to the Startgw.bat file to Windows Start > All
Programs > Startup.
NOTE: Right click on the Startup folder in the Program menu and select open
to locate the Startup folder.

Eugene, OR 97401
http://lsse64.com
41 | P a g e
TASK NOTE
Nightly Reboot configuration - optional
a. Edit the server Registry to enable automated logon.
b. Create Restart batch file.
c. Create Windows Schedule Task to trigger the Restart batch file.
Take this another step further by setting us a Windows Scheduled Task to
Reboot your server nightly at a time when users will not be in the system
and the reboot will not interfere with your backups.
1. Create/edit 3 Registry keys that will set your server to Auto Log on
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon
AutoAdminLogon
Set to 1 (0 zero = OFF or 1 one = ON).
DefaultUserName
set to the Logon Account that the LSSe64 gateway is configured to run
logged in as.
DefaultPassword
set the Logon Account password
NOTE: Since you are entering the password for the logged on account and it is not
encrypted in your Server registry it is best NOT to configure your LSSe64 Gateway
to run under the Administrator account; instead you should set up an
LSSe64Gateway account that is simply a member of Domain Users and use this
account for running your LSSe64 Gateway.
2. Create a batch file that will restart the server. Restart.bat Example:
Shutdown.exe /r /f /c ‘Automatic System Reboot with LSSe64 Gateway launch’
NOTE: Space between parameters is necessary on Windows Server 2008.

Eugene, OR 97401
http://lsse64.com
42 | P a g e
TASK NOTE
3. Log onto the Server Console as your ‘Domain Administrator’ and
Create a new Windows Schedule Task to trigger the Restart Server
batch file (RestartServer.bat).
Start > Administrative Tools > Task Scheduler > Action > Create Task
a. On the Task General Tab select option to ‘Run whether user is
logged on or not’.
b. Name the task: i.e. Scheduled Nightly Reboot.
c. Enter a description: i.e. Automated reboot with auto logon and
console lock batch file that runs on startup; LSSe64 Gateway will
launch and continue running with console locked (required for
LSSe64 Calendaring).
d. Select the option to ‘Run with highest privileges’.
d. Configure a ‘New Trigger’ that will begin on a Schedule; you can
set a daily schedule or define a weekly schedule with reboots
performed on specific days.
e. Select the option to ‘Stop task if it runs longer than’ and select a
period of time: i.e. 1 hour.
NOTE: Avoid rebooting during the period your backups are running or
Anti-Virus might be updating.

Eugene, OR 97401
http://lsse64.com
43 | P a g e
Client Server Administration task - Client continued - back to client admin task list Return to Content
TASK NOTE
f. Configure a ‘New Action’ that will Start a program.
g. Keep the default ‘Conditions’ (or edit as desired).

Eugene, OR 97401
http://lsse64.com
44 | P a g e
TASK NOTE
h. Configure ‘Settings’ by selecting the option to ‘Stop the task if it
runs longer than: set to a period long enough to complete a
reboot like 1 hour.
i. Select ‘Do not Start a New Instance from the dropdown menu
option for ‘If task is already running, then the following applies:’
j. Click OK and enter the necessary password.
NOTE: If this Scheduled Task gets launched in a remote session that
instance will prevent the actual scheduled reboot to fail since it is set to
NOT start another instance if already running.
5. Firm Defaults - System Settings and Defaults (SSD)
− Firm Defaults will be applied to new LSSe64 user accounts when
created so should be set prior to adding the user accounts
− LSS Support can answer questions and assist with review of how
Firm Defaults will behave, however it is the Firms responsibility
to understand and test their default settings for all enabled
LSSe64 modules.
− Firm Administrator for LSSe64 should also review ‘Codes and
Usage’ to configure default options for all modules
(i.e. Timekeepers, Document Type, Courts, Triggers, Activities, etc.)
See support section pages 53
through 57 for more details.
You are welcome to contact
support with your Firm Default
configuration questions:
(800) 331-4122

Eugene, OR 97401
http://lsse64.com
45 | P a g e
TASK NOTE
6. Configure full Delegate Access for LSSe64 Gateway account For LSSe64 Calendar appointments, deadlines, or task to be added to a
users Outlook the Active Directory user LSSe64Gateway needs to have
delegate access to that users Calendar, Task, and Inbox.
Option 1: Configure in Active Directory on Exchange tabs (if
Exchange Management Tools have been installed)
In active directory, open the user that requires LSSGateway to have
delegate access to their Outlook for calendar integration.
Go to Exchange Advanced Tab > Mailbox Rights button > Add >
select LSSGateway user
‘When you return to the mailbox rights list, LSSGateway should now
be listed > Click once to highlight (select) > change the permissions
as follows:
a. Clear all settings except for
b. Select ‘Read Permissions’
c. Select ‘Full Mailbox Access’
d. Click ‘OK’ to save
http://support.microsoft.com/kb/326894

Eugene, OR 97401
http://lsse64.com
46 | P a g e
TASK NOTE
6. Configure full Delegate Access for LSSe64Gateway account -
continued
Granting ‘LSSe64Gateway’ delegate permissions through Outlook
Option 2: Configure through Outlook - Granting ‘LSSe64Gateway’
delegate permissions through Outlook
Outlook 2003 and Outlook 2007:
Tools > Options > Delegates tab > Add > select ‘LSSe64Gateway’ user
> OK > select ‘LSSe64Gateway’ user that now appears in your
delegates list > click permissions.
Assign editor rights to Calendar, Tasks, and Inbox if you want to
receive notifications which are a configurable item in LSSe64.
Outlook 2010:
Go to File Tab > Info > Account Settings > Delegate Access > Add >
select ‘LSSe64Gateway’ user > OK > select ‘LSSe64Gateway’ user that
now appears in your delegates list > click permissions.
Assign editor rights to Calendar, Tasks, and Inbox if you want to
receive notifications which are a configurable item in LSSe64.

Eugene, OR 97401
http://lsse64.com
47 | P a g e
Gateway Calendaring Configuration - Client - list Return to Content
TASK PG NOTE
REQUIRED: Full Delegate Access for LSSe64Gateway account
Performed by Client
45 Firms implementing LSSe64 Calendaring must configure delegate
access to all LSSe64 users Outlook accounts; the LSSe64Gateway
this access to interface the LSSe64 scheduled events with each
user’s Outlook schedules.
1. Add LSSe64Gateway account to LSSe64 User list 48 Required only for Calendar integration to Outlook Schedules
2. Configure Outlook email profile for Calendar integration 49 Launch Outlook as LSSe64Gateway account having delegate access
to all LSSe64 users email accounts.
3. Install LSSe64 Client to run as the LSSe64 Gateway 50 Includes configuration of Outlook Integration for Calendaring
4. Configure Gateway machine to log on, launch, and Lock 52 Optional: In case you’re Gateway has an unexpected reboot.
5. Configure Windows Scheduled task to perform a nightly
reboot
53 Windows scheduled task will run a batch script to reboot the
server which helps to maintain optimal health.

Eugene, OR 97401
http://lsse64.com
48 | P a g e
Gateway Calendaring Configuration - Client continued – back to gateway task list Return to Content
TASK NOTE
1. Add LSSe64Gateway account to LSSe64 User list
Minimum ‘User Maintenance’ Security > General:
The Gateway PC (could run on the SQL server or just a workstation dedicated
to running the LSSe64 Gateway) will need to be logged in and running
under an active e-mail account having delegate access to all user
accounts who will be using the Calendaring integration. LSSe64 will be
launched using the ‘Gateway’ parameter alongside Outlook running
under the same user account; preferably a unique active directory
account named LSSe64Gateway having been created with an Exchange
e-mail account.
‘User Maintenance’ > ‘Calendar’ > ‘Outlook Integration’.
NOTE: The Gateway account and all users that need Calendaring events posted
to their Outlook schedules must have the Interface with Outlook option selected.

Eugene, OR 97401
http://lsse64.com
49 | P a g e
TASK NOTE
2. Configure Outlook email profile for Calendar integration We suggest using an account named LSSe64Gateway
a. Logon to computer that will be used to run the LSSe64
Gateway as LSSe64Gateway account; or you can log in as
administrator and configure Outlook to launch using the
LSSe64Gateway Outlook account.
NOTE: Do not install the gateway on your Exchange Server, of the LSSe54
SQL Server; it can be installed on a workstation level PC however the
Gateway PC should not be accessed by users. It must be logged in as the
LSSe64Gateway user (or launch Outlook with LSSe64Gateway profile) and
locked so the Gateway can run continually.
Optional: Take this another step further by setting us a Windows
Scheduled Task to Reboot your server nightly at a time when users
will not be in the system and the reboot will not interfere with your
backups.
Restart.bat Example:
shutdown.exe /r /f /c ‘Automatic LSS System Restart’
Optional: Edit Your Registry settings to enable auto logon (as
a precaution always backup your registry prior to making
changes):
There are 3 Registry keys settings that will set your server to
Auto Log on:
AutoAdminLogon
set to 1 (0 zero = OFF or 1 one = ON)
DefaultUserName
set to the Logon Account that gateway is configured to
run logged in as
DefaultPassword
set the Logon Account password
NOTE: You may need to create the necessary keys
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon

Eugene, OR 97401
http://lsse64.com
50 | P a g e
Gateway Calendaring Configuration - Client continued - back to gateway task list Return to Content
TASK NOTE
b. Install and configure Outlook. Install Outlook > Launch Outlook to configure for LSSe64Gateway account
− In Outlook 2007 > Select Tools > Account Settings > select the
‘E-mail’ tab > select the Exchange Account > and click the
‘Change’ option.
− In Outlook 2010 > Select the File Tab on
your Tool Ribbon > in the right panel
select Account Settings.
− Under ‘Microsoft Exchange Server’ clear the ‘Use Cached
Exchange Mode’> close and reopen outlook to apply the
change.
− NOTE: By default Outlook is installed using ‘Cached Exchange Mode’
this should be disabled as this can prevent your updates from getting
to the server until Outlook is closed.
− NOTE: If Outlook prompts for permission to access email
address information stored in Outlook you need to install an
Anti-Virus application - installing a free copy of Microsoft
Security Essentials or another Anti-Virus application will disable
this prompt. You can also disable the prompt manually in your
Trust Center > Programmatic Access to Never Warn which is not
recommended by Microsoft.
3. Install LSSe64 Client and configure to run as Gateway. NOTE: If installed on a workstation operating system (like windows 7),
make sure power settings are set to ‘always on’
a. Download and Install LSSe64 Workstation.
Since the Gateway will not use Add-ins Select 32-bit or 64-bit
platform based on the Operating System.
(Add-ins will NOT be installed so we are not concerned with the
Outlook platform)
http://www.lsse64.com/clients/
Username:
Password:
b. Run the LSSe64 Client installer. Unselect all options; loading Add-ins and launching the Folder Monitor
utilities on start will consume additional SQL CAL’s.

Eugene, OR 97401
http://lsse64.com
51 | P a g e
TASK NOTE
− NOTE: On the Gateway PC or Server you will unselect all
Add-in options for Word, Excel, Outlook, and Adobe in the
‘Optional Toolbar Integration’ dialog screen.
− NOTE: On the Gateway PC or Server you will unselect the
option to ‘Automatically launch LSS Folder Monitor after
Windows logon’ in the ‘Document Management Options
dialog screen.

Eugene, OR 97401
http://lsse64.com
52 | P a g e
TASK NOTE
c. Delete the icon created by the LSSe64 Workstation Installation
and create a new shortcut on the desktop so that you can edit
the Target Path adding the 'Gateway' parameter.
Edit the Target Path, adding the Gateway parameter to the path end:
‘C:Program FilesLegal Software Systems, IncLSSe64LSS.exe’ Gateway
4. Configure Gateway machine to log on, launch, and lock.
Optional automated login and launch process in a production
environment.
NOTE: To keep your LSS Gateway up and running even when the server reboots
unexpectedly you can configure your system to Log in automatically followed by
running the Restart batch files to launch Outlook and your LSSe64 Gateway.
a. Launch Outlook
b. Launch LSS.exe Shortcut using the ‘Gateway’ parameter
c. “c:program fileslegal software systems, inclsse64” lss.exe
gateway
d. Lock the workstation
a. Add the LSSe64Gateway user account as a User in LSSe64.
− The Gateway user does not require a Timekeeper code.
− Create user in LSSe64 (see Adding Users script)
− In User Maintenance select the 'Calendar' tab > In the
Outlook Integration box unselect 'Use Firm Defaults' and
unselect ‘Interface with Outlook’.

Eugene, OR 97401
http://lsse64.com
53 | P a g e
TASK NOTE
b. Create a batch file that will
− Launch outlook
− Launch LSS.exe in Gateway mode
− Lock the Workstation
Startgw.bat Example:
timeout /T 5
start /d "c:program filesMicrosoft officeoffice12"
outlook.exe
timeout /T 5
start /d "c:program fileslegal software systems,
inclsse64" lss.exe gateway
timeout /T 10
c:windowssystem32rundll32.exe user32.dll Lock
Workstation
5. Configure Windows Scheduled task to perform a nightly reboot.
Optional: Take this another step further by creating a Windows
Scheduled Task to reboot your server nightly at a time when users
will not be in the system and the reboot will not interfere with
your backups.
Restart.bat Example:
shutdown.exe /r /f /c "Automatic LSS System Restart"
NOTE: If installed on a workstation operating system (like windows
7), make sure power settings are set to ‘always on’.
To open Windows power options on Windows 7:
Windows ‘Start’ > ‘Run’ > enter 'powercfg.cpl' without the quotes and
click ‘OK’ to launch.
NOTE: Right click
on the Startup
folder in the
Program menu
and select open to
locate the Startup
folder and save
your Startup
batch file to this
location.

Eugene, OR 97401
http://lsse64.com
54 | P a g e
Verify SQL settings & create LSSe64 database - performed by LSS Support - list Return to Content
LSS SUPPORT SQL CONFIGURATION TASK PG LSSe64 APPLICATION TASK PG
1. Verify that SQL Server is set to Mixed Mode Authentication 55 1. Download 32-bit or 64-bit LSSe64 Workstation installers 61
2. Verify Full Text iFilter have been installed and run script to
register
55 2. Install LSSe64 Client on the SQL Server 61
3. Verify necessary SQL Protocols are enabled
(Shared Memory, Named Pipes, TCP/IP)
55 3. Launch the LSSe64 Client from your SQL Server 62
4. Create LSSe64 Database - saving database files on alternate
drive
56 4. Add Licenses keys for purchased modules 63
5. Verify Grant ‘View Server State’ is set for LSSe64 SQL account 57 5. USERS – Add Administrative User Account/s 63
6. Set LSSe64 SQL ‘User Mapping’ - to the LSSe64 database
(public)
58 6. Configure System Settings & Defaults (SSD) 64
7. Set LSSe64Admin AD ‘User Mapping’ - to the LSSe64
database
(db_owner & public)
58 7. Save a copy of the LSSConnectInfo.dat file after the
database connection has been established.
66
8. Set LSSe64Proxy AD ‘User Mapping’ - to the LSSe64 database
(db_owner & public)
58
9. Verify SQL Reporting Services Execution Account
configuration
58
10. Verify SQL Reporting Services Web Service URL configuration 58
11. Verify SQL Reporting Services Report Manager URL
configuration
59
12. Verify ADSI Linked Server configuration 60

Eugene, OR 97401
http://lsse64.com
55 | P a g e
Verify SQL settings & create LSSe64 database - performed by LSS Support - return to Support list Return to Content
LSS SUPPORT SQL CONFIGURATION TASK NOTE
5. Verify that SQL Server is set to ‘Mixed Mode Authentication’. − Open the Microsoft SQL Server Management Studio > in the left pane,
at the very top of the list, right-click your SQL server name and select
‘Properties’.
− In the left pane of the Server Properties page, select ‘Security’. In the
right pane, select ‘SQL Server and Windows Authentication mode’ >
Press OK to save these settings.
6. Verify Full Text iFilter have been installed and run scripts to register.
Select ‘New Query’ > type the script text into the Query window
> click ‘Execute’
− iFilters packs should be listed in Control Panel once installed
− Verify the path to Adobe iFilter has been added to Server Properties
PATH Environment Variables.
“c:program filesadobeadobe PDF iFilter 9 for 64-bit platformsbin”
− From SQL Management Studio Execute the following Query scripts to:
5. Load the iFilters:
sp_fulltext_service ‘load_os_resources’, 1
6. Register the iFilters:
sp_fulltext_service ‘verify_signature’, 0
7. Restart the SQL Server service.
8. Verify the expected newer document extensions like docx, xslx,
msg, are listed:
select * from sys.fulltext_document_types
7. Verify necessary SQL Protocols are enabled
(Shared Memory, Named Pipes, TCP/IP)
− In SQL Configuration Manager
− In the left panel expand the ‘SQL Server Network Configuration’ node
and select your SQL Instance
− In the right panel enable the following protocols:
Shared Memory | Named Pipes | TCP/IP
NOTE: Be sure to restart the
SQL Server service after
registering iFilters or you will
not see the expected
document type results.

Eugene, OR 97401
http://lsse64.com
56 | P a g e
8. Create LSSe64 Database - create data and log files for database on
alternate drive.
SQL Server Recovery Mode: Simple vs. Full
In the Recovery Model field, select Simple. The ‘simple’ recovery model uses
less disk space, and if you should ever need to restore the database, it will be
restored to the point in time where the backup took place. The ‘simple’
recovery mode is appropriate for most firms. The ‘full’ recovery model uses
much more disk space, requires management of transaction logs, but if you
should ever need to restore the database, you may have the option to restore
it to any specific point in time. The ‘full’ recovery model is appropriate for
firms who employ an on-staff or contracted SQL expert to manage the SQL
server for you.
− In SQL Management Studio select the Database navigation node >
right click and select ‘New Database’.
− On the ‘General’ page in the ‘Database name’ field enter ‘LSSe64’
− Edit the ‘Path’ for your LSSe64.mdf and LSSe64.log files from the
default path to the planned storage location (something other than the
drive where SQL was installed).
− Verify the ‘Options’ page ‘Recovery model’ is set to ‘Simple’, and we
recommend that you set the ‘Compatibility level’ to ‘SQL Server
2008’

Eugene, OR 97401
http://lsse64.com
57 | P a g e
9. Verify Grant ‘View Server State’ to LSSe64 SQL account is set in
‘Server Properties’.
− In SQL Management Studio select your (top node) SQL Server
Instance > right-click and select Properties.
ALSO VERIFY: LSSe64 must be db_owner to LSSe64 database to
initialize or create tables. This affects the Database utilities in LSSe64
during implementation.
− In the ‘Server Properties’ dialog select ‘Permissions’ in the Left
navigation panel > in the ‘Logins or Roles’ panel select the SQL account
‘LSSe64’.
− In the ‘Permissions for LSSe64’ panel locate the ‘View Server State’
permission and select the ‘Grant’ option > click ‘OK’ to save.

Eugene, OR 97401
http://lsse64.com
58 | P a g e
10. Set LSSe64 SQL ‘User Mapping’ to LSSe64 database (public)
− In SQL Management Studio > Object Explorer > Expand the SQL
− Expand the ‘Logins’ node and select the LSSe64 account > right
click > select ‘Properties’.
− In LSSe64 Login Properties dialog > ‘General’ page > make sure
the option for ‘SQL Server authentication’ is selected.
− Unselect the option to ‘Enforce password policy’ which will
automatically unselect the other 2 password options below.
− In LSSe64 Login Properties dialog > ‘User Mapping’ page > in the
‘Users mapped to this login’ panel > select the ‘MAP’ option for
the LSSe64 Database.
− With the LSSe64 database still selected, in the ‘Database role
membership for: LSSe64’ panel select ‘public’.
− Click OK to save.
11. Set LSSe64Admin AD ‘User Mapping’ - to the LSSe64 database.
(db_owner & public)
Map to the LSSe64 database as db_owner and public:
12. Set LSSe64Proxy AD ‘User Mapping’ - to the LSSe64 database.
(db_owner & public)
NOTE: Reporting will not work if db_owner is missing
Map to the LSSe64 database as db_owner and public:
13. Verify SQL Reporting Services Execution Account configuration.
Start > All Programs > the SQL Report Services Configuration Manager >
enter the new SQL Server name and the instance name (default is
MSSQLSERVER) that you created during installation in the ‘Reporting Services
Configuration’ dialog > click ‘Connect’.
− In the left panel, select ‘Execution Account’.
− In the right panel, select ‘Specify an execution account’ > enter the
account name as <domain>LSSe64Proxy > Click ‘Apply’.
14. Verify SQL Reporting Services ‘Web Service URL’ configuration.
In the Reporting Configuration Manager left panel select ‘Web Service URL’ >
in the right panel click on the ‘Report Server web Service URL’ hyperlink.
− Clicking on the hyperlink should open a browser reporting the
<SQL ServerReportserver_InstanceName> and the SQL Version.
Map to the
LSSe64
database as
‘public’

Eugene, OR 97401
http://lsse64.com
59 | P a g e
15. Verify SQL Reporting Services ‘Report Manager URL’ configuration
In the Reporting Configuration Manager left panel select ‘Report Manager
URL’ > in the right panel click on the ‘Virtual Directory URL’ hyperlink.
a. On the ‘Home’ page of the Report Manager website, click the
'Folder Settings' tab.
b. Click ‘New Role Assignment’.
c. In the ‘Group or user name’ field, enter the security group
identified above (i.e. <domain>Domain Users).
d. In the role list below, select 'Browser' and click ‘OK’ to save the
changes.
e. Create a second Role for LSSe64Admin to support publishing of
reports (assuming you are logged in as LSSe64Admin) Click ‘New
Role Assignment’.
f. In the ‘Group or user name’ field, enter the security group
identified above (i.e. <domain>LSSe64Admin).
g. In the role list below, select all options and click ‘OK’ to save the
changes.
h. On the Home page of the Report Manager website, in the top-
right corner, click the ‘Site Settings’ link.
i. You have completed adding Roles to ‘Folder Settings’ >
‘Security’.
j. Configure SQL Report Services Site Settings Security.
k. In the Reporting Configuration Manager select the Blue Menu
option ‘Site Settings’.
l. In the left Site Settings section select ‘Security’ and click the ‘New
Role Assignment’ option.
m. In the Group or Username field enter ‘<domain>LSSe64Proxy’.
n. Select the ‘System User’ option and click ‘OK’.
o. Create a second Role Assignment for LSSe64Admin (account in
use for implementation) in the left Site Settings index select
‘Security’ and click the ‘New Role Assignment’ option.
p. In the Group or Username field enter ‘<domain>LSSe64Admin’.
q. Select the ‘System Administrator’ option and click ‘OK.’

Eugene, OR 97401
http://lsse64.com
60 | P a g e
16. Verify ADSI Linked Server configuration
In SQL Management Studio Expand ‘Server Objects’ > select ‘Linked
Servers’ and right-click > Select 'Properties'
a. Linked Server - General page
− In the Linked server field = ADSI
− Server type option = ‘Other data source’
− Provider = ‘OLE DB Provider for 'Microsoft Directory
Services’
− Product Name = ‘LSSe64 Active Directory integration’.
b. Linked Server - Security page
− Under the selection ‘For a login not defined In the list above,
connections will’, select ‘Be made using this security
context:’
− Enter ‘<domain>LSSe64Proxy’ account in the ‘Remote
Login’ field and the account password in the ‘With
password’ field.

Eugene, OR 97401
http://lsse64.com
61 | P a g e
LSSe64 client install and database utilities- performed by LSS Support - return to Support list Return to Content
LSSe64 APPLICATION CONFIGURATION TASK NOTE
1. Download 32-bit or 64-bit LSSe64 Workstation installers
− Used for LSSe64 Database configuration and future
troubleshooting.
− Verify or Pre install current version of .Net 4 where the LSSe64
client gets installed.
a. Download the appropriate 32-bit or 64-bit Installer based on
your installed Microsoft Applications platform (32-bit Add-in
installer required for 32-bit application platform | 64-bit Add-in
installer required for 64-bit application platform) except where
productivity application Add-ins will not be used like on the SQL
Server or the computer where the LSSe64 Calendaring Gateway
runs.
NOTE: Download both platforms to a shared location for quick
deployment to all clients. Also after the LSSe64 initial configuration is
completed the LSSConnectInfo.dat file can be copied from:
Users<logged on user profile>AppDataRoamingLSSe64
Or depending on your operating system:
Documents and Settings<logged on user profile>Application DataLSSe64
Save to a shared location to help expedite client deployment.
http://lsse64.com/clients/
Username:
Password:
2. Install LSSe64 Client on the SQL Server
Launch the LSSe64 Client installer and click NEXT following the prompts:
NOTE: When installing on your SQL Server be sure to unselect all productivity
application Add-in options, and unselect the ‘Automatically launch LSS Folder
Monitor after Windows logon’ option as they are not necessary and will
count against your SQL client license total when enabled.

Eugene, OR 97401
http://lsse64.com
62 | P a g e
3. Launch the LSSe64 Client from your SQL Server
a. Enter the Database Connection details and a Report Folder
Name of LSSe64 Reports > Test the Database Connection > If the
test Passes you can click OK to launch the application.
NOTE: When using SQL Express or FULL SQL versions and are not
using the default instance name (MSSQLSERVER) you will need to
follow the Servername by the SQL Instance Name
<Servername><SQL_InstanceName>
i.e. Server4SQL2012_LSSe64
Report Server Folder Name – The name you enter here will be
created on the Report Server Website to differentiate the
LSSe64 reports from ant potential SQL reports that may be
present from other SQL installations.
b. Run the LSSe64 Database Utilities to build out the LSSe64
database tables and scripts
− After you install LSSe64 and complete the Database
connection details you can run the Database Utilities to
build out the LSSe64 tables and scripts in the LSSe64 SQL
database.
− First launch the LSSe64 Console > click OK if prompted about
invalid object names (this is expected since the database has not
yet been built out before your initial console launch).
− Run the first 3 Installation scripts in order (You may need to close the
LSSe64 console between steps to enable the next script option).
1. Create Full Text Catalogs.
2. Create Empty Tables.
Close console and reopen to
enable the next installation
script.
3. Publish Reports to the Report

Eugene, OR 97401
http://lsse64.com
63 | P a g e
4. Add Licenses keys for purchased modules
− LSS Support will need the Request Key, Modules Purchased, and
number of users purchased in order to generate a registration
code for your LSSe64 system.
− On each tab the ‘Request Key’ should be the same for all
Modules.
− Your registration is dependent on the hard drive where the
LSSe64 Database lives. If ever this drive fails and gets replaced
your software will need to be re-registered.
− Each purchased module will have a different registration code
and must be paired with the same user count used to generate
the code.
− For each purchased module, select the corresponding tab >
Select the ‘Licensed Components’ checkbox > enter the
’Concurrent Users’ count and ‘Registration Code’.
− Remember to click Save to apply changes
5. USERS – Add Administrative User Account/s
− To enable the remaining System Setting options for
configuration you must add at least one user.
− Select ‘User Accounts’ from the ‘Administration’ settings to open
the Users dialog > Click the Add Update button to bring up a list
of Active Directory accounts that have not yet been added to
LSSe64.

Eugene, OR 97401
http://lsse64.com
64 | P a g e
− Select the user you are currently logged into LSSe64 as;
LSSe64Admin; set Full Administrative Access.
− Select the Domain Administrator account; set Full Administrative
Access (will be helpful for future troubleshooting)
6. Exit the LSSe64 console and re-launch to enable your ‘System Setting
and Defaults’ (SSD) options.
− Complete the Firm Details on the ‘General’ tab (you will be
prompted for required fields like firm name, address, phone, and
fax before you can save.
− Review and complete defaults for each licensed module by
selecting the corresponding module tab like LSS Docs for
Document Management or the Calendar tab for
Calendar/Docketing in Case Management.
− To enable email notifications enter your email server name on
the General tab as the ‘SMTP Server Name’

Eugene, OR 97401
http://lsse64.com
65 | P a g e
− On the SSD > ‘LSS Docs’ tab you will need to enter the URL to a
storage location to house full native copies of files saved in the
Document Management module
− Files will be created/saved, modified, and deleted
programmatically to this location
− Copies of your stored email messages in Document
Management can be saved to the same native storage location
as the documents.
− Users should not be navigating to this location except when
researching errors or issues opening or saving files in Document
Management.
− Files saved to the native storage location should never be access
directly for editing, or deleting. Files should always be opened
through the Document Management interface.
− Also on the SSD > ‘LSS Docs’ tab you need to enter a Security
Group that includes all Active Directory Accounts that will be
allowed access to LSSe64 such as Domain Users, however could
be a Security Group created specifically for LSSe64 Users.
− You can also set preconfigured Document profiling options for
New LSSe64 Users.
− Users will have access to modify their personal preferences from
the profile search panel.

Linked-In_LSSe64 Master Guide for implementation and Use with Appendix

Linked-In_LSSe64 Master Guide for implementation and Use with Appendix

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (13)

Similar to Linked-In_LSSe64 Master Guide for implementation and Use with Appendix

Similar to Linked-In_LSSe64 Master Guide for implementation and Use with Appendix (20)

Linked-In_LSSe64 Master Guide for implementation and Use with Appendix