Forum Discussion

DelphinoCons's avatar
DelphinoCons
Copper Contributor
Jun 14, 2021

Teams tries to connect to network drives during start up - and ends up starting really slow

I run Microsoft Teams on MacOS and noticed the following, to much frustration:

 

I have a NAS on my home office network, which is not always connected. When Teams starts up, and the NAS is not connected (also when I'm travelling) it tries (without notification) to connect to this NAS, resulting in a startup time of up to 5 minutes, and 3-6 messages popping up that it cannot connect to the NAS.

It is not only frustrating, but also unnecessary - why would Teams need anything from a network storage location during startup?

 

Anyone who recognises this and knows how to get rid of it? I run on MacOS, so no registry hack solutions please 😉

  • Gmccray's avatar
    Gmccray
    Copper Contributor
    I have exactly the same problem. Is there a solution?
  • sferrari63's avatar
    sferrari63
    Copper Contributor

    Same problem, and same concern.  What is it looking for on that drive?

    • ralftrappp's avatar
      ralftrappp
      Copper Contributor
      That is what fixed it for me:

      - Uninstall Teams (On Mac I used AppCleaner for this to make sure it's really gone)
      - Disable all drives on startup (don't connect any drive on startup)
      - Install Teams again
      - Enable "connect drives at startup" again
  • DS_Resson's avatar
    DS_Resson
    Copper Contributor
    I've been having the same issue for several months now. Makes me very concerned about privacy issues.
    • ralftrappp's avatar
      ralftrappp
      Copper Contributor
      Same here. And have several colleagues cursing teams because of this behavior. Looks like the Microsoft guys either have always perfect network connection to their network drives, don't use home office at all or don't have any network drives in use. Otherwise they would have fixed that in a second.
  • msarangdhar's avatar
    msarangdhar
    Copper Contributor

    DelphinoCons 

     

    Have the same issue at startup, as well as at shutdown.  In fact, Teams locks up and becomes non-responsive trying shutdown if the network drive is not available.  Creepy behavior. 

    • DelphinoCons's avatar
      DelphinoCons
      Copper Contributor

      adam deltinger not right now, but all it says is Unable to connect to delphinosvr, followed by an OK button. Screenshots won’t show more than that, and in fairness I think it’s a clear design/implementation flaw. Teams had no business on that network location, certainly not during startup and login.

Resources