SOLVED

Skype Room System V2 device will not auto login to Skype for Business

%3CLINGO-SUB%20id%3D%22lingo-sub-45148%22%20slang%3D%22en-US%22%3ESkype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45148%22%20slang%3D%22en-US%22%3E%3CP%3EI%20recently%20deployed%20a%20SRS%20V2%20device%20and%20it%20will%20not%20auto%20launch%20SfB.%20Is%20there%20a%20way%20to%20achieve%20this%20without%20a%20reimage%20of%20the%20device%3F%20I%20should%20point%20out%20that%20everything%20is%20working%20fine.%20I%20just%20can't%20get%20it%20to%20auto%20launch%20SfB%20after%20the%20device%20is%20powered%20up%20and%20logins%20in%20to%20Windows%2010.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-45148%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeployment%20%26amp%3B%20Operations%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-101927%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-101927%22%20slang%3D%22en-US%22%3EThat%20fixed%20it%20for%20me%20after%20applying%20the%20Creators%20Update.%20Thank%20you!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-101342%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-101342%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Joshua%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20how%20I%20solved%20the%20Invalid%20Registry%20option%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFirst%20the%20problem%20only%20occured%20on%20my%20Skype%20Room%20System%20after%20the%20creators%20update.%20This%20is%20the%20registry%20key%20in%20question%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ecmd%20%2Fq%20%2Fc%20if%20exist%20%22%25SystemDrive%25%5CRigel%5Cx64%5CScripts%5CProvisioning%5Claunch.ps1%22%20(powershell%20-WindowStyle%20Hidden%20-ExecutionPolicy%20Unrestricted%20%25SystemDrive%25%5CRigel%5Cx64%5CScripts%5CProvisioning%5Claunch.ps1)%20else%20(start%20skype-mrx%3A%2F%2F)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20believe%20there%20is%20a%20typo%20in%20this%20line%20and%20it%20should%20actually%20say%20%3CEM%3Estart%20%22skype-mrx%3A%22%3C%2FEM%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20fix%20this%20I%20connected%20a%20keyboard%20and%20mouse%20to%20the%20Logitech%20Smart%20Dock%20(the%20usb%20port%20on%20the%20Surface%20Pro%20should%20be%20fine%20as%20well)%20right%20clicked%20on%20the%20Windows%20button%20and%20ran%20Command%20Prompt%20as%20Administrator.%20The%20Administrator%20password%20is%20sfb.%20From%20command%20prompt%20I%20typed%20%3CEM%3Estart%20%22skype-mrx%3A%22%3C%2FEM%3E.%20The%20command%20ran%20and%20now%20even%20after%20rebooting%20the%20problem%20is%20solved.%20I%20did%20not%20edit%20the%20registry%20key.%20I%20am%20typing%20this%20from%20memory%20as%20I%20did%20not%20expect%20this%20to%20fix%20the%20problem%20so%20I%20was%20fairly%20surprized%20when%20it%20did.%20I%20hope%20this%20helps!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Tyler%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-100875%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-100875%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20you%20found%20a%20resolution%20to%20this%20yet%3F%20%26nbsp%3BWe%20have%20many%20of%20these%2C%20this%20is%20the%20first%20to%20give%20me%20this%20skype-mrx%3A%2F%2F%20error.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-95599%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-95599%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20issue%20started%20happening%20to%20us%20after%20running%20the%20Creators%20Update.%20We%20are%20getting%20an%26nbsp%3Berror%20of%20skype-mrx%3A%2F%2F%26nbsp%3Binvalid%20value%20for%20registry%20when%20using%20the%20Skype%20account%2C%20but%20it%20works%20just%20fine%20under%20the%20Administrator%20account.%20They%20are%20not%20domain%20joined%20machines%20and%20so%20far%20the%20only%20way%20we've%20been%20able%20to%20resolve%20is%20to%20revert%20back%20to%20the%20pre-Creators%20Update%20version.%20I%20hesitate%20to%20run%20the%20update%20again%20in%20the%20event%20that%20it%20breaks%20again%20as%20we%20need%20these%20units%20operational.%20Has%20anyone%20else%20seen%20this%20issue%3F%20Does%20anyone%20have%20any%20ideas%20on%20what%20the%20cause%20may%20be%3F%20Thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-82601%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-82601%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20I%20ran%20into%20this%20too.%26nbsp%3B%20So%20I%20thought%20I%20would%20share%20my%20process%20for%20adding%20a%20machine%20to%20the%20domain.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EThe%20names%20should%20follow%20the%20standard%20server%20naming.%26nbsp%3B%20%3CREMOVED%3E%3C%2FREMOVED%3E%3C%2FLI%3E%3CLI%3EThe%20computer%20account%20must%20be%20first%20pre-created%20in%20the%20domain.%26nbsp%3B%20If%20this%20is%20not%20done%2C%20the%20system%20will%20get%20GPOs%20assigned%20to%20it%2C%20which%20will%20cause%20major%20issues%2C%20so%20make%20sure%20to%20PRE-CREATE%20the%20computer%20account%20at%20%3A%20%3CSTRONG%3EOU%20Path%3C%2FSTRONG%3E%3COL%3E%3CLI%3ERight%20click%20on%20the%20OU%20and%20choose%20new%20computer%3C%2FLI%3E%3CLI%3Eenter%20the%20computer%20name%2C%20all%20lower%20case%3C%2FLI%3E%3CLI%3EFor%20user%20or%20group%20choose%20Domain%20Admins%2C%20or%20another%20user%20account%20to%20add%20it%20the%20system.%26nbsp%3B%20I%20would%20recommend%20using%20your%20regular%20user%20account%20%3CFOR%20why%3D%22%22%3E%3C%2FFOR%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FLI%3E%3CLI%3EGo%20to%20the%20Skype%20Room%20System%3COL%3E%3CLI%3Eon%20the%20lower%20right%20corner%20click%20the%20gear%20icon%3C%2FLI%3E%3CLI%3Eclick%20settings%2C%20the%20password%20for%20Administrator%20is%20%3CREMOVED%3E%3C%2FREMOVED%3E%3C%2FLI%3E%3CLI%3EClick%20on%20Windows%20Settings%20and%20then%20Admin%20Sign%20in%3C%2FLI%3E%3CLI%3EClick%20on%20Administrator%20in%20the%20lower%20left%20corner%20and%20use%20the%20same%20password%3C%2FLI%3E%3CLI%3EFrom%20there%20change%20the%20computer%20name%3COL%3E%3CLI%3EClick%20on%20the%20Folder%20Explorer%3C%2FLI%3E%3CLI%3EExpand%20This%20PC%3C%2FLI%3E%3CLI%3EPres%20and%20hold%20on%20This%20PC%20to%20bring%20up%20the%20context%20menu%3C%2FLI%3E%3CLI%3EChoose%20Properties%3C%2FLI%3E%3CLI%3EUnder%20Computer%20name%20click%20Change%20settings%20on%20the%20right%3C%2FLI%3E%3CLI%3EIn%20the%20Computer%20Name%20Tab%2C%20click%20Change%20to%20rename%20the%20computer%3C%2FLI%3E%3CLI%3EEnter%20the%20computer%20name%2C%20and%20click%20Apply%2FOK%20and%20reboot%20the%20system%3C%2FLI%3E%3C%2FOL%3E%3C%2FLI%3E%3CLI%3EGo%20back%20to%20the%20administrator%20desktop%20like%20you%20did%20above%3COL%3E%3CLI%3EThis%20time%2C%20when%20you%20click%20Change%2C%20set%20the%20Member%20of%20Domain%20to%20%3CREMOVED%3E%20(Make%20sure%20the%20computer%20name%20has%20already%20been%20created%20in%20the%20correct%20OU)%3C%2FREMOVED%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FLI%3E%3CLI%3ERemote%20desktop%20to%20the%20system%20the%20username%20is%20.%5Cadmin%20and%20the%20same%20password%3COL%3E%3CLI%3EBecause%20adding%20the%20computer%20to%20the%20domain%20removes%20the%20auto%20logon%2C%20it%20has%20to%20be%20added%20manually.%26nbsp%3B%20A%20GPO%20will%20not%20add%20it%20correctly.%20Run%20the%20following%20from%20an%20elevated%20command%20prompt%3A%3C%2FLI%3E%3C%2FOL%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3Ereg%20add%20%22HKLM%5CSOFTWARE%5CMicrosoft%5CWindows%20NT%5CCurrentVersion%5CWinlogon%22%20%2Fv%20AutoAdminLogon%20%2Ft%20REG_SZ%20%2Fd%26nbsp%3B1%20%2Ff%3C%2FP%3E%3CP%3Ereg%20add%20%22HKLM%5CSOFTWARE%5CMicrosoft%5CWindows%20NT%5CCurrentVersion%5CWinlogon%22%20%2Fv%20DefualtUserName%20%2Ft%20REG_SZ%20%2Fd%20Skype%20%2Ff%3C%2FP%3E%3CP%3Ereg%20add%20%22HKLM%5CSOFTWARE%5CMicrosoft%5CWindows%20NT%5CCurrentVersion%5CWinlogon%22%20%2Fv%20DefualtPassword%20%2Ft%20REG_SZ%20%2Fd%26nbsp%3B%22%22%20%2Ff%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80865%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80865%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20just%20debugged%20and%20fixed%20an%20issue%20that%20sounds%20exactly%20like%20this%20yesterday.%20It%20will%20occur%20when%20upgrading%20from%203.0.0.0%20to%203.0.2.0.%20Note%2C%20you%20should%20only%20get%203.0.2.0%20if%20you%20are%20enrolled%20in%20our%20selfhost%20program.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20fixed%20it%20and%20are%20validating%20today.%20Expect%20to%20see%20a%203.0.5.0%20build%20posted%20to%20our%20selfhost%20ring%20in%20the%20next%20day%20or%20two.%20If%20that%20looks%20good%2C%20it%20will%20be%20released%20to%20everybody%20towards%20the%20end%20of%20the%20month.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80834%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80834%22%20slang%3D%22en-US%22%3E%3CP%3ESRS%20v3.0.2.0%20failing%20to%20login%20with%20the%20%22Skype%22%20profile%20just%20get%20a%20hung%20app%20experience%20however%20if%20I%20login%20as%20the%20admin%20and%20launch%20the%20app%20all%20works%20fine%3F%20Any%20idea's%20guys%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72134%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72134%22%20slang%3D%22en-US%22%3EHello%20David%2C%3CBR%20%2F%3EThanks%20for%20your%20recos%2C%20Anyway%20the%20detailled%20infos%20are%20on%20the%20technet%20with%20the%20load%20of%20the%20registry%20hive%20with%20the%20nt.dat%20file%20and%20my%20mistake%20was%20with%20the%20quotes%20for%20the%20proxy%20value.%20Once%20removed%20the%20quotes%20everything%20seems%20fine%20for%20the%20SFB%20profile.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-62470%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-62470%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20skype%20app%20works%20fine%20in%20our%20environment%20through%20proxy%2C%20so%20that%20should%20not%20be%20the%20reason.%20Have%20you%20turned%20on%20%22automatic%20proxy%20discovery%22%2C%20or%20have%20you%20set%20the%20proxy%20settings%20via%20gpo%20only%20for%20user%20accounts%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreets%3C%2FP%3E%3CP%3EJ%C3%B6rg%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-62345%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-62345%22%20slang%3D%22en-US%22%3Ebut%20does%20the%20skype%20profile%20even%20support%20the%20proxy%20%3F%20I%20doubt%20it%20because%20only%20my%20admin%20is%20able%20to%20use%20the%20edge%20browser%20with%20proxy%20then%20i'm%20able%20to%20launch%20the%20skype%20app.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20the%20skype%20app%20is%20not%20designed%20to%20go%20trough%20a%20proxy%20natively%2C%20how%20can%20i%20make%20it%20work%20under%20the%20Skype%20profile%20%3F%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20already%20check%20the%20reg%20entries%20mentionned%20in%20your%20previous%20posts%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61843%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61843%22%20slang%3D%22en-US%22%3EHi%20christophe%2C%3CBR%20%2F%3E%3CBR%20%2F%3EAfter%20you%20join%20the%20domain%2C%20please%20verify%20this%20regkey%20is%20set%20as%20follows%3A%20HKLM%5CSOFTWARE%5CMicrosoft%5CWindows%20NT%5CCurrentVersion%5CWinlogon%20AdminAutoLogon%20%3D%20(dword)%201%3CBR%20%2F%3E%3CBR%20%2F%3EJoining%20a%20domain%20has%20a%20tendency%20to%20clear%20this%20reg%20key%20even%20if%20no%20GPO%20policy%20is%20applied%20to%20the%20device.%20I%20recommend%20setting%20up%20a%20separate%20OU%20for%20your%20SRSv2%20device%20and%20creating%20a%20GPO%20to%20ensure%20this%20flag%20is%20set.%3CBR%20%2F%3E%3CBR%20%2F%3EStrongly%20recommend%20your%20domain%20joined%20SRS%20v2%20unit%20continue%20to%20auto%20login%20to%20the%20Skype%20user%20account%20(it%20has%20no%20password).%20For%20normal%20operation%20in%20a%20meeting%20room%2C%20SRS%20v2%20expects%20to%20be%20running%20under%20the%20Skype%20account%20to%20function%20properly%20(for%20example%2C%20the%20Skype%20user%20account%20is%20locked%20down%20security%20policies%20you%20will%20want%20when%20you%20leave%20it%20running%20in%20a%20meeting%20room).%3CBR%20%2F%3E%3CBR%20%2F%3EAdditional%20SRS%20v2%20management%20info%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt790549.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt790549.aspx%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61795%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61795%22%20slang%3D%22en-US%22%3EThanks%20Jorg%2C%20i%20will%20submit%20this%20idea%20as%20it%20becomes%20difficult%20to%20change%20the%20settings%20of%20autologon.%20This%20should%20be%20documented%20on%20technet%20when%20you%20join%20your%20machine%20into%20a%20domain.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61793%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61793%22%20slang%3D%22en-US%22%3E%3CP%3Ewe've%20set%20an%20IP-based%20ruleset%20on%20our%20proxy%20for%20our%20Skype%20Room%20Systems%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreets%3C%2FP%3E%3CP%3EJ%C3%B6rg%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61776%22%20slang%3D%22en-US%22%3ERE%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61776%22%20slang%3D%22en-US%22%3Ewhat%20are%20the%20best%20practices%20when%20you%20join%20a%20domain%20for%20the%20proxy%20authentification%20%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61767%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61767%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20default%20password%20for%20the%20Skype%20account%20is%20%22sfb%22..%20But%20you%20won't%20change%20the%20default%20user%20to%20admin%2C%20the%20Skype%20account%20is%20hardend%20and%20can%20execute%20only%20certain%20prgrams.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61737%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61737%22%20slang%3D%22en-US%22%3EHello%20David%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20joined%20my%20machine%20to%20my%20entreprise%20domain%20but%20i%20cannot%20use%20the%20skype%20default%20account%20with%20the%20autologon%2C%20i%20have%20to%20switch%20everytime%20to%20.%5Cadmin%20to%20get%20internet%20access.%20The%20GPO%20was%20denied%20on%20the%20SRS2%20machine.%20I%20can%20see%20it%20in%20the%20GPO%20report.%20How%20can%20i%20change%20the%20Skype%20default%20account%20to%20admin%20with%20athe%20auto%20launch%20of%20SFB.%20And%20what's%20the%20pwd%20for%20the%20Skype%20account%20%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47900%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47900%22%20slang%3D%22en-US%22%3EThank%20you%20Larry%20for%20the%20reply.%20This%20did%20work%20for%20me.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-46938%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46938%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20still%20autolaunch%26nbsp%3Bthe%20SRS%20Skype%20app%20and%20have%20it%20use%20your%20domain%20account%20for%20Skype.%26nbsp%3B%26nbsp%3B%26nbsp%3B%20At%20the%20device's%26nbsp%3Blogin%20screen%2C%20choose%20other%2C%20then%20enter%20an%20account%20in%20the%20format%20of%20yourmachinename%5Cskype.%26nbsp%3B%20From%20there%20just%20login%20without%20a%20password%20and%20the%20app%20should%20launch%2C%20at%20which%20point%20it%20will%20use%20the%20domain%20credentials%20you've%20loaded%20into%20the%20app%20to%20access%20Skype%20and%20Exchange.%26nbsp%3B%20Hopefully%20this%20may%20save%20you%20from%20re-imaging.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45518%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45518%22%20slang%3D%22en-US%22%3E%3CP%3EDavid%20I%20was%20logging%20in%20with%20a%20domain%20account%20enabled%20for%20SFB.%20I%20will%20probably%20reimage%20this%20SRS%20device%20next%20week%20now%20that%20my%20demo%20to%20my%20manager%20is%20over.%20Thank%20you%20for%20your%20input.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45439%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45439%22%20slang%3D%22en-US%22%3EMake%20sure%20the%20autologin%20is%20signing%20into%20the%20%22Skype%22%20user%20account.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20autolaunch%20behavior%20is%20triggered%20in%3A%3CBR%20%2F%3EHKU%5CSkype%5CSOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CRun%20%22SkypeRoomSystemLaunch%22%20where%20it%20will%20have%20a%20long%20command%20that%20ultimately%20protocol%20launch%20skype-mrx%3A%2F%2F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45435%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45435%22%20slang%3D%22en-US%22%3E%3CP%3EDavid%20thanks%20for%20the%20response.%20I%20was%20able%20to%20verify%20the%20registry%20key.%20There%20was%20another%20key%20missing%20I%20had%20to%20add%20for%20the%20password.%20Now%20my%20SRS%20device%20auto%20logs%20into%20the%20network%20but%20still%20will%20not%20auto%20launch%20SfB.%20Working%20on%20getting%20the%20OU%20setup.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45322%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45322%22%20slang%3D%22en-US%22%3EThanks%20for%20confirming%20J%C3%B6rg!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45320%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45320%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20noticed%20the%20same%20behaviour%20and%20applied%20the%20Fix%26nbsp%3BDavid%20mentionend.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreets%3C%2FP%3E%3CP%3EJ%C3%B6rg%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45311%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45311%22%20slang%3D%22en-US%22%3E%3CP%3EJoining%20the%20domain%20has%20a%20tendency%20to%20clear%20the%20autologon%20reg%20keys%2C%20causing%20the%20system%20to%20be%20stuck%20at%20windows%20login%20screen%20instead%20of%20booting%20up%20SfB.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECan%20you%20verify%20the%20following%20registry%20key%3A%26nbsp%3BHKLM%5CSOFTWARE%5CMicrosoft%5CWindows%20NT%5CCurrentVersion%5CWinlogon%20AdminAutoLogon%20%3D%20(dword)%201%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20this%20fixes%20the%20problem%2C%20I%20recommend%20creating%20a%20separate%20OU%20for%20Rigel%20devices%20and%20applying%20a%20GPO%20to%20that%20OU%20to%20set%20this%20registry%20key.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45209%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45209%22%20slang%3D%22en-US%22%3E%3CP%3EInteresting...I%20mentioned%20the%20above%20b%2Fc%20I%20joined%20the%20device%20to%20the%20domain%20and%20unknowningly%20put%20the%20computer%20object%20in%20an%20OU%20that%20received%20a%20GPO.%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Similar%20to%20your%20issue%20I%20wasnt%20able%20to%20get%20the%20Skype%20profile%20to%20auto%20launch%20and%20had%20to%20reimage%20the%20sfc%20pro%204%20get%20it%20working%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45200%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45200%22%20slang%3D%22en-US%22%3E%3CP%3EDavid%20I%20did%20join%20the%20device%20to%20a%20domain%20but%20put%20it%20in%20a%20non%20GPO%20OU%20in%20AD.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45197%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20V2%20device%20will%20not%20auto%20login%20to%20Skype%20for%20Business%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45197%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20you%20join%20the%20SrS%20device%20to%20a%20domain%3F%26nbsp%3B%26nbsp%3B%26nbsp%3B%20It%20may%20have%20possibly%20pulled%20down%20a%20GPO%20that%20modified%20the%20auto%20launch%20of%20the%20built%20in%20Skype%20profile%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I recently deployed a SRS V2 device and it will not auto launch SfB. Is there a way to achieve this without a reimage of the device? I should point out that everything is working fine. I just can't get it to auto launch SfB after the device is powered up and logins in to Windows 10. 

