Running IS2000 as a Service on the Server
Please go to the server (not using remote desktop) and log in as the local system admin.
- Close the Access Control Application and make sure that the associated drivers have stopped running.
- Run the Configuration Utility
- Make sure that the AutoLogon information is set correctly and that the SQL Logon information is set. Please test this before continuing, the software needs to start without any user intervention of password entry.
- From the Configuration Utility, check the box in Configuration Options to Run as a Service. You should get a message that states that the services installed successfully. Also make sure that the ‘Hide SQL Logon’ property is checked.
- Open up Services from the Administrative Tools section of Control Panel
- Locate the newly installed service (typically the name of the manufacturer) and make sure the service is set to run as the Local System admin.
- The driver services should be set as a startup type as manual and the access control application should be set to start Automatically.
- Test by starting the service of the main application manually. It should also start the driver service(s).
Configuring Driver Services
Note: As of software revision 8.6.98 all drivers will automatically be configured to run as a Windows Service. Improper configuration of the service accounts will cause the drivers to not start. Once the application has successfully installed / upgraded to version 8.6.98 or greater the Windows Services will automatically be installed. When the drivers start and no username and password has been specified for the driver service, then you will be prompted to enter this information. Please enter in the Local System Administrator for the Username and the password that correlates to this user. If a general Administrator account is used, please ensure this is the user account that was signed in during the installation of the Access Control Security application. This user must have the ability to start a Windows Service.
- Once the application has successfully installed / upgraded to version 8.6.98 or greater the Windows Services will automatically be installed. From Hardware Manager click on the pad lock and unlock the module this will allow editing of the screen.
- Highlight the Access Control Driver located in the hardware tree.
- From the Controller’s properties box, click on the drop down arrow to the right of the Windows Services Manager. This option will open Windows Services.
- From the Windows Services screen, highlight the Imron Access Control Driver service(s). With the service selected, right mouse-click and select Properties.
- From the Service Properties, click on the “Log On” tab.
- From the “Log On” tab click the “This Account” radio button.
- In the User Name box enter the user name for the Local System Administrator. If a general Administrator account is used please ensure this is the user account that was signed in during the installation of the Access Control Security application.
Note: This user must have the ability to start a Windows Service.
- In the Password box enter the password for the account entered in the User Name box.
- Confirm the password entered above.
- Click Apply.
- If the Service has already been started, click the Stop button to stop the Windows Service. This step must take place in order for the service to properly apply the changes.
- Click the Start button to Start the Windows Service.
- Click OK to exit the Service Properties.
Note: If mixed system is used containing multiple driver types, each Access Control Driver service will need to be configured using the steps above. Depending on the Operating System, it may be necessary to restart the PC in order for the services to properly display.
Configuring Service behavior when the Application Closes
- From IS2000 go to Hardware Manager.
- From Hardware Manager click on the pad lock and unlock the module this will allow editing of the screen.
- Highlight the Driver.
- From the Driver’s Properties box highlight “Stop when App Closes”. This feature will determine how the services function when the IS2000 Application is closed. Please note that in most cases this property should be set to ‘True’ for drivers that run on the IS2000 Server and to ‘False’ for drivers that run on an IS2000 Client.
Note: If the “Stop when App Closes” check box is set to a value of false and an upgrade is to occur, the services will need to be manually stopped before the upgrade will complete successfully.
Important Notes to Consider:
- The IS2000 application can be configured to run as a client or server.
- There can only be one IS2000 Server in the system and a virtually unlimited number of IS2000 clients. Multiple Regional IS2000 Servers can be configured for use in a multi-site scenario.
- A driver can run as a service without running the IS2000 Client for that PC, but the IS2000 Server MUST be running on at least one PC in the system, and the IS2000 Server can be setup to run as a service.
- The drivers can run on a different PC as long as they have access to the IS2000 Server’s shared Data folder (referred to as the RemotePath).
- The IS2000 Web Service MUST run on the same PC as the IS2000 Server and will only work if the IS2000 Server is running.
Running the Driver as a Service on the Client
- Install IS2000 as a client on the PC that will run the other Driver.
- Verify that the IS2000 client runs correctly and is looking at the correct database and the RemotePath is set to the shared Data folder of the IS2000 Server.
- Add the driver in Hardware Manager and set the Computer_Name property to the name of the IS2000 Client PC.
- Set the ‘Start/Stop when App Opens/Closes’ to ‘False’, which will allow the driver to run on the PC whether or not the IS2000 Client is running.
- Under the Windows Services Manager, we recommend configuring the driver Startup Type to be ‘Automatic’ so that it will start automatically on reboot. The driver(s) on the client PC run independently from the IS2000 Client, and only depends on SQL Server and the IS2000 Service that is running on the IS2000 Server. Please note the driver configuration for the client PC is different from the driver(s) that runs on a server. Driver(s) that run on the IS2000 Server MUST be configured as ‘Manual’ for the Startup Type. Drivers that run on the IS2000 Server typically have the ‘Start/Stop when App Opens/Closes’ property set to ‘True’.
- Under the Windows Services Manager, we recommend that you specify an account under the ‘Log On’, so that the service will continue to run when different users log on and off from the client PC.
- Under the Windows Services Manager, we recommend that you select the ‘Restart the Service’ for failures and set the ‘Restart service after’ property to 1 minute under the ‘Recovery’ tab.
Running the Driver as a Service on the Client (for builds older than 8.6.91)
**** UPDATE: The following steps only need to be performed if you are running a version of the software that is older than 8.6.91. Otherwise these steps are automatically done via Hardware Manager by use of the Driver’s ‘Stop when App Closes’ property.
Please go to the client PC that will run the service. If you are using remote desktop, then please connect using console mode (mstsc /console) and log in as the local system admin.
- Stop the driver that is currently running on the client PC.
- Open the registry (regedt32) and locate the HKEY_LOCAL_MACHINE\SOFTWARE\Imron Corporation\IS2000\OS section of the registry.
- Look for a String Value called Driver_Service. If this does not exist then create a new String Value called “Driver_Service” and set it equal to 1.
- Close the Registry and open up a Command Prompt.
- From the Command Prompt, navigate to the Remotepath\Drivers folder, using the cd (change directory command).
- Once you’ve navigated to the Remotepath\Drivers folder, enter the Driver’s exe name followed by the following parameter (-install).
Example for Mercury SCP/EPC: 12000 -install
Example for Onity Wireless Locks: 24000 -install
Example for HID VertX/Edge: 19000 -install
- Open up Services from the Administrative Tools section of Control Panel
- Locate the newly installed service (typically the name of the manufacture) and make sure the service is set to run as the Local System admin.
- The driver service should be set to start Automatically.
- Test by starting the service from the main application manually.
- If an error stating that it cannot locate the driver is generated, then make sure that a UNC path was used for the driver’s location. To change this you will need to go to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\<Driver EXE Name> section of the registry to edit the path location.