Lync for mac 2013 chrome the website sent back unusal

#LYNC FOR MAC 2013 CHROME THE WEBSITE SENT BACK UNUSAL WINDOWS#

The solution to eliminate the delay is rather simple вЂ“ monitor the System Event Log for EventID 5074, examine the event description for which Application Pool was just recycled, and fire up Scheduled Task to execute PS script which will simulate real meeting join request. Reports of type вЂњIt took forever to join the meeting this morningвЂќ were pouring in and frustration was growing fast. Because the pool web services are Hardware Load Balanced, there is great chance that unique user would hit pool member where the Application Pool was just recycled and expertise 22+ seconds delay. This fact might cause inconvenience under certain circumstances вЂ“ in my case a very large front end pool (nine pool members) and only 50 pilot users on this pool. In reality, it takes about 22 seconds for the very first meeting join request to be served after Application Pool Recycle. However, Meeting Join request requires extensive server side processing, not discussed in this article. Under normal circumstances, had we had a request for simple web page as, user would not experience visible delay because there is no complexity in assembling and serving this page. NET reloaded and we site is back serving requests. When the Application Pool recycles, all items in the memory are released, a new w3wp process is created, configuration read and applied. The web sites (Internal or External) and Virtual Directories within the sites are driven by IIS Worker Process and are logically defined within IIS Application Pools.

#LYNC FOR MAC 2013 CHROME THE WEBSITE SENT BACK UNUSAL WINDOWS#

Client then sends new GET request with destination Web Service of the pool where the meeting will be hosted and meeting join completes.ДЄs Lync server is installed on Windows Server, HTTP requests are served by Internet Information Services (IIS).

When user click Lync meeting link in format, the request is processed by Director Pool member (if Simple URL points to Director), where after Meeting Discovery, Director Web Service will respond with вЂњ301 Moved permanentlyвЂќ to the original request.

In this article I will explain the background of the вЂњissueвЂќ and describe possible solution.

A pattern was not observed (although there is one, just not obvious at first) вЂ“ it would happen to random users, at random time, joining different meeting IDвЂ™s on different pools. Users from the pilot (50 people) group would report prolonged (up to 30 seconds) delay between the splash screen and the actual Lync Meeting join. Recently IвЂ™ve worked with large enterprise customer on troubleshooting strange issue with Lync Meeting join.

Lync for mac 2013 chrome the website sent back unusal