SOLVED
Home

MS Teams MSI?

%3CLINGO-SUB%20id%3D%22lingo-sub-40339%22%20slang%3D%22en-US%22%3EMS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-40339%22%20slang%3D%22en-US%22%3E%3CP%3EWhere%20is%20the%20.msi%26nbsp%3Bhiding%20at%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-40339%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-400913%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-400913%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F36938%22%20target%3D%22_blank%22%3E%40Karl%20Julson%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20someone%20explain%20to%20me%20how%20to%20modify%20the%20Teams%20MSI%20with%20Orca%20to%20use%20the%20following%20option%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Emsiexec%20%2Fi%20Teams_windows_x64.msi%20OPTIONS%3D%22noAutoStart%3Dtrue%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EFor%20the%20life%20of%20me%20I%20cannot%20figure%20out%20where%20to%20add%20this%20option%20in%20the%20msi%20to%20create%20a%20working%20transform%20to%20deploy%20with%20software%20assignment%26nbsp%3BGPO.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-360138%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-360138%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20removed%20it%20from%20appdata.%20Didnt%20helped.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-357070%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-357070%22%20slang%3D%22en-US%22%3E%3CP%3EThat%E2%80%99s%20what%20I%20thought%20but%20turns%20out%20not%20much%20is%20changing%20with%20Teams%20being%20added%20to%20Office%20365%20ProPlus%20for%20new%20installs%20-%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%E2%80%98%3CEM%3ETeams%20is%20installed%20with%20Office%20365%20ProPlus%20in%20the%20same%20way%20that%20Teams%20is%20installed%20if%20you%20use%20the%20%3C%2FEM%3E%3C%2FSPAN%3E%3CEM%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2FMicrosoftTeams%2Fmsi-deployment%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMSI-based%20installer%20for%20Teams%3C%2FA%3E.%20For%20each%20new%20user%20that%20signs%20into%20the%20device%2C%20the%20Teams%20installer%20runs%20and%20the%20Teams%20application%20is%20installed%20in%20the%20user's%20AppData%20folder%E2%80%99%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-357037%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-357037%22%20slang%3D%22en-US%22%3EProbably%20teams%20is%20executed%20from%20appdata.%20If%20so%20you%20need%20to%20remove%20that%20too.%3CBR%20%2F%3ELuckily%20this%20(poor)%20msi%20design%20might%20come%20to%20an%20end%20soon%20as%20Microsoft%20will%20add%20teams%20to%20Office%20365.%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2FDeployOffice%2Fteams-install%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2FDeployOffice%2Fteams-install%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-356475%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-356475%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3CBR%20%2F%3E%3CBR%20%2F%3EWhen%20I%20uninstall%20Teams%20msi%20client%20from%20a%20machine%20it%20gets%20uninstalled.%20But%20signing%20off%20and%20signing%20in%20in%20that%20machine%20we%20can%20Microsoft%20Teams.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253948%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253948%22%20slang%3D%22en-US%22%3E%3CP%3EAgreed.%20I%20even%20attempted%20to%20install%20the%20%22S%20Mode%22%20version%20and%20as%20reviewers%20mentioned%3B%20complete%20fail.%26nbsp%3B%20The%20store%20is%20a%20great%20idea%20if%20and%20only%20if%20Microsoft%20supported%20it%20and%203rd%20parties%20would%20follow.%26nbsp%3B%20So%20many%20major%20players%20and%20yet%20no%20love.%26nbsp%3B%20Then%20again%2C%20Microsoft%20does%20not%20even%20seem%20to%20fully%20back%20MSI%20installers.%26nbsp%3B%20Not%20everyone%20has%20SCCM%20in%20their%20environments.%20MS%20even%20trying%20to%20push%20Intune%20but%20Intune%20only%20seems%20to%20work%20with%20MSI%20only%20packages.%20Total%20headache%20for%20SMB%20admins.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253944%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253944%22%20slang%3D%22en-US%22%3E%3CP%3EOdd%20that%20the%20Teams%20in%20the%20MS%20Store%20is%20only%20for%20Windows%2010%20%22S%22..%3C%2FP%3E%3CP%3EAs%20it's%20getting%20quite%20a%20few%20updates%20it%20would%20be%20a%20nightmare%20to%20have%20to%20deploy%20this%20everywhere%20quite%20often..%26nbsp%3B%20At%20least%20it%20self%20updates%20in%20the%20users%20profile.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253940%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253940%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20there%20been%20any%20update%20on%20Teams%20with%20MSI%20working%3F%20I%20see%20the%20same%20results%20mentioned%20here%20where%20it%20careates%20an%20EXE%20under%20PF(x86)%26nbsp%3B%20but%20no%20shortcut%20or%20anything.%20And%20I%20am%20installing%20the%20x64%20bit%20as%20downloaded.%20This%20would%20not%20be%20an%20issue%2C%20if%20Teams%20was%20available%20in%20the%20Store....%26nbsp%3B%20MS%20needs%20to%20be%20better%20at%20supporting%20their%20Store%20if%20they%20ever%20expect%203rd%20Party%20apps%20to%20show%20up.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-200528%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-200528%22%20slang%3D%22en-US%22%3ECuriosly%2C%20I%20found%20that%20depending%20on%20what%20browser%20I%20use%2C%20I%20either%20get%20.EXE%20files%20or%20.MSI%20files%20from%20those%20links.%20That%20had%20me%20confused%20for%20a%20while.%20Edge%20%3D%20EXE%20files.%20IE%20%3D%20MSI%20files.%20Go%20figure.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-184528%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-184528%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20really%20seems%20like%20an%20afterthought%2C%20and%20in%20addition%2C%20is%20poorly%20executed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20been%20deploying%20the%20standalone%20Teams%20installer%20using%20SCCM's%20per-user%20function%20which%20works%20fairly%20well%20for%20us.%20The%20benefit%20is%20all%20users%20have%20an%20updated%20client%20and%20I%20don't%20have%20to%20bother%20chasing%20new%20versions.%20If%20you%20have%20a%20similar%20environment%20I'd%20recommend%20using%20this%20method%20instead.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EC'mon%20Microsoft!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-184485%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-184485%22%20slang%3D%22en-US%22%3E%3CP%3EMSI%20package%20has%20finally%20been%20released%20by%20Microsoft%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20title%3D%22Teams%20MSI%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fmsi-deployment%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%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%3EHowever%2C%20their%20method%20is%20still%20unconventional%3A%20Installs%20in%20the%20Program%20Files%20dir%20but%20doesn't%20run%20from%20there.%20It%20simply%20copies%20the%20data%20over%20to%20%25AppData%25%20and%20%25localAppData%25%20whenever%20a%20new%20user%20logs%20in%20to%20the%20machine%20that%20has%20the%20Teams%20MSI%20deployed%20to.%20Not%20kosher%2C%20Microsoft.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-184096%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-184096%22%20slang%3D%22en-US%22%3E%3CP%3EInstalling%20the%2064bit%20MSI%20actually%20puts%20the%20Teams.exe%20in%20the%20x86%20program%20files%20folder%20!!%3F!%3F%26nbsp%3B%20Then%20the%20Run%20key%20in%20the%20registry%20is%20trying%20to%20resolve%20to%20%25ProgramFiles%25%20which%20doesn't%20include%20the%20(x86)%3F%3F%3C%2FP%3E%3CP%3ESurely%20the%20MSI%20should%20be%20installing%20the%20%22Teams%20Installer%22%20to%20%22C%3A%5CProgram%20Files%22%20.%3C%2FP%3E%3CP%3EEven%20after%20all%20of%20this%20the%20Run%20key%20doesn't%20install%20Teams%20with%20the%20--checkinstall%20switch%3F%3C%2FP%3E%3CP%3ESeems%20very%20badly%20put%20together..%20All%20it%20does%20is%20place%20the%20installer%20and%20run%20it%20in%20the%20users%20profile%20at%20login...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-182380%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-182380%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20installed%20both%20the%2032%20and%2064%20bit%20versions%20of%20the%20Teams%20MSI%20but%20it%20doesn't%20run%20for%20existing%20or%20new%20users.%26nbsp%3B%20The%20Teams.exe%20file%20is%20installed%20into%20C%3A%5CProgram%20Files%20(x86)%5CTeams%20Installer%5C%20and%20can%20be%20run%20by%20double%20clicking%20it%2C%20but%20there%20is%20no%20auto%20run%20on%20logon.%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3EDavid%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-182371%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-182371%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20several%20times%20to%20install%20teams%20through%20the%20MSI%20installer%20and%20the%20client%20did%20not%20show%20up.%3CBR%20%2F%3EThen%20I%20noticed%20that%20after%20the%20msi%20installation%2C%20only%20new%20user%20profiles%20get%20the%20client%2C%20but%20not%20existing%20user%20profiles.%3CBR%20%2F%3EFor%20me%20that%20looks%20like%20a%20bug%2C%20right%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%2C%3CBR%20%2F%3EOliver%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181657%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181657%22%20slang%3D%22en-US%22%3EThey're%20now%20properly%20signed..%20Apologies%20on%20this.%3CBR%20%2F%3E%3CBR%20%2F%3Ec%3A%5Cusers%5Cadmin%5Cdocuments%5Csigcheck%5CTeams_windows_x64.msi%3A%3CBR%20%2F%3E%20Verified%3A%20Signed%3CBR%20%2F%3E%20Signing%20date%3A%203%3A44%20PM%204%2F10%2F2018%3CBR%20%2F%3E%20Publisher%3A%20Microsoft%20Corporation%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181656%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181656%22%20slang%3D%22en-US%22%3EThey're%20now%20signed%20properly.%3CBR%20%2F%3E%3CBR%20%2F%3Ec%3A%5Cusers%5Cadmin%5Cdocuments%5Csigcheck%5CTeams_windows_x64.msi%3A%3CBR%20%2F%3E%20Verified%3A%20Signed%3CBR%20%2F%3E%20Signing%20date%3A%203%3A44%20PM%204%2F10%2F2018%3CBR%20%2F%3E%20Publisher%3A%20Microsoft%20Corporation%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181655%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181655%22%20slang%3D%22en-US%22%3E%3CP%3EMSI%20files%20are%20now%20properly%20signed%2C%20after%20confirming%20via%20SigCheck%20and%20with%20Engineering%20on%20my%20side.%20Please%20feel%20free%20to%20download%20the%20latest%20version%20which%20has%20this%20fixed.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%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%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fmsi-deployment%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ec%3A%5Cusers%5Cadmin%5Cdocuments%5Csigcheck%5CTeams_windows_x64.msi%3A%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Verified%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Signed%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Signing%20date%3A%26nbsp%3B%26nbsp%3B%203%3A44%20PM%204%2F10%2F2018%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Publisher%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Microsoft%20Corporation%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178077%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178077%22%20slang%3D%22en-US%22%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%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fmsi-deployment%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-176663%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-176663%22%20slang%3D%22en-US%22%3E%3CP%3EApologies%20Karl%2C%20I've%20updated%20my%20post%20to%20include%20the%20link%20to%20the%20official%20Teams%20document%20repository%20which%20has%20both%2C%20rather%20than%20just%20linking%20them%20directly.%20I'm%20not%20aware%20of%20any%20other%20download%20location%20other%20than%20the%20direct%20links%20available%20from%20within%20that%20article%20at%20this%20time.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EKind%20regards%3CBR%20%2F%3EBen%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-176553%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-176553%22%20slang%3D%22en-US%22%3E%3CP%3EI%20wouldn't%20touch%20the%20files%20from%20those%26nbsp%3Bauto%20download%20links%26nbsp%3Bwith%20a%2010%20foot%20pole.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-176414%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-176414%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20MSI's%20are%20not%20signed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-176404%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-176404%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20per%20the%20update%20to%20the%20Teams%20documentation%20on%2021%2F03%2F2018%2C%20these%20are%20now%20available%3B%3C%2FP%3E%0A%3CP%3E32-bit%3B%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fteams32bitmsi%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fteams32bitmsi%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E64-bit%3B%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fteams64bitmsi%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fteams64bitmsi%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3ELinks%20to%20both%20are%20available%20on%20the%20official%20Teams%20Document%20repository%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fmsi-deployment%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EKind%20regards%3CBR%20%2F%3EBen%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172574%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172574%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20looks%20like%20it%20is%20on%20their%20radar%20and%20they%20are%20working%20on%20it.%20Here%20is%20a%20link%20to%20the%20request%20on%20the%20Microsoft%20Teams%20forum%3A%20%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F17380159-improve-install-options-install-for-all-users-an%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F17380159-improve-install-options-install-for-all-users-an%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHopefully%20an%20MSI%20package%20is%20coming%20soon.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-154595%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-154595%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENoting%20that%20stateless%20means%20staff%20logon%20to%20a%20different%20VDI%20at%20each%20logon.%20How%20will%20the%20auto%20update%20part%20work%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-154176%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-154176%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEasy%20to%20deploy.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1.%26nbsp%3BRepackage%20teams%20from%20user%20directory%3C%2FP%3E%0A%3CP%3E2.%20Set%20package%20for%20all%20users%2C%20copy%20fro%20users.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E3.%20Set%20firewall%20rule%20dynamic%20for%20each%20user.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E4.%20MS%20Teams%20will%20update%20it%20itself.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E5.%20Configure%20required%20configuration%2C%20hotkeys%20as%20example.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20same%20for%20uninstall.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-154008%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-154008%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20how%20do%20we%20install%20Teams%20on%20a%20stateless%20VDI%20desktops%3F%20Trying%20to%20rollout%20to%2015%2C000%20staff.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134957%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134957%22%20slang%3D%22en-US%22%3EI%20use%20the%20same%20detection.%20On%20testing%20the%20detection%20failed.%20When%20I%20manually%20looked%2C%20the%20registry%20settings%20was%20there.%20The%20solution.%20I%20used%20an%20installer%20script.%20After%20running%20Teams%20setup%2C%20the%20script%20has%20a%20loop%20to%20detect%20the%20registry%20key.%20When%20detected%20the%20loop%20exits.%20That%20solution%20maked%20SCCM%20happy.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134884%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134884%22%20slang%3D%22en-US%22%3E%3CP%3EI%20use%20the%20HKCU%5CSoftware%5CMicrosoft%5CWindows%5CCurrentVersion%5CUninstall%5CTeams%20key%26nbsp%3Bfor%20detection%20in%20SCCM%2C%20deployed%20for%20the%20logged%20on%20user.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-131896%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-131896%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20need%20to%20revisit%20your%20batch%20file.%20If%20you%20uninstall%20Microsoft%20Teams%2C%20the%20file%20you%20use%20for%20detection%20is%20still%20on%20disk%2C%20along%20with%20a%20.dead%20file.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-116402%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-116402%22%20slang%3D%22en-US%22%3E%3CP%3EI%20would%20say%2C%20that%20yes%2C%20it%20looks%20that%20way.%20I%20am%20using%20the%20Pro%20version.%20If%20you%20can't%20deploy%20it%20as%20the%20logged%20on%20user%2C%20it%20won't%20work.%20The%20install%20does%20not%20require%20admin%20rights%20so%20any%20user%20can%20install%20on%20their%20own.%20Not%20sure%20that%20helps%20you%20but%20that%20is%20all%20I%20have%20left%20to%20offer%20other%20than%20upgrading%20to%20PDQ%20Pro.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-116398%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-116398%22%20slang%3D%22en-US%22%3E%3CP%3EI%20saw%20it%20but%20it's%20dimmed%20and%20said%20that%20only%20available%20in%20Pro%20and%20Enterprise%20edition%3F%20So%2C%20it%20means%20i%20cant%20use%20PQD%20FREE%20Edition%20to%20deploy%20Teams%3F%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20523px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F22157iF38FA1E372FE066E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%221.png%22%20title%3D%221.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-116365%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-116365%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20you%20deploy%20it%2C%20select%20Logged%20On%26nbsp%3BUser%20for%20the%20Run%20As%20setting%20and%20you%20should%20be%20all%20set.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-116360%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-116360%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Thet%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Teams%20installs%26nbsp%3Bonly%20for%20the%26nbsp%3Baccount%20installing%20it.%20If%20you%20would%20log%20into%20that%20PC%20with%20the%20Domain%20Administrator%20(not%20recommended)%20you%20would%20see%20Teams%20installed.%20Therefore%20you%20have%20to%20run%20the%20install%20as%20the%20user%20that%20will%20use%20Teams.%20This%20fact%20is%20the%20point%20that%20this%20threads%20exists.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20look%20further%20up%20this%20thread%20there%20is%20method%20via%20Group%20Policy%20to%20check%20to%20see%20if%20Teams%20is%20installed%20and%2C%20if%20not%2C%20install%20it%20for%20the%20logged%20in%20user.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-116189%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-116189%22%20slang%3D%22en-US%22%3E%3CP%3EI%20tried%20to%20deploy%20Microsoft%20Teams%20using%20PQD%20as%20follow%2C%20but%20my%20PC%20is%20not%20getting%20installed%3F%20I%20am%20using%20PQD%20FREE%20edition%2C%20used%20-s%20for%20a%20silent%20installation%20and%20configure%20as%20follow%20N%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETarget%20PC%20is%20domain%20joined%20and%20using%20a%20domain%20administrator%20account%20to%20install.%20The%20result%20panel%20showed%20that%20the%20deployment%20is%20successful%20but%20when%20I%20checked%20the%20target%20PC%2C%20it's%20not%20installed%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20776px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F22120i954EA66EB85E3BD4%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%225.png%22%20title%3D%225.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20725px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F22121i447BE034EB889B48%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%226.png%22%20title%3D%226.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-116062%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-116062%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20isn't%20very%20IT%20admin%20friendly.%20That%20said%2C%20I%20was%20able%20to%20deploy%20it%20with%20PDQ%20Delpoy%20using%20Teams_windows_x64.exe%20using%20the%20-s%20command.%20FWIW%2C%20it%20does%20not%20require%20Admin%20rights%20to%20install%20and%20it%20is%20really%20just%20a%20custom%20interface%20for%20SharePoint.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68567%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68567%22%20slang%3D%22en-US%22%3ERunning%20this%20app%20in%20a%20virtual%20desktop%20environment%20looks%20like%20a%20non-starter%20as%20well.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68310%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68310%22%20slang%3D%22en-US%22%3E%3CP%3ESven%2C%20looks%20at%20Ian's%20post%20above%20for%20installation%20via%20Group%20Policy.%20It%20works%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAgreed%20that%20they%20should%20have%20an%20MSI.%20You%20will%20find%20that%20this%20product%20is%20not%20very%20IT%20administration%20friendly%20overall.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68309%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68309%22%20slang%3D%22en-US%22%3E%3CP%3ELooks%20like%20some%20sort%20of%20nupkg%20package%20that%20is%20installed%26nbsp%3Bindividually%20for%20every%20user%20(userhome%2Fappdata).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20deploying%20this%20package%20with%20Intune%20and%20failed.%20It%20got%20installed%20but%20for%20user%20%22SYSTEM%22%20because%20everything%20in%20Intune%20is%20silently%20installed%20in%20SYSTEM%20context.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20already%20had%20this%20issues%20with%20Dynamics%20CRM%20Plugin%20and%20that%20unavoidable%20Eula%20thing.%20Come%20on%20Microsoft%2C%20you%20can%20do%20this%20better.%20Enterprise%20needs%20.msi%20for%20easy%20deployment%20over%20MDM%20or%20Group%20Policy.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67815%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67815%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20deployed%20in%20my%20enviroment%20through%20sccm%20by%20using%20detection%20method.%20It%20worked%20finee.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fsccmtitbits.blogspot.in%2F2017%2F05%2Fdeploying-microsoft-teams-through-sccm.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fsccmtitbits.blogspot.in%2F2017%2F05%2Fdeploying-microsoft-teams-through-sccm.html%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-62596%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-62596%22%20slang%3D%22en-US%22%3EYou%20wont%20be%20able%20to%20disable%20updates%2C%20Teams%20changes%20regularly%20at%20the%20backend%2C%20the%20client%20needs%20to%20be%20kept%20very%20much%20up%20to%20date%20in%20order%20to%20connect.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-62592%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-62592%22%20slang%3D%22en-US%22%3E%3CP%3EHI%2C%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20guide%20me%20how%20you%20deployed%20MS%20Team%20through%20SCCM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%26nbsp%3B%3C%2FP%3E%3CP%3EKush%20Kumar%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F40344%22%20target%3D%22_blank%22%3E%40Zigurds%20Kr%C4%93sli%C5%86%C5%A1%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20to%20deploy%26nbsp%3BMS%20Teams%20via%20SCCM%202012%20as%20MSI%20or%20APPV.%3C%2FP%3E%3CP%3EAs%20far%20now%20have%20founs%20solution%20how%20to%20deploy%20application%20for%20users.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20%26nbsp%3Bis%20there%20is%20an%20option%20to%20disable%20auto%20update%2C%20notification%20for%20new%20version's%20%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%26nbsp%3B%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-46197%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46197%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20to%20deploy%26nbsp%3BMS%20Teams%20via%20SCCM%202012%20as%20MSI%20or%20APPV.%3C%2FP%3E%3CP%3EAs%20far%20now%20have%20founs%20solution%20how%20to%20deploy%20application%20for%20users.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20%26nbsp%3Bis%20there%20is%20an%20option%20to%20disable%20auto%20update%2C%20notification%20for%20new%20version's%20%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-40818%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-40818%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3CBR%20%2F%3EI%20have%20deployed%20teams%20to%20all%20users%20last%20week%20like%20this.%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20make%20a%20share%20map%20on%20the%20server%20that%20is%20accessible%20for%20everyone%2C%20with%20teams%20installer.exe%20and%20a%20installer.bat%3CBR%20%2F%3EIn%20the%20installer.bat%20you%20enter%3A%3CBR%20%2F%3E%3CBR%20%2F%3EIF%20EXIST%20%22C%3A%5CUsers%5C%25username%25%5CAppData%5CLocal%5CMicrosoft%5CTeams%5CUpdate.exe%22%20GOTO%20end%3CBR%20%2F%3E%5C%5Cshared%20path%5CTeams_windows_x64.exe%20--silent%3CBR%20%2F%3E%3Aend%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20save%20the%20.bat%3CBR%20%2F%3ENow%20you%20add%20the%20script%20as%20a%20Logon%20script%20under%20User%20Configuration%20in%20a%20Group%20policy.%3CBR%20%2F%3EAnd%20add%20Script%20Parameters%20%2FS%3CBR%20%2F%3E%3CBR%20%2F%3E%5C%5Cshared%20path%5Cinstall%20teams.bat%3CBR%20%2F%3E%2FS%3CBR%20%2F%3E%3CBR%20%2F%3ENow%20the%20script%20checks%20if%20Teams%20is%20already%20installed%20and%20if%20not%20it%20installs%20Teams%20silently.%3CBR%20%2F%3EHope%20this%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-40684%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-40684%22%20slang%3D%22en-US%22%3ETrue%2C%20unfortunately%20no%20MSI's%20yet.%20Do%20you%20use%20the%20native%20GPO%20deployment%20method%20in%20AD%20or%20are%20you%20using%20something%20else%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-40645%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-40645%22%20slang%3D%22en-US%22%3E%3CP%3EPeople%20really%20need%20an%20MSI%20so%20they%20can%20deploy%20from%20AD.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-40353%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-40353%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20.exe%20is%20available%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fteams.microsoft.com%2Fdownloads%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fteams.microsoft.com%2Fdownloads%3C%2FA%3E%3C%2FP%3E%3CP%3EDoes%20that%20help%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-442601%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-442601%22%20slang%3D%22en-US%22%3EI%20know%20this%20is%20early%20days%20in%20the%20new%20version%20of%20edge%2C%20but%20if%20we%20are%20going%20to%20deploy%20it%20to%20an%20organisation%2C%20we%20are%20going%20to%20need%20an%20msi%20we%20can%20deploy%20via%20sccm%20and%20upgrade%20on%20the%206%20weekly%20release%20cycle.%20We'll%20also%20need%20gpo%20to%20control%20and%20the%20ability%20to%20force%20ie11%20via%20an%20Enterprise%20mode%2F%20legacy%20browse%20equivalent%20for%20our%20old%20legacy%20apps%20that%20only%20run%20in%20ie8%20mode.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-442618%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-442618%22%20slang%3D%22en-US%22%3EHi!%3CBR%20%2F%3EHave%20you%20read%20this%20doc%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fmsi-deployment%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fmsi-deployment%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-442641%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20MSI%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-442641%22%20slang%3D%22en-US%22%3ENo%2C%20sorry%20I%20thought%20I%20was%20searching%20(%20on%20a%20phone%20)%20the%20edge%20forums%20that%20I%20just%20joined%20and%20ended%20up%20with%20in%20teams%3C%2FLINGO-BODY%3E
Karl Julson
Occasional Contributor

