tag:blogger.com,1999:blog-7510536084528411099.comments2022-12-24T05:34:36.368-05:00Mastering Microsoft UCAnonymousnoreply@blogger.comBlogger22125tag:blogger.com,1999:blog-7510536084528411099.post-23895121362876509672015-07-14T10:24:32.284-04:002015-07-14T10:24:32.284-04:00Mark,
Thanks for following up. That was going to ...Mark,<br /><br />Thanks for following up. That was going to be my suggestion based on the changes Kemp has made. There was some contention around the interpretations of the previous RFC between Microsoft and Kemp. This was also impacting Exchange in a Hybrid/migration scenario, hence the new options available in 7.1.<br /><br />Glad you got it sorted out!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-75307482201024310692015-07-13T15:09:02.991-04:002015-07-13T15:09:02.991-04:00"Ignore Continue-100" option has been ch..."Ignore Continue-100" option has been changed to "RFC-7231 Compliant" option as of version 7.1Anonymoushttps://www.blogger.com/profile/08464610348896549179noreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-64067216943266797652015-07-13T14:45:19.824-04:002015-07-13T14:45:19.824-04:00Any idea why Ignore Continue-100 is not a selectab...Any idea why Ignore Continue-100 is not a selectable option in KEMP version 7.1-26-15?<br />Is there another option that can be selected in order to fix this problem?<br /><br />Choices are RFC-2616 Compliant, Require 100-Continue, RFC-7231 Compliant.<br /><br />Thank you.Anonymoushttps://www.blogger.com/profile/08464610348896549179noreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-1195031005986467502014-02-07T03:24:18.303-05:002014-02-07T03:24:18.303-05:00Thank You!
Great help while I got stuck in the sam...Thank You!<br />Great help while I got stuck in the same situation doing Lync 2010 update. Cheers :-)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-36185112692635680572013-11-16T08:52:01.182-05:002013-11-16T08:52:01.182-05:00You are my hero!!
Was searching the web and logs e...You are my hero!!<br />Was searching the web and logs etc for hours and could not find it.<br />Until I hit your blog because I found the right error code and googled it.<br />I applied KB2809243 this morning and now facing the problem with Edge Access service not starting with error 1067.<br />In eventlog lyncserver I found these errors and followed your steps (with first post by anonymous extra info). It fixed it right away!!<br />I did not get the relationship with the update but now I think I do. Someone else is working on implementing O365 in my domain. Probably he made some adjustments which now form to be a problem restarting the services for the first time with my update.Mikehttps://www.blogger.com/profile/00353482564339750289noreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-32540036417465512112013-10-29T16:12:43.703-04:002013-10-29T16:12:43.703-04:00Bhargav,
Thanks for the insight. Very helpful.
...Bhargav,<br /><br />Thanks for the insight. Very helpful.<br /><br />-PhilAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-71515430437625828722013-10-29T15:40:36.584-04:002013-10-29T15:40:36.584-04:00Hello Phil,
Great post. I think it is important f...Hello Phil,<br /><br />Great post. I think it is important for me to add some context. The issue at hand is data passing through LM that isn't RFC conformant for "100 continue" handling. The testing the cmdlet is intermittent and you get error sometimes like you mentioned. This does not affect user experience from what I have seen in my deployments.<br /><br />However, if necessary, you can apply the change mentioned here which than forces KEMP LM to ignore RFC conformance and continue processing messages.<br /><br />Thanks,<br />BhargavBhargav Shuklahttp://www.bhargavs.comnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-42195530289744418272013-08-28T10:24:19.357-04:002013-08-28T10:24:19.357-04:00That is how I would have handled it as well. Glad...That is how I would have handled it as well. Glad it helped.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-27716696823276643302013-08-13T07:30:35.484-04:002013-08-13T07:30:35.484-04:00Hi,
I have been trying for several days to get th...Hi,<br /><br />I have been trying for several days to get the Lync migration working with Office 365. But had no luck to overcome 'The Registrar "sipfed.online.lync.com" does not exist'<br /><br />I have posted the issue on the below forum:<br /><br />http://community.office365.com/en-us/forums/166/p/184965/544529.aspx<br /><br />ThanksOHarbehttps://www.blogger.com/profile/06375562367212232562noreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-7797085505225862052013-08-08T10:35:38.319-04:002013-08-08T10:35:38.319-04:00Got the same issue between onpremise Lync 2010 inf...Got the same issue between onpremise Lync 2010 infra and Lync online.<br />-> Removed the Lync online hosting provider since we allow the federated domains one by one.<br /><br />Thanks for the tip !Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-47084900036103261082013-08-06T07:30:05.022-04:002013-08-06T07:30:05.022-04:00Thanks for posting this. I was running into this i...Thanks for posting this. I was running into this issue in Lync 2010 after applying the latest CU patches (not sure why). In the control panel, under external user access on the federated domains tab, removing sipfed.online.lync.com from the federated domain 'push.lync.com' fixed the issue. On the provider tab, I kept sipfed.online.lync.com as an edge server entry for the hosted provider for LyncOnlinePushNotifications for our mobility clients.<br /><br />Thanks!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-66374514570814397352012-09-19T04:49:08.986-04:002012-09-19T04:49:08.986-04:00Great tips! Thanks so much...I printed this out an...Great tips! Thanks so much...I printed this out and shared it with the entire office. :)Elliehttp://saasplaza.com/noreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-24420797568981643112012-07-17T14:40:25.363-04:002012-07-17T14:40:25.363-04:00Chris,
In this case, we have a firewall sitting i...Chris,<br /><br />In this case, we have a firewall sitting in front of the F5. On the firewall we are doing a PAT from (outside/Internet) 443 -> 4443 (inside) which then lands on the FE VIP.<br /><br />It's hard to tell the network layout from your description, but I'm not sure that this can be accomplished by a single F5.<br /><br />Following the F5 Deployment Guide, you'll see that 80/443 are required to publish the Lync Internal Web Services, while 8080/4443 are used to publish the Lync External Web Services. This means that for the Lync Front End VIP, a VS will exist for all the ports already mentioned (80,443,8080,4443). You will need another device doing PAT from 443 -> 4443 for traffic from the outside, or use a different VIP to redirect traffic if landing on the same F5 which hosts the Front End VIP. <br /><br />Authentication settings are different between the Lync Internal and External web sites, so using 1 Front End VIP and forwarding 80/443 to 8080/4443 will not work.<br /><br />Sorry for the long (and possibly confusing) response, but hopefully that clears things up.<br /><br />-PhilAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-90757924135462655622012-07-16T10:26:32.180-04:002012-07-16T10:26:32.180-04:00Do you have a seperate Virtual server with a publi...Do you have a seperate Virtual server with a public IP that forwards the traffic on to this VS? Are you using an iRule for URLs? <br />I currently have a VS for 443 and one for 80 traffic, they forward to pools of 4443 and 8080 (internal FE). this does not work and I am trying to figure out where my problem is.Anonymoushttps://www.blogger.com/profile/14221975091507542282noreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-59990886114147609662012-06-27T22:04:36.866-04:002012-06-27T22:04:36.866-04:00Thanks Abhay.
CRL checks are done "on demand...Thanks Abhay.<br /><br />CRL checks are done "on demand," meaning when the certificate is presented to the server/client. It should then download a copy of the CRL and cache it until the "Next Update" time indicated on the CRL. Then whenever a certificate is presented it will check the locally cached CRL until the "Next Update" time, at which point a new CRL should be retrieved and checked.<br /><br />There are some other factors that might influence how this occurs, but what I described above would be the default.<br /><br />-PhilAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-40662189626815326732012-06-27T21:53:26.212-04:002012-06-27T21:53:26.212-04:00Though I don't see it very often, Lync can be ...Though I don't see it very often, Lync can be deployed internally only (no external access, no external web conferencing). In that case, a reverse proxy isn't needed and therefore the configuration would not be required on the F5. I think that is all the note from the deployment guide is indicating.<br /><br />-PhilAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-4905685089869507912012-06-27T21:45:26.926-04:002012-06-27T21:45:26.926-04:00Hi Kieran,
I do not believe the AudioCodes gatewa...Hi Kieran,<br /><br />I do not believe the AudioCodes gateways support a SAN certificate. If you follow the instructions above, you'll see that we actually generated the CSR from the gateway directly. <br /><br />The certificate on the Lync server only contains names relevant to the Lync server itself. See this article for the certificate SN/SAN best practices for both Standard and Enterprise Edition deployments.<br /><br />http://technet.microsoft.com/en-us/library/gg398094.aspx<br /><br />Let me know if you need further clarification.<br /><br />-PhilAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-60919505400370568492012-06-24T21:13:45.835-04:002012-06-24T21:13:45.835-04:00I'm configuring a very similar setup with Audi...I'm configuring a very similar setup with AudioCodes and TLS between Lync. Did you just add the DNS name of the gateway as a subject alternative name on the Lync certificate? I'm just not sure how to get the certificate right on the Lync server and make sure TLS is configured correctly.<br /><br />Cheers.kieranbaileyhttps://www.blogger.com/profile/04662595473316236770noreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-57050494465061341922012-06-20T16:11:48.323-04:002012-06-20T16:11:48.323-04:00The title says F5 without a reverse proxy but the ...The title says F5 without a reverse proxy but the first graphic says "this virtual server is only necessary when using a reverse proxy" <br />This seems to conflictAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-26897613786114063572012-06-19T14:34:03.021-04:002012-06-19T14:34:03.021-04:00Hi PHIL,
Excellent article.
Is there a specific s...Hi PHIL,<br />Excellent article. <br />Is there a specific schedule of CRL checks or are they done on a realtime basis?Abhay Kamathhttps://www.blogger.com/profile/06962683823118876392noreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-42628259752926442912012-05-21T18:13:05.446-04:002012-05-21T18:13:05.446-04:00Thanks for the info Freezer. I'll check it ou...Thanks for the info Freezer. I'll check it out. Odd that the AudioCodes engineer I worked with on this issue didn't mention this. The Mediant 1k was only deployed earlier this year (2012), so if this was publicly available I assume we would have upgraded to that rev. I'll follow up with him or my SE and verify this. Thanks.<br /><br />-PhilAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7510536084528411099.post-89794920137323741022012-05-21T05:08:30.902-04:002012-05-21T05:08:30.902-04:00The details above are for v6.2, all of these issue...The details above are for v6.2, all of these issues have been addressed at v6.4 (which has been available since June 2011).<br /><br />The 6.4 GUI is significantly easier to use, and there's no need to jump around all those pages.Anonymousnoreply@blogger.com