Andrew explained that ACCPAC CRM uses a Named Seat license schema.  One Named Seat is locked in for each user with the purchase of  a corresponding license for each.  The total number of users must be equivalent to the number of licenses purchased, or an error message will appear and the extra user will not be saved into the system.  The system automatically installs a user named "CRM user", which is used for communicating to other databases, not for regular logons.  So when you buy 10 licenses, the system will actually give you 11.  When installing for the first time, you can leave the license key blank in order to activate the 30-day free trial. 

The installation process has been somewhat simplified, since some NTFS rights are now automatically granted.  The step that required a user to set up the assignments of these rights has been eliminated.  Read and write permissions in the security section have now been set to default, which also resolves some issues as well. Authentication methods are also used to check anonymous access on internet guest accounts.

Some tips that Andrew gave for a smooth installation were:

• You should create a new domain user if your database and the IIS server (your CRM location) are on separate machines.
• Never change the password for the IUSR_machine name account.
• Do not use the CRM user as a regular logon account.
• If  you make a client a resource - then you can't log on to that user. 

The live demo went well, the program prompted for appropriate fields and was very strait forward.

- END -

Go back to the ACCPAC Partnership Conference Intro page.  Visit our home page featuring reviews of all the top products.