Where is the .msi hiding at?

49 Replies

The .exe is available here: https://teams.microsoft.com/downloads

Does that help?

People really need an MSI so they can deploy from AD. 

True, unfortunately no MSI's yet. Do you use the native GPO deployment method in AD or are you using something else?
Solution

Hi,
I have deployed teams to all users last week like this.

You make a share map on the server that is accessible for everyone, with teams installer.exe and a installer.bat
In the installer.bat you enter:

IF EXIST "C:\Users\%username%\AppData\Local\Microsoft\Teams\Update.exe" GOTO end
\\shared path\Teams_windows_x64.exe --silent
:end

You save the .bat
Now you add the script as a Logon script under User Configuration in a Group policy.
And add Script Parameters /S

\\shared path\install teams.bat
/S

Now the script checks if Teams is already installed and if not it installs Teams silently.
Hope this helps.

Hi, 

 

Looking to deploy MS Teams via SCCM 2012 as MSI or APPV.

As far now have founs solution how to deploy application for users. 

 

But  is there is an option to disable auto update, notification for new version's ? 

 

Thanks. 

HI, 

Please guide me how you deployed MS Team through SCCM.

 

Thanks 

Kush Kumar


@Zigurds Krēsliņš wrote:

Hi, 

 

Looking to deploy MS Teams via SCCM 2012 as MSI or APPV.