27 Replies

Did you join the SrS device to a domain?    It may have possibly pulled down a GPO that modified the auto launch of the built in Skype profile

David I did join the device to a domain but put it in a non GPO OU in AD.

Interesting...I mentioned the above b/c I joined the device to the domain and unknowningly put the computer object in an OU that received a GPO.    Similar to your issue I wasnt able to get the Skype profile to auto launch and had to reimage the sfc pro 4 get it working again.

Joining the domain has a tendency to clear the autologon reg keys, causing the system to be stuck at windows login screen instead of booting up SfB.

 

Can you verify the following registry key: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon AdminAutoLogon = (dword) 1

 

If this fixes the problem, I recommend creating a separate OU for Rigel devices and applying a GPO to that OU to set this registry key.

We've noticed the same behaviour and applied the Fix David mentionend.

 

Greets

Jörg

Thanks for confirming Jörg!

David thanks for the response. I was able to verify the registry key. There was another key missing I had to add for the password. Now my SRS device auto logs into the network but still will not auto launch SfB. Working on getting the OU setup.

Best Response confirmed by Rob Scott (Occasional Contributor)
Solution
Make sure the autologin is signing into the "Skype" user account.

The autolaunch behavior is triggered in:
HKU\Skype\SOFTWARE\Microsoft\Windows\CurrentVersion\Run "SkypeRoomSystemLaunch" where it will have a long command that ultimately protocol launch skype-mrx://

