User login

[Chris]

Hi folks,

Just curious. I manage a small 30-pc network at work and
we currently issue passwords to our users. These
passwords are known to us, and we frequently use them to
login with the user accounts for installations,
troubleshooting, etc. Is this common practise in the
industry for small business?

I understand that large businesses allow users to create
their own passwords, however I don't understand how the IT
staff is able to effectively troubleshoot without being
logged in with the user's profile. How is this issue
overcome?

Any insight would be appreciated.

Thanks

 

[Guest]

I manage a small network also(between 30-40 machines) but
we let the users pick their own passwords.

The way to handle that is if you need to logon as a
particular user you can just change their password in
Active Directory and notify them of it so they know how to
logon their next time and change their password after they
logon.

IMO, it's never good to know any passwords other than your
own/administrative passwords.

 

[Joe Mahma]

Hi folks,

Just curious. I manage a small 30-pc network at work and
we currently issue passwords to our users. These
passwords are known to us, and we frequently use them to
login with the user accounts for installations,
troubleshooting, etc. Is this common practise in the
industry for small business?

Common? Yes. Recommended? No.

I understand that large businesses allow users to create
their own passwords, however I don't understand how the IT
staff is able to effectively troubleshoot without being
logged in with the user's profile. How is this issue
overcome?

In secure environments, a user cannot install software. There are
special users (usually desktop guys and Domain Admins) whose accounts
have that priviledge. So we don't usually need to use the user's
account. On the occasions where something is wrong with that would
require us to use their account, we schedule it with them, and have
them log in for us. An Admin should never need to know anyone's
password but their own.

This is to protect you more than it is to protect anyone else. All it
takes is for that user account to be used to commit some theft or
malicious act, and you become a suspect.

 

[Jlmc]

I have a Standard practice of changing the users password to their login
name when I do after hours maintenance. I also set the require password
change at next logon when I have completed. All the users know this so when
they logon the next morning and the userid is Administrator they know their
valid password for the day and are prompted to change it.

 

[Chris]

Thanks guys. Some excellent info here.

-----Original Message-----
I have a Standard practice of changing the users password to their login
name when I do after hours maintenance. I also set the require password
change at next logon when I have completed. All the users know this so when
they logon the next morning and the userid is Administrator they know their
valid password for the day and are prompted to change it.




.