As far now have founs solution how to deploy application for users. 

 

But  is there is an option to disable auto update, notification for new version's ? 

 

Thanks. 


 

You wont be able to disable updates, Teams changes regularly at the backend, the client needs to be kept very much up to date in order to connect.

I have deployed in my enviroment through sccm by using detection method. It worked finee. 

 

http://sccmtitbits.blogspot.in/2017/05/deploying-microsoft-teams-through-sccm.html

 

Looks like some sort of nupkg package that is installed individually for every user (userhome/appdata).

 

I tried deploying this package with Intune and failed. It got installed but for user "SYSTEM" because everything in Intune is silently installed in SYSTEM context.

 

I already had this issues with Dynamics CRM Plugin and that unavoidable Eula thing. Come on Microsoft, you can do this better. Enterprise needs .msi for easy deployment over MDM or Group Policy.

 

Sven, looks at Ian's post above for installation via Group Policy. It works well.

 

Agreed that they should have an MSI. You will find that this product is not very IT administration friendly overall.

Running this app in a virtual desktop environment looks like a non-starter as well.

It isn't very IT admin friendly. That said, I was able to deploy it with PDQ Delpoy using Teams_windows_x64.exe using the -s command. FWIW, it does not require Admin rights to install and it is really just a custom interface for SharePoint.