David I was logging in with a domain account enabled for SFB. I will probably reimage this SRS device next week now that my demo to my manager is over. Thank you for your input.

You can still autolaunch the SRS Skype app and have it use your domain account for Skype.    At the device's login screen, choose other, then enter an account in the format of yourmachinename\skype.  From there just login without a password and the app should launch, at which point it will use the domain credentials you've loaded into the app to access Skype and Exchange.  Hopefully this may save you from re-imaging.

Thank you Larry for the reply. This did work for me.
Hello David,

I joined my machine to my entreprise domain but i cannot use the skype default account with the autologon, i have to switch everytime to .\admin to get internet access. The GPO was denied on the SRS2 machine. I can see it in the GPO report. How can i change the Skype default account to admin with athe auto launch of SFB. And what's the pwd for the Skype account ?

Thanks

The default password for the Skype account is "sfb".. But you won't change the default user to admin, the Skype account is hardend and can execute only certain prgrams.

what are the best practices when you join a domain for the proxy authentification ?

we've set an IP-based ruleset on our proxy for our Skype Room Systems 

 

Greets

Jörg

Thanks Jorg, i will submit this idea as it becomes difficult to change the settings of autologon. This should be documented on technet when you join your machine into a domain.
Hi christophe,

After you join the domain, please verify this regkey is set as follows: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon AdminAutoLogon = (dword) 1

Joining a domain has a tendency to clear this reg key even if no GPO policy is applied to the device. I recommend setting up a separate OU for your SRSv2 device and creating a GPO to ensure this flag is set.

Strongly recommend your domain joined SRS v2 unit continue to auto login to the Skype user account (it has no password). For normal operation in a meeting room, SRS v2 expects to be running under the Skype account to function properly (for example, the Skype user account is locked down security policies you will want when you leave it running in a meeting room).

Additional SRS v2 management info here: https://technet.microsoft.com/en-us/library/mt790549.aspx
but does the skype profile even support the proxy ? I doubt it because only my admin is able to use the edge browser with proxy then i'm able to launch the skype app.

If the skype app is not designed to go trough a proxy natively, how can i make it work under the Skype profile ?

I have already check the reg entries mentionned in your previous posts

The skype app works fine in our environment through proxy, so that should not be the reason. Have you turned on "automatic proxy discovery", or have you set the proxy settings via gpo only for user accounts?

 

Greets

Jörg