Comet And RDP
From CometWiki
m |
|||
| (2 intermediate revisions not shown) | |||
| Line 3: | Line 3: | ||
This page applies to the following: | This page applies to the following: | ||
| - | Comet32 version | + | Comet32 version .495 and later |
| - | Comet Security | + | Comet Security and File Servers version 15.03 and later |
We have found that a very efficient and economical way to connect multiple Comet users to a virtual Comet Host is to use Remote Desktop (Windows Terminal Services). This document outlines How to set this up. | We have found that a very efficient and economical way to connect multiple Comet users to a virtual Comet Host is to use Remote Desktop (Windows Terminal Services). This document outlines How to set this up. | ||
| - | Previous versions of Comet and Comet Server Products and Comet16 will not | + | Previous versions of Comet and Comet Server Products and Comet16 will not play well with Windows Terminal services. Since each remote Desktop Client had the same IP address, The server would not be able to tell one user from another. |
| - | Comet Server software previously relied on the client's IP address to distinguish between one comet and another. | + | Comet Server software previously relied on the client's IP address to distinguish between one comet and another. Now, the Comet Server software relies only on node name. |
Comet Services must be installed as Windows Services. In particular, a single instance of the Comet File server must be available to all users simultaneously. | Comet Services must be installed as Windows Services. In particular, a single instance of the Comet File server must be available to all users simultaneously. | ||
| Line 18: | Line 18: | ||
Each Comet connecting to the comet File Server must have a unique Node name. This is enforced by the Security server, but we need to emphasize it here because it is very important. | Each Comet connecting to the comet File Server must have a unique Node name. This is enforced by the Security server, but we need to emphasize it here because it is very important. | ||
| - | |||
== Step-by-Step == | == Step-by-Step == | ||
| Line 30: | Line 29: | ||
Configure the Remote Desktop Server to Restrict each user to a single session: | Configure the Remote Desktop Server to Restrict each user to a single session: | ||
| + | Click: | ||
| - | '''Administrative Tools/Remote Desktop Services/Remote Desktop Session Host Configuration''''' click on Restrict each user to a single session. In the dialog, make sure that Restrict each user to a single session is checked. | + | '''Startup/Administrative Tools/Remote Desktop Services/Remote Desktop Session Host Configuration''''' click on Restrict each user to a single session. In the dialog, make sure that Restrict each user to a single session is checked. |
Configure as many windows users as needed for full Comet Access. | Configure as many windows users as needed for full Comet Access. | ||
Latest revision as of 20:14, 7 March 2016
Comet and Windows Remote Desktop or Terminal Services
This page applies to the following:
Comet32 version .495 and later
Comet Security and File Servers version 15.03 and later
We have found that a very efficient and economical way to connect multiple Comet users to a virtual Comet Host is to use Remote Desktop (Windows Terminal Services). This document outlines How to set this up.
Previous versions of Comet and Comet Server Products and Comet16 will not play well with Windows Terminal services. Since each remote Desktop Client had the same IP address, The server would not be able to tell one user from another.
Comet Server software previously relied on the client's IP address to distinguish between one comet and another. Now, the Comet Server software relies only on node name.
Comet Services must be installed as Windows Services. In particular, a single instance of the Comet File server must be available to all users simultaneously.
Each user logged into the RDP Host must have a unique Windows user login name. This requirement may be set in the RDP host configuration.
Each Comet connecting to the comet File Server must have a unique Node name. This is enforced by the Security server, but we need to emphasize it here because it is very important.
Step-by-Step
Purchase a copy of Windows server. A standard edition is just fine. The current price from Amazon (11/2015) is $653.88.
Purchase as many Microsoft (per user) CALS as you need The current price from Amazon (11/2015) is $149.00 for 5 users. Depending on the number of users, a bulk license may be less expensive.
Or purchase these from your virtual IT provider.
Configure the Remote Desktop Server to Restrict each user to a single session:
Click:
Startup/Administrative Tools/Remote Desktop Services/Remote Desktop Session Host Configuration click on Restrict each user to a single session. In the dialog, make sure that Restrict each user to a single session is checked.
Configure as many windows users as needed for full Comet Access.
Configure as many comet nodes in the comet .ini file as there are users.
Log into windows for each user and create a shortcut on their desktop with the appropriate node name (C:\comet\comet.exe pn=node00), etc.
Now each Comet user will have their own RDP desktop with the correct Comet shortcut.