I tried to deploy Microsoft Teams using PQD as follow, but my PC is not getting installed? I am using PQD FREE edition, used -s for a silent installation and configure as follow N

 

Target PC is domain joined and using a domain administrator account to install. The result panel showed that the deployment is successful but when I checked the target PC, it's not installed?

 

Any ideas? 

 

5.png

 

6.png

 

Hello Thet,

 

The Teams installs only for the account installing it. If you would log into that PC with the Domain Administrator (not recommended) you would see Teams installed. Therefore you have to run the install as the user that will use Teams. This fact is the point that this threads exists.

 

If you look further up this thread there is method via Group Policy to check to see if Teams is installed and, if not, install it for the logged in user.

When you deploy it, select Logged On User for the Run As setting and you should be all set.

I saw it but it's dimmed and said that only available in Pro and Enterprise edition? So, it means i cant use PQD FREE Edition to deploy Teams?1.png

I would say, that yes, it looks that way. I am using the Pro version. If you can't deploy it as the logged on user, it won't work. The install does not require admin rights so any user can install on their own. Not sure that helps you but that is all I have left to offer other than upgrading to PDQ Pro.

You need to revisit your batch file. If you uninstall Microsoft Teams, the file you use for detection is still on disk, along with a .dead file.

 

I use the HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall\Teams key for detection in SCCM, deployed for the logged on user.

