Hi there,
I've already learned quite a bit just from browsing this forum, but I can't find anything to answer this question definitively.
Does Shoretel Connect have any sort of local cache? The reason I'm asking this is that I have a couple individuals across my domain whose Connect application will not connect. They get a basic error message, "Unable to find your server at %servername%". This is not a networking or a routing problem because other individuals in the same office location are fine. The affected users are fine if they login to another PC. Uninstalling, deleting reg keys, deleting any leftover folders, restarting and reinstalling does not help. In one instance I recreated a person's local and roaming profile and it did help, which leads me to believe there is something local that gets 'stuck' in this failure state and prevents the client from connecting. Obviously blowing away profiles is not a sustainable solution to this issue.
Also having issues with IP480 handsets not able to use CAS features, but that's a story for another forum post if our integrator can't help...
I've already learned quite a bit just from browsing this forum, but I can't find anything to answer this question definitively.
Does Shoretel Connect have any sort of local cache? The reason I'm asking this is that I have a couple individuals across my domain whose Connect application will not connect. They get a basic error message, "Unable to find your server at %servername%". This is not a networking or a routing problem because other individuals in the same office location are fine. The affected users are fine if they login to another PC. Uninstalling, deleting reg keys, deleting any leftover folders, restarting and reinstalling does not help. In one instance I recreated a person's local and roaming profile and it did help, which leads me to believe there is something local that gets 'stuck' in this failure state and prevents the client from connecting. Obviously blowing away profiles is not a sustainable solution to this issue.
Also having issues with IP480 handsets not able to use CAS features, but that's a story for another forum post if our integrator can't help...
