SOLVED

Shared Computers and Teams use

%3CLINGO-SUB%20id%3D%22lingo-sub-559629%22%20slang%3D%22en-US%22%3EShared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-559629%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20shared%20Windows%20computers%20that%20multiple%20staff%20members%20use.%26nbsp%3B%20Currently%2C%20we%20use%20Skype%20for%20Business%20Client%20on%20these%20computers%20and%20staff%20can%20log%20in%20and%20log%20out%20of%20the%20client%20when%20they%20are%20on%20or%20leaving%20the%20service%20desk%20computer.%26nbsp%3B%20But%20with%20Teams%2C%20it%20is%20my%20understanding%20that%20the%20client%20is%20tied%20to%20a%20single%20Office%20365%20account%20and%20Windows%20user%20profile.%26nbsp%3B%20I%20could%20have%20users%20use%20the%20online%20web%20version%20of%20Teams%20but%20we%20have%20a%20need%20for%20screen%20sharing%20for%20remote%20support%2C%20which%20the%20online%20web%20version%20of%20Teams%20does%20not%20support.%26nbsp%3B%20Given%20these%20variables%2C%20what%20is%20my%20best%20option%20for%20deploying%20Teams%20on%20shared%20Windows%20computers%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-559629%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EShare%20computers%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-559650%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-559650%22%20slang%3D%22en-US%22%3EYeah%2C%20teams%20installs%20in%20the%20user%20profile!%20Only%20the%20RDS%20version%20will%20install%20in%20the%20default%20windows%20installation%20folder!%3CBR%20%2F%3E%3CBR%20%2F%3EI%20suggest%20creating%20separate%20user%20profiles%20in%20windows%20and%20let%20users%20login%20once%20in%20that%20and%20have%20their%20teams%20setup%20instead%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-559658%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-559658%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72542%22%20target%3D%22_blank%22%3E%40adam%20deltinger%3C%2FA%3E%26nbsp%3BMultiple%20user%20profiles%20is%20not%20an%20option%20for%20us%2C%20as%20there%20are%20too%20many%20users%20and%20this%20would%20bog%20down%20Windows%20performance%20significantly.%26nbsp%3B%20I'm%20thinking%20use%20a%20generic%20account%20for%20the%20client%20(just%20to%20have%20remote%20access%20in%20place%20for%20my%20I.T.%20help%20desk)%20and%20individuals%20could%20simply%20use%20the%20online%20web%20version%20for%20collaboration%20specific%20to%20their%20Office%20365%20account.%26nbsp%3B%20Does%20that%20make%20sense%3F%26nbsp%3B%20Is%20there%20a%20better%20mousetrap%20I'm%20not%20thinking%20of%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-559667%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-559667%22%20slang%3D%22en-US%22%3EIt%20sound%20doable!%20Create%20an%20inprivate%20browser%20session%20icon%20on%20the%20desktop%20they%20can%20use%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-559748%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-559748%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20just%20seems%20like%20the%20Teams%20client%20would%20allow%20User%20A%20to%20log%20out%20and%20User%20B%20to%20login.%26nbsp%3B%20Is%20there%20no%20way%20for%20end%20users%20to%20easily%20login%20and%20log%20out%20of%20the%20Teams%20client%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-559841%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-559841%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F338235%22%20target%3D%22_blank%22%3E%40psneathen%3C%2FA%3E%26nbsp%3Bin%20the%20top%20right%20corner%20of%20the%20app%20is%20the%20settings%20icon.%20click%20on%20that%20and%20you'll%20see%20the%20option%20to%20log%20out.%20logging%20out%20immediately%20opens%20up%20the%20log%20in%20window%20for%20the%20next%20user.%20I%20use%20about%205%20different%20accounts%20on%20my%20desktop%20app%20without%20creating%20different%20windows%20profiles.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-559846%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-559846%22%20slang%3D%22en-US%22%3EYeah%20this%20is%20possible%2C%20but%20it%20also%20depends%20on%20your%20environment%20how%20well%20it%20works!%20If%20you%20have%20SSO%20etcetera%20this%20will%20mess%20that%20up!%20Also%20users%20need%20to%20make%20sure%20to%20log%20out%20each%20time%20from%20the%20client%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-559848%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-559848%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F19689%22%20target%3D%22_blank%22%3E%40Kelly%20E%3C%2FA%3E%26nbsp%3BNow%20that%20is%20embarrassing.%26nbsp%3B%20I%20can't%20believe%20I%20missed%20that.%26nbsp%3B%20Thank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-559855%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-559855%22%20slang%3D%22en-US%22%3E%3Aface_with_tears_of_joy%3A%20thought%20you%20tried%20that%20already%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-735438%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-735438%22%20slang%3D%22en-US%22%3E%3CP%3EShared%20computers%20and%20teams.%26nbsp%3B%20With%20teams%20installing%20per%20user%2C%20is%20it%20fair%20to%20say%20that%20it%20also%20periodically%20updates%20per%20user%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20it%20does%20update%20per%20user%2C%20does%20that%20mean%20that%20it%20could%20potentially%20cause%20problems%20for%20users%2C%20during%20a%20call%3F%26nbsp%3B%20Could%20a%20user%20sign%20onto%20the%20shared%20PC%20with%20their%20own%20credentials%2C%20open%20teams%2C%20start%20a%20call%20and%205%20minutes%20into%20find%20the%20call%20dropped%20and%20have%20to%20restart%2C%20due%20to%20an%20update%20that%20has%20occurred%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20curious%20if%20anyone%20else%20has%20had%20this%20issue%20happen%20to%20them%20in%20the%20past%2C%20as%20it's%20only%20an%20unproven%20theory%20based%20on%20some%20feedback%20on%20one%20shared%20PC%20in%20the%20company.%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESam.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1300413%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1300413%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72542%22%20target%3D%22_blank%22%3E%40adam%20deltinger%3C%2FA%3E%26nbsp%3BLike%20the%20idea.%26nbsp%3B%20For%20clients%20that%20have%20hundreds%20of%20staff%20that%20move%20from%20site%20to%20site%20on%20a%20daily%20basis%2C%20it's%20nice%20for%20them%20to%20be%20able%20to%20walk%20up%20to%20any%20unmanaged%2C%20workgroup%20PC%20and%20get%20on%20their%20web%20portals.%26nbsp%3B%20Like%20to%20call%20it%20the%20Kiosk%20model%20to%20staff.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1404110%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1404110%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F338235%22%20target%3D%22_blank%22%3E%40psneathen%3C%2FA%3E%26nbsp%3BI'm%20pretty%20sure%20that%20the%20Teams%20desktop%20client%20caches%20each%20users%20login%20credentials%2C%20so%20you%20only%20need%20to%20know%20the%20username%2Femail%20of%20someone%20that%20previously%20logged%20into%20Teams%20on%20that%20shared%20PC%20profile%2C%20and%20you%20can%20access%20their%20Teams%20account.%20We%20have%20this%20problem%20currently.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1805847%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20Computers%20and%20Teams%20use%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1805847%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F292546%22%20target%3D%22_blank%22%3E%40Gasmanz%3C%2FA%3E%26nbsp%3Bwe%20have%20that%20problem%20too%2C%20it%20is%20a%20very%20bad%20one%20because%20apparently%20you%20cannot%20get%20rid%20of%20an%20account%20that%20correctly%20logged%20in%20in%20the%20past.%3CBR%20%2F%3EWho%20knows%20how%20to%20fix%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

