On Wed, Oct 14, 2009 at 19:17, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx> wrote:
ÂThat always bugged me a bit, but, as I said, they were behind locked doors.
When we set up a domain at that time, autologin went away due to requiring CAD to log in.

I'm not really seeing why you associate the SAK requirement with
autologin - they're not really related. I believe you can do
autologon, even with the SAK requirement on.

ÂThe
network consultant is as well, he says he has NEVER set up a non-server PC
to do this.

I can perfectly understand the Autologon requirement for Clients in
some cases, for example in the Point of Sale systems we deploy,
Autologon is usually enabled to a heavily restricted user which just
runs the Point of Sale application. And has no access to any important
data. The PoS application also has it's own user management and screen
locking mechanisms.

But why would one anyone ever use Autologon on a server?

What else can I give them as reasons?

Don't reason. Policy is policy. Passwords are required, not optional,
not open for discussion. There's no way you can ever win such an
argument, as people that want autologon on their clients are obviously
out of touch with reality. Thus, an argument based on facts like
security is going to fall on deaf ears.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.