tag:blogger.com,1999:blog-330512563102289335.comments2024-03-13T00:57:41.117-07:00TsooRaDtsooradhttp://www.blogger.com/profile/17928837963455872673noreply@blogger.comBlogger207125tag:blogger.com,1999:blog-330512563102289335.post-38617644095082052802019-01-08T10:33:02.972-08:002019-01-08T10:33:02.972-08:00This script still works for sfb 2015 on server 201...This script still works for sfb 2015 on server 2016.<br />This script still works for sfb 2019 on server 2019.<br /><br />Desktop-Experience no longer needed for either on server 2016 or higher.tsooradhttps://www.blogger.com/profile/17928837963455872673noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-76152821471351162012018-01-22T07:25:34.745-08:002018-01-22T07:25:34.745-08:00All I can say is "been there, done that!"...All I can say is "been there, done that!" I could not have written it better myself and completely agree. Following CU update testing DR scenarios we ended up with orphaned CMS and despite several hours of working with Microsoft the problem could not be resolved and full DR procedures were performed. Very hard to get Microsoft to admit to the problem and certainly seems no effort to fix. We have a very unreliable DR process with Skype currently, which is a very uncomfortable position to be in.Anonymoushttps://www.blogger.com/profile/06634049294967922220noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-24120513053977428062018-01-22T06:27:54.377-08:002018-01-22T06:27:54.377-08:00All I can say is, "been there done that!"...All I can say is, "been there done that!"I could not have written this better myself. "you must be kidding me” category is very true. Having got ourselves (or Skype got itself) into orphaned CMS situation through DR scenario testing following a CU update, Microsoft spent hours working with us in trying to fix it, in the end I had to call it a day and implement full DR procedures to get everything back to normal. There is very little acknowledgment from Microsoft on this issue and certainly seemingly no attempt to fix it. I now have no trust in Skype failover at all. Anonymoushttps://www.blogger.com/profile/06634049294967922220noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-14307495481004113112017-10-24T08:08:59.019-07:002017-10-24T08:08:59.019-07:00FYI - I opened a MS case for that same error Diagn...FYI - I opened a MS case for that same error Diagnostic ID 24118; Reason="Application accepts invitations via static registration only." under different circumstances. This is the answer I got:<br />Diagnostic ID 24118; Reason="Application accepts invitations via static registration only."<br /><br />Since we don't have the information on what exact issue had occurred when this error message was captured and we are solely relying on the information mentioned in the ticket - IM Message sent from internal Lync client to Lync Mobile client, below is the possible scenario where this error can occur and its possible causes.<br /><br />Scenario# When an IM message is sent from an internal Lync Client to a Lync Mobility client, then the Internal user might get an error message saying the IM was not sent even though the Lync Mobility client has received the IM message.<br /><br />Reviewing the logs, we will notice 403 Forbidden with the error message - "Application accepts invitations via static registration only"<br /><br />Possible Cause 1# On the Front-End server and the Reverse proxy if there is a Certificate with multiple Subject Alternative Names (SAN) and in case one of the URL mentioned in the SAN entries is not reachable then you would see this error in the logs.<br /><br />Possible Cause 2# We have also seen this kind of error in the logs when SSCH (Server Side Conversation History) is not enabled then Auto Accept of IM messages on the Mobility clients might not work when the user is inactive on the device and this would lead to the error message.<br />John Crouchhttps://www.blogger.com/profile/16995929952586893413noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-51685833050665368192017-04-13T00:46:43.456-07:002017-04-13T00:46:43.456-07:00What do they charge for a /29 block?What do they charge for a /29 block?shaitandhttps://www.blogger.com/profile/02146073995466863946noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-21465873954477056812017-04-06T07:50:20.410-07:002017-04-06T07:50:20.410-07:00The tip from victor was the good one for me.
Thank...The tip from victor was the good one for me.<br />Thanks for sharing your experience. :)StiXhttps://www.blogger.com/profile/18380523345461688746noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-5476409573889097412017-03-08T16:03:19.598-08:002017-03-08T16:03:19.598-08:00@zyphen
"But I do know what fixed this issue ...@zyphen<br />"But I do know what fixed this issue – the federation SRV record being added to the internal DNS zone and modification of the Edge Server host files so that they can find the SRV target by IP."<br /><br />So, create a federation srv record internally for the edge server to find. And if that SRV has a target of xyz@domain.com, and you need that for something else internally, you can go to the edge server, and put an entry into the host file for the target of the federation SRV record. When the Edge server looks up the federation SRV record, it will also try to resolve the target - and when it finds that target FQDN in its host file, it will use it.<br />So you give the edge server access edge out as your FQDN for target of the federation SRV, and the host file gets the PUBLIC access edge IP = FQDFN and problem solved.<br /><br />Clear as mud?<br /><br /><br />tsooradhttps://www.blogger.com/profile/17928837963455872673noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-10279045870709374752017-03-07T15:13:13.166-08:002017-03-07T15:13:13.166-08:00Hey what do you mean by "And then modified th...Hey what do you mean by "And then modified the host file on each Edge server to have the public IP for themselves"<br /><br />we are having the exact same issueZyphenhttps://www.blogger.com/profile/15872151245968145752noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-36182547565000779022017-01-06T13:46:51.306-08:002017-01-06T13:46:51.306-08:00The fact they're starting to come up on the Mi...The fact they're starting to come up on the Microsoft approved phone list is a big for excitement in the partner community. Comparing to the big dog on the block there is a lot of GOOD reasons this phone will kill in 2017. Oh and don't forget native SILK support!The Tall Onehttps://www.blogger.com/profile/13774737565318354134noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-80413769499488133672016-12-23T09:01:26.838-08:002016-12-23T09:01:26.838-08:00Thanks for the blog post. Do you know if anyone t...Thanks for the blog post. Do you know if anyone that completed a security review of the Yealink T48G phones? I'm trying to find out if this phone is suitable for use in a medical office, financial planning office, etc.<br /><br />Thanks!<br /><br />Anonymoushttps://www.blogger.com/profile/03997321153470324384noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-32676032392395644372016-10-16T12:31:28.234-07:002016-10-16T12:31:28.234-07:00I do use this device with Win10 and have zero prob...I do use this device with Win10 and have zero problems.tsooradhttps://www.blogger.com/profile/17928837963455872673noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-42697935876057489352016-08-31T07:16:39.368-07:002016-08-31T07:16:39.368-07:00I was getting the same error 58 while running DCPR...I was getting the same error 58 while running DCPROMO on a W2012R2 server on an IPV4-only network. Looking at the logs, I found errors in the system log that IPV6 adapters were failing to register. I resolved this by disabling the IPV6 transitional adapters:<br /><br />netsh interface 6to4 set state disabled<br />netsh interface teredo set state disabled<br />netsh interface isatap set state disabled<br /><br />That done, DCPROMO ran w/out any errors.Anonymoushttps://www.blogger.com/profile/12008821200309451224noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-73270181907984907822016-08-15T08:52:23.894-07:002016-08-15T08:52:23.894-07:00Hi,
Do you use it with Windows 10? Unfortunately ...Hi,<br /><br />Do you use it with Windows 10? Unfortunately it just work for calls for me, in the BT600, it blinks blue the whole time.<br /><br />Unknownhttps://www.blogger.com/profile/07651561065837784356noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-66046561188109492512016-08-05T07:28:22.471-07:002016-08-05T07:28:22.471-07:00I have an H820e and love it as well. But the batt...I have an H820e and love it as well. But the battery life is starting to diminish. I'm not seeing any option to replace the battery. Am I missing something or do they really expect you to replace the entire headset when it no longer holds a charge?IGnatius T Foobarhttps://www.blogger.com/profile/15664986058467587907noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-59338727827702827722016-08-03T14:18:45.940-07:002016-08-03T14:18:45.940-07:00@Gw999 - I agree. My point in all of this is the ...@Gw999 - I agree. My point in all of this is the support of the non-msft clients. those browsers and operating systems are deprecating support for the SHA-1, and we need to respond to the requirements of supporting what is becoming a larger slice of the client-world.tsooradhttps://www.blogger.com/profile/17928837963455872673noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-68505348810094798602016-08-03T06:17:43.326-07:002016-08-03T06:17:43.326-07:00Hi John,
Thanks for this. I've been looking in...Hi John,<br />Thanks for this. I've been looking into the whole SHA-1 deprecation thing recently to see if there will be any impact on Lync Server/SfB Server environments. It's clear that publically-signed certs signed using SHA-1 will be impacted on January 1st 2017 (Chrome/Firefox) and Feb 14th 2017 (IE/Edge). However, my understanding is that internal CAs will not be affected as they are not in the Microsoft Trusted Root Program (ref: "Will the policy impact certificates that chain up to an internal root that is not part of the Microsoft Trusted Root Program?" http://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx#Y). Also: "In summary, as of now (May 2015), Microsoft's SHA-1 deprecation only impacts SSL and code-signing certs issued by CAs in the Windows Root Certification Program. Any CA not in that program will be treated as a private/enterprise CA and Microsoft's current (as of 5/15/2015) SHA-1 deprecation policies does not apply." http://social.technet.microsoft.com/wiki/contents/articles/31296.implementing-sha-2-in-active-directory-certificate-services.aspx.<br /><br />Cheers,<br />GarryGW999https://www.blogger.com/profile/16431857176937457078noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-56184759643568722502016-07-01T08:38:48.691-07:002016-07-01T08:38:48.691-07:00excellent stuff. thanks for the data and keep it c...excellent stuff. thanks for the data and keep it coming.twardzikhttps://www.blogger.com/profile/11284264042497331759noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-28255647758490755602016-06-27T11:12:23.025-07:002016-06-27T11:12:23.025-07:00Thanks for your post, I was running into the same ...Thanks for your post, I was running into the same error and wasn't able to get it working until I did the "recreate Summary Tables" action.cwewhttps://www.blogger.com/profile/02986652796609310901noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-87829721340064121232016-05-16T12:27:51.546-07:002016-05-16T12:27:51.546-07:00What FW where you using
We have found issues with ...What FW where you using<br />We have found issues with 35.8.0.9,35.8.0.11, 35.8.0.14, 35.8.0.17, 35.8.0.21,35.8.0.23 and 35.8.0.25.<br />There FW game is a real wackamole. fix something break another. <br />the last 4 FW totally broke Calendar and BToEStefanhttps://www.blogger.com/profile/13956440397896811905noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-26094976209899179052016-05-05T17:25:09.889-07:002016-05-05T17:25:09.889-07:00Argahlji, the cert is removed from the local compu...Argahlji, the cert is removed from the local computer personal container.tsooradhttps://www.blogger.com/profile/17928837963455872673noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-79941021885829189382016-04-11T10:22:21.072-07:002016-04-11T10:22:21.072-07:00Where did you remove the cert from? Local User Com...Where did you remove the cert from? Local User Computer or Exchange Server?Argahljihttps://www.blogger.com/profile/02599854536167016255noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-45751077610744712562016-02-12T17:42:49.993-08:002016-02-12T17:42:49.993-08:00@Rob, I am not an Android user, so my empirical te...@Rob, I am not an Android user, so my empirical tests are "I don't know" - but I will note that the Win and iOS clients updated...my SfB client on my phone is v 6.2.1502 and has zero problems.<br />tsooradhttps://www.blogger.com/profile/17928837963455872673noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-31257128042272713802016-02-09T13:07:45.667-08:002016-02-09T13:07:45.667-08:00Has there been any changes from the Lync 2013 Andr...Has there been any changes from the Lync 2013 Android mobile client to the Skype for Business 2015 client of the same flavor. I have no issues with MS remote thick client users logging in but with the S4B client it hangs there. FYI: We are using an edge server....Anonymoushttps://www.blogger.com/profile/14263306293686451839noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-20728600462917090872015-11-19T11:30:07.328-08:002015-11-19T11:30:07.328-08:00@Paul,
sounds like you have it figured out. If th...@Paul,<br />sounds like you have it figured out. If the AG is already formed, then you can take any DB on the active node, and then follow the process above. <br /><br />@ Karthikeyan,<br />I think you have the install-csdatabase command wrong.<br />see https://technet.microsoft.com/en-us/library/gg399044.aspx<br />Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn atl-sql-001.litwareinc.com -SqlInstanceName rtc -DatabasePaths "G:\CSDB"<br /><br />I did the following - and my reasoning...<br />"install-csdatabase -centralmanagementdatabase -sqlserverfqdn SQLAlwaysOn-A.tsoorad.net -databasepaths c:\sfbdata"<br /><br />Install the database<br />Central management<br />Sql server fqdn - my AG name (or my active node as I created the CMS DB before I made up the AG)<br />No need for an instance name, there was only one running on that server.<br />Database paths... I had the entire SfB data running in c:\sfbdata.tsooradhttps://www.blogger.com/profile/17928837963455872673noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-35481990399823014762015-11-18T05:59:53.531-08:002015-11-18T05:59:53.531-08:00Hi John,
Great post..!! As you mentioned, we need...Hi John,<br /><br />Great post..!! As you mentioned, we need to create the Lync related DB's before having Availability groups.<br /><br />I created the CMS DB's and published the topology. before creating a Availability group, I would also like to create Lync User and application related DB's using the following commands..Tt fails with "Install-CsDatabase : Command setup failed: A network-related or instance-specific error occurred while establishing a connection to SQL Server" Is there any problem with below command??<br /><br />Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn –ForInstance S4BAON_RTC -DatabasePathMap $BEPath<br />Karthikeyan Annaduraihttps://www.blogger.com/profile/08164824226069372247noreply@blogger.com