Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

SPS on Shared PC

  Asked By: Jill    Date: Jan 07    Category: Sharepoint    Views: 771

What is the recommended way to handle authenticating multiple users who
share a common logon on a PC so their MySite and document ownership is



8 Answers Found

Answer #1    Answered By: Jennifer Jones     Answered On: Jan 07

The 'common logon' is the AUTHENTICATED user on
the PC. If that is the user who is accessing 'MySite' then there is no way
to distinguish who the individual is who is logged on as the 'common logon'

Answer #2    Answered By: Annie Norris     Answered On: Jan 07

But they are able to authenticate to Outlook Web Access with basic auth,
which allows one user to check his email quickly, then let the next
person on to do the same. I was hoping someone had a similar method for
SPS without forcing the entire company to use basic authentication.
Maybe a new virtual server that points to the same portal but uses

Answer #3    Answered By: Kalyan Pujari     Answered On: Jan 07

But what happens on OWA? They enter the mailbox name and then they enter
their logon  credentials. they are not using the same 'common logon'
credentials to get intpo the OWA.

Answer #4    Answered By: Cheryl Kelley     Answered On: Jan 07

This is just an Internet Explorer setting.
Tools/Internet Options/Security tab. Go to the zone where the portal is
listed and open Custom settings.
All the way down at the bottom of the list is "User
Authentication/Logon/Prompt User for Authentication"
Then every person opening the site will be prompted for his logon  which
does not have to be the same as the desktop (console) session and that
is who he or she is to SPS. Train your users  to close IE before they
walk away from the computer or someone else can continue their session
with their logon session. You may want to adjust the time out on SPS.

Answer #5    Answered By: Titus Sweet     Answered On: Jan 07

Keep in mind that if the protal is in the local internet zone then every web
server that is in the that zone that requires authentication even if IIS is
set for NTLM authentication will require the user to provide their logon
credentials. I not saying that this is wrong but why not just have the
individuals logon  the common  PC with their own account and create a profile
on the PC?

Answer #6    Answered By: Laura Walker     Answered On: Jan 07

The PCs run manufacturing shop floor software 24x7 to track job progress
and it's a pain to logoff the job, logoff the user, logon  as a new user,
and log back on to the job in the shop floor software, just so someone
else can use the portal with their own credentials. And yes, if with
this method SPS starts prompting for credentials for every area or site
change, then that's going to be prohibitive. We may need to provide
some sort of TS solution. I just figured someone else had dealt with
this and had a "best practice" solution.

Answer #7    Answered By: Christop Mcfadden     Answered On: Jan 07

Our solution has been to have auto-logon PCs, and then remove access
rights to the Portal to the users  set to log on to the machines. This
way, the machine comes up automatically, and the users are prompted
when they attempt to access the portal. Luckily, our apps run through
an authentication mechanism, so there's no further prompts past the

It's far from a 'best practice', but it may be something else to consider.

Answer #8    Answered By: Victoria Bell     Answered On: Jan 07

I would not put it in the Local Intranet zone on that particular
computer. I would put it in the Trusted zone which requires
authentication by default.

Profiles do occupy disk space especially if you have lots of people
using the same computer.

Didn't find what you were looking for? Find more on SPS on Shared PC Or get search suggestion and latest updates.