Multiple Passwords

[Sanitoeter]

Dear SevenForums,
I'm curious if I can enable multiple passwords for one user, looking forward to your answers!

 

[richnrockville]

simple answer is NO. each userid is tied to a single password.

Inquiring minds would like to know why you would want to use multiple passwords for a single userid?

Some people just leave the password blank which of course is a security hole..

Rich

 

[Dzomlija]

The best (and only) solution that comes to mind is to change your password regularly. But if your enquiry is prompted by what I'm guessing, then it doesn't matter how many passwords you have, or how often your change them, because having a password that is easily discoverable is almost as bad as no password at all.

The best advice would be to pick you password, and stick with it. Make sure you pick something that no-one can associate with you, such as family names, phone numbers, birthdays, pets names, etc.

You can also make a password harder to guess by numerising it. That is, replacing common letters with similar numbers. An E becomes a 3, L becomes 7, O becomes 0, Z becomes 2, etc, I becomes 1, etc. Using mixed upper and lowercase letters is also a good idea. Also, the longer the password, the better (the longest I currently use for various archive encryption programs is 37 characters long...)

For example, DZOMLIJA if used as a password, would become D20M71JA.

 

[sherwint]

I would like to have multiple passwords for a single Windows Login for the following reasons:
1. Need a single user account accessible by multiple users, need the same desktop and folders for all.
2. Would like a unique password for each of the users to track who did what when.

 

[Golden]

simple answer is NO. each userid is tied to a single password.

As above - its not not possible. A user account can only have one password.

 

[Alejandro85]

I would like to have multiple passwords for a single Windows Login for the following reasons:
1. Need a single user account accessible by multiple users, need the same desktop and folders for all.
2. Would like a unique password for each of the users to track who did what when.

But if you share the same account for many people, you can't track who did what, that's precisely handled by using multiple accounts, so security records are kept based on the login used. If you need this kind of control, you MUST use separate accounts.

A question, why is imperative to share a desktop? The of separate accounts is that each one uses the desktop they like the more regardless of others, and keeps his own documents and configurations independently. If you need to share documents among all users they can always use the built-in "public" folder of Win7 where everyone can read and write by default, or place a specific folder for such usage, so each one gets his own private files plus the shared ones.

 

[sherwint]

Multiple passwords for single login

A PC is used for PowerPoint presentations (an another application like PowerPoint). The presentations are changed weekly. Currently four people have the Login ID and password to log in and run the system.

Recently, someone logged in and did something that completely changed the desktop and also changed the PowerPoint presentation. The only way to recover was to go back to a Restore Point, which solved the problem.

It would have been nice to know who logged in and made the change but since all four people use the same Login ID and password, there is no way to find out who made the change. I was hoping that the Event Log would be able to log the user and/or password but it looks like the user is always N/A anyway, so another beautiful theory ruined by a brutal gang of facts.

 

[mmkarimi]

I know that is possible to have a common user with several username and passwords, in the university every one uses his own id and pass to access to any computer, the same user/pass works on every pcs in university...

I wonder how it is set up, and how they linked computer to the server to log on. I was searching for the answer so I found this forum... does any one know the trick??

 

[Nigsy]

The PCs in your university are basically, dumb terminals, that is, they are just images contained on a server and you are logged to a specific domain which controls your access, also known as thin clients.

This allows you to log on to any terminal on that Domain as you. It's also known as 'Single Sign On'

 

[benjy206]

Yes for that kind of access you need to be set up as a domain. Like we use here in work. But you need a sever for that. Then to track who did what is possible but not legal because you would be having there personel information and password's so I couldn't help you with the tracking info part.

 

[mmkarimi]

The PCs in your university are basically, dumb terminals, that is, they are just images contained on a server and you are logged to a specific domain which controls your access, also known as thin clients.

This allows you to log on to any terminal on that Domain as you. It's also known as 'Single Sign On'

Yes for that kind of access you need to be set up as a domain. Like we use here in work. But you need a sever for that. Then to track who did what is possible but not legal because you would be having there personel information and password's so I couldn't help you with the tracking info part.

that exactly is, but can you tell me how i could have one with about 7 computers at my work space, can you send me a link or describe how or tell me some keywords..

 

[benjy206]

What do you want a link to? Like for a domain set guide or so?

 

[mmkarimi]

a link that describe the way to build this kind of domain based users with win7 or xp so i could construct such accounts on computers at work, is it clear what mean..

 

[benjy206]

You need window server such as 2003/2008 you can't build a domain with xp/7. So if you wanted to to set up a domain you would need to buy windows 2008 or so.

 

[mmkarimi]

thanks benjy, I already have access to win server 2010, but the problem is, I dont know how to organize such user accounts, can you help me with that?

 

[benjy206]

Well first of all you need to set up a domain and connect the computers to the domain. Then you could map a drive on the server to the computers and have all the business data saved on to that. Then everyone can save there presentation's to the server and that way you don't need the same log on to the pc. I don't think you can set up a domain with 2010 as it is an exchange not really a server

 

[mmkarimi]

So i will search for how to set up a domain and how to map a drive,
i'll comment here if there would other problems or find any good article..

 

[benjy206]

How To Set Up A Network Domain

Thats how you can set up a domain, there is a lot of work in it. But that's what you need to do what you want. Sorry I couldn't be any other help to you but that's the only way.

 

[Kari]

Two statements in one post, both wrong:

The PCs in your university are basically, dumb terminals, that is, they are just images contained on a server and you are logged to a specific domain which controls your access, also known as thin clients.

In domain environment you can log in with your domain credentials from any computer which has been joined to domain. It most certainly does not have to be a dumb terminal.

This allows you to log on to any terminal on that Domain as you. It's also known as 'Single Sign On'

That's not what Single Sign On (SSO) means!

SSO is the access control system where system uses only one password, the domain password is also password for other systems and applications the user needs. Signing in to domain sends login information to other systems and applications user needs so that a single login to domain is enough, user does not have to separately login to different systems and applications he/she uses.

A typical SSO environment would be one where user logs in to domain which opens his/her Windows desktop, automatically logs the user to company intranet, and opens Office or Lotus Notes without asking users credentials.

For SSO to work all joined applications and systems have to have the same password. When password to domain expires and is changed it also has to be changed on all SSO systems and applications to match the new domain password.

More: Single sign-on - Wikipedia, the free encyclopedia

Kari

 

[benjy206]

Two statements in one post, both wrong:

The PCs in your university are basically, dumb terminals, that is, they are just images contained on a server and you are logged to a specific domain which controls your access, also known as thin clients.

In domain environment you can log in with your domain credentials from any computer which has been joined to domain. It most certainly does not have to be a dumb terminal.

This allows you to log on to any terminal on that Domain as you. It's also known as 'Single Sign On'

That's not what Single Sign On (SSO) means!

SSO is the access control system where system uses only one password, the domain password is also password for other systems and applications the user needs. Signing in to domain sends login information to other systems and applications user needs so that a single login to domain is enough, user does not have to separately login to different systems and applications he/she uses.

A typical SSO environment would be one where user logs in to domain which opens his/her Windows desktop, automatically logs the user to company intranet, and opens Office or Lotus Notes without asking users credentials.

For SSO to work all joined applications and systems have to have the same password. When password to domain expires and is changed it also has to be changed on all SSO systems and applications to match the new domain password.

More: Single sign-on - Wikipedia, the free encyclopedia

Kari

Yes that is very correct Kari. But isn't that more in the past now? Well is here in our office