We have shared Windows computers that multiple staff members use.  Currently, we use Skype for Business Client on these computers and staff can log in and log out of the client when they are on or leaving the service desk computer.  But with Teams, it is my understanding that the client is tied to a single Office 365 account and Windows user profile.  I could have users use the online web version of Teams but we have a need for screen sharing for remote support, which the online web version of Teams does not support.  Given these variables, what is my best option for deploying Teams on shared Windows computers?

12 Replies
Highlighted
Yeah, teams installs in the user profile! Only the RDS version will install in the default windows installation folder!

I suggest creating separate user profiles in windows and let users login once in that and have their teams setup instead
Highlighted

@adam deltinger Multiple user profiles is not an option for us, as there are too many users and this would bog down Windows performance significantly.  I'm thinking use a generic account for the client (just to have remote access in place for my I.T. help desk) and individuals could simply use the online web version for collaboration specific to their Office 365 account.  Does that make sense?  Is there a better mousetrap I'm not thinking of?

Highlighted
It sound doable! Create an inprivate browser session icon on the desktop they can use
Highlighted

It just seems like the Teams client would allow User A to log out and User B to login.  Is there no way for end users to easily login and log out of the Teams client?

Highlighted

@psneathen in the top right corner of the app is the settings icon. click on that and you'll see the option to log out. logging out immediately opens up the log in window for the next user. I use about 5 different accounts on my desktop app without creating different windows profiles.

Highlighted
Yeah this is possible, but it also depends on your environment how well it works! If you have SSO etcetera this will mess that up! Also users need to make sure to log out each time from the client
Highlighted
Best Response confirmed by psneathen (New Contributor)
Solution

@Kelly E Now that is embarrassing.  I can't believe I missed that.  Thank you.

Highlighted
:face_with_tears_of_joy: thought you tried that already
Highlighted

Shared computers and teams.  With teams installing per user, is it fair to say that it also periodically updates per user?  

 

If it does update per user, does that mean that it could potentially cause problems for users, during a call?  Could a user sign onto the shared PC with their own credentials, open teams, start a call and 5 minutes into find the call dropped and have to restart, due to an update that has occurred? 

 

I am curious if anyone else has had this issue happen to them in the past, as it's only an unproven theory based on some feedback on one shared PC in the company. :)

 

Thanks 

 

Sam.

Highlighted

@adam deltinger Like the idea.  For clients that have hundreds of staff that move from site to site on a daily basis, it's nice for them to be able to walk up to any unmanaged, workgroup PC and get on their web portals.  Like to call it the Kiosk model to staff. 

Highlighted

@psneathen I'm pretty sure that the Teams desktop client caches each users login credentials, so you only need to know the username/email of someone that previously logged into Teams on that shared PC profile, and you can access their Teams account. We have this problem currently.

Highlighted

@Gasmanz we have that problem too, it is a very bad one because apparently you cannot get rid of an account that correctly logged in in the past.
Who knows how to fix it?