Windows Login question

  • Thread starter Thread starter te_butts
  • Start date Start date
T

te_butts

I was wondering if there is a good way to handle this situation.

I have a user "person1" that is on a domain (this is in a business
environment), and "person2" else needs access to a single program only
accessible from "person1" login. "person2" needs access to this program for
a few hours, and "person1" is obviously concerned about "person2" having
access to "person1" emails, documents etc. "person1" will be out of town.

This program is based on login, and the only person who has access to this
program is "person1".

The option of creating a windows login for "person2" is not available, and
creating a login into this program for "person2" is not an option.

I hope this isn't too confusing.

Thanks
 
"te_butts" <tebutts@discussions.microsoft.com> wrote in message
news:478C6AF8-D5BD-459A-9C9F-636AB0802A1C@microsoft.com...
>I was wondering if there is a good way to handle this situation.
>
> I have a user "person1" that is on a domain (this is in a business
> environment), and "person2" else needs access to a single program only
> accessible from "person1" login. "person2" needs access to this program
> for
> a few hours, and "person1" is obviously concerned about "person2" having
> access to "person1" emails, documents etc. "person1" will be out of town.
>
> This program is based on login, and the only person who has access to this
> program is "person1".
>
> The option of creating a windows login for "person2" is not available, and
> creating a login into this program for "person2" is not an option.
>
> I hope this isn't too confusing.
>
> Thanks

Your question was "I was wondering if there is a good way to handle
this situation.". Seeing that you can't/won't create a login for Person2
and that you can't/won't make the program accessible to Person2,
the answer has to be "No, not under Windows."

Unless you are prepared to ease your restrictions, you will have to
get someone to stand behind Person2 to ensure that he/she is not
up to some mischief.

You could, of course, create a scheduled job that revokes all access
for Person1 to his/her own files during a few fixed hours. However,
such a scheme would be fragile: easy to beat, likely to cause never-
ending troubles. Not recommended.
 
"te_butts" <tebutts@discussions.microsoft.com> wrote in message
news:478C6AF8-D5BD-459A-9C9F-636AB0802A1C@microsoft.com...
>I was wondering if there is a good way to handle this situation.
>
> I have a user "person1" that is on a domain (this is in a business
> environment), and "person2" else needs access to a single program
> only
> accessible from "person1" login. "person2" needs access to this
> program for
> a few hours, and "person1" is obviously concerned about "person2"
> having
> access to "person1" emails, documents etc. "person1" will be out of
> town.
>
> This program is based on login, and the only person who has access
> to this
> program is "person1".

You want person1 to have access and the only user to have access. Yet
you want person2 to have access but refuse to actually define that
person2 by creating an user account for person2. You choose to let
person2 share someone else's account, so you chose to let person2 do
whatever person1 can do. *User* privileges are based on the *user*
account but you want to let more than one person be handled as one
*user*.

The program is based on the login. Well, obviously that means the
program is only allowed to be executed by that particular user
account - and you are letting more than one person login under the
same user account.

> The option of creating a windows login for "person2" is not
> available, and
> creating a login into this program for "person2" is not an option.

Your choice not to give each user their own login. Also your choice
to enforce ridiculous restrictions on each user having their own
account.

> I hope this isn't too confusing.

Nope. People make weird decisions all the time.
 
Back
Top