I use the same detection. On testing the detection failed. When I manually looked, the registry settings was there. The solution. I used an installer script. After running Teams setup, the script has a loop to detect the registry key. When detected the loop exits. That solution maked SCCM happy.

So how do we install Teams on a stateless VDI desktops? Trying to rollout to 15,000 staff. 

Hi, 

 

Easy to deploy. 

 

1. Repackage teams from user directory

2. Set package for all users, copy fro users. 

3. Set firewall rule dynamic for each user. 

4. MS Teams will update it itself. 

5. Configure required configuration, hotkeys as example. 

 

The same for uninstall. 

 

Noting that stateless means staff logon to a different VDI at each logon. How will the auto update part work?

It looks like it is on their radar and they are working on it. Here is a link to the request on the Microsoft Teams forum: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/17380159-improve-install-optio...

 

Hopefully an MSI package is coming soon.

Highlighted

As per the update to the Teams documentation on 21/03/2018, these are now available;

32-bit; http://aka.ms/teams32bitmsi

64-bit; http://aka.ms/teams64bitmsi

Links to both are available on the official Teams Document repository here.

 

Kind regards
Ben

 

The MSI's are not signed.

I wouldn't touch the files from those auto download links with a 10 foot pole.

Apologies Karl, I've updated my post to include the link to the official Teams document repository which has both, rather than just linking them directly. I'm not aware of any other download location other than the direct links available from within that article at this time.

 

