Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Office Help Home

Overview

Clubs choosing to host their Office/POS environment locally, will need to install the application(s) on their Club’s local workstations after the application Server is built and configured.  Installing the Office applications on local workstations is the responsibility of the Club’s local IT Technician. These instructions are guidelines to assist your local IT Tech in installing both the Clubessential Management Application (CMA) and the Point of Sale (POS).

If you are interested in Clubessential providing this service, please contact support to discuss estimated hours, cost, and to schedule an appointment.

Use Case

Due to a Club’s IT depth, the Club has opted to host the Office application locally, rather than going with a hosted environment solution.  Once the initial Server has been configured, the Club then installs the appropriate applications on the local workstations within their Pro Shop,  Administrative Office, Dining Rooms, and Spa so all designated users may log-in and access the necessary programs.


Content

 

Prerequisites to Installation 

  1. The shared application folder can be mapped to a network drive on all workstations, though we recommend using the Universal Naming Convention (UNC) path. (Example: \\SRV-NAME\Clubessential).  

    Note: Using the UNC path can help minimize spread of viruses.


  2. You must log in to the machine using the Windows user account of the user that will be using the software.  The Office and POS applications must be installed for each user on a PC or Terminal Services user.

  3. The user’s permissions must include local administrator rights for the prerequisite install. The prerequisites are a global install and may be installed as the administrator of a machine – separate from Office and POS.
    If you receive any errors during the installation process, please refer to the Common Questions and Concerns section found at the bottom of this guide.  Reach out to support if you encounter any errors.

Installing CMA and POS 

  1. Install the Clubsoft Prerequisites by going to the Clubessential shared folder > Setup > double click Clubsoft Application Suite Prerequisites.msi then follow the prompts to install it (Next > Install > Finish).


2. Install the Clubessential Management Application (CMA) by going to the Clubessential shared folder > Setup > CMA > double click on Setup.exe then click Install.

NOTE: It is not required for Office to be installed on the Food & Beverage POS terminals, however, many clubs prefer to do this so that Food and Beverage Managers can make quick changes during service if necessary.


3. Install the Point of Sale (POS) by going to Clubessential shared folder > Setup > POS > double click on Setup.exe then click Install.


 


Best Practices

When mapping the shared application folder, use the UNC path to reduce risk of spreading viruses.

While it is not required, installing the Clubessential Office Management Application at the POS stations is oftentimes helpful for the Food and Beverage Managers to be able to make quick edits/updates to the system.

 

FAQs

Q.  What version of Windows can I use?

A.  Clubessential software is no longer tested for Windows XP or previous versions of Windows Operating System.  In terms of Server environment, Clubessential software is no longer tested for Windows Server 2003 or previous versions of Windows Server Operating System since they are no longer supported by Microsoft.


 

Q.  When launching the application for the first time, I was asked to select the appropriate connection file.  What is it? 

A.  When launching the application for the first time, you may be asked to select the appropriate database connection file. If so, browse to the Clubessential shared folder and select the DefaultConnection.xml file.


 

Q.  When launching the application for the first time, connection to the SQL database failed.  Now what? 

A.  If connection to the database fails when launching the application for the first time, check that the user has rights to the SQL database and has local administrator rights.

If the user has access to both the SQL database and local admin, follow these steps:

1. Click the + sign next to Connection Options.


2. Click the Edit Connection button.


3. Check to make sure the Server Name and the Database Name fields have the correct information.  Server name should be the SQL Server computer name and the instance name. In most cases this will be SERVER\CLUBESSENTIAL.

Database name is typically MERCURY in a single database club. Username/Password or Integrated Security options should remain unchanged from the original installation.

 

Q.  What do I do when application Shows “Inaccessible Logs” Error?

A.  If you receive the following error, “Inaccessible Logs; Security Data Portal Dot Fetch Error,” follow the instructions below: 

Warning: Modifying the registry incorrectly can cause serious system-wide problems. Please make sure to create a backup of the Registry prior to making any changes. 

1.      Go to Start Menu and launch the Registry Editor. 

2.      Within the Registry Editor go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. 

3.      Right-click eventlog and choose permissions.  Add full control permissions for Authenticated Users. (Note: If Authenticated Users is not found, click add and type in Authenticated Users). 

4.      Expand eventlog, right-click security, and choose permissions. Click add, type “Authenticated Users” and click OK.

5.      Add full control, and then click OK.


Downloadable Guide

Installing Office (CMA/POS) on Local Workstations - Onsite Server - Guide


 

 

  • No labels