Guys/Gals, You are missing the point here. The beta just released is a substituto to IMs such as ICQ/MSN but with the advantage that the server run in a system which is comtrolled by a given company. That is, the workers of such company can still enjoy the benefits of IMs in a enterprise level without both the spam from a global server as well as the extra security that messages are not sent outside of a given network (except if some client is outside of it, but it would still not go to a public server).
So, RAdmin as we know with versions 2.2 then 3.0 beta is one product for remote handling of a system while the new product RCS and RCC is a substitute for general IMs in a controlled enterprise level. So, please do get to know what you are actually testing so that we get to ask/reply on the pertinent topic
So, in the original topic of this thread the idea would be to have the server running in a given system in the enterprise and all clients connected through such server. If, however, one wishes to test the features using just two computers it can be done, as long as one of them act up as a server, but the real thing would be to have both connected through a dedicate (or not) server. A web server (or file server) in an enterprise could make up an excelent server for RCS wheer RCCs would connect through.
I am new to this, so I have to ask, to be sure if I have got this right; the Radmin Viewer 3.0 is to be used for connections outside local networks, and the
Communication Client 3.0, together with Communication server 3.0 is to be used only for local networks?
If so, will there be another update on the remote admin server 2.2 to implement new functions, or is the RCS 3.0 version ment to be used under both conditions?
In my business environment, it would be nice to be able to login and have a buddy list with other people in the organization (like of using msn or aim but in this case it would be secure and private). RCS seems to be more of a chat room than an instant messenger.
For instance a teacher in room 13 could send an instant message to the teacher in room 22 to ask if they want to go to lunch. This would be more appropriate than asking the person in a chat room environment where multiple people in the organization could see it. All of these instant messages could be logged to a file on the server.
RCS seems to be pretty good for very small meetings in a very trusted environement, however, my organization would rather meet in person than to join a chat room. RCS still needs the extra security features that I mentioned in my earlier post:
Is there a way to grant a user operator access to the #general channel?
I have some ideas to greatly enhance the communication server. There should be more security attributes under RAdmin security and WinNT security. Instead of just having, "all access", "chat" and "audio chat", there should be an administrator security attribute. This administrator security attribute should give the user operator rights to every channel regardless of who created it. Also, another operator should not be able to remove the operator rights from a user who is granted this administrator security attribute. A user with the administrator security attribute should be able to kick users and edit chat messages (after all there is a mute option, why not kick?). There should also be an option for administrators to control which users can access certain channels. For example, an administrator could create a channel that only other administrators could view. A user with the administrator security attribute should also be able to make announcements, which show up in every open channel such as "Server will be shutting down in 10 minutes for scheudled maintenance! Please try connecting again in one hour."
There should also be a security attribute to allow a user to create a new channel, instead of just giving all users rights to do it.
There should also be an option (disabled by default) to allow annonymous access (user must enter a nickname but is not required to enter a password) to certain pre-specified channels. For a large meeting, it may not be desirable to setup user accounts for every person that is to take place in the meeting. Even a meeting with over 10 members could be tedius to setup.
Lastly, there should be a way to disable a user (not completely delete and have to re-create) so they can't join until the administrator re-enables their account. This could serve as a temporary ban function.
I think these changes would greatly enhance the communication server by increasing the security and putting more options into the hands of the people in charge. What do you guys think?
I think if all of these features were implemented that you'd sell more licenses of RCS, including to my organization.