Kind regards
Ben

MSI files are now properly signed, after confirming via SigCheck and with Engineering on my side. Please feel free to download the latest version which has this fixed. 

 

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

 

c:\users\admin\documents\sigcheck\Teams_windows_x64.msi:
        Verified:       Signed
        Signing date:   3:44 PM 4/10/2018
        Publisher:      Microsoft Corporation

They're now signed properly.

c:\users\admin\documents\sigcheck\Teams_windows_x64.msi:
Verified: Signed
Signing date: 3:44 PM 4/10/2018
Publisher: Microsoft Corporation
They're now properly signed.. Apologies on this.

c:\users\admin\documents\sigcheck\Teams_windows_x64.msi:
Verified: Signed
Signing date: 3:44 PM 4/10/2018
Publisher: Microsoft Corporation

Hi,

 

I tried several times to install teams through the MSI installer and the client did not show up.
Then I noticed that after the msi installation, only new user profiles get the client, but not existing user profiles.
For me that looks like a bug, right?

Thanks,
Oliver

We have installed both the 32 and 64 bit versions of the Teams MSI but it doesn't run for existing or new users.  The Teams.exe file is installed into C:\Program Files (x86)\Teams Installer\ and can be run by double clicking it, but there is no auto run on logon.

Thanks

David

