Virtual Dongle
From CometWiki
(Difference between revisions)
(Created page with "Comet Security Server Virtual Dongle Installation The Virtual Dongle Server was released with Comet Server Products version 13. Here are the requirements to use it: *A signed E...") |
|||
| Line 1: | Line 1: | ||
| - | Comet Security Server Virtual Dongle Installation | + | == Comet Security Server Virtual Dongle Installation == |
| + | |||
The Virtual Dongle Server was released with Comet Server Products version 13. Here are the requirements to use it: | The Virtual Dongle Server was released with Comet Server Products version 13. Here are the requirements to use it: | ||
| Line 7: | Line 8: | ||
*You'll need a dongle server registration file called DRB.txt. This will be emailed to you when your order for the virtual dongle is processed. | *You'll need a dongle server registration file called DRB.txt. This will be emailed to you when your order for the virtual dongle is processed. | ||
*The Comet Security Server must have a reliable internet connection. | *The Comet Security Server must have a reliable internet connection. | ||
| - | *The Comet Security Server must be running as a service and have administrator privileges. | + | *The Comet Security Server must be running as a service and have '''administrator privileges'''. |
| - | If you are replacing an existing USB or parallel dongle: | + | <br>If you are replacing an existing USB or parallel dongle: |
*Install Server Products vsn 13 or higher on your server and make sure all is well using the existing dongle. | *Install Server Products vsn 13 or higher on your server and make sure all is well using the existing dongle. | ||
*Put the DRB.txt file into your Comet Services folder. This is the same folder where you installed the Server Products release. | *Put the DRB.txt file into your Comet Services folder. This is the same folder where you installed the Server Products release. | ||
*Stop the Comet Services then remove the old dongle. | *Stop the Comet Services then remove the old dongle. | ||
| - | *Make sure your internet connection is working and restart the Comet Services. When you restart the services it should process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. NOTE: It is recommended that you simply restart the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle. | + | *Make sure your internet connection is working and restart the Comet Services. When you restart the services it should process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you simply restart the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.''' |
*Return the old dongle to Signature Systems so that the permanent certificate can be issued. | *Return the old dongle to Signature Systems so that the permanent certificate can be issued. | ||
| - | If you are installing a new system: | + | <br>If you are installing a new system: |
*Make sure your internet connection is working on the server where the Comet Services will be installed. | *Make sure your internet connection is working on the server where the Comet Services will be installed. | ||
*Create the Comet Services folder. | *Create the Comet Services folder. | ||
*Put the DRB.txt file into that folder. | *Put the DRB.txt file into that folder. | ||
| - | *Install Server Products vsn 13 or higher on your server. When it asks if you want to restart Windows, say "No". Then use the Windows Services program to start the Comet Services. It will process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. NOTE: It is recommended that you start the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle. | + | *Install Server Products vsn 13 or higher on your server. When it asks if you want to restart Windows, say '''"No"'''. Then use the Windows Services program to start the Comet Services. It will process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. '''NOTE: It is recommended that you start the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.''' |
Revision as of 17:43, 20 December 2013
Comet Security Server Virtual Dongle Installation
The Virtual Dongle Server was released with Comet Server Products version 13. Here are the requirements to use it:
- A signed EULA must be on file with Signature Systems that includes the conditions of using a virtual dongle. You'll find the current End User License Agreement.pdf here: [1]
- You'll need a dongle server registration file called DRB.txt. This will be emailed to you when your order for the virtual dongle is processed.
- The Comet Security Server must have a reliable internet connection.
- The Comet Security Server must be running as a service and have administrator privileges.
If you are replacing an existing USB or parallel dongle:
- Install Server Products vsn 13 or higher on your server and make sure all is well using the existing dongle.
- Put the DRB.txt file into your Comet Services folder. This is the same folder where you installed the Server Products release.
- Stop the Comet Services then remove the old dongle.
- Make sure your internet connection is working and restart the Comet Services. When you restart the services it should process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. NOTE: It is recommended that you simply restart the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.
- Return the old dongle to Signature Systems so that the permanent certificate can be issued.
If you are installing a new system:
- Make sure your internet connection is working on the server where the Comet Services will be installed.
- Create the Comet Services folder.
- Put the DRB.txt file into that folder.
- Install Server Products vsn 13 or higher on your server. When it asks if you want to restart Windows, say "No". Then use the Windows Services program to start the Comet Services. It will process the DRB.txt, retrieve and install the new demo license certificate, and come up. You should check the CSecSrv.log file for activity logging. It's in the LOGS folder that will be created under your Comet Services folder. NOTE: It is recommended that you start the Comet Services using the Windows Services program rather than rebooting Windows. This is to be sure that your TCP/IP services are fully initialized before the Comet Services start. This is only an issue when first registering your dongle.
