|
Mark. Lazarus wrote: < I was using an arbitrarily low number to make the point, but in reality there can easily be 1,000 or more users, each w/ 2 or 3 sessions. What real advantage is there to assign the system administrator another task? Unless you're in a high security environment I think that named devices provide little advantage in the way of security and much in the way of administrative overhead.> Sorry Mark, guess it depends on how you view this, but named devices the way WE do it DEFINITELY provide things that we need. We have users connecting via TCP/IP and the way the PC is setup, the device session created IS named. For tech support/help desk we KNOW for sure at what location this device is located instantly based on our naming conventions. We also have applications that check "various things" and the named device is necessary for this to work. Not to mention that a printer needs to know what device to send a message/messages back to... And the list goes on <BG> Might be different for you, but there is NO WAY we could get by with "nameless" devices :-) JMHO ! Chuck +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.