Installing the 64bit MSI actually puts the Teams.exe in the x86 program files folder !!?!?  Then the Run key in the registry is trying to resolve to %ProgramFiles% which doesn't include the (x86)??

Surely the MSI should be installing the "Teams Installer" to "C:\Program Files" .

Even after all of this the Run key doesn't install Teams with the --checkinstall switch?

Seems very badly put together.. All it does is place the installer and run it in the users profile at login...

MSI package has finally been released by Microsoft:

 

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

 

However, their method is still unconventional: Installs in the Program Files dir but doesn't run from there. It simply copies the data over to %AppData% and %localAppData% whenever a new user logs in to the machine that has the Teams MSI deployed to. Not kosher, Microsoft.

This really seems like an afterthought, and in addition, is poorly executed.

 

I've been deploying the standalone Teams installer using SCCM's per-user function which works fairly well for us. The benefit is all users have an updated client and I don't have to bother chasing new versions. If you have a similar environment I'd recommend using this method instead.

 

C'mon Microsoft!

Curiosly, I found that depending on what browser I use, I either get .EXE files or .MSI files from those links. That had me confused for a while. Edge = EXE files. IE = MSI files. Go figure.

Has there been any update on Teams with MSI working? I see the same results mentioned here where it careates an EXE under PF(x86)  but no shortcut or anything. And I am installing the x64 bit as downloaded. This would not be an issue, if Teams was available in the Store....  MS needs to be better at supporting their Store if they ever expect 3rd Party apps to show up. 

