Home

Hide generic/unlicensed users from MS Teams

%3CLINGO-SUB%20id%3D%22lingo-sub-401166%22%20slang%3D%22en-US%22%3EHide%20generic%2Funlicensed%20users%20from%20MS%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-401166%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20running%20the%20Teams%20System%20Wide%20msi%20x64%20(or%20x32)%20installer%20we%20see%20the%20following%20Startup%20entry%20called%20%22Program%22%3A%20(See%20attached%20screenshot%20-%20Program.png)%20After%20digging%20through%20the%20registry%2C%20this%20startup%20entry%20appears%20to%20be%20tied%20to%20the%20Teams%20System%20Wide%20installer%3A%20(See%20attached%20screenshot%20-%20Reg-TeamsMachInstallerBeforeUpdate.png)%20Using%20the%20%25ProgramFiles%25%20variable%20we%20attemped%20to%20navigate%20to%20the%20directory%20noted%20in%20the%20reg%20value%2C%20but%20it%20doesn't%20exist%20under%20%22C%3A%5CProgram%20Files%5CTeams%20Installer%22.%20It%20does%20exist%20under%20%22C%3A%5CProgram%20Files%20(x86)%5CTeams%20Installer%22%3A%20(See%20attached%20screenshot%20-%20TeamsEXE_Actual_Location.png)%20And%20if%20we%20change%20the%20Reg%20Value%20noted%20above%20from%20%25ProgramFiles%25%20to%20C%3A%5CProgram%20Files(x86)%3A%20(See%20attached%20screenshot%20-%20RegUpdate.png)%20We%20see%20the%20%22Program%22%20entry%20get%20replaced%20with%20the%20Teams%20program%20under%20Startup%3A%20(See%20attached%20screenshot%20-%20MicrosoftTeams-StartupProgram_AfterRegUpdate.png)%20Now%20this%20doesn't%20appear%20to%20be%20causing%20an%20issue%20running%20the%20app%2C%20but%20I%20fear%20that%20seeing%20a%20%22Generic%22%20Program%20listing%20under%20startup%20my%20lead%20folks%20to%20believe%20there%20is%20an%20issue%20or%20falsely%20report%20as%20malware.%20I%20also%20don't%20know%20if%20manually%20changing%20or%20scripting%20the%20change%20in%20the%20reg%20location%20is%20a%20good%20idea%2C%20as%20it%20may%20cause%20issues%20later%20on%20with%20updating%20the%20app.%20I'm%20hoping%20this%20is%20a%20known%20issue%20or%20someone%20on%20the%20Teams%20Dev%20side%20can%20take%20a%20look%20at%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-401166%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-440079%22%20slang%3D%22en-US%22%3ERe%3A%20Hide%20generic%2Funlicensed%20users%20from%20MS%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-440079%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2395%22%20target%3D%22_blank%22%3E%40Cian%20Allner%3C%2FA%3E%26nbsp%3BNot%20attempting%20to%20block%20access%2C%20just%20simply%20pointing%20out%20that%20the%20listing%20for%20Teams%20in%20startup%20appears%20broken%20by%20showing%20as%20%22Program%22%20instead%20of%20%22Microsoft%20Teams%22.%20The%20reasoning%20for%20wanting%20to%20point%20this%20out%20is%20because%20some%20may%20not%20be%20able%20to%20identify%20what%20the%20blank%20listing%20for%20%22Program%22%20is%20referring%20to%20and%20may%20suspect%20malware.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-401201%22%20slang%3D%22en-US%22%3ERe%3A%20Hide%20generic%2Funlicensed%20users%20from%20MS%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-401201%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I%E2%80%99d%20be%20interested%20in%20the%20overall%20requirement%2C%20access%20to%20Teams%20is%20controlled%20by%20the%20licence%20as%20you%20probably%20know%2C%20so%20unlicensed%20users%20should%20get%20no%20access%20to%20Teams%20in%20the%20first%20place%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fuser-access%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fuser-access%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20want%20to%20control%20startup%2C%20that%20can%20be%20done%20via%20deployment%20%3CSPAN%3E%22noAutoStart%3Dtrue%22%3A%3C%2FSPAN%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fmsi-deployment%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fmsi-deployment%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20want%20to%20block%20installation%20for%20users%20there%20are%20some%20suggestions%20here%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FPrevent-Teams-Windows-App-Installation%2Ftd-p%2F299301%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FPrevent-Teams-Windows-App-Installation%2Ftd-p%2F299301%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGenerally%2C%20I%E2%80%99d%20stay%20away%20from%20the%20registry%2C%20unless%20it%20was%20an%20official%20documented%20procedure%20otherwise%20it%20may%20change%20in%20the%20future%20or%20have%20unexpected%20results%2C%20especially%20with%20upgrades%20and%20what%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
AdamStorm15
New Contributor

After running the Teams System Wide msi x64 (or x32) installer we see the following Startup entry called "Program": (See attached screenshot - Program.png) After digging through the registry, this startup entry appears to be tied to the Teams System Wide installer: (See attached screenshot - Reg-TeamsMachInstallerBeforeUpdate.png) Using the %ProgramFiles% variable we attemped to navigate to the directory noted in the reg value, but it doesn't exist under "C:\Program Files\Teams Installer". It does exist under "C:\Program Files (x86)\Teams Installer": (See attached screenshot - TeamsEXE_Actual_Location.png) And if we change the Reg Value noted above from %ProgramFiles% to C:\Program Files(x86): (See attached screenshot - RegUpdate.png) We see the "Program" entry get replaced with the Teams program under Startup: (See attached screenshot - MicrosoftTeams-StartupProgram_AfterRegUpdate.png) Now this doesn't appear to be causing an issue running the app, but I fear that seeing a "Generic" Program listing under startup my lead folks to believe there is an issue or falsely report as malware. I also don't know if manually changing or scripting the change in the reg location is a good idea, as it may cause issues later on with updating the app. I'm hoping this is a known issue or someone on the Teams Dev side can take a look at this.

2 Replies

Hi, I’d be interested in the overall requirement, access to Teams is controlled by the licence as you probably know, so unlicensed users should get no access to Teams in the first place:

 

https://docs.microsoft.com/en-us/microsoftteams/user-access

 

If you want to control startup, that can be done via deployment "noAutoStart=true":  

 

https://docs.microsoft.com/en-us/microsoftteams/msi-deployment

 

If you want to block installation for users there are some suggestions here:

 

https://techcommunity.microsoft.com/t5/Microsoft-Teams/Prevent-Teams-Windows-App-Installation/td-p/2...

 

Generally, I’d stay away from the registry, unless it was an official documented procedure otherwise it may change in the future or have unexpected results, especially with upgrades and what not.

 

 

 

 

@Cian Allner Not attempting to block access, just simply pointing out that the listing for Teams in startup appears broken by showing as "Program" instead of "Microsoft Teams". The reasoning for wanting to point this out is because some may not be able to identify what the blank listing for "Program" is referring to and may suspect malware. 

Related Conversations
Hiding account information for guests
bfrohnh in Microsoft Teams on
7 Replies