SL Install (Guide For Users) Manual

Microsoft® Business Solutions–Solomon
Installation Guide
Release 6.5
11/2005
Copyright
Manual copyright © 2005 Microsoft Corporation. All rights reserved.
Your right to copy this documentation is limited by copyright law and the terms of the software license
agreement. As the software licensee, you may make a reasonable number of copies or printouts for
your own use. Making unauthorized copies, adaptations, compilations, or derivative works for
commercial distribution is prohibited and constitutes a punishable violation of the law.
Trademarks
Microsoft, ActiveX, Excel, FRx, FrontPage, Outlook, SharePoint, Visual Studio, Windows, and Windows
Server are either registered trademarks or trademarks of Microsoft Corporation, FRx Software
Corporation, or their affiliates in the United States and/or other countries. FRx Software Corporation is
a subsidiary of Microsoft Corporation. Crystal Reports is a registered trademark of Business Objects
SA.
The names of actual companies and products mentioned herein may be trademarks or registered
marks - in the United States and/or other countries - of their respective owners.
The examples companies, organizations, products, domain names, e-mail addresses, logos, people,
places, and events depicted herein are fictitious. No association with any real company, organization,
product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred.
Warranty disclaimer
Microsoft Corporation disclaims any warranty regarding the sample code contained in this
documentation, including the warranties of merchantability and fitness for a particular purpose.
Limitation of liability
The content of this manual is furnished for informational use only, is subject to change without notice,
and should not be construed as a commitment by Microsoft Corporation. Microsoft Corporation
assumes no responsibility or liability for any errors or inaccuracies that may appear in this manual.
Neither Microsoft Corporation nor anyone else who has been involved in the creation, production or
delivery of this documentation shall be liable for any indirect, incidental, special, exemplary or
consequential damages, including but not limited to any loss of anticipated profit or benefits, resulting
from the use of this documentation or sample code.
License agreement
Use of this product is covered by a license agreement provided with the software product. If you have
any questions, please call the Microsoft Business Solutions Customer Assistance Department at 800-
456-0025 (in the United States or Canada) or +1-701-281-6500.
Publication Date
November 2005
Table of Contents iii
Table of Contents
Introduction 1
Audience.......................................................................................................................................... 1
Installation Preparation 3
Overview .......................................................................................................................................... 3
Summary of Tasks for New and Existing Microsoft Solomon Installations ................... 3
Pre-Installation Checklist ................................................................................................................ 5
Microsoft Solomon Installation Setup Options............................................................................ 11
Planning Security 13
Microsoft Solomon Security Best Practices................................................................................. 13
Physical Security ........................................................................................................................... 16
For the Employees ........................................................................................................................ 17
For the Administrator .................................................................................................................... 17
Securing the Server Operating System ........................................................................................ 18
Authentication................................................................................................................. 18
Access Control................................................................................................................. 21
Single Sign-on ................................................................................................................. 22
External Security Firewall ............................................................................................... 22
Virus Protection ............................................................................................................................. 22
Types of Viruses .............................................................................................................. 23
Virus Prevention Best Practices ..................................................................................... 23
ISA Server 2004............................................................................................................................ 24
ISA Server Policies .......................................................................................................... 24
Network Security Strategies ......................................................................................................... 24
Wireless Networks .......................................................................................................... 26
Network Security Scenarios ........................................................................................... 26
Security Update Management...................................................................................................... 29
Additional SQL Server 2000 Security Settings............................................................................ 30
Guide for New Microsoft Solomon Installations 31

Overview ........................................................................................................................................ 31
Installation Using the Microsoft Solomon CDs ............................................................................ 31
Microsoft SQL Server Installation................................................................................................. 39
Creating Databases ...................................................................................................................... 40
Creating an Empty Database Scenario.......................................................................... 41
Creating a Demo – Solomon Professional or Solomon Standard Database............... 44
Creating an Additional Empty Application Database .................................................... 46
Logging On Using the Demo System and Application Databases................................ 47
Preparing the Demo System and Application Databases............................................. 47
Logging On Using the Empty System and Application Databases ............................... 48
Preparing the Empty System and Application Databases ............................................ 49
Installing Supporting Applications................................................................................................ 50
Solomon Web Order Starter Site.................................................................................... 50
Crystal Reports® for Solomon ........................................................................................ 57
Removing an Earlier Version of Crystal Reports ........................................................... 57
Installing Crystal Reports® Version 10........................................................................... 58
Microsoft Office Project Connector for Solomon........................................................... 61
Using Windows Authentication....................................................................................... 62
Using Project Server Authentication .............................................................................. 66
Installing the Project Connector..................................................................................... 71
Installing the PSA Accounting View to the Microsoft Project Professional .................. 77
iv Installation Guide
Setting Up the Connection Between the Microsoft Project and Microsoft Solomon
Databases .......................................................................................................................82
Installing Microsoft Project Connector Components to the Microsoft Project
Professional 2002 or 2003 Client Workstation ............................................................87
Adding the PSA COM Add-In to Microsoft Project Professional ....................................90
Setting Up Microsoft Solomon on Workstations..........................................................................95
Client Workstation Setup — Executing Microsoft Solomon from a Shared Directory on
the Server ........................................................................................................................95
Client Workstation Setup — Running Microsoft Solomon from the Local Client
Workstation .....................................................................................................................98
Installing Crystal Reports® for Solomon on a Local Workstation .................................98
Updating an Existing Microsoft Solomon Installation 101

Overview.......................................................................................................................................101
Update Prerequisites...................................................................................................................101
Removing an Existing Microsoft Solomon Installation ..............................................................102
Removing Microsoft Solomon Workstation Components ...........................................102
Removing Server Components.....................................................................................102
Installation Using the Microsoft Solomon CDs ..........................................................................104
Updating Databases....................................................................................................................104
Updating Databases from 4.1x/4.2x/4.5x/5.x/6.x to 6.5..........................................105
Prepare SQL Server 7.0 Databases for running with SQL Server 2000 ....................108
Using Database Update after Completing the Database Maintenance Scenario .....109
Updating Microsoft Solomon Client Workstations.....................................................................110
Updating Custom Crystal Reports®.............................................................................................112
Troubleshooting 113
Restoring Microsoft Solomon System Database Table Views ..................................................113
Technical Resources for Microsoft Solomon .............................................................................115
Section Contents...........................................................................................................115
Terminology Definitions ................................................................................................115
Technology Tidbits.........................................................................................................115
Backup and Restore Procedures .................................................................................117
Registered Controls.......................................................................................................119
Solomon.ini....................................................................................................................119
Appendices 121
Appendix A: Microsoft SQL Server Optimization Notes .............................................................121
Supported Microsoft SQL Server Versions...................................................................121
Microsoft SQL Server 2000..........................................................................................121
Appendix B: Updating the Application Database with Schema Information ............................125
Appendix C: Manually Creating Stored Procedures and Table PA_Connect ............................127
Appendix D: Restoring Connector Functionality to Microsoft Project Server ...........................131
Appendix E: Microsoft Solomon Support....................................................................................133
Important Phone Numbers and Internet Addresses ...................................................133
Index 135
Introduction 1
Introduction
This guide provides instructions for installing Microsoft® Business Solutions–Solomon in the following
environments:
• Microsoft® Windows® 2000 Professional Service Pack 4
• Microsoft® Windows® 2000 Server Service Pack 4
• Microsoft® Windows® XP Professional Service Pack 2
• Microsoft® Windows Server™ 2003 Service Pack 1
• Microsoft® SQL Server™ 2000 Standard Edition Service Pack 3a and Service Pack 4
• Microsoft® SQL Server™ 2005
The following sections are included:
• Installation Preparation — This section provides an overview of the installation and upgrade
processes and a Pre-Installation Checklist to help you address tasks you must perform before you
begin installation. This section also describes the options you will see in the Microsoft Solomon
Setup window.
• Security Planning — This section addresses security issues and recommendations for ways to
create a more secure environment.
• Guide for New Microsoft Solomon Installations — This section provides steps to help those who do
not currently have Microsoft Solomon installed.
• Updating an Existing Microsoft Solomon Installation — This section provides steps to help you
upgrade your present Microsoft Solomon installation to release 6.5.
• Troubleshooting — This section provides solutions, hints, and tips to help you resolve common
installation, setup, and maintenance issues.
• Appendices — This section provides additional information about optimizing Microsoft SQL Server
optimization and updating application databases with Microsoft Solomon schema information.
Audience
The Microsoft Business Solutions–Solomon Installation Guide is written for the novice as well as the
veteran software installer. It includes checklists and other aids to help make your installation a
successful experience.
2 Installation Guide
Installation Preparation
This section will help you prepare for your Microsoft Solomon installation. The section includes:
• Overview — Read this section for a brief summary of what will happen during and after your
installation.
• Pre-Installation Checklist — You must perform many of the tasks on this list before you begin your
installation.
• Microsoft Solomon Installation Setup Options — This section describes what you will see on the
Microsoft Business Solutions-Solomon installation setup screen.
Overview
Where possible, Microsoft Solomon Setup detects operating environment characteristics and installs
the components that are appropriate for that environment. Setup also prompts you to answer
necessary questions up front so that file copying can proceed efficiently.
Remember, Microsoft Solomon Setup complements, but does not replace, careful installation planning
and preparation.
Summary of Tasks for New and Existing Microsoft Solomon Installations

First-time installation Upgrading an existing installation
Complete the Pre-Installation Checklist and Complete the Pre-Installation Checklist and
perform all tasks unless they are listed as perform all tasks unless they are listed as
optional. optional.
Perform a system backup of the application Perform a system backup of the application
server. server.
Perform a system backup of the database If the Delta.mnu file has been customized, save
server. a copy in Solomon\Backup so that you can
restore it after the installation is complete.
Install Microsoft Solomon on the application Perform a database backup of the Microsoft
server. Solomon system and application databases.
If you do not have Microsoft SQL Server and Remove all existing Microsoft Solomon clients
appropriate service packs already installed, from client workstations.
install them on the database server.
Create databases. Remove the existing Microsoft Solomon
installation from the application server.
If you intend to implement Web-based sales Install Microsoft Solomon on the application
orders, install the Solomon Web Order Starter server.
Site.
Install supporting application Crystal Reports on Install the appropriate Microsoft SQL Server
the application server. service packs on the database server.
If you intend to use Microsoft® Office Project Update databases.
Connector for Solomon, install Project
Connector.
Install FRx Financial Reporter and FRx If you intend to implement Web-based sales
components on the application server using orders, install the Solomon Web Order Starter
your FRx 6.7 CD. Installation documentation is Site.
included on the CD. After you install FRx 6.7,
you must also install Service Pack 3. Download
Service Pack 3 for FRx 6.7 from
ftp://ftp.greatplains.com/dynamicsftp/FRx67/S
P3/FRxsp673073_Solomon.zip.
First-time installation Upgrading an existing installation

Set up Microsoft Solomon on client Unless you have Crystal Reports for Solomon
workstations. Version 10 already installed, remove the
previous version of Crystal Reports from the
server and workstations that will access
Microsoft Solomon.
Set up Crystal Reports 10 on the appropriate Unless you have Crystal Reports for Solomon
workstations. Version 10 already installed on the application
server, install it on the server.
Set up FRx Financial Reporter and FRx If you intend to use Microsoft® Office Project
components on the appropriate workstations Connector for Solomon, install Project
using your FRx 6.7 CD. See the installation Connector.
documentation on the CD. After you install FRx
6.7, you must also install Service Pack 3.
Download Service Pack 3 for FRx 6.7 from
Unless you have version FRx 6.7 SP3 already
installed on the application server, install FRx
Financial Reporter and FRx components on the
server using your FRx 6.7 CD. Installation
documentation is included on the CD. After you
install FRx 6.7, you must also install Service
Pack 3. Download Service Pack 3 for FRx 6.7
from
Set up Microsoft Solomon on client
workstations.
Unless you have Crystal Reports version 10
already installed on the appropriate
workstations, set up Crystal Reports 10 on
workstations.
Unless you already use Crystal Reports 10,
update customized Crystal Reports.
Unless you have version FRx 6.7 SP3 already
installed on the appropriate workstations, set
up FRx Financial Reporter and FRx components
on workstations using your FRx 6.7 CD. See the
installation documentation on the CD. After you
install FRx 6.7, you must also install Service
Pack 3. Download Service Pack 3 for FRx 6.7
from
Pre-Installation Checklist
The following checklist is provided to help you prepare for your Microsoft Solomon installation and to
give you a record to refer to during future upgrade installations.
Note: The input of other individuals during the installation process might be helpful and, in some
cases, necessary. For example, you might need to consult with your database administrator when
questions arise about how to store your Microsoft Solomon data. Be sure the resources you need are
available during pre-installation planning and during the installation or upgrade process.
If you plan to use Microsoft Office 2000, 2003, or XP and Microsoft Solomon on the same workstation,
install Office 2000 or 2003 first, followed by Microsoft Solomon.
Contact your authorized Microsoft Solomon partner or certified consultant well in advance of your
planned installation date to make sure that your operating system, database, and hardware
environment are appropriate for the Microsoft Solomon installation.
(Optional) On the line below, record the computer name(s) of the server(s) where you will create or
update the Microsoft Solomon application and databases. The applications and databases can be
installed on separate servers.
Application server name _____________________________________________
Database server name _____________________________________________
Where can I find the computer name?
1. Right-click My Computer on the desktop of the server where you will install Microsoft
Solomon.
2. Choose Properties from the shortcut menu.
3. The Full Computer Name is on the Network Identification (Windows 2000) or Computer Name
(Microsoft® Windows XP, Microsoft® Windows Server™ 2003) tab of System Properties.
Complete these steps on each server where you will install Microsoft Solomon.
(Optional) On the lines below, record the computer name(s) of the workstations where you will
install Microsoft Solomon. Attach a separate sheet of paper if necessary.
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
Locate your Microsoft Solomon Release 6.5 CDs.
How many CDs should I have and what do the CDs contain?
• Volume 1 contains the Microsoft Solomon system and application files, including Tools for
Visual Basic and Adobe® Acrobat® Reader®.
• Volume 2 contains Adobe® Acrobat® Reader®, Crystal Reports® for Solomon, Project
Connector components that are installed on the server running Microsoft Project Server and
workstations running Microsoft Project Professional 2002 or 2003, Solomon Web Order
Starter Site, Microsoft SQL Server 2000 Service Pack 4, Microsoft Office XP Smart Tag
Manager, and the Microsoft Solomon user guides.
On the line below, record the edition of Microsoft Solomon that you will install.
_____________________________________________
Which Microsoft Solomon edition?
During installation, you will receive a prompt to choose the Microsoft Solomon edition you plan to
install. When Choose Edition appears, select from these choices:
• Single-User Solomon Standard

• Multi-User Solomon Standard (3 to 10 users)
• Solomon Professional (3 to an unlimited number of users)
Verify the edition you are installing by checking the Registration Report provided to you by
Services Solutions. If necessary, confirm your edition with your authorized Microsoft Solomon
partner or certified consultant.
If you are installing Microsoft Solomon for multiple users over a network, identify the mapped
server share where you will install it. Verify that available disk space is adequate for your
installation. For additional help in determining configuration requirements, contact your
authorized Microsoft Solomon partner or certified consultant.
Review “Creating Databases” on page 40 to determine:
• Which databases will be created during this installation
• Their approximate sizes
• The server and path to the location where they will be stored
• Their names
• Their types
Record the information on the lines below. Consult your database administrator, your authorized
Microsoft Solomon partner, your certified consultant, or technical support if you need assistance.
Note: Your Microsoft Solomon installation must include at least one system database. You must
also decide whether you will create demo databases. Demo databases are useful for training and
testing unfamiliar areas of the software without affecting your live data.
Empty Databases
_________________________________________ System Application
_________________________________________ Server (include path)
Demo Databases — Demo companies are included with Microsoft Solomon. The databases that
contain these companies are:
• Solomon Professional application databases are DemoSolomonApp10 (companies 0010 and
0020) and DemoSolomonApp60 (companies 0060, 0070, and 0080). The demo system
database for both companies is DemoSolomonSystem.
• Solomon Standard application database is DemoStandardApp51 (company 0051). The
system database is DemoStandardSystem.
You should use these names for your demo databases if possible.
On the line below, record the Microsoft SQL Server version installed on the workstation or server
where you will create or update the Microsoft Solomon databases.
_____________________________________________
Which Microsoft SQL Server version do I have?
Microsoft Solomon release 6.5 supports Microsoft SQL Server 2000 Standard Edition with Service
Pack 3a and Service Pack 4, as well as SQL Server 2005. Service Pack 4 is included on the
Volume 2 CD (\MSSQL2000\ SQL2000-KB884525-SP4-x86-ENU.exe). Microsoft SQL Server must
be purchased separately. Contact your Microsoft Solomon partner.
If you already have Microsoft SQL Server installed, you can determine the SQL Server version by
using the OSQL or ISQL utility or the Query window in SQL Server Query Analyzer and type (or copy
and paste):
SELECT SERVERPROPERTY (‘productversion’), SERVERPROPERTY
(‘productlevel’)
The following table shows the relationship between product version the SQL Server release and
product level:
Product Version SQL Server 2000 Release and Product Level

8.00.194 Original SQL Server 2000
8.00.384 SQL Server 2000 SP1
8.00.534 SQL Server 2000 SP2
8.00.760 SQL Server 2000 SP3
8.00.818 SQL Server 2000 SP3a
8.00.2039 SQL Server 2000 SP4
For more information on determining your Microsoft SQL Server version, go to
http://support.microsoft.com/default.aspx?scid=kb;en-us;321185.
Warning: Microsoft has identified an issue with the final build of Microsoft SQL Server Service Pack 4
that relates to having Address Windowing Extensions (AWE) support enabled. This issue only affects
computers with more than two gigabytes (2 GB) of memory where AWE has been explicitly enabled.
Microsoft has issued an update to correct this problem. For more information about this service pack,
go to http://www.microsoft.com/sql/downloads/2000/sp4.asp. For more information about the
correction for the AWE issue, go to http://support.microsoft.com/default.aspx?kbid=899761.
If you will install Microsoft Solomon Web Order, review “Solomon Web Order Starter Site” on
page 50.
If you will install a Web Order Starter Site, verify that the Web server where you will install it meets
the following hardware and software minimum requirements. Remember, these are minimum
requirements. Actual needs will depend on your anticipated transaction processing load:
• 1.0 GHz or higher processor speed
• 256 MB of RAM (512+ MB recommended)
• 2 GB of available hard disk space (4 GB recommended)
• Microsoft Windows 2000 Server (with IIS 5.0 or higher)
Load or install all required and related software and hardware resources on the server and
workstations where you will install Microsoft Solomon. Make sure that all environment settings are
correct.
Determine whether you will install Microsoft Solomon Tools for Visual Basic.
How can I determine whether I should install Microsoft Solomon Tools for Visual
Basic?
See whether Tools for Visual Basic is included on the Registration Report provided by Services
Solutions. If necessary, confirm that you should install Tools for Visual Basic by contacting your
authorized Microsoft Solomon partner or certified consultant.
Perform a system backup on the server where you will install Microsoft Solomon. Contact your
system administrator if you need assistance.
Note: Be sure to create a backup of all custom Crystal Reports in your existing Microsoft Solomon
installation so that they can be restored after you install Microsoft Solomon. See “Updating
Custom Crystal Reports” on page 112 for more information.
You must log on as the local Administrator or as a member of the local Administrators group at the
server where you will install Microsoft Solomon. Failure to log on with Administrator privileges will
cause problems in the installation.
Note: If you use Active Directory, you must log on as a member of the Domain Administrators
group, which in turn needs to be part of the local Administrators group.
Performing full or client installations of Microsoft Solomon on Windows 2000 Server or Windows
Server 2003 requires Administrator rights because the installation process must update the
Windows registry. You might also need to reboot the server during or after installation.
On the server where you will install Microsoft Solomon, close all currently running programs and
stop SQL Server Services.
Because Microsoft Solomon Setup may need to update files used by other programs or services, it
is important to complete this step before starting Microsoft Solomon Setup.
How do I stop and restart SQL Server Services?

SQL Server 2000
Use the SQL Services Service Manager or the Services screen to stop and restart SQL Server
Services in Windows 2000, Windows XP, or Windows Server 2003.
> To stop services using Service Manager (recommended procedure):
1. Right-click the Service Manager icon in the notification area at the far right of the taskbar.
The Service Manager icon resembles a server with either a green triangle , which
indicates that the service is running, or a red square within a circle , which indicates
that the service is stopped.
2. Choose MSSQLServer | Stop. SQL Server Services stop. A message stating
SQLServerAgent will shut down might appear.
Figure 1: SQL Server Service Manager

3. Click Yes.
Note: If this message appears, remember to restart SQLServerAgent when restarting

MSSQLServer. If SQLServerAgent does not restart, any backups or other jobs scheduled
in Microsoft SQL Server will not run.
> To start services using Service Manager (recommended procedure):

When restarting SQL Server Services, repeat the procedure for stopping the service, except
choose MSSQLServer | Start. You can also start SQLServerAgent using the Service Manager
by right-clicking the icon in the taskbar and choosing Open SQL Server Service Manager. Click
the Services arrow, select SQL Server Agent, and click the green triangle. You can also use the
Services Administrative Tool to restart the SQLServerAgent service using the procedure below.
> To stop and start services using the MSSQLSERVER Properties dialog box:
1. Click the Start button, point to Settings, and then click Control Panel.
2. In the Control Panel, double-click Administrative Tools, and then double-click Services.
3. Scroll down until you see MSSQLSERVER, and then double-click to select it.
4. In the MSSQLSERVER Properties dialog box under Service Status, click the Stop button.
SQL Server Services stop.
5. A message stating SQLServerAgent will also shut down might appear. Click OK to stop the
SQLServerAgent.

MSSQLServer. If SQLServerAgent is not restarted, any backups or other jobs scheduled in
Microsoft SQL Server will not run.
6. When restarting SQL Server Services, select the service, then click the triangle on the
Services toolbar or choose Start from the Action menu. Remember to restart
SQLServerAgent (if needed) when restarting MSSQLServer.
SQL Server 2005

Use the SQL Server Configuration Manager or the Services screen to stop and restart SQL Server
Services in Windows 2000, Windows XP, or Windows Server 2003.
> To stop and start services using SQL Server Configuration Manager (recommended
procedure):
1. Click the Start button, and then point to Programs | Microsoft SQL Server 2005 |
Configuration Tools.
2. Click SQL Server Configuration Manager.
3. Click the SQL Server 2005 Services icon in the left pane under SQL Server Configuration
Manager.
4. Right-click the SQL Server (MSSQLSERVER) service listed in the right pane of the window.
5. Select Restart to stop and resume the SQL Server 2005 services.
> To stop and start services using the MSSQLSERVER Properties dialog box:
1. Click the Start button, point to Settings, and then click Control Panel.
2. In the Control Panel, double-click Administrative Tools, and then double-click Services.
3. Scroll down until you see SQL Server (MSSQLSERVER), and then double-click to select it.
4. Under Service Status, click the Stop button. SQL Server Services stop.
5. A message stating SQLServerAgent will also shut down might appear. Click OK to stop the
SQLServerAgent.

MSSQLServer. If SQLServerAgent does not restart, any backups or other jobs scheduled
in Microsoft SQL Server will not run.
6. When restarting SQL Server Services, select the service, then click the triangle on the
Services toolbar or choose Start from the Action menu. Remember to restart
SQLServerAgent (if needed) when restarting MSSQLServer.
If an earlier 32-bit release of Microsoft Solomon is installed (Release 4.x, 5.x or 6.x), you must
remove the earlier release from all workstations and from the server where it is installed before
starting this installation. If you do not remove the earlier release before beginning this installation,
Microsoft Solomon Setup will require that you do so and will initiate the removal before starting
the installation.
How do I remove an earlier release of Microsoft Solomon?
Be sure to perform a system backup before you follow these steps:
1. Select Start | Settings | Control Panel.
2. Choose Add/Remove Programs.
3. Select your current Microsoft Solomon release in the Install/Uninstall list. If you are
performing these steps at the server where the earlier release of Microsoft Solomon is
installed, you must remove all Microsoft Solomon Clients installed on workstations and on the
server first, before removing Microsoft Solomon (see “Removing an Existing Microsoft
Solomon Installation” on page 102 for more information).
4. Click Add/Remove.
Your Pre-Installation Checklist is now complete. Be sure to print it so you can refer to it during the
installation tasks.
Microsoft Solomon Installation Setup Options

The Microsoft Business Solutions-Solomon setup window displays at the start of the installation
process.
Figure 2: Microsoft Business Solutions-Solomon setup window

Microsoft Business Solutions–Solomon setup includes the following options:
• Solomon Installation Guide — Opens the Solomon Installation Guide in Adobe Acrobat Reader .pdf
file format. To install Adobe Acrobat Reader, select Adobe® Acrobat® Reader® before selecting
Solomon Installation Guide.
• Solomon including Tools for Visual Basic — Starts the Microsoft Solomon Setup process.
• Solomon Web Order Starter Site — If you are accessing the Microsoft Solomon Volume 1 CD when
you choose this option, you will be prompted to insert the Volume 2 CD into the CD drive. Insert
the Volume 2 CD and select Solomon Web Order Starter Site to start the Solomon Web Order
Starter Site setup.
• Crystal Reports® — If you are accessing the Microsoft Solomon Volume 1 CD when you choose this
option, you will be prompted to insert the Volume 2 CD into the CD drive. Insert the Volume 2 CD
and select Crystal Reports® to start Crystal Reports setup. Install Crystal Reports if you plan to
modify standard Microsoft Solomon reports or create custom reports.
• Microsoft® SQL Server™ — Prompts you to exit Microsoft Solomon Setup and insert the Microsoft
SQL Server installation CD into the CD drive.
• Microsoft Project Connector — If you have the Microsoft Solomon Volume 1 CD in the CD drive
when you choose this option and then choose a selection from the Project Connector components
list, you will be prompted to insert the Volume 2 CD into the CD drive. Insert the Volume 2 CD, and
select Microsoft Project Connector to start the setup for the Microsoft Office Project Connector for
Solomon.
• Microsoft® Office XP Smart Tag Manager — Installs Microsoft Office XP Smart Tag Manager to set
up and enable Microsoft Business Solutions Smart Tags.
If you are accessing the Microsoft Solomon Volume 1 CD when you choose this option, you will
receive a prompt to insert the Volume 2 CD into the CD drive. Insert the Volume 2 CD, and select
Microsoft Office XP Smart Tag Manager to start the Office XP Smart Tag Manager setup.
• FRx® — If you choose FRx®, you will receive a prompt to use your FRx CD to perform the
installation.
• Adobe® Acrobat® Reader® — Installs Adobe Acrobat Reader 5.0.5 on your computer.
• Browse CD — Opens Windows Explorer.
• Exit Installation — Quits Microsoft Solomon Setup.
If an earlier release of Microsoft Solomon is not installed on your workstations or server, proceed to
“Guide for New Microsoft Solomon Installations” on page 13.
If you are updating an earlier release of Microsoft Solomon, continue with “Updating an Existing
Microsoft Solomon Installation” on page 101.
Planning Security
This section includes:
• Microsoft Solomon Security Best Practices
• Application Server E-mail Security
• Physical Security
• For the Employees
• For the Administrator
• Securing the Server Operating System
• Virus Protection
• ISA Server 2004
• Network Security Strategies
• Security Update Management
• Additional SQL Server 2000 Security Settings
Microsoft® Windows®, the foundation of Microsoft Solomon, provides sophisticated standards-based
network security. In the broadest sense, security involves planning and considering trade-offs. For
example, a computer can be locked in a vault and only accessible to one system administrator. This
computer may be secure, but it is not very usable because you cannot connect it to any other
computer. You need to consider how to make the network as secure as possible without sacrificing
usability.
Most organizations plan for external attacks and construct firewalls, but many companies do not
consider how to mitigate a security breach once a malicious user gets inside the firewall. Security
measures in your client’s environment will work well if users are not required to perform too many
procedures and steps to conduct business in a secure manner. Implementing security policies should
be as easy as possible for users or they will tend to find less secure ways of doing things.
Since the size of Microsoft Solomon implementations can vary a great deal, it is important to carefully
consider the needs of a smaller client and to weigh the effectiveness of security against the costs that
may be involved. As your client’s trusted advisor, use your best judgment to recommend a policy that
helps to meet security needs without creating a burden that will ultimately cause the client to stop
enforcing the policy.
Microsoft Solomon Security Best Practices

In order to run a secure Microsoft Dynamics SL environment, you need to take steps to secure communications
between the Microsoft Dynamics SL client and Microsoft SQL Server.
If you are using Microsoft SQL Server 2000, we recommend that you use Secure Sockets Layer (SSL)
protocol certificates to secure the communication link between the Microsoft Dynamics SL client and
Microsoft SQL Server 2000. When you configure SQL Server for SSL, all of the data transmitted
between client and server (and vice versa) can be encrypted to ensure that data remains confidential
while in transit between the client and the SQL Server. If you currently do not use SSL certificates, you
can issue your own certificates using Microsoft Certificate Services, which is an optional component of
Microsoft Windows Server, or request or purchase certificates from a commercial certificate authority.
Microsoft SQL Server 2005 encrypts the pre-logon credential exchange by default but, to encrypt the
entire session of communication between SQL Server 2005 and Microsoft Dynamics SL, you will need
to follow the instructions in the Microsoft SQL Server 2005 Books Online manual.
For more information about securing your network, refer to the following Web sites:
Securing data access
http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/dnnetsec/html/SecNetch12.asp
Using SSL certificates to have all client/server based communication encrypted
http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/dnnetsec/html/secnetht19.asp
Using Microsoft SQL Server 2005
http://www.microsoft.com/sql/2005/default.mspx
By following some general rules in administration, you can help to increase the security of the
Microsoft Solomon environment:
• Assuming that system administrator has administrative privileges, employees do not need
administrative privileges over the domain. These user accounts should be restricted to Domain
Users.
• Assuming that the business owner or manager has administrative privileges, users, such as
accounts payable coordinators, cashiers, or sales representatives, do not need administrative
privileges over the domain. These user accounts should be restricted to Domain Users.
• Users must not be members of the Microsoft® Windows® Guests group. Guests group members
who connect to Microsoft Windows 2000 Server to execute Windows Terminal Server or to
Windows Server 2003 via Remote Desktop will not have access to Microsoft Solomon. They will
receive an abnormal program termination message, and Solomon will not load.
• Passwords should not be reused. It is often common practice to reuse passwords across systems
and domains. For example, an administrator responsible for two domains might create Domain
Administrator accounts in each that use the same password, and even set local administrator
passwords on domain computers that are the same across the domain. In such a case, a
compromise of a single account or computer can lead to a compromise of the entire domain.
• After installation is complete and the databases are created or updated to a newer Microsoft
Solomon version, you should consider changing the “master login” password. When changing the
Master login password, it must be accomplished through Database Administration (98.270.00).
This password should be kept confidential. It should warrant the same protection you give to the
Microsoft SQL Server™ sa password. All database access is funneled through the master login
and requires the highest level of protection. The “master login” password should only be known to
your system administrators.
• Domain Administrator accounts should not be used as service accounts. It is also common
practice to use Domain Administrator accounts as service accounts for common services such as
backup systems. However, this poses a security risk, because the password must be stored, or
cached, locally on every computer where the service resides. The password can easily be retrieved
by anyone with administrative rights over the computer. In such a case, the compromise of one
computer can lead to the compromise of the entire domain. Service accounts should never be
Domain Administrator accounts, and they should be limited in privilege as much as possible.
• Although Microsoft Solomon is supported on several operating systems, it is best to use the latest
operating systems with the most up-to-date security features. Also, operating system editions that
are for business purposes typically have more security features. For example, the Encrypting File
System (EFS), found in Windows® XP Professional but not in Windows XP Home Edition, allows
encrypting of files and folders for added security of sensitive data against theft or hackers.
Restricted File Access, also found only in Professional, allows restricting access to selected files,
applications, and other resources.
• Use the Windows Update tool provided with Windows 2000, Windows XP, and Windows Server™
2003 to apply the most current security updates. Use the Automatic Update feature of Windows to
keep your machines up to date. Sites with many computers can reduce IT costs and ensure
update compliance by using Microsoft Systems Management Server. For more information, go to
http://www.microsoft.com/smserver/default.mspx.
• For security surrounding the Microsoft Solomon executable files, Microsoft suggests following the
principle of least privilege: give users only the minimum privileges required to access data and
functionality.
Examples of files that should be considered for this level of security are:
– General Ledger Consolidation files
– Payroll ACH files and scripts
– Payroll Tax tables
– Transaction Import files, Control macros, data files, and log files
– EDI Transaction files
– Microsoft Solomon Event logs
– Microsoft Solomon executables
– Microsoft Solomon Standard reports
– Microsoft Solomon User reports\SDG\Receive directories
• When using the Access Rights screen, assign rights to Microsoft Solomon Groups, then add users
to the groups. This will help in maintaining the rights of your Microsoft Solomon users.
• A recommended practice is to have users log on to Microsoft Solomon using an integrated logon.
For more information, refer to “Adding Users” in the Microsoft Business Solutions–Solomon
System Manager Release 6.5 user guide (SAF_SM.pdf), which is located in the User Manuals
folder of your Solomon installation and on the Volume 2 CD. A key benefit of using integrated
logons is the ability to use the security features of your Windows server environment to enforce
strong password and password expiration policies with minimal intervention by administrators.
• If you choose not to use the integrated logon for authenticating users, be sure to use a strong
password methodology for Microsoft Solomon user passwords. Although Microsoft Solomon does
not enforce passwords that expire, you should implement a manual process that requires your
employees to change their Microsoft Solomon password at random intervals.
• If you use the Microsoft Office Project Connector for Solomon, the ...\Solomon\PA\MSPXML folder
temporarily stores Solomon SOAP requests to Microsoft Project Server that were rejected for
various reasons (for example, the project is checked out or Microsoft Project Server is temporarily
offline). By default, the MSPXML folder grants full access to all users who have access to the
Solomon directory (typically, all Solomon users), potentially allowing those users to view and alter
the data in the XML documents. To prevent this, grant Read, Write, and Delete permissions only to
the users who have rights to the Resubmit Batches (PA.MSS.00) utility, which is accessed from
the Microsoft Project Connector Setup (PA.MSP.00) screen. Grant only Write permission for the
folder to all other Solomon users.
• If you have installed, or plan to install, the Smart Tag Manager feature, you should review the
security model it employs in the “Administration Setup” section of the Microsoft Business
Solutions–Solomon Office XP Smart Tag Manager Release 6.5 guide
(SolomonSmartTagManager.pdf), and follow its recommendations as well. The security for that
feature is based on Windows NT® Authentication.
• If you have installed, or plan to install, the Web Order feature, you should review the security
model it employs, and follow its recommendations as well. For more information, see the
Microsoft Business Solutions–Solomon Release 6.5 Web Order user guide (\User
Manuals\Program Files\Solomon\SIV_WC.pdf on the Microsoft Solomon Volume 2 CD).
• The Application Server feature has a sub-feature where it can process requests based on e-mails
from your remote employees. This feature could be exploited by hackers if they chose to send a
destructive request via Application Server. Microsoft recommends that you:
– Create a specific exchange account for the application server to read from.
– Make a list of employees you will allow to use this feature and only allow e-mail from those
individuals to be processed by the Application Server’s e-mail account. When setting up these
users within Solomon make sure to include their unique email address in the EMail Address
field and check the Active Application Server User checkbox. Application Server will only
accept emails from these specific accounts.
• Be more restrictive on access rights for the following features. These are features that should be
used by trusted employees and administrators.
– DB Update (DB.UPD.ATE)
– Customization Manager Menu Items
– Application Server (96.010.00)
– Access Rights Maintenance (95.270.00)
– Access Rights(95.600.00) report
– Database Administration (98.270.00)
– Database Physical Integrity (95.500.00)
– Possible Values Import (PV.REC.00)
– Report Control Maintenance (98.280.00)
– User Maintenance (95.260.00)
– Group Maintenance (95.280.00)
– Crystal Reports Designer
– Payroll module
– Password Maintenance (PA.PSD.00) if you use Project Management and Accounting
– Web Order module
Physical Security
Physical security represents the best place to start preventing malicious attacks. For example, if a
hard disk drive is stolen, eventually the data on that drive will be stolen as well. Discuss the following
physical security issues when developing a policy with your client:
• For larger deployments with dedicated IT departments, ensure server rooms and places where
software and manuals are stored are locked.
• Machines in the category would include:
– The Microsoft SQL Server database server
– The file server where the Microsoft Solomon executables reside
– The file server used as the Application Server
– The IIS server for Web Order
– The IIS server for Business Portal
– The Microsoft Project Server
• Keep unauthorized users away from the power and reset switches on the server(s).
• Consider removing the floppy disk drive from client workstations.
• Ensure burglar alarms are installed, regardless of how sensitive the data is.
• Ensure backups of critical data are stored offsite and that software is stored in fireproof
containers when not in use.
• If possible, deploy Microsoft Solomon through a Terminal Services implementation. Install
Microsoft Solomon onto a Terminal Server and have the client log in to the server to access
Microsoft Solomon. With this implementation, the Microsoft Solomon files are installed only on
one machine, thus limiting the ability for attackers to attack the Microsoft Solomon Binaries, and
you only have to maintain security on one computer.
For the Employees

It is a good idea to limit administrative rights across all products and features. As a default, clients
should give employees read-only access to system functions, unless they require greater access to
perform their jobs. Microsoft suggests following the principle of least privilege: give users only the
minimum privileges required to access data and functionality. For example, avoid requiring
administrative rights as a default to run features.
Disgruntled and former employees are a threat to network security. When speaking with your clients
regarding security, approach them with the following policy regarding employees:
• Conduct pre-employment background investigations.
• Expect “revenge” from disgruntled employees and former employees.
• Make sure clients deactivate all associated Windows accounts and passwords when an employee
leaves. For reporting purposes, do not delete users.
• Train users to be alert and to report suspicious activity.
• Do not grant privileges automatically. If users do not need access to particular computers,
computer rooms, or sets of files, ensure that they do not have access.
• Train supervisors to identify and respond to potential employee problems.
• Monitor system usage for unusual activity.
• Make sure that employees understand their roles in maintaining network security.
• Give a copy of the company policies to every employee.
• Do not allow users to install their own software.
For the Administrator

We highly recommend that your clients’ system administrators keep up with the latest security fixes
available from Microsoft. Hackers are very adept at combining small bugs to enable large intrusions
into a network. Administrators should first ensure that each individual computer is as secure as
possible, and then add security updates. To that end, many links and resources are provided
throughout this guide to help in finding valuable information and best practices.
Complexity comprises another tradeoff for securing your network. The more complex the network, the
more difficult it will be to secure or fix it once an intruder has successfully gained access. The
administrator should document the network topography thoroughly, with a goal toward keeping it as
simple as possible.
Security is primarily concerned with risk management. Because technology is not a cure-all, security
requires a combination of technology and policy. That is, there will never be a product that you can
simply unpack and install on the network, instantly achieving perfect security. Instead, security is a
result of both technology and policy — that is, it is how the technology is used that ultimately
determines the security level of a network. Microsoft delivers security-conscious technology and
features, but only the administrator and the management, with your guidance, can determine the right
policies for each organization. Be sure to plan for security early in the implementation and deployment
process. Understand what your client wants to protect and what they are willing to do to protect it.
Finally, develop contingency plans for emergencies before they happen. Couple thorough planning
with solid technology and your client will have great security. For more information about general
security, see “The Ten Immutable Laws of Security Administration,” located at
http://www.microsoft.com/technet/archive/community/columns/security/essays/10salaws.mspx.
Securing the Server Operating System

Although you may find many smaller clients do not have a server operating system, it is important that
you understand and can communicate security best practices to larger clients with more complex
network environments. Also, be aware that many of the policies and practices throughout this section
can easily be applied to those clients with only client operating systems.
The concepts in this section apply to both the Microsoft Windows 2000 Server and Microsoft Windows
Server 2003 products, although this information has been extracted mainly from Windows Server
2003 Online Help. Windows Server 2003 offers a robust set of security features. Windows Server
2003 Online Help contains complete information about all security features and procedures.
For additional information for Windows 2000 Server, visit the Windows 2000 Server Security Center,
located at http://www.microsoft.com/technet/security/prodtech/win2000/default.mspx.
For Windows Server 2003, Microsoft has published the Windows Server 2003 Security Guide, located
at http://www.microsoft.com/technet/security/prodtech/win2003/w2003hg/sgch00.mspx
The primary features of the Windows server security model that are of the most concern are
authentication, access control, and single sign-on:
• Authentication represents the process by which the system validates a user’s identity through
their logon credentials. A user’s name and password are compared with an authorized list. If the
system detects a match, access is granted to the extent specified in the permissions list for that
user.
• Access control limits user access to information or computing resources based on the users’
identity and their membership in various predefined groups. Access control is typically used by
system administrators for controlling user access to network resources such as servers,
directories, and files and is typically implemented by granting permissions to users and groups for
access to specific objects.
• Single sign-on allows a user to log on to the Windows domain once, using a single password, and
authenticate to any computer in the Windows domain. Single sign-on enables administrators to
implement secure password authentication across the Windows network, while providing end
users with ease of access.
The following sections provide a more detailed description of these three key features for securing
your environment.
Authentication
Authentication is a fundamental aspect of system security. It confirms the identity of any user trying to
log on to a domain or access network resources. The weak link in any authentication system is the
user’s password.
Passwords provide the first line of defense against unauthorized access to the domain and local
computers. Suggest the following password best practices where appropriate for the client’s
organization.
Password Protection
• Always require strong passwords. For more information, see “Strong Passwords” below.
• If passwords must be written down on a piece of paper, store the paper in a secure place and
destroy it when it is no longer needed.
• Never share passwords with anyone.
• Use different passwords for all user accounts.
• Change passwords immediately if they have been compromised.
• Be careful about where passwords are saved on computers. Some dialog boxes, such as those for
remote access and other telephone connections, present an option to save or remember a
password. Selecting this option poses a potential security threat because the password is stored
in the system registry.
Strong Passwords
The role that passwords play in securing an organization’s network is often underestimated and
overlooked. As mentioned, passwords provide the first line of defense against unauthorized access to
your organization. The Windows Server 2003 family has a new feature that checks the complexity of
the password for the Administrator account during the setup of the operating system. If the password
is blank or does not meet complexity requirements, the Windows Setup dialog box appears warning of
the dangers of not using a strong password for the Administrator account. In a workgroup
environment, a user will not be able to access a computer over the network using an account with a
blank password. Weak passwords provide attackers with easy access to computers and the network,
while strong passwords are considerably harder to crack, even with the password-cracking software
that is available today.
Password-cracking tools continue to improve, and the computers used to crack passwords are more
powerful than ever. Password-cracking software uses one of three approaches: intelligent guessing,
dictionary attacks, and brute-force automated attacks that try every possible combination of
characters. Given enough time, the automated method can crack any password. However, strong
passwords are much harder to crack than weak passwords. A secure computer has strong passwords
for all user accounts.
A weak password:
• Is no password at all.
• Contains the user’s user name, real name, or company name.
• Contains a complete dictionary word. For example, the word Password is a weak password.
A strong password:
• Is at least seven characters long.
• Does not contain the user’s user name, real name, or company name.
• Does not contain a complete dictionary word.
• Is significantly different from previous passwords. Passwords that increment (Password1,
Password2, Password3 ...) are not strong.
• Contains characters from each of the four groups listed in the following table.
Group Examples
Uppercase letters ABCD
Lowercase letters abcd
Numerals 01234
Symbols `~!@#$%^&*()_+- {}|[]\:“‘<>?,./
Examples of strong passwords are Pa$sw0rD and J*p2leO4>F.
A password can meet most of the criteria of a strong password but still be rather weak. For example,
Hello2U! is a relatively weak password even though it meets most of the criteria for a strong password
and also meets the complexity requirements of password policy. H!elZl2o is a strong password
because the dictionary word is interspersed with symbols, numbers, and other letters. It is important
to educate clients, managers, and their users about the benefits of using strong passwords and to
teach them how to create passwords that are actually strong.
Passwords can be created containing characters from the extended ASCII character set. Using
extended ASCII characters increases the number of characters users can choose when they create a
password. As a result, it might take more time for password-cracking software to crack passwords that
contain these extended ASCII characters than it does to crack other passwords. Before using extended
ASCII characters in your password, test them thoroughly to make sure that passwords containing
extended ASCII characters are compatible with other applications that the organization uses. Be
especially cautious about using extended ASCII characters in passwords if the organization uses
several different operating systems.
You can find extended ASCII characters in the Character Map. Some extended ASCII characters should
not be used in passwords. Do not use a character if a keystroke is not defined for it in the lower-right
corner of the Character Map dialog box. For more information about how to use Character Map, see
Windows Server Online Help.
Examples of passwords that contain characters from the extended ASCII character set are kUµ!¶0o
and Wf©$0k#»g¤5ªrd.
The client can implement a password policy that enforces password complexity requirements. For
more information about this policy, see “Password Must Meet Complexity Requirements” on the
Microsoft Windows Server 2003 TechCenter Web site.
Defining the Password Policy
When helping your client define the password policy, be sure to create a policy that will require all user
accounts to have strong passwords. The following Windows Server settings require strong passwords.
• Define the Enforce password history policy setting so that several previous passwords are
remembered. With this policy setting, users cannot use the same password when their password
expires.
• Define the Maximum password age policy setting so that passwords expire as often as necessary
for the client’s environment, typically, every 30 to 90 days.
• Define the Minimum password age policy setting so that passwords cannot be changed until they
are more than a certain number of days old. This policy setting works in combination with the
Enforce password history policy setting. If a minimum password age is defined, users cannot
repeatedly change their passwords to get around the Enforce password history policy setting and
then use their original passwords. Users must wait the specified number of days to change their
passwords.
• Define a Minimum password length policy setting so that passwords must consist of at least a
specified number of characters. Long passwords — seven or more characters — are usually
stronger than short ones. With this policy setting, users cannot use blank passwords and they
need to create passwords that are at least a certain number of characters long.
• Enable the Password must meet complexity requirements policy setting. This policy setting checks
all new passwords to ensure that they meet basic strong password requirements. For a full list of
these requirements, see “Password Must Meet Complexity Requirements” in Windows Server
Online Help.
Defining an Account Lockout Policy
Be cautious when defining the account lockout policy. The account lockout policy should not be set
haphazardly. Although the probability of thwarting an unauthorized attack on your client’s organization
is increased with account lockout policy, it is possible also to lock out authorized users unintentionally,
which can be very costly for your client.
If the client decides to apply the account lockout policy, set the Account lockout threshold policy
setting to a high enough number that authorized users are not locked out of their user accounts
simply because they mistype a password.
Authorized users can be locked out if they change their passwords on one computer, but not on
another computer. The computer that is still using the old password will continuously attempt to
authenticate the user with the old password, and it will eventually lock out the user account. This
might be a costly consequence of defining an account lockout policy, because the authorized users
cannot access network resources until their accounts are restored. This issue does not exist for
organizations that use only domain controllers that are members of the Windows Server family.
For more information about account lockout policy, see “Account Lockout Policy Overview” in Windows
Server Online Help. For information about how to apply or modify account lockout policy, see “To Apply
or Modify Account Lockout Policy,” also in Windows Server Online Help.
Access Control
A Windows network and its resources (including Microsoft Solomon files) can be secured by
considering what rights users, groups of users, and other computers have on the network. You can
secure a computer or multiple computers by granting users or groups specific user rights. You can
secure an object, such as a file or folder, through assigning permissions to allow users or groups to
perform specific actions on that object. Key concepts that make up access control include:
• Permissions
• Ownership of objects
• Inheritance of permissions
• User rights
• Object auditing
Permissions
Permissions define the type of access granted to a user or group for an object or object property such
as files, folders, and registry objects. Permissions are applied to any secured objects such as files or
registry objects. Permissions can be granted to any user, group, or computer. It is a good practice to
assign permissions to groups.
Ownership of Objects
An owner is assigned to an object when that object is created. By default in Windows 2000 Server, the
owner is the creator of the object. This has changed in Windows Server 2003 for objects created by
members of the Administrators group.
When a member of the Administrators group creates an object in Windows Server 2003, the
Administrators group becomes the owner, rather than the individual account that created the object.
This behavior can be changed through the Local Security Settings Microsoft Management Console
(MMC) snap-in, using the setting System objects: Default owner for objects created by members of the
Administrators group. No matter what permissions are set on an object, the owner of the object can
always change the permissions on an object. For more information, see “Ownership” in Windows
Server Online Help.
Inheritance of Permissions
Inheritance allows administrators to assign and manage permissions easily. This feature automatically
causes objects within a container to inherit all the inheritable permissions of that container. For
example, the files within a folder, when created, inherit the permissions of the folder. Only permissions
marked to be inherited will be inherited.
User Rights
User rights grant specific privileges and logon rights to users and groups in your computing
environment. For information about user rights, see “User Rights” in Windows Server Online Help.
Object Auditing
You can audit users’ access to objects. You can then view these security-related events in the security
log using the Event Viewer. For more information, see “Auditing” in Windows Server Online Help.
Access Control Best Practices

• Assign permissions to groups rather than to users. Because it is inefficient to maintain user
accounts directly, assigning permissions on a user basis should be the exception.
• Use Deny permissions for certain special cases. For instance, you can use Deny permissions to
exclude a subset of a group which has Allow permissions. Use Deny permissions to exclude one
special permission when you have already granted full control to a user or group.
• Never deny the Everyone group access to an object. If you deny the Everyone group permission to
an object, that group includes administrators. A better solution would be to remove the Everyone
group, as long as you give other users, groups, or computers permissions to that object.
• Assign permissions to an object as high on the tree as possible and then apply inheritance to
propagate the security settings through the tree. You can quickly and effectively apply access
control settings to all children or a subtree of a parent object. By doing this, you gain the greatest
breadth of effect with the least effort. The permission settings you establish should be adequate
for the majority of users, groups, and computers.
• Explicit permissions can sometimes override inherited permissions. Inherited Deny permissions do
not prevent access to an object if the object has an explicit Allow permission entry. Explicit
permissions take precedence over inherited permissions, even inherited Deny permissions.
• For permissions on Active Directory® objects, make sure you understand the best practices
specific to Active Directory objects. For more information, see “Best Practices for Assigning
Permissions on Active Directory Objects” in Windows Server 2003 Online Help.
Single Sign-on
A key feature of Windows Server family authentication is its support of single sign-on. Single sign-on
allows a user to log on to the Windows domain once, using a single password, and authenticate to any
computer in the Windows domain without having to reenter that password.
Single sign-on provides two main security benefits for:
• A user, the use of a single password or smart card reduces confusion and improves work
efficiency.
• Administrators, the amount of administrative support required for domain users is reduced,
because the administrator needs to manage only one account per user.
Authentication, including single sign-on, is implemented as a two-part process: interactive logon and
network authentication. Successful user authentication depends on both of these processes. For more
information about how to configure the Windows single sign-on feature, see Windows Server Online
Help.
External Security Firewall

A firewall is a piece of hardware or software that prevents data packets from either entering or leaving
a specified network. To control the flow of traffic, numbered ports in the firewall are either opened or
closed to information packets. The firewall looks at several pieces of information in each arriving or
departing packet: the protocol through which the packet is being delivered, the destination or sender
of the packet, the type of content that is contained in the packet, and the port number to which it is
being sent. If the firewall is configured to accept the specified protocol through the targeted port, the
packet is allowed through. Microsoft Windows Small Business Server 2003 Premium Edition ships
with Microsoft Internet Security and Acceleration (ISA) Server 2004 as its firewall solution.
Virus Protection
A computer virus is an executable file that is designed to replicate itself, erase or corrupt data files
and programs, and avoid detection. In fact, viruses are often rewritten and adjusted so that they
cannot be detected. Viruses are often sent as e-mail attachments. Antivirus programs must be
updated continuously to look for new and modified viruses. Viruses are the number one method of
computer vandalism.
Antivirus software is specifically designed for the detection and prevention of virus programs. Because
new virus programs are created all the time, many makers of antivirus products offer periodic updates
of their software to customers. Microsoft strongly recommends implementing antivirus software in
your client’s environment.
Virus software is usually installed at each of these three places: user workstations, servers, and the
network where e-mail comes into (and in some cases, leaves) the organization.
Types of Viruses
There are three main types of viruses that infect computer systems: boot-sector viruses, file-infecting
viruses, and Trojan horse programs.
Boot-Sector Viruses
When a computer starts, it scans the boot sector of the hard disk before loading the operating system
or any other startup files. A boot-sector virus is designed to replace the information in the hard disk’s
boot sectors with its own code. When a computer is infected with a boot-sector virus, the virus’ code is
read into memory before anything else. After the virus is in memory, it can replicate itself onto any
other disks that are in use in the infected computer.
File-Infecting Viruses
The most common type of virus, a file-infecting virus, attaches itself to an executable program file by
adding its own code to the executable file. The virus code is usually added in such a way that it
escapes detection. When the infected file is run, the virus can attach itself to other executable files.
Files infected by this type of virus usually have a .com, .exe, or .sys file name extension.
Some file-infecting viruses are designed for specific programs. Program types that are often targeted
are overlay (.ovl) files and dynamic-link library (.dll) files. Although these files are not run, executable
files call them. The virus is transmitted when the call is made.
Damage to data occurs when the virus is triggered. A virus can be triggered when an infected file is run
or when a particular environment setting is met (such as a specific system date).
Trojan Horse Programs
A Trojan horse program is not really a virus. The key distinction between a virus and a Trojan horse
program is that a Trojan horse program does not replicate itself; it only destroys information on the
hard disk. A Trojan horse program disguises itself as a legitimate program, such as a game or utility.
When it’s run, though, it can destroy or scramble data.
Virus Prevention Best Practices

The spread of a computer virus can be prevented. Here are some tips to avoid infection that you
should share with your clients:
• Install a virus protection solution that scans incoming messages from the Internet for viruses
before the messages pass the router. This will ensure that e-mails are scanned for known viruses.
• Know the source of the documents that are received. Documents should not be opened unless
they are from someone the client feels is trustworthy.
• Talk to the person who created the document. If the users are at all unsure whether the document
is safe, they should contact the person who created the document.
• Use the Microsoft Office macro virus protection. In Office, the applications alert the user if a
document contains macros. This feature allows the user to either enable or disable the macros as
the document is opened.
• Use virus-scanning software to detect and remove macro viruses. Virus-scanning software can
detect and often remove macro viruses from documents. Microsoft recommends the use of
antivirus software that is certified by the International Computer Security Association (ICSA).
For more information about viruses and computer security in general, go to the following Microsoft
Security Web sites:
• Microsoft Trustworthy Computing: Security (http://www.microsoft.com/security/default.asp)

• Security documentation on Microsoft TechNet (http://www.microsoft.com/technet
/security/Default.mspx)
ISA Server 2004

Internet Security and Acceleration (ISA) Server 2004 securely routes requests and responses between
the Internet and client computers on the internal network.
ISA Server acts as the secure gateway to the Internet for clients on the local network. The ISA Server
computer is transparent to the other parties in the communication path. The Internet user should not
be able to tell that a firewall server is present, unless the user attempts to access a service or go to a
site where the ISA Server computer denies access. The Internet server that is being accessed
interprets the requests from the ISA Server computer as if the requests originated from the client
application.
When you choose Internet Protocol (IP) fragment filtering, you enable the Web Proxy and Firewall
services to filter packet fragments. By filtering packet fragments, all fragmented IP packets are
dropped. A well-known “attack” involves sending fragmented packets and then reassembling them in
such a way that may cause harm to the system.
ISA Server features an intrusion detection mechanism, which identifies the time when an attack is
attempted against a network and performs a set of configured actions (or alerts) in case of an attack.
If Internet Information Services (IIS) is installed on the ISA Server computer, you must configure it to
not use the ports that ISA Server uses for outgoing Web requests (by default, 8080) and for incoming
Web requests (by default, 80). For example, you can change IIS to monitor port 81, and then configure
the ISA Server computer to direct the incoming Web requests to port 81 on the local computer running
IIS.
If there is a conflict between ports that ISA Server and IIS use, the setup program stops the IIS
publishing service. You can then change IIS to monitor a different port and restart the IIS publishing
service.
ISA Server Policies

You can define an ISA Server policy that dictates inbound and outbound access. Site and content rules
specify which sites and content can be accessed. Protocol rules indicate whether a particular protocol
is accessible for inbound and outbound communication.
You can create site and content rules, protocol rules, Web publishing rules, and IP packet filters.
These policies determine how the ISA Server clients communicate with the Internet and what
communication is permitted.
Network Security Strategies

Because the design and deployment of an IP Internetworking environment requires balancing private
and public network concerns, the firewall has become a key ingredient in safeguarding network
integrity. A firewall is not a single component. The National Computer Security Association (NCSA)
defines a firewall as “a system or combination of systems that enforces a boundary between two or
more networks.” Although different terms are used, that boundary is frequently known as a perimeter
network. The perimeter network protects your intranet or enterprise local area network (LAN) from
intrusion by controlling access from the Internet or other large networks.
The following illustration shows a perimeter network bounded by firewalls and placed between a
private network and the Internet in order to secure the private network.
Figure 3: Basic Perimeter Network

Organizations vary in their approach to using firewalls for providing security. IP packet filtering offers
weak security, is cumbersome to manage, and is easily defeated. Application gateways are more
secure than packet filters and easier to manage because they pertain only to a few specific
applications, such as a particular e-mail system. Circuit gateways are most effective when the user of
a network application is of greater concern than the data being passed by that application. The proxy
server is a comprehensive security tool that includes an application gateway, safe access for
anonymous users, and other services. Here is some information about these different options:
• IP Packet Filtering. IP packet filtering was the earliest implementation of firewall technology.
Packet headers are examined for source and destination addresses, Transmission Control
Protocol (TCP), and User Datagram Protocol (UDP) port numbers, and other information. Packet
filtering is a limited technology that works best in clear security environments where, for example,
everything outside the perimeter network is not trusted and everything inside is. In recent years,
various vendors have improved on the packet filtering method by adding intelligent decision-
making features to the packet-filtering core, thus creating a new form of packet filtering called
stateful protocol inspection. You can configure packet filtering to either (1) accept specific types of
packets and deny all others or (2) deny specific types of packets and accept all others.
• Application Gateways. Application gateways are used when the actual content of an application is
of greatest concern. That they are application-specific is both their strength and their limitation,
because they do not adapt easily to changes in technology.
• Circuit Gateways. Circuit gateways are tunnels built through a firewall connecting specific
processes or systems on one side with specific processes or systems on the other. Circuit
gateways are best employed in situations where the person using an application is potentially a
greater risk than the information carried by the application. The circuit gateway differs from a
packet filter in its ability to connect to an out-of-band application scheme that can add additional
information.
• Proxy Servers. Proxy servers are comprehensive security tools, which include firewall and
application gateway functionality, that manage Internet traffic to and from a LAN. Proxy servers
also provide document caching and access control. A proxy server can improve performance by
caching and directly supplying frequently requested data, such as a popular Web page. A proxy
server can also filter and discard requests that the owner does not consider appropriate, such as
requests for unauthorized access to proprietary files.
Be sure the client takes advantage of those firewall security features that can help them. Position a
perimeter network in the network topography at a point where all traffic from outside the corporate
network must pass through the perimeter maintained by the external firewall. You can fine-tune
access control for the firewall to meet the client’s needs and can configure firewalls to report all
attempts at unauthorized access.
To minimize the number of ports that you need to open on the inner firewall, you can use an
application layer firewall, such as ISA Server 2004.
For more information about TCP/IP, see “Designing a TCP/IP Network,” located at
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-
us/dnsbb_tcp_overview.asp.
Wireless Networks
By default, wireless networks are typically configured in a manner that allows eavesdropping on the
wireless signals. They can be vulnerable to a malicious outsider gaining access because of the default
settings on some wireless hardware, the accessibility that wireless networks offer, and present
encryption methods. There are configuration options and tools that can protect against eavesdropping
but keep in mind that they do nothing to protect the computers from hackers and viruses that enter
through the Internet connection. Therefore, it is extremely important to include a firewall to protect the
computers from unwanted intruders on the Internet.
For more information about protecting a wireless network, see “How to Make Your 802.11b Wireless
Home Network More Secure,” located at http://support.microsoft.com/default.aspx?scid=kb;en-
us;309369.
Note: Microsoft Solomon is currently not supported in a wireless environment.
Network Security Scenarios

The level of network security that the client’s organization requires will depend on several factors. It
usually comes down to a compromise between budget and the need to keep the corporate data safe.
It is possible for a small company to provide a very complex security structure that will provide the
highest level of network security possible, but a small company may not be able to afford that level of
security. In this section, we will look at four scenarios and make recommendations in each that will
provide varying levels of security at a relative cost.
No Firewall
If your client has a connection to the Internet but no firewall, some measure of network security needs
to be implemented. There are simple network firewall appliances, as described in the next section,
that provide enough security to deter most would-be hackers.
One Simple Firewall
The minimum level of security recommended is a single firewall between the Internet and your client’s
data. This firewall may not provide any level of advanced security and should not be considered very
secure. But it is better than nothing.
Figure 4: Simple Firewall

Hopefully, the client’s budget will allow for a more secure solution that will protect their corporate
data. One such solution is ISA Server. The increased cost of this additional server provides a great deal
more security than your average consumer firewall, since they typically only provide network address
translation (NAT) and packet filtering.
Figure 5: ISA Server Firewall

An ISA Server single firewall solution is more secure than an entry-level firewall appliance and provides
Windows-specific security services.
One Existing Firewall
If the client has an existing firewall that separates their intranet from the Internet, you may want to
consider an additional firewall that provides multiple ways to configure internal resources to the
Internet.
One such method is Web publishing. This is when an ISA Server is deployed in front of an
organization’s Web server that is providing access to Internet users. With incoming Web requests, ISA
Server can impersonate a Web server to the outside world, fulfilling client requests for Web content
from its cache. ISA Server forwards requests to the Web server only when the requests cannot be
served from its cache.
Another method is server publishing. ISA Server allows publishing internal servers to the Internet
without compromising the security of the internal network. You can configure Web publishing and
server publishing rules that determine which requests should be sent to a server on the local network,
providing an increased layer of security for the internal servers.
Figure 6: Existing Firewall with ISA Server Added
Two Existing Firewalls

The fourth scenario is where the organization has two firewalls in place with an established perimeter
network (DMZ). One or more of these servers is providing reverse proxy services so that Internet
clients are not accessing servers on the intranet directly. Instead, one of the firewalls, ideally the
internal firewall, is intercepting network requests for internal servers, inspecting those packets, and
then forwarding them on behalf of the Internet host.
Figure 7: Two Existing Firewalls

This scenario is similar to the preceding scenario after the second firewall is added. The only
difference is that the internal firewall that supports reverse proxy is not an ISA Server. In this scenario,
you should work closely with the managers of each firewall to define server publishing rules that
adhere to the security policy.
Security Update Management

Operating systems and applications are often immensely complex. They can consist of millions of lines
of code, written by many different programmers. It is essential that the software works reliably and
does not compromise the security or stability of the IT environment. To minimize any problems,
programs are tested thoroughly before release. However, attackers continually strive to find
weaknesses in software, so anticipating all future attacks is not possible.
For many organizations, update management will form a part of their overall change and configuration
management strategy. However, whatever the nature and size of the organization, it is vital to have a
good update management strategy, even if the organization does not yet have effective change and
configuration management in place. The vast majority of successful attacks against computer systems
occur to those systems where security updates have not been installed.
Security updates present a specific challenge to most organizations. Once a weakness has been
exposed in software, attackers will generally spread information about it quickly throughout the hacker
community. When a weakness occurs in its software, Microsoft will strive to release a security update
as soon as possible. Until the update is deployed, the security the client depends upon and expects
may be severely diminished.
In the Microsoft Solomon environment, you will need to ensure that your clients have the most recent
security updates throughout their system. To ease this task, you should work with the client to
consider using the technologies that Microsoft has made available. These include:
• Microsoft Security Notification Service. The Security Notification Service is an e-mail list that
distributes notices whenever an update becomes available. These notices serve as a valuable
piece of a proactive security strategy. They are also available at the Microsoft TechNet Microsoft
Security Notification Service Web site:
http://www.microsoft.com/technet/security/bulletin/notify.mspx.
• Microsoft Automatic updates. Windows can automatically apply security updates to your
machines.
• Microsoft Security Bulletin Search. The Security Bulletin search tool is available at the HotFix &
Security Bulletin Service Web site at http://www.microsoft.com/technet/security/current.aspx.
The client can determine which updates they need based on the operating system, applications,
and service packs they are currently running.
• Microsoft Baseline Security Analyzer (MBSA). This graphical tool is available at the Microsoft
Baseline Security Analyzer Web site:
http://www.microsoft.com/technet/security/tools/mbsahome.mspx. This tool works by comparing
the current status of a computer against a list of updates maintained by Microsoft. MBSA also
performs some basic security checks for password strength and expiration settings, guest account
policies, and a number of other areas. MBSA also will look for vulnerabilities in Microsoft Internet
Information Services (IIS), SQL Server™ 2000, Exchange 5.5, Exchange 2000, and Exchange
Server 2003.
• Microsoft Software Update Services (SUS). Formerly known as Windows Update Corporate Edition,
this tool enables enterprises to host on local computers all critical updates and security rollup
packages (SRPs) available on the public Windows Update site. This tool works with a new release
of automatic update (AU) clients to form the basis for a powerful automatic download and install
strategy. The new AU client set includes a client for Windows 2000 and Windows Server 2003
operating systems and has the ability to automatically install downloaded updates. For more
information about Microsoft SUS, go to
http://www.microsoft.com/windows2000/windowsupdate/sus/default.asp.
• Microsoft Systems Management Server (SMS) Software Update Services Feature Pack. The SMS
Software Update Services Feature Pack contains a number of tools aimed at easing the process of
issuing software updates throughout the enterprise. The tools include a Security Update Inventory
Tool, a Microsoft Office Inventory Tool for Updates, the Distribute Software Updates Wizard, and
an SMS Web Reporting Tool with Web Reports Add-in for Software Updates. For more information
about each tool, see
http://www.microsoft.com/smserver/downloads/20/featurepacks/suspack/.
Talk to your clients regarding each of these tools and encourage their use. It is very important that
security issues are addressed as quickly as possible, while maintaining the stability of the
environment.
Additional SQL Server 2000 Security Settings

As Microsoft Solomon relies intrinsically on SQL Server 2000, it is important that you take measures to
increase the security of the client’s SQL Server 2000 installation. The following steps will help increase
SQL Server security:
• Make sure that the latest operating system and SQL Server 2000 service packs and updates are
installed. Check the Microsoft Trustworthy Computing Security Web site
(http://www.microsoft.com/security/default.asp) for the latest details.
• For file system-level security, make sure all SQL Server 2000 data and system files are installed
on NTFS partitions. You should make the files accessible only to administrative or system-level
users through NTFS permissions. This will safeguard against users accessing those files when the
MSSQLSERVER service is not running.
• Use a low-privilege domain account or the LocalSystem (recommended) account for SQL Server
2000 service (MSSQLSERVER). This account should have minimal rights in the domain and should
help contain (but not stop) an attack to the server in case of compromise. In other words, this
account should have only local user-level permissions in the domain. If SQL Server 2000 is using
a Domain Administrator account to run the services, a compromise of the server will lead to a
compromise of the entire domain. To change this setting, use SQL Server Enterprise Manager to
make the change. The access control lists (ACLs) on files, the registry, and user rights will be
changed automatically.
• Most editions of SQL Server 2000 are installed with two default databases, Northwind and pubs.
Both databases are sample databases that are used for testing, for training, and for general
examples. They should not be deployed within a production system. Knowing that these
databases are present can encourage an attacker to attempt exploits involving default settings
and default configuration. If Northwind and pubs are present on the production SQL Server 2000
computer, they should be removed.
• Auditing of the Microsoft SQL Server 2000 system is disabled by default, so no conditions are
audited. This makes intrusion detection difficult and aids attackers in covering their tracks. At a
minimum, you should enable auditing of failed logins.
For the most up-to-date SQL Server 2000 security information, see
http://www.microsoft.com/sql/techinfo/administration/2000/security/default.asp.
Guide for New Microsoft Solomon

Installations
Overview
This section covers the following topics for those who do not currently have Microsoft Solomon
installed:
• “Installation Using the Microsoft Solomon CD” on page 31 guides you through installing the
Microsoft Solomon application files on your company’s application server. These steps apply to
both new and upgrade installations.
• “Microsoft SQL Server Installation” on page 39 prompts you to install the Microsoft SQL Server
database software on your company’s database server.
• “Creating Databases” on page 40 describes the various databases you can create and how to
create them.
• “Installing Supporting Applications” on page 50 guides you through the installation process for the
applications that provide added functionality to Microsoft Solomon.
• “Setting Up Microsoft Solomon on Workstations” on page 95 explains how to set up workstations
that will connect to your Microsoft Solomon application environment.
Note: Installation instructions for FRx are on the FRx CD.
Installation Using the Microsoft Solomon CDs

This section walks you through the steps to use the product CDs to install Microsoft Solomon on your
server. Note that this section pertains equally to creating new installations and updating existing
installations. It describes the steps for running Microsoft Solomon Setup for both purposes.
If you plan to run Microsoft Solomon locally on a client workstation rather than from a shared server
drive, turn to “Client Workstation Setup — Running Microsoft Solomon from the Local Client
Workstation” on page 98.
> To install Microsoft Solomon using the Microsoft Solomon CDs:
1. Log on as the local Administrator or as a member of the local Administrators group at the
server where you will install Microsoft Solomon. Failure to do so will cause problems in the
installation.
Note: If Active Directory you are using Active Directory, you must log on as a member of the
Domain Administrators group, which in turn needs to be part of the local Administrators
group.
2. Insert the Microsoft Solomon Volume 1 CD into the CD drive.
a.) If AutoPlay is enabled on the CD drive, the Microsoft Business Solution-Solomon setup
window automatically appears.
b.) If AutoPlay is not enabled, run Setup.exe in the root directory of the Microsoft Solomon
Volume 1 CD by choosing Start | Run and browsing to the CD drive.

3. Select Solomon including Tools for Visual Basic.
Microsoft Solomon Setup determines whether your computer needs a new version of the OLE
Automation engine program. If it does, Install appears.
Figure 9: Install
Note: Updating the automation files requires that you reboot your computer. If you cannot
reboot the computer now without disrupting other users, click Cancel and resume installation
later, when rebooting the server will cause the least amount of disruption.
4. Click OK. Information appears.
Figure 10: Information
5. Click OK. The computer will reboot. If Microsoft Solomon Setup does not restart automatically,
restart it by repeating step 1b.).
Note: If SQL Server starts automatically when the operating system starts, you may have to
stop SQL Server Services again. See “How do I stop and restart SQL Server Services?” on
page 9 for information on how to stop SQL Server services.
Welcome appears, advising you to exit all Windows® programs before continuing.
Figure 11: Welcome

6. If programs are running in Windows, Please Close Running Programs appears. Quit all
Windows programs that are currently running on the server, including those displayed as task
buttons in the notification area at the far right of the Windows taskbar, before continuing.
Note: Do not disable virus detection/protection software.
7. Click Next.
Software License Agreement appears, asking you to accept or decline the Microsoft Solomon
software license agreement.
8. Carefully read the software license agreement.
9. If you agree to the terms of the license agreement, click Yes. If you decline, another window
appears advising you Microsoft Solomon 6.5 Setup will stop operating.
Instructions appears.
Figure 12: Instructions

10. Read the installation notes, and then click Next.
Choose Edition appears, prompting for the edition to install.
Figure 13: Choose Edition

11. Click the appropriate Microsoft Solomon edition. See “Which Microsoft Solomon edition?” on
page 5 for information about determining your Microsoft Solomon edition.
Choose Destination Location appears, displaying the default destination folder for the
Microsoft Solomon installation.
Figure 14: Choose Destination Location

12. Microsoft Solomon program files should be installed in the default destination folder
(C:\Program Files\Solomon) or at least one directory level from the hard disk root directory
(for example, {drive letter}:\Solomon\Solomon 6_5\) since the folder you install Microsoft
Solomon to, the \Solomon 6_5 folder in the example, must be shared in order to support
connections by multiple workstations. Verify that the folder to be shared is acceptable for
sharing.
• If you want to install Microsoft Solomon in the default destination folder, click Next to
continue.
• If you want to override the default destination folder, click Browse to locate the folder
where you want to install Microsoft Solomon. If the destination folder does not already
exist, Microsoft Solomon Setup will ask whether it should create it, allowing you to
confirm that you have selected the correct location. Click Next.
13. If this is an upgrade installation and Microsoft Solomon Setup detects a previous Microsoft
Solomon installation, it requires you to remove the previous installation before continuing.
Click Yes to uninstall.
14. If this is an upgrade installation and Microsoft Solomon Setup detects an existing Microsoft
Solomon menu file (Delta.mnu) in the selected destination folder, it lets you save a backup of
the existing menu file in the backup subdirectory.

15. Click Yes to have Microsoft Solomon Setup back up the existing menu file.
Select Microsoft Business Solutions Solomon Applications appears, displaying the
applications and modules that are available.
Figure 16: Select Microsoft Business Solutions Solomon Applications

16. Select the modules and applications you plan to install. Be sure to select Web Order in the
E-commerce Series if you wish to install Solomon Web Order applications.
Strongly recommended: Select only those applications and modules you need to install. Do
not automatically select all applications and modules.
Note: You can install the Microsoft Solomon user guides by selecting the Solomon User
Manuals option on the Microsoft Solomon Volume 2 CD Installation Setup screen. User guides
are provided in Adobe Acrobat PDF format.
17. Click Next.

18. If you selected Client Setup Utility in the Foundation Series, and Microsoft Solomon Setup
detects a previous Microsoft Solomon client installation, it requires you to remove the
previous installation before continuing.
Click Yes to uninstall.
19. If you selected Tools for Visual Basic in the Tools Series, Software License Agreement appears
again, this time asking you to accept or decline the Microsoft Solomon Tools for Visual Basic
license agreement.
Carefully read the software license agreement. To accept the terms of the license agreement,
click Yes.
If you decline, another window appears advising you Microsoft Solomon 6.5 Setup will stop
operating. You can cancel Setup, accept the license agreement and continue the installation,
or click the Back button to remove Tools from the list of modules you chose to install.
20. If you selected Customization Manager in the Foundation Series, Customization Features
appears, prompting for the type of customization features to use with the Solomon
Customization Manager module.
Figure 17: Customization Features

After reading about the choices, select the appropriate customization option.
• VBA features — Installing Visual Basic for Applications (VBA) features allows you to create
new customizations using VBA code and to translate existing Basic Script Language (BSL)
customizations to VBA code. If you prefer to upgrade to VBA, choose VBA features.
• BSL features — Installing the Basic Script Language (BSL) features allows installations
that are upgrading to avoid being forced to use VBA if they prefer to continue using
current customizations written in BSL. Choose BSL features if you prefer to continue
writing and editing code using BSL.
21. Click Next. Select Program Folder appears, prompting for the destination of Microsoft
Solomon program icons.
Figure 18: Select Program Folder

22. In Program Folders, specify the folder where Microsoft Solomon Setup should add the
program icons. Accept the default folder name, type a different folder name, or select a folder
from the Existing Folders list.
23. Click Next to continue.
The message “Calculating space requirements. Please wait…” appears briefly.
Figure 19: Calculating Space Requirements message

Start Copying Files appears, listing all current installation selections.
Figure 20: Start Copying Files

24. Verify that all installation selections are correct. If a change is needed, click Back until arriving
at the incorrect selection, and then make the correct selection. Click Next until Start Copying
Files displays again.
25. Review the selections to make sure they are correct.
26. Click Next.
Microsoft Solomon Setup copies files from the Microsoft Solomon Volume 1 CD. If the Client
Setup Utility in the Foundation Series is selected (step 16), Microsoft Solomon Setup next
executes the Microsoft Solomon client setup program.
27. After Microsoft Solomon Setup finishes installing files, View Readme File appears, prompting
you to review the Microsoft Solomon ReadMe.txt file.
Figure 21: View Readme File dialog box

28. Click Yes.
29. Review ReadMe.txt file on the screen, or choose File | Print to print it.
30. After reviewing or printing, close the file by closing Notepad. Setup Complete appears.
Figure 22: Setup Complete

31. Click Finish.
Now that Microsoft Solomon Setup has finished installing the application files, you can create or
update databases.
• If this is a new installation of Microsoft Solomon, proceed to “Creating Databases” on page
40.
• If you are updating an existing installation of Microsoft Solomon, proceed to “Updating
Databases” on page 104.
Microsoft SQL Server Installation

At a minimum, Microsoft® SQL Server 2000 Standard Edition with Service Pack 3a or Service Pack 4 is
required for installation with Microsoft Solomon. The Microsoft Solomon Volume 2 CD includes Service
Pack 4. Microsoft SQL Server is a separate purchase from Microsoft Solomon. Contact your Microsoft
Solomon partner for more information.
For additional help in determining configuration requirements, contact your authorized Microsoft
Solomon partner or certified consultant.
You must install Microsoft SQL Server and start the service(s) before you can create Microsoft
Solomon databases. See “Creating Databases” on page 40.
> To install Microsoft SQL Server:
1. Insert the Microsoft SQL Server CD into the CD drive. Microsoft SQL Server setup starts.
2. Follow the on-screen prompts to install Microsoft SQL Server.
Note: Microsoft Solomon requires that you install Microsoft SQL Server using the default
settings for Sort Order and Character Set.
3. Follow the instructions in “Appendix A: Microsoft SQL Server Optimization Notes” on page 121
to set up Microsoft SQL Server for use with Microsoft Solomon.
Creating Databases
An application database contains all of the accounting data for an individual financial entity. A system
database contains shared site-specific data such as database field attributes, edit characteristics,
product registrations, customizations, and Microsoft Solomon screen-level security.
You must set up a working Microsoft Solomon application database (also known as a production or
empty database) and a system database before you can begin entering business data into Microsoft
Solomon.
Before you installed Microsoft Solomon, you recorded information about your databases on your Pre-
Installation Checklist. Retrieve the printout of your list. It will be important in the following steps.
Database Maintenance (98.290.00) can create databases based on four different scenarios:
• Empty Databases — Use this scenario to create a new system database and a new application
(production) database.
• Demo – Professional Edition — Use this scenario to create a database for demonstrating the
features in Solomon Professional. This scenario includes demonstration data for the Financial
Management, Inventory and Order Processing, Manufacturing, Field Service Management, and
Project Management and Accounting modules. It also includes Multi-Company support.
• Demo – Standard Edition — Use this scenario to create a single-company database for
demonstrating the Solomon Standard features. This scenario contains only Financial Management
Series data.
• Additional Empty Application Database — Use this scenario to create an additional application
database for use with an existing system database.
> To create Microsoft Solomon databases:
Note: These procedures must be performed by the Microsoft Solomon system administrator.
1. Confirm that the SQL Server service is running and restart it if necessary. Refer to “How do I
stop and restart SQL Server Services?” on page 9 for information about starting SQL Server
services.
2. From the Start menu, select the Database Maintenance icon in the Microsoft Solomon
program folder. Database Maintenance (98.290.00) appears.
Figure 23: Database Maintenance (98.290.00)

3. In Destination SQL Server Name, Login ID, and Password, type the Microsoft SQL Server
name, login ID (sa), and password.
4. Click Connect to connect to the SQL Server.
5. Click the Create Databases tab.
Figure 24: Database Maintenance (98.290.00), Create Databases tab

6. Follow the setup instructions for the type of database you are creating:
• “Creating an Empty Database Scenario”
• “Creating a Demo – Solomon Professional or Solomon Standard Database” on page 44
• “Creating an Additional Empty Application Database” on page 46
Creating an Empty Database Scenario

> To create an empty Microsoft Solomon database:
1. Choose Empty Databases from the Scenarios list.
2. Click Advanced.
Advanced Configuration Settings appears.
Figure 25: Advanced Configuration Settings

3. Change System Database Name, System Database Size (MB), Server Location of Database
Files, and Server Location of Transaction Log under System Database Definition, if desired.
4. Change Database Name, Size, Database Path, and Transaction Log Path under Application
Database Definition, as needed.
5. Click Ok. The Create Databases tab reappears.
6. Click Create. SQL Master60SP Login appears if you have not yet created the Master60sp
user. This will not happen if you have already installed a Microsoft Solomon 6.0 Service Pack
1 or higher database already on this SQL Server.
Note: If you have already created the Master60sp user, the Sysadmin Login dialog box
appears. Proceed to step 10.
Figure 26: SQL Master60sp Login

7. In the Password box, enter a password for the Master60sp user that satisfies the strong
password requirements listed in the dialog box.
8. In Confirm Password, type the password again.
9. Click Ok. SYSADMIN Login appears.
Figure 27: SYSADMIN Login

10. In the Password box, type a password for the Solomon SYSADMIN user that satisfies the
strong password requirements listed in the dialog box.
Note: For more information about strong passwords, see “Strong Passwords” on page 19.
11. In the Confirm Password box, type the password again.
12. Click OK. The Login dialog box appears.
Note: The Login dialog box will appear only if the Master60SP login already exists.
Figure 28: Login

13. In the Password box, type the password for the Master60sp user.
14. Click OK. Database creation begins.
15. When “Database creation process complete” appears, click OK.
16. Click Close.
17. Review the Dbbuild.log file in the \Eventlog folder. If the empty database creation was
successful, Dbbuild.log will only contain the times the process started and ended.
18. If you need to create additional empty application databases for use with the system
database you just created, proceed to “Creating an Additional Empty Application Database”
on page 46.
If you are finished creating databases, proceed to “Logging On Using the Empty System and
Application Databases” on page 48.
Creating a Demo – Solomon Professional or Solomon Standard Database

> To create a demo database for Solomon Professional or Solomon Standard:
1. Choose Demo – Solomon Edition or Demo – Standard Edition from the Scenarios list.
2. Click Advanced. Advanced Configuration Settings appears.
Note: Demo companies are included with Microsoft Solomon 6.5. The established application
database names for these companies are:
• DemoSolomonApp10 (companies 0010 and 0020)

• DemoSolomonApp60 (companies 0060, 0070, and 0080)
The demo system database name is DemoSolomonSystem.
Use these names for your demo databases when feasible.
3. If necessary, change System Database Name, System Database Size(MB), Server Location of
Database Files, and Server Location of Transaction Log under System Database Definition.
4. Change Database Name, Size, Database Path, and Transaction Log Path under Application
Database Definition, as needed.
6. Click Create.
SQL Master60SP Login appears if you have not yet created the Master60sp user. This will not
happen if you have already installed a 6.0 SP1 or higher database already on this SQL Server.
Note: If you have already created the Master60sp user, the Sysadmin Login dialog box
appears. Proceed to step 10.
Figure 30: SQL Master60sp Login

7. In the Password box, enter a password for the Master60sp user that satisfies the strong
password requirements listed in the dialog box. See “Strong Passwords” on page 19 for
additional information regarding strong passwords.
8. In Confirm Password, re-type the password, and then click Ok.
SYSADMIN Login appears.
Figure 31: SYSADMIN Login

9. In the Password box, type a password for the Solomon SYSADMIN user that satisfies the
Note: For more information about strong passwords, see “Strong Passwords” on page 19.
10. In the Confirm Password box, re-type the password, and then click Ok.
The Login dialog box appears.
Note: The Login dialog box will appear only if the Master60SP login already exists.
Figure 32: Login

11. In the Password box, type the password for the Master60sp user.
12. Click OK. Database creation begins.
14. Click Close.
15. Review the Dbbuild.log file, in the Eventlog folder of your Solomon installation. If the database
creation was successful, Dbbuild.log contains only the start and end times for the process. If
Dbbuild.log contains other text, contact Support Services for assistance.
16. Proceed to “Logging On Using the Demo System and Application Databases” on page 47.
Creating an Additional Empty Application Database

> To create an additional empty application database:
1. Choose Additional Empty Application Database from the Scenarios list this will only be
applicable after you have created your original empty database.
2. Click Advanced. Advanced Configuration Settings appears.

3. In the Application Database Definition area, complete the Database Name, Size, Database
Path, and Transaction Log Path boxes.
Note: Do not enter information in the boxes under System Database Definition. The system
database is defined in step 6 below.

5. Click Create. Identify System Database (98.290.40) appears.
Figure 34: Identify System Database (98.290.40)

6. Select the appropriate system database for your new application database from the System
Database Name list.
7. Click Ok. Database creation begins.
9. Click Close.
10. Review the Dbbuild.log file in the \Eventlog folder. If database creation is successful, the
Dbbuild.log contains the start and end times for the process.
Logging On Using the Demo System and Application Databases

> To log on using the Microsoft Solomon demo system and application databases:
1. From the Start menu, select the Solomon icon in the Microsoft Solomon program folder to
start Microsoft Solomon. Login (98.000.00) appears.
2. Click System Database. Find Database (98.000.01) appears.
3. Specify the Microsoft SQL Server name.
4. Press TAB.
5. Select the appropriate system database name (for example, DemoSolomonSystem) and click
OK.
6. In Company, enter or select the company ID associated with the application database (for
example, 0060 for DemoSolomonApp60).
7. Press TAB twice to move to the Password box, and then type the password you created in
step 9 under “Creating a Demo – Solomon Professional or Solomon Standard Database.”
8. Click OK.
9. Continue with “Preparing the Demo System and Application Databases.”
Preparing the Demo System and Application Databases

Preparing databases for operation means loading them with data contained in Microsoft Solomon .csv
files. These data include:
• System messages
• Possible values records
• Report control information
> To prepare the demo system and application databases:
1. Select Utility | DB Update. Database Update (DB.UPD.ATE) appears.
2. In Directory, browse for …\DB\CSVs.
3. Select messages.msg, pvrec.csv, and rptcontrol.csv from the Files list by clicking on them. It is
not necessary to hold down the CTRL key or SHIFT key.
4. Click Begin Processing.

5. Click OK when processing is complete.
6. Exit Database Update (DB.UPD.ATE).
Your Solomon databases are ready to use. To install other applications that provide additional
functionality to Microsoft Solomon, proceed to “Installing Supporting Applications” on page 50.
Logging On Using the Empty System and Application Databases

> To log on using the Microsoft Solomon empty system and application databases:
1. Start Microsoft Solomon. Login (98.000.00) appears.
2. Click System Database.
3. Specify the Microsoft SQL Server name.
4. Press TAB.
5. Select the name of the system database that you created in “Creating an Empty Database
Scenario.”
6. Click OK.
7. Verify that Company is blank.
8. Type the password defined in step 10 of “Creating an Empty Database Scenario.”
9. Click OK to log on.
10. Select Utility | Company Maintenance. Company Maintenance (98.280.00) appears.
Figure 35: Company Maintenance (98.280.00)

11. At least one company must be set up. Follow these steps to define the company:
a.) In Company ID, type a code to identify the company. It can be up to 10 characters long.
Example: 0040
b.) In Company Name, type the company name.
c.) In Database Name, specify the application database name from step 4 of the “Empty
Databases” section on page 6.
d.) In the Address through Employer Tax ID boxes, type the company’s address and other
related information.
12. Select Actions | Save.
13. Close the screen.
14. Select File | Close Company.
15. Select File | Open Company.
16. Specify the appropriate company (for example, 0040). You can also select the company from
a list of possible values by pressing F3.
17. Press TAB to move to the Password box.
18. Specify the user ID as SYSADMIN and type the corresponding password,
19. Click OK
20. Continue with “Preparing the Empty System and Application Databases.”
Preparing the Empty System and Application Databases

Preparing databases for operation means loading them with data contained in Microsoft Solomon .csv
files. These data include:
• System messages
• Possible values records
• Report control information
> To prepare the empty system and application databases:
1. Select Utility | DB Update. Database Update (DB.UPD.ATE) appears.
2. At Directory, browse for …\DB\CSVs.
3. Select messages.msg, pvrec.csv, and rptcontrol.csv from the Files list by clicking on them. It is
not necessary to hold down the CTRL key or SHIFT key.
5. When processing is complete, click OK to finish preparing the production system and
application databases.
6. Close Database Update (DB.UPD.ATE).
Note: Complete steps 7 through 10 if Solomon Multi-Company is installed.
7. Choose Module | Multi-Company | Multi-Company Setup. Multi-Company Setup (13.950.00)

appears.
8. Select Activate Multi-Company with Inter-Company Processing.
10. Close Multi-Company Setup (13.950.00).
11. Choose Module | General Ledger. The General Ledger menu appears.
12. Define information required for General Ledger module setup.
a.) Set up the retained earnings and YTD net income accounts in Chart of Accounts
Maintenance (01.260.00).
b.) Define subaccount (organizational) information in Subaccount Maintenance (01.270.00).
c.) Define ledger information in Ledger Maintenance (01.310.00).
13. Choose Module | General Ledger | GL Setup. GL Setup (01.950.00) appears.
14. Define the appropriate setup information in the Options, Fiscal Info, and Currency Info tabs.
Note: The previous step is required. However, you cannot complete all fields on the tabs until you
first define certain General Ledger module setup information: retained earnings and YTD net
income accounts, subaccounts, and ledgers. See step 12.

16. Close GL Setup (01.950.00).
17. Register Microsoft Solomon.
It is strongly recommended that you register your Microsoft Solomon system immediately after
completing the installation to avoid running out of TRIALLOC database accesses.
Installing Supporting Applications

Solomon Web Order Starter Site
General Installation Information
A complete installation of Solomon Web Order consists of two parts:
1. Installing the Solomon Web Order module.
2. Installing a Solomon Web Order Starter Site.
Before an order can be submitted using Web Order, it must be possible to submit an order using Sales
Orders (40.100.00) in Order Management.
Web Order Starter Site System Information
Web Order Starter Site is an Active Server Pages application that is installed on a Web server running
Microsoft® Internet Information Services (IIS). It is recommended but not required that your Web Order
Starter Site run on its own dedicated Web server.
Requirements
Before running the setup program for the Web Order Starter Site, verify that the following are installed
and running on the Web Order Starter Site dedicated Web server:
Microsoft IIS
Microsoft Solomon Web Order
Microsoft Solomon Order Management
Microsoft Solomon Inventory
Windows Script 5.6 (available for download from Microsoft, www.microsoft.com/vbscript)
ActiveX Data Objects (ADO) 2.6 or later (available for download from Microsoft,
www.microsoft.com/data/download.htm).
Internet Explorer 6.0 Service Pack 1 or later (available for download from Microsoft,
www.microsoft.com/ie/).
Note: The Web server on which you plan to install your Solomon Web Order Starter Site meets the
minimum requirements listed in the “Pre-Installation Checklist” on page 5.
Installing the Solomon Web Order Starter Site

> To install the Solomon Web Order Starter Site:
1. Insert the Microsoft Solomon Volume 2 CD into the CD drive of the Solomon Web Order
Starter Site server.

2. Click Solomon Web Order Starter Site. The Welcome dialog box appears and advises you to
close Windows programs before continuing with the installation.
3. Click Next.
The Software License Agreement dialog window appears, asking you to accept or decline the
Microsoft Solomon software license agreement.
5. Click Yes to accept.
If you click No to decline, Exit Setup appears and prompts you to exit or resume the Solomon
Web Order Starter Site setup.
6. Select Components appears, prompting for the Solomon Web Order Starter Site components
to install.
Figure 37: Select Components

7. Make sure that both components are selected.
8. Click Next. Commerce Site Server Name appears prompting for the name of the server
machine that will host the Solomon Web Order Starter Site.
Figure 38: Commerce Site Server Name

9. In Server, type the name of the Web Order Starter Site server. This is the name of the Web
server that will host the Starter Site.
10. To make the Solomon Web Order system accessible using the Internet, make sure you type a
fully qualified domain name. For example, if the server name is mysiteserver and the domain
name is mydomain.com, type mysiteserver.mydomain.com in Server.
11. Click Next.
Commerce Site Alias appears.
Figure 39: Commerce Site Alias

12. In Site Alias, type the name of the Solomon Web Order Starter Site virtual directory.
13. Site Alias is a name that identifies the starter site application. It is part of the URL used to
access the application. For example, if the server name you typed in step 9 is MyServer and if
you type WebOrder as the Site Alias, then the URL to access the application will be
http://MyServer/WebOrder.
Note: You must use a new name for the virtual directory. Do not use the name of an existing
virtual directory.
14. Click Next. Commerce Site Location appears, prompting for the Solomon Web Order Starter
Site directory.
Figure 40: Commerce Site Location

15. Type the physical path to the folder where the setup program should install the Solomon Web
Order Starter Site Active Server Pages (ASP) applications.
Note: The Solomon Web Order Starter Site directory must be a new directory, not an existing
directory.
16. Click Next. Commerce Site Information appears, prompting for a descriptive title for the
Solomon Web Order Starter Site.
Figure 41: Commerce Site Information

17. In Title, type the name of the Solomon Web Order Starter Site. This title can be changed after
Web Order Starter Site setup is complete.
18. Click Next. Database Setup and Login appears.
Figure 42: Database Setup and Login

19. In Server, type the name of the database server where the Microsoft Solomon application
database to use for Solomon Web Order is located.
20. In Database, type the name of the Microsoft Solomon application database to use for
Solomon Web Order.
21. In User and Password, type the SQL Server user name (sa) and password that the Solomon
Web Order Starter Site should use to connect to the database specified in database setup
(see step 18).
22. Click Next.
Test Database Connection appears.
Figure 43: Test Database Connection

23. If you click Yes and the database connection tests successfully, a message states, Connected
OK.
If the connection fails, an error message displays. Verify that the values for Server, Database,
User, and Password are correct. Also verify that the database server is running and accessible
from the Web server. If the values for Server, Database, User, and Password are correct and
test connection still fails, you can continue with the installation and resolve the connection
issue when your installation is finished.
24. If you click No, Solomon Web Order Starter Site setup proceeds with the current database
connection values. Start Copying Files appears.

25. Verify that all the choices you made for your Web Order Starter Site installation are correct.
26. If changes are needed, click Back until arriving at the incorrect selection.
27. Make the correct selection.
28. Click Next until returning to Start Copying Files.
29. Review the selections again to make sure they are correct.
30. Click Next. After a few seconds, a message displays informing you that the new site was
created successfully.
Figure 45: Information

31. Click OK. The setup program copies the application and system files to the appropriate
directories.
Setup Complete appears.

32. Click Finish to complete the Solomon Web Order Starter Site installation and exit the setup
program.
Note: If Setup Complete displays a message advising you to reboot the Solomon Web Order Starter
Site server, please do so. It may be necessary to reboot the server to fully register all new DLL files in
the system registry.
Solomon Web Order Module Setup

The Solomon Web Order module must be set up for operation before users can log on and place
orders using the Solomon Web Order Starter Site. Module setup procedures include:
• Defining Web Order configuration information in Web Order (83.950.00).
• Configuring inventory sites for use in the Web Order Starter Site in Inventory Sites (10.255.00). By
default, inventory sites are not automatically visible in the Web Order Starter Site.
• Setting up Web Order users and user groups in Web Order Maintenance (83.200.00).
See the Web Order user guide in \User Manuals\Program Files\Solomon\siv_wc.pdf on your Microsoft
Solomon Volume 2 CD for additional information.
Crystal Reports® for Solomon

Crystal Reports® for Solomon Version 10 is required only if you plan to design new reports. Unless you
have version 10 already installed, you must remove Crystal Reports from the server and workstations
before you install version 10.
Removing an Earlier Version of Crystal Reports

> To remove an earlier version before installing Crystal Reports for Solomon Version 10:
1. Remove Crystal Reports using Add/Remove Programs in the Windows Control Panel.
2. In Windows Explorer, delete all Crystal Reports program folders. A typical path is \Program
Files\Crystal Decisions\Crystal Reports\.
3. Locate the following files in \Crystal\Utilities on the Microsoft Solomon Volume 2 CD:
uSCR5_16.exe uSCR6_32.exe
4. Open the self-extracting executable file appropriate for the version of Crystal Reports to be
removed.
Example: If the 32-bit version of Crystal Reports is installed, uSCR6_32.exe is the correct file
to open.
5. Follow the instructions in the Install.txt file that is included in the self-extracting file.
6. Verify that Crystal Reports is completely removed from the server and workstation hard drives
by searching in Windows Explorer for the following files:
CRW.net CRR*.exe
CRW32.net CRPE.dll
CRW.exe CRPE32.dll
CRW32.exe
Note: Possible cleanup of the registry keys might be needed. Contact your system administrator
for assistance with this task.
Installing Crystal Reports® Version 10

> To install Crystal Reports® for Solomon Version 10 on the server (repeat these steps at each
workstation):
1. Insert the Microsoft Solomon Volume 2 CD into the server’s CD drive.

2. Select Crystal Reports® in the Microsoft Business Solutions-Solomon setup window. Crystal
Reports for Solomon Setup appears and advises you to close Windows programs before
continuing with the installation.
Figure 48: Crystal Reports for Solomon Setup

3. Click Next. License Agreement appears.
4. Carefully read the software license agreement, and select I accept the License Agreement.
5. Click Next. Select Installation Type appears.
Figure 49: Select Installation Type

6. Select Typical.
7. Verify the path specified in Destination Folder:
• If the default destination folder is correct, click Next to continue.
• If the default destination folder is not correct, click Browse to locate the correct folder or
type in the desired location.
8. Click Next.
9. Follow the remaining prompts to finish installing Crystal Reports.
10. When Crystal Reports has been successfully installed appears, click Finish. Crystal Reports
has been installed on the server.
Figure 50: Crystal Reports has been successfully installed

Crystal Enterprise — In Crystal Reports Setup, you may be asked if you want to install Crystal
Enterprise. Crystal Enterprise is not included with Microsoft Solomon and is not supported by Microsoft
Solomon Technical Support.
When using Crystal Reports with Microsoft Solomon, keep the following in mind:
• Microsoft Solomon does not use Crystal Reports dictionaries.
• Crystal Reports supports Microsoft Solomon user access control. Any user who is in Crystal
Reports is counted as a Microsoft Solomon seat license.
• To access Crystal Reports, you must be logged on to Microsoft Solomon using a valid user ID and
password.
• Crystal Reports service packs and hot fixes from Business Objects SA are not compatible with
Crystal Reports for Microsoft Solomon.
Note: Due to changes in the standard reports in Microsoft Solomon, customized reports from the 4.x,
5.x, and 6.x releases may not run without modification. Contact your authorized Microsoft Solomon
partner or certified consultant if your customized reports do not run.
Microsoft Office Project Connector for Solomon

Integrating the Microsoft Solomon and Microsoft Project Server databases entails installing
components, running scripts, or configuring options on the following computers (some computers can
contain more than one application or service):
• The server where Microsoft Solomon application files are installed (install components)
• The server where Microsoft Project 2002 or 2003 is installed (install components)
• The IIS server where Business Portal provides Web access to Microsoft Solomon functionality
(install components and configure access)
• The database server that holds the Microsoft Project 2002 or 2003 database (run scripts)
• The workstations where the Microsoft Solomon client is installed (install components)
• The workstations where the Microsoft Project Professional 2002 or 2003 client is installed (install
components)
Setting Up Users for the Project Connector
In order to use the integration between Microsoft Solomon and Microsoft Project, you must be a valid
user in both systems. Using identical logins facilitates trouble-free integration. Whether you choose
Windows authentication or Project Server authentication, the user ID and name should remain
consistent between Microsoft Project and Microsoft Solomon. The following instructions are intended
to serve only as recommendations, not as requirements. If your company’s system authentication and
authorization policies permit, using these configuration options will help assure a smooth and
successful user experience.
Note: Using Windows authentication entails less user intervention than Project Server authentication
and is the recommended authentication method. If you choose Project Server authentication, each
user must supply additional credentials in order to log the PSA COM add-in (the component used for
entering Microsoft Solomon Project Management and Accounting information) into Microsoft Project
Server each time the Microsoft Project Professional client is started. Furthermore, when new projects
are created in a Microsoft Solomon environment that uses Project Server authentication, the owner of
the Project Server user ID in Microsoft Project Connector Setup (PA.MSP.00) must log on to Microsoft
Project Server and publish each new project. Failure to do so results in the project being inaccessible
to other users, including the project’s manager, until the designated user publishes it to Microsoft
Project Server.
Using Windows Authentication

> To set up Windows authentication on Microsoft Project Server:
1. Log on to Microsoft Project Web Access as a user with administrative privileges.
Figure 51: Microsoft Project Web Access, Home page

2. Select Admin. Administration overview displays.
Figure 52: Microsoft Project Web Access, Administration overview page

3. Select Manage users and groups. Users displays.
Figure 53: Microsoft Project Web Access, Users page

4. Select Add User. Add User displays.
Figure 54: Microsoft Project Web Access, Add User page

5. In the Authenticate user by area, click Windows Authentication, using the Windows User
Account.
6. In Windows User Account, type the Windows account information using the format
DomainID\UserID.
7. In E-mail, type the user’s e-mail address.
8. In User Name, type the user’s name as it should appear in the enterprise resource pool.
9. Select the user’s group, category, and global permission.
10. Click Save Changes.
> To set up Windows authentication on Microsoft Project Professional 2002 or 2003:
1. Open Microsoft Project Professional 2002 or 2003 and select Tools | Enterprise Options |
Microsoft Project Server Accounts.
Figure 55: Opening Microsoft Project Server Accounts

Microsoft Project Server Accounts displays.
Figure 56: Microsoft Project Server Accounts

2. Click Add.
Account Properties displays.
Figure 57: Account Properties

3. In Account Name, type a description for the account.
4. In Microsoft Project Server URL, type the URL for Microsoft Project Server.
5. In the When connecting area, click Use Windows user account.
6. Click Test Connection to confirm the validity of the information you entered.
7. Click OK.
8. In Project Server Accounts under When Starting, select Manually Control Connection State.
9. Click OK.
> To set up Windows authentication on Microsoft Solomon:

1. Log on to Microsoft Solomon as a user with update access rights to Employee and Resource
Maintenance (PA.EMP.00). Employee and Resource Maintenance (PA.EMP.00) displays.
Figure 58: Employee and Resource Maintenance (PA.EMP.00)

2. For a new employee, enter all required information. For an existing employee, retrieve the
employee’s record.
3. In User ID, type the user ID used to log on to the domain.
4. Click Save.
5. Close Employee and Resource Maintenance (PA.EMP.00).
Using Project Server Authentication

> To set up Microsoft Project Server authentication on Microsoft Project Server 2002 or 2003:
Note: When integrated employees are created in Microsoft Solomon, a Project Server
authenticated user is created automatically.
1. Log on to Microsoft Project Web Access as a user with administrative privileges.
Figure 59: Microsoft Project Web Access, Home page

2. Select Admin. Administration overview displays.
Figure 60: Microsoft Project Web Access, Administration overview page

3. Click Manage users and groups. Users displays.
Figure 61: Microsoft Project Web Access, Users page

4. Click Add User. Add User displays.
Figure 62: Microsoft Project Web Access, Add User page

5. In Authenticate user by, click Microsoft Project Server authentication, using a logon ID and
password.
6. In User Account, type the user’s name as it should appear in the enterprise resource pool.
7. In E-mail, type the user’s e-mail address.

8. In Password, type the password that the user will use to log on to Project Connector.
9. In Confirm Password, type the password again.
10. Select the user’s group, category, and global permission.
11. Click Save Changes.
> To set up Project Server authentication on Microsoft Project Professional 2002 or 2003:
1. Open Microsoft Project Professional 2002 or 2003 and select Tools | Enterprise Options |
Microsoft Project Server Accounts.
Figure 63: Opening Microsoft Project Server Accounts

Microsoft Project Server Accounts displays.
Figure 64: Microsoft Project Server Accounts

2. Click Add. Account Properties displays.
Figure 65: Account Properties

3. In Account Name, type a description for the account.
4. In Microsoft Project Server URL, type the URL for Microsoft Project Server.
5. In the When connecting area, click Use a Microsoft Project Server account.
6. In User name, type the user’s name exactly as you entered it in User Account in step 6 of
“Using Project Server Authentication” on page 66.
7. Click Test Connection to confirm the validity of the information you entered.
8. Click OK.
9. In Project Server Accounts under When Starting, select Manually Control Connection State.
10. Click OK.
> To set up Project Server authentication on Microsoft Solomon:

1. Log on to Microsoft Solomon as a user with update access rights to Employee and Resource
Maintenance (PA.EMP.00).
Figure 66: Employee and Resource Maintenance (PA.EMP.00)

2. For a new employee, enter all required information. For an existing employee, retrieve the
employee’s record.
3. In User ID, type the user ID that will be used to log on to both Microsoft Solomon and
Microsoft Project Connector exactly as you entered it in step 6 of “Using Project Server
Authentication” on page 66.
4. Click Save.
5. Close Employee and Resource Maintenance (PA.EMP.00).
Installing the Project Connector

> To add the Project Connector components to the Microsoft Solomon application environment:
If you selected the Project Controller module in step 0 of “Installation Using the Microsoft Solomon
CDs,” you have already installed the Project Connector components that Microsoft Solomon
needs, although you must still install additional components for the Microsoft Project Server and
Microsoft Project Professional application environments.
> To add the Project Connector to the Microsoft Project Server application environment:
1. Close all other running programs on the server where Microsoft Project Server is installed.
Because Microsoft Project Connector for Solomon Setup may need to update files used by
other programs or services, it is important to complete this step before starting Microsoft
Project Connector for Solomon Setup.
2. Insert the Microsoft Solomon Volume 2 CD into the CD drive of the server where Microsoft
Project Server is installed.
Note: The Microsoft Project Server must have SQL Server Client Utilities installed, even if the
Microsoft Project database is on a different server. If SQL Server client utilities are not
installed, the scripts to update the Microsoft Project database cannot run.

3. Select Microsoft Project Connector. The Microsoft Project Connector for Solomon installation
screen appears.
Figure 68: Microsoft Project Connector for Solomon window

4. Select Microsoft Project Server components. Welcome displays, advising you to exit other
Windows programs before continuing.
Figure 69: Welcome

5. Click Next. Software License Agreement displays, offering the option to accept or decline the
end-user license agreement.
6. Carefully read the software license agreement. Click Yes. If you decline, another window
appears advising you that Microsoft Project Connector for Solomon Setup will stop operating.
Select Components displays, prompting you to select the version of Microsoft Project Server
you are using.
Figure 70: Select Components

7. Select the appropriate option for your version of Microsoft Project Server and click Next. The
initial Microsoft Project Connector for Solomon Setup Information screen displays.
Figure 71: Microsoft Project Connector for Solomon Setup Information

8. Type the URL for Microsoft Project Web Access and click Next. The second Microsoft Project
Connector for Solomon Setup Information screen displays.
Figure 72: Microsoft Project Connector for Solomon Setup Information

9. On the Microsoft Project Connector for Solomon Setup Information screen, do the following:
• In Microsoft Project Server Name, type the name of the database server that hosts the
Microsoft Project Server database.
• In Microsoft Project Server Database Name, type the name of the Microsoft Project
Server database (usually ProjectServer, sometimes with a four-digit number appended).
• In Project Server SQL User ID, type the login for the SQL Server administrative user (if you
use SQL Server authentication instead of Windows authentication, this is usually “sa”).
• In Project Server SQL User Password, type the password for the SQL Server administrative
user. Note that, since a blank administrative password poses a security risk, password is
a required entry. If you choose to leave the system administrator password blank, you will
need to perform the manual procedure in “Appendix C: Manually Creating Stored
Procedures and Table PA_Connect” on page 127.
• In IIS Virtual Root Directory, type the path to the folder where the database scripts and log
files will be stored (such as …\Inetpub\wwwroot\PSA\).
10. Click Next. Two informational windows appear, displaying the commands currently being
executed and log file information.
Since the number of files copied is small, Setup Complete displays almost immediately.

11. Click Finish. After Microsoft Project Connector for Solomon Setup completes all operations, it
exits automatically. Keep the CD in the drive, however, as you will need to reference a file on
the CD when you proceed to step 3 on page 78.
12. Check the log files PA_Connect.txt and InitMSPProject.txt in the Temp folder for your computer
(for example, ..\Windows\Temp\). If the commands ran successfully, the log files contain a
series of digits followed by greater than signs (1> 2> 3>, etc.). If errors occurred, the log files
contain text describing the nature of the errors. Correct the errors and rerun the Microsoft
Project Server components option of Microsoft Project Connector for Solomon Setup or
continue with the manual setup procedures described in “Appendix C: Manually Creating
Stored Procedures and Table PA_Connect” on page 127.
13. If this is an upgrade installation, open Microsoft Project Connector Setup (PA.MSP.00) after
you have installed the updated server extension and resubmit the Microsoft Solomon
connection information. Be sure to click Test Connection to verify that Microsoft Project
Server can access Microsoft Solomon.
Note: In obscure cases, the server name recorded in the PDS.wsdl file is “servername," rather
than the name of the server where Microsoft Project Server is installed. If you are unable to
establish or restore connectivity between the Solomon and Microsoft Project databases after
completing all of the steps in this section, follow these steps:
a.) Browse to ...\Program Files\Microsoft Office Project Server 2003 (or Microsoft Project
Server 2002)\IIS Virtual Root\PDS.wsdl.
b.) Right-click on the PDS.wsdl file, and then select Open With.
c.) In Open With, select Notepad, and then click OK.
d.) When the file opens in Notepad, scroll down until you see the following indented line:
<soap:address location="http://servername/ProjectServer/PDS.WSDL"/>
e.) Verify that the name of your server appears instead of “servername.”
f.) If the PDS.wsdl file contains “servername," replace “servername” with the name of the
server where Microsoft Project Server is installed.
g.) Save and close the file.
Installing the PSA Accounting View to the Microsoft Project Professional

The Project Connector includes a new view that displays the Project Series Task ID, Revenue, and
Other Expenses for integrated tasks. Installing the PSA Accounting view to your Microsoft Project
Server environment entails modifying the enterprise global template. Be sure to back up the
enterprise global template before you install the new view.
Note: You must have administrative permission to open the enterprise global template in order to
perform this procedure.
> To install the PSA Accounting View to Microsoft Project Server:

1. Back up the enterprise global template by opening Microsoft Project Professional 2002 or
2003 and selecting Tools | Enterprise Options | Backup Enterprise Global.
Figure 74: Backup Enterprise Global

The Save As dialog displays.
Figure 75: Enterprise Global Save As dialog

2. Maintain the location and file name as needed, then click Save.
3. Open Windows Explorer and browse to the Microsoft Solomon Volume 2 CD.
4. Open the MSPPSAServer folder and double-click PSAView.mpt to open the Microsoft Project
template file.
5. Select Tools | Enterprise Options | Open Enterprise Global.
Figure 76: Open Enterprise Global

6. When both the enterprise global template and PSAView.mpt are open, select Tools |
Organizer. Microsoft Project Organizer displays.
Figure 77: Microsoft Project Organizer, Views tab

7. Be sure that the drop-down lists at the bottom of the screen show PSAView and Checked-out
Enterprise Global (it does not matter which is on the left and which is on the right).
8. In PSAView, highlight PSA Accounting View and click Copy >>. If PSAView is on the right, the
Copy button will appear as << Copy.
PSA Accounting View appears in the Checked-out Enterprise Global area.
Figure 78: Organizer after Adding the PSA Accounting View to the Enterprise Global
9. Click the Tables tab.
10. In PSAView, highlight PSA Accounting Table and click Copy >>. PSA Accounting Table appears
in the Checked-out Enterprise Global area.
Figure 79: Microsoft Project Organizer, Tables tab

11. If you use Microsoft Project Server 2002, click the Fields tab. This step is not necessary if you
use Microsoft Project Server 2003.
12. If you use Microsoft Project Server 2002, in PSAView highlight all three fields (to select all
three fields, click the first field, hold down SHIFT, and click the third field) and click Copy >>.
This step is not necessary if you use Microsoft Project Server 2003.
Other Expenses, Project Management and Accounting Task ID, and Revenue appear in the
Checked-out Enterprise Global area.
Figure 80: Microsoft Project Organizer, Fields tab

13. Click Close to close Organizer.
14. Close file PSAView.mpt.
15. Close the enterprise global template, clicking Yes to “Do you want to save changes to
Checked-out Enterprise Global?”
16. To display the PSA Accounting View in Microsoft Project Professional, you must first close
Microsoft Project, then re-open it and select View | PSA Accounting View.
Figure 81: Microsoft Project showing the PSA Accounting View

The PSA Accounting View adds columns for Project Series Task ID, Revenue, and Other
Expenses to the Enterprise Gantt Chart. The Revenue and Other Expenses amounts originate
in Project Management and Accounting as actual transactions and update the Microsoft
Project database in display-only mode (once saved, existing Project Accounting Task IDs are
also display-only).
Note: Each user can specify a default view for Microsoft Project Professional by opening
Microsoft Project and selecting Tools | Options. On the View tab, select the Default view drop-
down to display the list of available views. Select a view and click OK.
To make a specific view the default view for all users, open the enterprise global template and
select Tools | Options. On the View tab, select the Default view drop-down to display the list of
available views. Select a view and click OK.
Figure 82: Selecting the PSA Accounting View as the default view
Setting Up the Connection Between the Microsoft Project and Microsoft

Solomon Databases
The following instructions are intended for IT/IS personnel who do not implement/configure the
Microsoft Solomon application environment. Following this procedure will provide the minimum
configuration necessary to connect the Microsoft Solomon and Microsoft Project databases and to
test the connection from all workstations that will use the integration.
If you are responsible for both installing and implementing the integration, please read the full setup
instructions in the section “Setting Up the Integration Between the Microsoft Solomon and Microsoft
Project Server Databases” in the Microsoft Project Connector Implementation and User Guide before
proceeding.
1. If you are using SSL with Microsoft Project Server, browse to the following location:
• If you are using Microsoft Project Server 2002, go to … \Program Files\Microsoft Project
Server\IIS Virtual Root\PDS.WSDL.
• If you are using Microsoft Project Server 2003, go to … \Program Files\Microsoft Office
Project Server 2003\IIS Virtual Root\PDS.WSDL.
2. Right-click on the PDS.WSDL file, and select Open With.
3. Choose Select the program from a list, and then click OK.
4. In Open With, select Notepad, and then click OK.
5. When the file opens in Notepad, scroll down until you see the following indented line:
<soap:address location="http://servername/ProjectServer/PDS.WSDL"/>
6. Change “http” to “https” and also verify that “servername” is the name of your Microsoft Project
Server.
7. Save and then close the file.
8. Start Microsoft Solomon.
9. Select Project Controller from the Module list. The Project Controller menu displays.
Figure 83: Project Controller menu

10. Click Project Controller Setup. Project Controller Setup (PA.SET.00) displays.
Figure 84: Project Controller Setup (PA.SET.00), General Information tab

11. Click Microsoft Project Connector Setup. Microsoft Project Connector Setup (PA.MSP.00) displays.
Figure 85: Microsoft Project Connector Setup (PA.MSP.00), General Parameters tab
12. Select Activate Microsoft Project Connector.
13. Click the Microsoft Project Connection tab.
Figure 86: Microsoft Project Connector Setup (PA.MSP.00), Microsoft Project Connection tab
For more information about authentication methods, see “Setting Up Users for the Project
Connector” on page 61.
14. In Server URL Name, type the URL of the server that hosts the Microsoft Project Server application
environment.
15. If you select Windows Authentication, users are authenticated and authorized without any added
user intervention. If it is not selected, Microsoft Project uses Project Server authentication, which
involves prompting each user for credentials each time Microsoft Project is started. Selecting this
checkbox disables Project Server User ID and Password.
16. Project Server User ID is enabled if Windows Authentication is not selected. Type the user ID that
Project Management and Accounting will use to log on to Microsoft Project.
Note: If you elect to use Project Server authentication, be aware that the user ID in Microsoft
Project is case-sensitive. The user ID in this field must exactly match (in case sensitivity) the user
ID in Microsoft Project. The user Administrator is a built-in account in Microsoft Project and the “A”
must be capitalized if you choose to type it here. Furthermore, when new projects are initially
created in a Microsoft Solomon environment that uses Project Server authentication, the user
specified at Project Server User ID must log on to Microsoft Project Server and publish each new
project. Failure to do so results in the project being inaccessible to other users, including the
project’s manager, until the designated user publishes it to Microsoft Project Server.
17. Password is enabled if Windows Authentication is not selected. Type the password for the Project
Server User ID. The password is encrypted to prevent accidental discovery by unauthorized
persons.
18. After typing the information for all fields on this tab, click Test Connection to test the connection to
Microsoft Project Server. If the information supplied on this tab is correct, PC Message Number
1391, “Connection Successful,” appears.
19. Click the Solomon Connection tab.
Figure 87: Microsoft Project Connector Setup (PA.MSP.00), Solomon Connection tab
20. In Database Server Name, type the name of the server that hosts the Microsoft Solomon
databases.
21. In Application Database Name, type the name of the Microsoft Solomon application database that
will integrate with the Microsoft Project Server specified on the Microsoft Project Connection tab.
22. In System Database Name, type the name of the Microsoft Solomon system database used by the
application database specified in Application Database Name.
23. In SQL Server User ID, type the user ID that Microsoft Project will use to log on to the Microsoft
Solomon database. Since the purpose of the SQL Server login is to transmit information between
the two server environments, be sure that the login is exactly the same as in Microsoft SQL Server
and set the permissions for this user ID accordingly.
24. In Password, type the password for the SQL Server User ID. The password is encrypted to prevent
accidental discovery by unauthorized persons.
25. After typing the information for all fields on this tab, click Test Connection to test the connection to
the Microsoft Solomon databases. If the information supplied on this tab is correct, PC Message
Number 1391, “Connection Successful,” appears.
26. Click Save.
27. Once you have confirmed that connectivity between the Microsoft Solomon and Project Server
databases is functioning correctly from all client workstations that are set up to use the
integration, you may need to clear Activate Microsoft Project Connector in Microsoft Project
Connector Setup (PA.MSP.00) until the implementation is complete. If you do not perform the
implementation of the Project Connector features when all client installations are complete, users
will have access to the integration features before they are properly configured. If you choose to
clear Activate Microsoft Project Connector until all implementation tasks have been completed,
Microsoft Project users who have the PSA COM add-in installed on their workstation will receive
the message “The Solomon Integration to Microsoft Project Server is not activated” each time they
connect to Microsoft Project Server.
Installing Microsoft Project Connector Components to the Microsoft

Project Professional 2002 or 2003 Client Workstation
Each client workstation in a Microsoft Project Server 2002 or 2003 environment must have certain
additional resources loaded on its local hard disk in order to access and use the integration. Complete
the client workstation setup procedures at each client workstation to have access to the integration
features.
Important: You must have Administrator rights on the computer due to the need to register
components.
> To install the integration components to Microsoft Project Professional 2002 or 2003:
Figure 88: Microsoft Business Solutions–Solomon setup window

2. Select Microsoft Project Connector. The Microsoft Project Connector for Solomon installation
screen appears.
Figure 89: Microsoft Project Connector for Solomon window

3. Select Microsoft Project Professional components. If Microsoft Solomon Setup detects a
previous client add-in, Question appears.
Figure 90: Question

4. Click Yes. Welcome displays, advising you to exit other Windows programs before continuing.
Figure 91: Welcome

5. Close all running programs other than virus protection software and click Next. Software
License Agreement displays, offering the option to accept or decline the end-user license
agreement.
6. Carefully read the software license agreement. Click Yes. If you decline, another window
appears advising you Microsoft Project Connector for Solomon Setup will stop operating.
7. Click Finish. After Microsoft Project Connector for Solomon Setup completes all operations, it
exits automatically.

Adding the PSA COM Add-In to Microsoft Project Professional

To assign valid Project Management and Accounting project and task IDs to projects and tasks using
Microsoft Project, you must first add the PSA COM add-in to the Microsoft Project Professional toolbar.
In Microsoft Project Professional 2002 or 2003:
1. Choose View | Toolbars | Customize.
Figure 93: Customizing the Microsoft Project toolbar

2. In Customize, click the Commands tab and highlight the Tools category.
Figure 94: Customize window

3. Scroll down the list of commands and select COM Add-Ins.
4. Drag the COM Add-Ins button to the toolbar.
Figure 95: Microsoft Project toolbar customized with COM Add-Ins button
5. Click Close to close Customize.
6. Click COM Add-Ins. COM Add-Ins displays.
Figure 96: COM Add-Ins

7. Click Add.
Important: Microsoft Project Connector for Solomon Setup copies PSAAddin.dll to …\WinNT (or
Windows) \System32, making it accessible to all users of each workstation. Browse to the System32
folder and select the file from there.
8. Select PSAAddIn.dll and click OK.
Figure 97: Add Add-In

9. Make sure that Solomon Integration is selected and click OK.
Figure 98: COM Add-Ins after adding Solomon Integration
Note: You might receive a message, “You are not connected to Solomon,” immediately after adding
the PSA add-in. The likely cause of this message is that the connection to Project Management and
Accounting has not been set up.
You might also see a logon prompt. If the connection to Project Management and Accounting is set up,
you can log on the add-in by providing the appropriate credentials.
Figure 99: PSA Add-in Logon Prompt

10. Since the add-in loads when you start Microsoft Project, close Microsoft Project Professional, then
reopen it. If the Solomon Integration toolbar does not appear automatically, add it to Microsoft
Project by selecting View | Toolbars | Solomon Integration.
Figure 100: Adding the Solomon Integration toolbar

The Solomon Integration toolbar is small enough that you can place it on the same row as an
existing toolbar.
Figure 101: The Solomon Integration toolbar
Note: Since the Solomon Integration toolbar writes data to the Microsoft Solomon database from
Microsoft Project, each user who has the COM add-in installed in Microsoft Project Professional must
also be a Microsoft Solomon user.
Setting Up Microsoft Solomon on Workstations

Each client workstation must have certain resources loaded on its local hard disk in order to access
and use Microsoft Solomon. Two client workstation setup options are available:
• Execute Microsoft Solomon from a shared directory on the server
• Execute Microsoft Solomon from the local client workstation (only for workstations that will not
have network access to Microsoft Solomon)
You must complete one of the client workstation setup procedures at each client workstation where
access to Microsoft Solomon is required.
Client Workstation Setup — Executing Microsoft Solomon from a Shared

Directory on the Server
> To set up a workstation to execute Microsoft Solomon from a shared server directory:
1. Log on as the local Administrator or as a member of the local Administrators group at each
workstation where Microsoft Solomon will be set up. Failure to do so will cause problems in
the setup.
Note: If Active Directory is being used, you must log on as a member of the Domain
Administrators group, which in turn needs to be part of the local Administrators group.
2. Map a network drive to the shared application folder on the server where the Microsoft
Solomon programs are installed. For example:
E:\<computer_name>\<share_name>
where:
<computer_name> is the computer name of the server.
<share_name> is the share name established for the directory above the Microsoft
Solomon directory on the server (for example, SolomonShare).
Example: If the Microsoft Solomon application files are in C:\Program Files\Solomon,

then share the \Program Files\ directory and the map the drive to that shared directory.
3. Run Setup.exe from the …\Wrkstn subdirectory to start the Microsoft Solomon client setup.
Welcome appears, advising you to exit other Windows programs before continuing.
Figure 102: Welcome

4. Click Next. Choose Destination Location appears.

5. Click Next to accept the path and folder displayed.
If a path does not appear, click Browse and navigate via the mapped network drive to the
shared folder where the Microsoft Solomon application files are located.
Note: If Microsoft Solomon Setup detects an existing installation, it requires you to remove it
before continuing. Click Yes to uninstall. If existing Microsoft Solomon databases must be
made compatible with release 6.5, see “Updating an Existing Microsoft Solomon Installation”
on page 101.
Select Program Folder appears.

6. Click Next to accept the Microsoft Solomon program folder displayed.
Start Copying Files appears, displaying the disk space required to complete the installation.

7. Click Next. After Setup copies all resources to the workstation’s hard disk and registers them
where needed, Setup Complete appears.

8. Click Finish.
Client Workstation Setup — Running Microsoft Solomon from the Local

Client Workstation
To install Microsoft Solomon so that it can be used by a single user on a local drive, follow the
installation steps in the “Installation Using the Microsoft Solomon CDs” section on page 31.
Installing Crystal Reports® for Solomon on a Local Workstation

Before installing Crystal Reports for Solomon Version 10 on the workstation, it will be necessary to
remove any previous versions of Crystal Reports.
> To remove an earlier version of Crystal Reports before installing Crystal Reports for Solomon
Version 10:
1. Remove Crystal Reports using Add/Remove Programs in the Windows Control Panel.
2. In Windows Explorer, delete all Crystal Reports program folders. A typical path is \Program
Files\Seagate Software\Crystal Reports.
3. Locate the following files in \Crystal\Utilities on the Microsoft Solomon Volume 2 CD:
4. Open the self-extracting executable file appropriate for the version of Crystal Reports to be
removed. For example, if the 32-bit version of Crystal Reports is installed, uSCR6_32.exe is
the correct file to open.
5. Follow the instructions in the Install.txt file that is included in the self-extracting file.
6. Verify that Crystal Reports is completely removed from the server and workstation hard drives
by searching in Windows Explorer for the following files:
CRW.net CRR*.exe
CRW32.net CRPE.dll
CRW.exe CRPE32.dll
CRW32.exe
Note: Possible cleanup of the registry keys may be needed. Contact your system administrator for
assistance with this task.
> To install Crystal Reports version 10 on a local workstation:


2. Select Crystal Reports® in the Microsoft Business Solutions-Solomon setup window. Crystal
Reports Setup appears.
3. If no other version of Crystal Reports is installed, the Crystal Reports Welcome appears. If
another version is found, follow the removal procedure on page 98.
4. Click Next. License Agreement appears.
6. Click I accept the License Agreement.
7. Click Next. Select Installation Type appears.
8. Click Typical.
9. Verify the path specified in Destination Folder:
• If the default destination folder is correct, click Next to continue.
• If the default destination folder is not correct, click Browse to locate the correct folder or
type in the desired location.
10. Click Next.
11. Follow the remaining prompts to finish installing Crystal Reports.
12. When Crystal Reports has been successfully installed appears, click Finish. The Crystal
Reports installation is finished.
Crystal Enterprise — In Crystal Reports Setup, you may be asked if you want to install Crystal
Enterprise. Crystal Enterprise is not included with Microsoft Solomon and is not supported by
Technical Support.
When using Crystal Reports with Microsoft Solomon, keep the following in mind:
• Microsoft Solomon does not use Crystal Reports dictionaries.
• Crystal Reports supports Microsoft Solomon user access control. Any user who is in
Crystal Reports is counted as a Microsoft Solomon seat license.
• To access Crystal Reports, you must be logged on to Microsoft Solomon using a valid user
ID and password.
• Crystal Reports service packs from Crystal Decisions are not compatible with Crystal
Reports for Microsoft Solomon. Microsoft Business Solutions provides these service
packs.
Note: Due to changes in the standard reports, customized reports from Microsoft Solomon 4.x
and 5.x may not run without modification. Contact your authorized Microsoft Solomon partner
or certified consultant if your customized reports do not run with Microsoft Solomon.
Updating an Existing Microsoft

Solomon Installation
Overview
This section explains how to update an existing Microsoft Solomon installation.
• “Removing an Existing Microsoft Solomon Installation” on page 102 describes how to remove
existing Microsoft Solomon installations on servers and client workstations to prepare for
installing.
• “Installation Using the Microsoft Solomon CDs” on page 104 explains how to use Microsoft
Solomon Setup to install Microsoft Solomon. These steps apply to both new and upgrade
installations.
• “Updating Databases” on page 104 describes how to update existing Microsoft Solomon
databases to operate with Microsoft Solomon.
• “Installing Supporting Applications” on page 50 describes the procedure for installing applications
included with Microsoft Solomon 6.5. Note that, unless you have Crystal Reports 10 already
installed, you must remove the previous version of Crystal Reports from the server and
workstations in order to install Crystal Reports 10. This section includes the following topics:
– “Removing an Earlier Version of Crystal Reports” on page 57 describes how to remove the
previous installation of Crystal Reports in order to install Crystal Reports version 10.
– “Installing Crystal Reports® Version 10” on page 58 describes how to install Crystal Reports
10.
• “Updating Microsoft Solomon Client Workstations” on page 110 explains how to update Microsoft
Solomon client workstations to this release.
Be sure to grant access rights to enable users to access the new Microsoft Solomon applications,
screens, and reports. Contact your authorized Microsoft Solomon partner or certified consultant to
obtain a list of new features in Microsoft Solomon. Rights granted previously to screens and reports
will remain intact. This step helps you set up rights to screens added in Microsoft Solomon.
Update Prerequisites
Create a backup of the application server, including all custom Crystal Reports so that they can be
restored after Microsoft Solomon is installed.
Important: Microsoft Solomon 4.10 or higher is required in order to update directly to release 6.5. If
you currently use a release older than Microsoft Solomon 4.10, contact your authorized Microsoft
Solomon partner or certified consultant about how to upgrade your Microsoft Solomon environment to
Microsoft Solomon 4.10 so that you can install Microsoft Solomon 6.5.
To verify the Microsoft Solomon release currently installed, see “Which Microsoft Solomon edition?” on
page 5 of the Pre-Installation Checklist.
Removing an Existing Microsoft Solomon Installation

Note: Be sure to perform a system backup before you follow these steps. In addition, remove the
Microsoft Solomon client from all workstations before removing it from the server. If your Delta.mnu
file has been customized, save a copy in the \Solomon\Backup folder so that you can restore it after
the installation is complete.
On the “Pre-Installation Checklist” on page 5, you were instructed to remove any existing 32-bit
release of Microsoft Solomon (release 4.x or later) from all client workstations and from the server
where it is installed before you start your Microsoft Solomon 6.5 installation. Otherwise, Microsoft
Solomon 6.5 Setup will require that you do so and will initiate the removal before starting the
Microsoft Solomon 6.5 installation.
If you missed those steps, you can perform them now.
Removing Microsoft Solomon Workstation Components

You must remove any existing Microsoft Solomon client installation before beginning your Microsoft
Solomon Release 6.5 installation. If you do not, Microsoft Solomon Release 6.5 may not install
correctly.
You must remove all client workstation components before removing the server components. If you do
not, Microsoft Solomon Client will not uninstall correctly.
> To remove all Microsoft Solomon Client files from each workstation:
1. On the Windows Control Panel, double-click Add/Remove Programs.
2. Choose Microsoft Business Solutions Solomon release number Client (where release number
is the number of the earlier release you want to uninstall).
3. Click Change/Remove. Click Yes in Confirm File Deletion.
4. Click Yes if you receive a prompt to remove Visual Basic for Applications.
5. Click Yes to All when you receive a prompt to remove shared components.
Note: When removing a Microsoft Solomon release before 4.21 Service Pack 2, clicking Yes To All
removes certain files from the Windows Registry, which may cause Microsoft SQL Server’s
Enterprise Manager to be temporarily unavailable. Reinstalling Microsoft Solomon along with the
Microsoft Solomon client re-registers the required files, making Enterprise Manager available
again.
Removing Server Components

Microsoft Solomon server components include Microsoft Solomon program files, supporting product
program files, and database components. To remove Microsoft Solomon Release 6.5 from the server,
complete the following steps in the order presented:
> To remove Microsoft Solomon from the server:
1. At the server where Microsoft Solomon is installed, open the Windows Control Panel.
2. Double-click Add/Remove Programs.
3. Select your current Microsoft Solomon release in the Install/Uninstall list. If you installed the
earlier release of the Microsoft Solomon client, you must first remove the Microsoft Solomon
Client by selecting Microsoft Business Solutions Solomon {release number} Client. See
”Removing Microsoft Solomon Workstation Components” for instructions.
4. Click Change/Remove.
5. Click Yes in Confirm File Deletion. S4Client appears.
Figure 108: Install/Uninstall dialog

6. Since you already removed the previous Microsoft Solomon client, click OK to remove
Microsoft Solomon program files.
7. If you receive a prompt to remove Visual Basic for Applications, click Yes.
8. If you receive a prompt to Remove Shared File, click Yes To All.
Note: When removing a Microsoft Solomon release before 4.21 Service Pack 2, clicking Yes
To All removes certain files from the Windows Registry, which may cause Microsoft SQL
Server’s Enterprise Manager to be temporarily unavailable. Reinstalling Microsoft Solomon
along with the Microsoft Solomon client re-registers the required files, making Enterprise
Manager available again.
9. When the uninstall process completes, click Details to view any files that could not be
removed.
10. View your file system to make sure the Solomon or Solomon IV folder (often under \Program
Files) was removed. If it still exists, delete it.
11. Reboot your computer.
12. Make sure no registry files appear in the Microsoft|Solomon program area of the registry.
Enlist the assistance of someone in your organization who is an expert on working with the
registry or call Microsoft Solomon Technical Support; see “Appendix E: Microsoft Solomon
Support” on page 133 for contact information.
Installation Using the Microsoft Solomon CDs

The procedure for installing the release 6.5 components of Microsoft Solomon is the same for upgrade
installations as it is for new installations. See “Installation Using the Microsoft Solomon CDs” on page
31 for instructions. When Microsoft Solomon Setup completes, continue the upgrade process by
following the instructions beginning with “Updating Databases” below.
Updating Databases
Before updating databases for use with Microsoft Solomon Release 6.5, make sure you first upgrade
your version of Microsoft SQL Server to Microsoft SQL Server 2000 Standard Edition with Service
Pack 3a or Service Pack 4. To purchase your upgrade, contact your authorized Microsoft Solomon
partner.
Important Points:
• Back up all Microsoft Solomon system and application databases before beginning the following
procedure.
• The update procedure deletes all standard Microsoft Solomon data in three system database
tables: Messages, Screen, and Rptcontrol. It then imports the current Microsoft Solomon required
data and repopulates the three tables.
• All records that you added to the Messages, Screen, or Rptcontrol table will remain intact. If
changes were made to standard records in these tables, however, the changes will be overwritten.
If changes were made to the database schema, it will be necessary to verify that these changes
are still in place after the update to Microsoft Solomon Release 6.5 is complete.
• The ScreenCategory and ScreenMenu records that define the menu for the EVERYONE user group
are replaced during an upgrade. Any changes or additions that you have made to these records
will be lost after you install Microsoft Solomon Release 6.5.
The Database Maintenance (98.290.00) utility can update Microsoft Solomon databases based on a
single scenario, 4.1x/4.2x/4.5x/5.x/6.x to 6.5.
> To update Microsoft Solomon databases:
1. Log on to the database server as the Administrator.
2. Back up all Microsoft Solomon system and application databases.
3. From the Start menu, select the Database Maintenance icon in the Microsoft Solomon
program folder. Database Maintenance (98.290.00) appears.

6. Click the Update Databases tab.
Figure 110: Database Maintenance (98.290.00), Update Databases tab
Updating Databases from 4.1x/4.2x/4.5x/5.x/6.x to 6.5

> To update databases from Microsoft Solomon Release 4.1x, 4.2x, 4.5x, 5.x or 6.x:
1. In Update Scenarios, click 4.1x/4.2x/4.5x/5.x/6x to 6.5.
2. Select the system database name from the System Database Name list.
3. In Databases, select one application database associated with the System Database
specified in step 2.
4. Click Update Database to apply the update to the databases.

• If you have not already created the Master60sp user, SQL Master60SP Login appears.
Figure 111: SQL Master60sp Login screen

a.) In the Password box, enter a password for the Master60sp user that satisfies the
b.) In Confirm Password, type the password again.
c.) Click Ok,
• If you have created the Master60sp user, the Login dialog box appears.
Figure 112: Login screen

a.) In the Password box, type the Master60sp user password.
b.) Click OK.
5. After you click OK in either the SQL Master60sp Login or the Login dialog box, Default
Password appears.
Figure 113: Default Password screen

6. Following the strong password requirements in the Default Password dialog box, type a
password in the Password and Confirm Password boxes that will replace any blank password.
7. Click OK to start the update process.
8. When the update is finished, the 9829000 message appears.
Figure 114: 9829000 message
Note: If the update was unsuccessful, you will not see this message. Instead, a database
update failure message will appear.
9. Click OK.
10. Click Close.
11. Review the Dbbuild.log file in the \Eventlog folder. A successful database update results in a
zero-byte Dbbuild.log file.
12. Follow the instructions in “Using Database Update after Completing the Database
Maintenance Scenario” on page 109 to continue the database update process.
13. Repeat this process for each remaining system database and respective application
databases.
Prepare SQL Server 7.0 Databases for running with SQL Server 2000
The Prepare SQL Server 7.0 Databases for running with SQL Server 2000 scenario is required to
ensure that Microsoft Solomon databases are ready for use with Microsoft SQL Server 2000.
Before running a database update scenario, make sure that you have upgraded your Microsoft SQL
Server to at least Microsoft SQL Server 2000 Standard Edition with Service Pack 3a or Service Pack 4.
See “Updating Databases” on page 104 for more information.
Note: Do not run the Prepare SQL Server 7.0 Databases for running with SQL Server 2000 scenario if
you have not upgraded from SQL Server 7.0 to SQL Server 2000. If it is necessary for you to use this
scenario, it should be run after a SQL Server 7.0 database has been upgraded to SQL Server 2000
and before logging on to the database in Microsoft Solomon.
After the Microsoft Solomon databases have been upgraded to SQL Server 2000 and before running
Microsoft Solomon, prepare the databases.
1. Run Database Maintenance (98.290.00).
3. In Update Scenarios, click Prepare SQL Server 7.0 Databases for running with SQL Server 2000.
4. Click Update Database.
This process takes a short time and allows Microsoft Solomon to access the databases on a SQL
Server 2000 database server.
Using Database Update after Completing the Database Maintenance

Scenario
After completing a database maintenance scenario (see “Updating Databases” on page 104), you
must use Database Update (DB.UPD.ATE) to populate the Microsoft Solomon system database with
current system data.
Note: Populating the Screen table occurs during database creation (databases are created using
Database Maintenance (98.290.00)). The Screen.csv file is no longer a part of Database Update
(DB.UPD.ATE).
> To use Database Update (DB.UPD.ATE):

1. Start Microsoft Solomon.
2. Log on as SYSADMIN to the system database and company (for example,
DemoSolomonSystem and company 0060).
3. Choose Utility | DB Update. Database Update (DB.UPD.ATE) appears.
4. Select all application databases associated with the company specified in step 2.
5. In Directory, browse for …\DB\CSVs.
6. From the Files list, select messages.msg, pvrec.csv, and rptcontrol.csv. You do not need to
hold down the CTRL or SHIFT key to select multiple files.
8. When processing is complete, click OK.
9. Repeat steps 1 through 8 for each additional system and application database combination.
10. Back up all system and application databases.
Updating Microsoft Solomon Client Workstations

> To update Microsoft Solomon client workstations:
1. Log on as the local Administrator or as a member of the local Administrators group at each
workstation that will be updated for Microsoft Solomon 6.5. This is required. Failure to do so
will cause problems in the setup.
Note: If Active Directory is being used, you must log on as a member of the Domain
Administrators group, which in turn needs to be part of the local Administrators group.
2. Map a network drive to the shared application folder on the server where the Microsoft
Solomon programs are installed. For example:
E:\<computer_name>\<share_name>
where:
<computer_name> is the computer name of the server.
<share_name> is the share name established for the directory above the Solomon
directory on the server (for example, SolomonShare).
Example: If Microsoft Solomon is installed in C:\Program Files\Solomon, then \Program

Files\ is the shared directory and the mapping is to that shared directory.
3. Run Setup.exe from the …\Wrkstn subdirectory on the server where Microsoft Solomon is
installed to start the Microsoft Solomon client setup. Welcome appears, advising you to exit
other Windows programs before continuing.
Figure 115: Welcome

4. Click Next. Choose Destination Location appears.

5. Click Next to accept the path and folder displayed.
If no path is displayed, click Browse and navigate via the mapped network drive to the shared
folder where the Microsoft Solomon application files are located.
Note: If the Microsoft Solomon Setup program detects an existing client installation, it
requires you to remove it before continuing. Click Yes to uninstall. If existing Microsoft
Solomon databases must be made compatible with release 6.5, see “Updating an Existing
Microsoft Solomon Installation” on page 101.
Select Program Folder appears.

6. Click Next to accept the Microsoft Solomon program folder displayed.

Start Copying Files appears, displaying the disk space required to complete the installation.

7. Click Next. After all resources are copied to the workstation’s hard disk, Setup Complete
appears.
8. Click Finish.
Updating Custom Crystal Reports®

Crystal Reports® for Solomon Version 10 is shipped with Microsoft Business Solutions–Solomon
Release 6.5. Most Microsoft Solomon standard reports were created in this version of Crystal Reports.
> To update custom Crystal Reports:
Open and save all existing custom reports.
This ensures that current customizations are incorporated into the reports. This also helps ensure
the compatibility of the reports with the Crystal Reports 10 print engine used in Microsoft
Solomon.
Note: In most cases, opening and saving custom reports is sufficient for updating them to version 10.
However, in certain cases it may be necessary to make minor report layout adjustments to your
custom reports to ensure that the output is acceptable. For example, you may notice that a field value
on a custom report is truncated. If you experience this problem, open the affected report in Crystal
Reports and extend the length of the truncated fields.
Expect that you may need to adjust the layout of custom reports as necessary whenever the version of
Crystal Reports integrated with Microsoft Solomon changes.
Troubleshooting 113
Troubleshooting
Restoring Microsoft Solomon System Database Table
Views
Two occurrences can create the need to restore the Microsoft Solomon system database table views:
• Dropping views in an application database
• Changing the name of the system database
Note: The following procedures must be performed by the Microsoft Solomon system administrator.
> To restore the system database table views:

1. Start the Database Maintenance (98.290.00) utility by selecting the Database Maintenance
icon in the Microsoft Solomon program folder.
Database Maintenance (98.290.00) appears.


5. In the System Database Name list, click your system database name.
6. In Databases, click the appropriate application databases.
7. Click Update Views to update to the databases.
8. Click OK.
9. Click Close.
Troubleshooting 115
Technical Resources for Microsoft Solomon

Section Contents
• Terminology Definitions — Key terms as they are used in Microsoft Solomon.
• Technology Tidbits — Foundational changes appearing in Microsoft Solomon 6.5.
• Backup and Restore Procedures — Processes used to back up and restore to databases of the
same or different names.
• Registered Controls — Proper uninstall and re-install processes, as well as how to register a
control manually.
• Solomon.ini — How Microsoft Solomon uses the Solomon.ini file.
Terminology Definitions
This section defines terms associated with Microsoft Solomon:
• View — A view is an alternate way of looking at data in one or more tables. Microsoft Solomon
uses database views in many reports to facilitate the multi-company or inter-company
implementation. To continue the company metaphor, we view the system database’s Company
table.
• Index — An index is a set of pointers that are logically ordered by the values of a key. Indexes
provide quick access to data and can enforce uniqueness on the rows in a table. Indexes are used
everywhere in Microsoft Solomon. They are foundational to the performance of a database
structure.
• Stored Procedure — A stored procedure is a multi-statement compiled Transact-SQL query with
control-of-flow language that can take parameters and allows user-declared variables, conditional
execution, and other powerful programming features. Stored procedures are used within Microsoft
Solomon to perform tasks such as database navigation and possible values lookups. They are
also used in database views.
• Proper Order of Rebuild — If a view is incorrect or dropped due to an error, the proper order of
build is the correct way to recreate the view and the underlying components on which the view
depends.
• Backup/Restore — Backup/restore is the process of making a physical backup copy of a database
and subsequently restoring the database from the backup to the computer system.
Backup/restore implements the standard Microsoft SQL Server Backup and Restore utility
programs.
• Registered Controls — A registered control is an object with a visible interface used within
Microsoft Solomon. Control examples include text boxes in a Microsoft Solomon screen,
Swimapi.dll, and Solomon Customization Manager components. Here, the scope of registered
controls is limited to installing, registering, and unregistering critical controls. It includes common
issues that may cause conflict when you are removing Microsoft Solomon.
• Solomon.ini File — The Solomon.ini file is used by Microsoft Solomon applications to control user-
specific and global preferences in the Microsoft Solomon environment.
Technology Tidbits
Recommended Protocols for Microsoft SQL Server
• TCP/IP Sockets is the recommended protocol for production environments. TCP/IP is the
communication protocol used by the server and workstation and is also the standard Internet
protocol. Sockets transport database calls across the TCP/IP protocol. The terms TCP/IP Sockets
and Sockets are used interchangeably.
• NetBEUI and Named Pipes are a protocol alternative to TCP/IP Sockets. NetBEUI is the
communication protocol used by the server and workstation. Named Pipes is a method of
transporting database calls across the NetBEUI protocol. The terms NetBEUI/Named Pipes and
Named Pipes are used interchangeably.
Note: Use the SQL Server Client Configuration Utility to validate proper protocols on the workstation
and the server. The protocols on both machines must match in order to establish a connection.
Company Record
The central storage point for companies, the company record in the system database cross-references
the application database(s) where a company’s financial data is stored. Since companies can have a
one-to-one or a one-to-many relationship of company to application database, the Company table is
the central cross-reference for all companies.
Preset companies exist within the demo databases included on the Microsoft Business Solutions–
Solomon Release 6.5 Volume 1 CD. These databases are built from the \Solomon\Demo database
subdirectory. They contain these companies and application databases:
Company Application Database Name

0010 DemoSolomonApp10
0051 DemoStandardApp51
Since the system database’s company table stores the relationship of company to application
database, backing up and restoring to a different database name invalidates the company records
(backup and restore procedures are discussed later).
AcctXRef Record
To facilitate cross-referencing accounts, subaccounts, and company information, Microsoft Solomon
uses a table called AcctXRef. This table is built when you first set up the chart of accounts or
subaccounts and is rebuilt when you make and save changes in Chart of Accounts Maintenance
(01.260.00) or Subaccount Maintenance (01.270.00).
Using SQL Server Optimization Within Microsoft Solomon
Microsoft Solomon makes extensive use of views. A view is an alternate way of viewing records or
multiple records in a single or multiple databases. When creating custom reports, it is good practice to
implement views to facilitate Microsoft Solomon reporting, advanced features, functionality, and
performance.
Consider how views are used in Microsoft Solomon:
• Reports — Most of the critical reports used by Microsoft Solomon are based on views. Therefore, if
you need additional fields on a report, the modifications must be made in the view used by that
report.
• Advanced features and functionality — Views are used as part of multi-company or inter-company
implementations to facilitate viewing the system database’s company table. The company table is
the single repository for company and database relationships.
• Performance — Views and stored procedures use Microsoft SQL Server Transact SQL (TSQL) to
create performance-optimized processes that execute in the SQL Server’s workspace. This allows
time-consuming processes to be executed on the SQL Server, saving considerable time. Processes
can run from 10 to 100 times faster using this methodology.
Note: Should you need to recreate database views, certain activities must subsequently occur to
complete the process. This is due to the nature of the company metaphor throughout the database.
See “Appendix A: Microsoft SQL Server Optimization Notes” on page 121 for more information.
Troubleshooting 117
Backup and Restore Procedures

Regular database backups and periodic testing of the restore process is strongly recommended.
Backing up databases and restoring them to their original name should not present problems and
does not require special handling. To do this, use Microsoft SQL Server.
Backing up a database and restoring it to a different database name can cause problems if not
handled properly. This results from the tracking of application databases by company table in the
system database.
For example, suppose a company configuration looks like this:
Company Original Application Database Name New Application Database Name

0010 DemoSolomonApp10 NEWAPPDB
0020 DemoSolomonApp10 NEWAPPDB
0051 DemoStandardApp51
If restored to a different database name, Company 0010, stored in the system database, is still
pointing to DemoSolomonApp10, not the new database name. To correct this, issue the following SQL
statement in Microsoft Query Analyzer against the system database:
Update company set databaseName = ‘NEWAPPDB’ where company = ‘0010’ or where company =
‘0020’
Problems result due to the views within that database now pointing to different database names. This
type of processing happens in the following business-use cases:
• Taking a snapshot of a database to test with or report from
• Setting up a database to deliver to the customer
• Setting up a database to develop on using customer data for testing
> Use the following recommended procedure to back up and restore a database from one name to
another:
1. Back up the original application and system databases (for example, ORIGINALAPPDB and
ORIGINALSYSDB) to a backup device.
2. Restore the databases to new names (for example, NEWAPPDB and NEWSYSDB).
3. In Query Analyzer, choose the new system database (NEWSYSDB) from the DB list.
4. Issue the following SQL statements in NEWSYSDB to update the Company and Domain
records to reference the new application database (NEWAPPDB):
Update Company set DatabaseName = ‘NEWAPPDB’ where CpnyID = ‘YOURCOMPANYID’
Update Domain set DatabaseName = ‘NEWAPPDB’ where DatabaseName = ‘OLDAPPDB’
Note: Make sure the correct database is selected from the Query Analyzer DB list before
executing these statements.
5. If restoring to a new server, also execute the following SQL statement:

Update Domain set ServerName = @@ServerName
6. Rebuild the NEWAPPDB and NEWSYSDB views as described below.
> To rebuild views:

1. Click the Database Maintenance icon in the Microsoft Solomon program group.
Database Maintenance (98.290.00) appears.


5. In the System Database Name list, click your system database name.
6. In Databases, click the appropriate application databases.
7. Click Update Views.
8. Click OK.
9. Click Close.
Troubleshooting 119
Registered Controls
Microsoft Solomon’s 32-bit architecture introduced the use of registered controls. These controls can
range from add-on product controls that facilitate data input to Microsoft Solomon’s kernel file
Swimapi.dll. Registered controls are installed and registered in the workstation’s Registry database.
Microsoft Solomon 6.5 setup automatically installs and registers the necessary components. After
Microsoft Solomon 6.5 is installed on a server, the following components are installed:
• Solomon — Program files for Microsoft Solomon
• Solomon Release 6.5 Client — Controls required to run Microsoft Solomon
You must remove any existing Microsoft Solomon client installation before beginning Microsoft
Solomon Release 6.5 installation. If you do not, Microsoft Solomon Release 6.5 may not install
correctly.
You must remove all client workstations before removing the server components. If you do not,
Microsoft Solomon Client will not uninstall correctly.
Improperly removing Microsoft Solomon Release 6.5 can result in unusual program behavior and
unexpected results. The recommended procedure for removing Microsoft Solomon Release 6.5 is
described in “Removing Microsoft Solomon Workstation Components” and “At the server where
Microsoft Solomon is installed, open the Windows Control Panel.” on page 102.
Solomon.ini
Microsoft Solomon uses the Solomon.ini file to save workstation-specific information such as the last
database that was logged on to, printer preferences, and other settings.
Solomon.ini is divided into sections indicated by double brackets [ ]. Each section performs its own
characteristic functions. See the System Manager Manual Appendix A for more information on the
Solomon.ini settings. For example, the [Company] section stores local company login information.
Under each section are several settings that control the workstation’s options.
[Company] — Company section
CompanyID=0010 — CompanyID setting
UserID=SYSADMlN — UserID setting
Solomon.ini is specific to the local workstation and stored in \Windows (or \Winnt) folder. If a setting
or section is not found in the Solomon.ini, the program looks in alternate locations. The behavior
occurs in the following order:
1. After executing Parent.exe, Microsoft Solomon looks for \Windows\Solomon.ini on the local client
workstation.
2. If Solomon.ini does not exist, the program creates it with just the basic sections needed. These
sections are [System32 Database] and [Company].
3. For sections Parent.exe does not find locally, the program then looks in the Solomon.ini in the
same tree structure from which Parent.exe was called on the server.
4. If a setting is not found in the local Solomon.ini, it is obtained from the server’s Solomon.ini.
A section and settings in the local \Windows\Solomon.ini overrides the same section and detail line(s)
in the shared Solomon.ini on the server. If a setting is found in the local Solomon.ini, it overrides the
settings in the server’s Solomon.ini.
Appendices 121
Appendices
Appendix A: Microsoft SQL Server Optimization Notes
This Appendix presents information on installing and setting up Microsoft SQL Server to operate with
Microsoft Solomon Release 6.5.
Supported Microsoft SQL Server Versions

Microsoft Solomon Release 6.5 supports Microsoft SQL Server 2000 Standard Edition with Service
Pack 3a or Service Pack 4. Microsoft SQL Server must be purchased separately from Microsoft
Solomon.
Microsoft SQL Server 2000

For an application user, the interface to Microsoft Solomon remains unchanged. The underlying
database, Microsoft SQL Server 2000, is optimized for performance as well as usability.
> To set dynamic and reserve memory:
1. Load Enterprise Manager.
2. Under SQL Server Group, select the server name where Microsoft Solomon databases are
maintained.
3. Right-click the server name.
4. Select Properties. SQL Server Properties appears.
Figure 123: SQL Server Properties

5. Click the Memory tab.
6. Select Dynamically configure SQL Server memory.
7. Set Minimum (MB) to 0MB. Set Maximum (MB) by moving the slider to the right approximately
80%.
The following chart is provided as a guideline:
Server Memory SQL Server Memory

128 MB 100 MB
256 MB 205 MB
512 MB 410 MB
1 GB 820 MB
1.5 GB 1230 MB
2 GB 1640 MB
8. Click OK. The following message window appears:
Figure 124: SQL Server service message window

9. Ask all SQL Server users to log out so that SQL Server Services can be stopped and restarted
safely.
10. Click Yes. This stops and restarts the SQL Server Services.
11. Close Enterprise Manager.
Appendices 123
Appendices 125
Appendix B: Updating the Application Database with

Schema Information
> To update the Microsoft Solomon application database with schema information:
1. Click the Database Maintenance icon in the Microsoft Solomon program group. Database
Maintenance (98.290.00) appears with the Connect Server tab active.

3. Click Connect to connect to the SQL Server on which to update Microsoft Solomon database
schema information.

5. In System Database Name and Databases, select the system and application databases to
which the Microsoft Solomon updates apply.
6. In Update Scenarios, select the option Field and Record Maintenance Update.
7. Click Update Database to apply the update to the databases.
Appendices 127
Appendix C: Manually Creating Stored Procedures and

Table PA_Connect
If Microsoft Solomon Setup did not create the table PA_Connect or the stored procedures in the
Microsoft Project Server database, you will have to perform the following steps manually. This is
typically due to the use of SQL Server authentication with a blank password for the “sa” user, which is
not recommended, as a blank password poses a security risk and causes vulnerability to viruses.
> Create the table PA_Connect in the Microsoft Project Server database.
1. Open Microsoft SQL Server Query Analyzer and connect to the server that hosts the Microsoft
Project database.
Figure 127: Connect to SQL Server

2. Select your Project Server database (usually ProjectServer, sometimes with a four-digit
number appended) from the list of databases on the server.
Figure 128: Select the ProjectServer database

3. Choose File | Open, browse to the folder specified in step 6 on page 73 (such as,
…\Inetpub\wwwroot\PSA\), and select file PA_Connect.sql.
Figure 129: Open Query File

4. Click Open.
5. Choose Query | Execute. SQL Query Analyzer confirms its success by reporting “The
command(s) completed successfully.”
Figure 130: Completed query

6. Close SQL Query Analyzer.
7. Check the log file PA_Connect.txt in the folder specified in step 6 on page 73 (such as,
…\Inetpub\wwwroot\PSA\). If the commands executed successfully, the log file contains a
series of digits followed by greater than signs (1> 2> 3>, etc.). If errors occurred, the log file
contains text describing the nature of the errors. Correct the errors and rerun the procedure,
beginning with step 1 on page 127.
8. Create stored procedures in the Microsoft Project Server database.
Appendices 129
9. Browse to the folder specified in step 6 on page 73 (such as, …\Inetpub\wwwroot\PSA\),

right-click on the file InitMSPProject.sql, and click Open With. You may receive the following
warning.
Figure 131: Open With Caution

10. Click Open With.
11. Scroll down the list of programs and choose WordPad to open the file.
Figure 132: Open With WordPad

12. Click OK.
13. Find the following line near the beginning of the file:
osql /S servername /U sa /P password /d ProjectServerDBName /i InitMSPProject.sql /o
InitMSPProject.txt
Figure 133: InitMSPProject.sql

14. Edit the line, replacing servername with the name of the server that hosts the Microsoft
Project Server database, password with the SQL Server administrative password (usually for
the user “sa”), and ProjectServerDBName with the name of the Microsoft Project database
(usually ProjectServer, sometimes with a four-digit number appended).
15. Copy the edited line, excluding the leading dashes, to the system clipboard and close the file.
Note: You must decide whether to save the changes made to the file. You might choose not to
save changes for security reasons — remember that the file now contains the administrative
password for SQL Server.
16. Open a command line window by clicking Start | Run. At Open, type cmd.
Figure 134: Opening a command line window

17. Navigate to the folder specified in step 6 on page 73 (such as …\Inetpub\wwwroot\PSA\).
Paste the contents of the clipboard into the command line window by clicking on the graphic
in the upper-left corner of the screen and selecting Edit | Paste.
Figure 135: Pasting the command into the command line window
18. Press ENTER.

19. When the command prompt reappears, type Exit to close the command line window.
20. Check the log file InitMSPProject.txt in the folder specified in step 6 on page 73 (such as,
…\Inetpub\wwwroot\PSA\). If the commands executed successfully, the log file contains a
series of digits followed by greater than signs (1> 2> 3>, etc.). If errors occurred, the log file
contains text describing the nature of the errors. Correct the errors and rerun the procedure,
beginning with step 8 on page 128.
Appendices 131
Appendix D: Restoring Connector Functionality to

Microsoft Project Server
When a Microsoft Solomon 5.5 or 5.5 Service Pack 1 client is removed from the machine where the
Microsoft Project Server application is installed, several SOAP DLL files are also removed
inadvertently. The client installation and removal processes have been addressed in Microsoft
Solomon 6.5.
> To repair Microsoft Project Server:
1. Copy the following files from the Wrkstn folder of the Microsoft Solomon installation
(C:\Program Files\Solomon\Wrkstn\Windows\WinSys) to C:\Program Files\Common
Files\MSSoap\Binaries:
• HLSC10.dll
• WISC10.dll
• XHSC10.dll
2. Copy the following files from the Wrkstn folder of the Microsoft Solomon installation
(C:\Program Files\Solomon\Wrkstn\WinSys\Register) to C:\Program Files\Common
Files\MSSoap\Binaries:
• MSSOAP1.dll
• MSSMO.dll
3. Copy the following file from the Wrkstn folder of the Microsoft Solomon installation
(C:\Program Files\Solomon\Wrkstn\Windows\WinSys) to C:\Program Files\Common
Files\MSSOAP\Binaries\Resources\1033:
• MSSOAPR.dll
The above files can also be found on the product CD in the folder
D:\SolIV\Wrkstn\Windows\WinSys or D:\SolIV\Wrkstn\Windows\WinSys\Register
(where D: is the CD drive).
Note: The following statements executed at a command prompt would accomplish the correct
moves from a Microsoft Solomon CD in Drive D:
Copy D:\SolIV\Wrkstn\Windows\Winsys\HLSC10.dll C:\Program Files\Common

Files\MSSOAP\Binaries
Copy D:\SolIV\Wrkstn\Windows\Winsys\WISC10.dll C:\Program Files\Common
Copy D:\SolIV\Wrkstn\Windows\Winsys\XHSC10.dll C:\Program Files\Common
Copy D:\SolIV\Wrkstn\Windows\Winsys\Register\MSSOAP1.dll C:\Program
Files\Common Files\MSSOAP\Binaries
Copy D:\SolIV\Wrkstn\Windows\Winsys\Register\MSSMO.dll C:\Program Files\Common
Copy D:\SolIV\Wrkstn\Windows\Winsys\Register\MSSOAPR.dll C:\Program
Files\Common Files\MSSOAP\Binaries\Resources\1033
4. Adjust the Security rights on the ViewDrop folder (C:\Program Files\Microsoft Project
Server\Bin\ViewDrop):
• Use the Properties page of the Directory and the Security Tab to allow access to the
Directory for all users of Microsoft Project Server.
Note: The ViewDrop sub-directory must also be re-created in this following path with access
available to all Microsoft Project Server users: C:\Program Files\Microsoft Project
Server\Bin\ViewDrop
Right-click the ViewDrop folder and select Security. Verify these accounts and permissions:
Full Control permissions:
Administrators group
System
Read and Write permissions:
Authenticated Users
Internet Guest accounts
Appendices 133
Appendix E: Microsoft Solomon Support

Various support plans are available that provide the exact product support you need for your Microsoft
Solomon installation:
• Local support through your Microsoft Solomon partner or consultant
• Support by mail from Microsoft Solomon Support
• Electronic Microsoft Solomon Support access (fax, e-mail, Web-based)
• Telephone support, including priority telephone support plans
• CustomerSource on the Web at www.microsoft.com/BusinessSolutions/CustomerSource
• Visit www.microsoft.com/businesssolutions/services for the latest details on these professional
support services
Important Phone Numbers and Internet Addresses
Microsoft Business Solutions 800-456-0025 U.S. and Canada

701-281-6500 Worldwide
Fax 425-936-7329 include e-mail alias of addressee
Microsoft Solomon Technical Support Guaranteed and Premium Support clients only
• Via Phone 888-477-7877
• Via Internet www.microsoft.com/BusinessSolutions
Training/Seminars Phone — 800-476-5666

Fax — 425-936-7329 include ATTN: Microsoft Business
Solutions University, mbsuniv@microsoft.com
Product Registration Phone — 800-476-5666

Fax — 425-936-7329
mbssalop@microsoft.com
Index 135
Index
A E
Access control 21 Edition 5
Account lockout policy 20 Solomon Professional 6
AcctXRef record 116 Solomon Standard 6
Adding PSA COM add-in to Microsoft Project Employees, security considerations 16
Professional 90 Empty application database, preparing 49
Administrative rights 13, 16 Empty system database, preparing 49
Antivirus software 22 Existing Microsoft Solomon installations 101
Audience 1 removing 102
Authentication 18, 22
B F
File-infecting viruses 23
Backup procedures 117 Firewalls 22, 24, 26
Baseline Security Analyzer 29
Boot sector viruses 23
Bulletins, security 29 H
Hardware firewalls 22, 24, 26
C
Cashier security considerations 16
Checklist, pre-installation 5
I
Client workstation setup Implementation planning security 13
executing Microsoft Solomon from Inheritance of permissions 21
the local client workstation 98 Installation
Client workstations, updating 110 Crystal Reports 57
Company record 116 Crystal Reports on local
Computer name 5 workstation 98
Connector functionality, restoring 129 existing Microsoft Solomon
Creating applications 101
databases 40 integration components to Microsoft
Creating manually stored procedures and Project Professional 2002 client
table PA_Connect 125 workstation 87
Crystal Reports 57 Microsoft SQL Server 39
installation on local workstation 98 preparation 3
installing 57 Project Connector 71
updating 112 PSA Accounting View to Microsoft
Custom Crystal Reports, updating 112 Project Server 2002 77
support products 50
using Microsoft Solomon CDs 31
D Internet connection firewalls 22, 24, 26
ISA Server 2004 24
Database
creating 40
demo 6
updating 104
L
DB update LAN security strategies 24
using after completing database Local area network security strategies 24
maintenance scenario 109 Lockout policy 20
Demo Logging on
database 6 authentication 18
preparing application database 47 single sign-on 22
preparing system database 47 using demo application database 47
Device firewalls 22, 24, 26 using demo system database 47
M P
MBSA 29 Passwords 19
Microsoft Baseline Security Analyzer 29 Perimeter networks 24
Microsoft Internet Security and Permissions 21
Acceleration 24 Physical security 15
Microsoft Office Project Connector for Planning security 13
Solomon 61 Pre-installation checklist 5
Microsoft Project Professional Preparing
Adding PSA COM add-in 90 demo application database 47
Microsoft Security Bulletin search tool 29 demo system database 47
Microsoft Security Notification Service 29 empty application database 49
Microsoft Software Update Services 29 empty system database 49
Microsoft Solomon SQL Server 7.0 databases for running
CD installation 31 with SQL Server 2000 108
CDs 31 Prerequisite update 101
edition 5 Procedures
installation setup options 11 backup 117
installation tasks 3 restore 117
installations 3 Project Connector 61
installing existing applications 101 installation 71
Internet addresses 131 setting up users 61
new installations 31 Protocols for Microsoft SQL Server 115
phone numbers 131 PSA Accounting View installation 77
setup on workstations 95 PSA COM, adding add-in to Microsoft Project
support 131 Professional 90
technical resources 115
uninstall workstation
components 102, 119 R
updating client workstations 110
workstation components Record
uninstall 102, 119 AcctXRef 116
Microsoft SQL Server company 116
2000 1, 7 Registered controls 119
2000 security settings 30 Removing existing Microsoft Solomon
installation 39 installations 102
optimization notes 121 Restore
recommended protocols 115 connector functionality 129
supported versions 121 database view 113
version 200 0 121 procedures 117
Microsoft Systems Management Server Rights
Software Update Services Feature administrative 13, 16
Pack 30 Windows user 21
Risk management See Security
N S
Network security 24
Notification Service, Security 29 Schema, updating application database 123
Security
access control 21
O account lockout policy 20
administrator responsibilities 16
Object auditing 21 authentication 18
Object ownership, Windows Server best practices 13
security 21 bulletins and updates 29
Operating systems employees and 16
security 18 firewalls 22, 24, 26
update management 29 ISA Server 2004 24
Overview 3 network 24
Owners, object ownership 21 Notification Service 29
object auditing 21
object ownership 21
overview 13
Index 137
passwords 19 Update
permissions 21 application database with Microsoft
physical 15 Solomon Schema information 123
single sign-on 22 custom Crystal Reports 112
SQL Server 2000 settings 30 databases 104
virus protection 22 databases from 4.1x through 6.x to
Windows Server best practices 18 6.5 105
Server components, uninstall 102 Microsoft Solomon client
Setting up workstations 110
client workstation 98 prerequisites 101
connection between Microsoft Project User rights, Windows Server security 21
and Microsoft Solomon Users setup 61
databases 82 Using
Microsoft Solomon on DB update after completing database
workstations 95 maintenance scenario 109
Microsoft Solomon options 11 SQL Server optimization within
Solomon Web Order module 56 Microsoft Solomon 116
users 61
Single sign-on 22
SMS Software Update Services Feature V
Pack 30
Software Virus protection 22
antivirus programs 22
firewalls 22, 24, 26
Update Services 29 W
Solomon Web Order module setup 56
Solomon.ini 119 Web Order
SQL Server 7.0, preparing databases for module setup 56
running with SQL Server 2000 108 starter site 50
SQL Services Service Web Order Starter Site
start 9, 10 installation 50
Stored procedures and table PA_Connect, requirements 50
manually creating 125 system information 50
Strong passwords 19 Websites
Support for security information 23
Microsoft Solomon 131 for virus protection information 23
product installation 50 Windows Server operating systems
Supported Microsoft SQL Server security 18
versions 121 See also Operating systems
SUS 29 Wireless networks 26
System database Workstation
preparing 49 client setup 98
preparing demo 47 setting up Microsoft Solomon 95
Systems Management Server Software uninstall components 102, 119
Update Services Feature Pack 30
T
Technical resources for Microsoft
Solomon 115
Technology tidbits 115
Terminology definitions 115
Tools for Visual Basic 8
Trojan horse programs 23
Troubleshooting 113
restoring a database view 113
U
Uninstall
Microsoft Solomon workstation
components 102, 119
server components 102

SL Install (Guide For Users) Manual

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SL Install (Guide For Users) Manual

Transféré par

Droits d'auteur :

Formats disponibles

Microsoft® Business Solutions–Solomon

Guide for New Microsoft Solomon Installations 31

Updating an Existing Microsoft Solomon Installation 101

Summary of Tasks for New and Existing Microsoft Solomon Installations

First-time installation Upgrading an existing installation

• Single-User Solomon Standard

Product Version SQL Server 2000 Release and Product Level

How do I stop and restart SQL Server Services?

Figure 1: SQL Server Service Manager

Note: If this message appears, remember to restart SQLServerAgent when restarting

> To start services using Service Manager (recommended procedure):

Note: If this message appears, remember to restart SQLServerAgent when restarting

SQL Server 2005

Note: If this message appears, remember to restart SQLServerAgent when restarting

Microsoft Solomon Installation Setup Options

Figure 2: Microsoft Business Solutions-Solomon setup window

Microsoft Solomon Security Best Practices

For the Employees

For the Administrator

Securing the Server Operating System

Access Control Best Practices

External Security Firewall

Virus Prevention Best Practices

• Microsoft Trustworthy Computing: Security (http://www.microsoft.com/security/default.asp)

ISA Server 2004

ISA Server Policies

Network Security Strategies

Figure 3: Basic Perimeter Network

Note: Microsoft Solomon is currently not supported in a wireless environment.

Network Security Scenarios

Figure 4: Simple Firewall

Figure 5: ISA Server Firewall

Figure 6: Existing Firewall with ISA Server Added

Two Existing Firewalls

Figure 7: Two Existing Firewalls

Security Update Management

Additional SQL Server 2000 Security Settings

Guide for New Microsoft Solomon

Note: Installation instructions for FRx are on the FRx CD.

Installation Using the Microsoft Solomon CDs

Figure 8: Microsoft Business Solutions-Solomon setup window

4. Click OK. Information appears.

Figure 10: Information

Figure 11: Welcome

Note: Do not disable virus detection/protection software.

Figure 12: Instructions

Choose Edition appears, prompting for the edition to install.

Figure 13: Choose Edition

Figure 14: Choose Destination Location

Figure 15: Choose Destination Location

Figure 16: Select Microsoft Business Solutions Solomon Applications

17. Click Next.

Figure 17: Customization Features

Figure 18: Select Program Folder

Figure 19: Calculating Space Requirements message

Figure 20: Start Copying Files

Figure 21: View Readme File dialog box

Figure 22: Setup Complete

Microsoft SQL Server Installation

Figure 23: Database Maintenance (98.290.00)

Figure 24: Database Maintenance (98.290.00), Create Databases tab

Creating an Empty Database Scenario

Figure 25: Advanced Configuration Settings

Figure 26: SQL Master60sp Login