Odd that the Teams in the MS Store is only for Windows 10 "S"..

As it's getting quite a few updates it would be a nightmare to have to deploy this everywhere quite often..  At least it self updates in the users profile.

Agreed. I even attempted to install the "S Mode" version and as reviewers mentioned; complete fail.  The store is a great idea if and only if Microsoft supported it and 3rd parties would follow.  So many major players and yet no love.  Then again, Microsoft does not even seem to fully back MSI installers.  Not everyone has SCCM in their environments. MS even trying to push Intune but Intune only seems to work with MSI only packages. Total headache for SMB admins. 

Hello,

When I uninstall Teams msi client from a machine it gets uninstalled. But signing off and signing in in that machine we can Microsoft Teams.

Probably teams is executed from appdata. If so you need to remove that too.
Luckily this (poor) msi design might come to an end soon as Microsoft will add teams to Office 365.
https://docs.microsoft.com/en-gb/DeployOffice/teams-install

That’s what I thought but turns out not much is changing with Teams being added to Office 365 ProPlus for new installs -

 

Teams is installed with Office 365 ProPlus in the same way that Teams is installed if you use the MSI-based installer for Teams. For each new user that signs into the device, the Teams installer runs and the Teams application is installed in the user's AppData folder’

 

 

I have removed it from appdata. Didnt helped.

@Karl Julson 

 

Can someone explain to me how to modify the Teams MSI with Orca to use the following option:

 

msiexec /i Teams_windows_x64.msi OPTIONS="noAutoStart=true"

 

For the life of me I cannot figure out where to add this option in the msi to create a working transform to deploy with software assignment GPO. 

I know this is early days in the new version of edge, but if we are going to deploy it to an organisation, we are going to need an msi we can deploy via sccm and upgrade on the 6 weekly release cycle. We'll also need gpo to control and the ability to force ie11 via an Enterprise mode/ legacy browse equivalent for our old legacy apps that only run in ie8 mode.
No, sorry I thought I was searching ( on a phone ) the edge forums that I just joined and ended up with in teams
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
30 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies