Shawn Harry | Shawn Harry
1
archive,paged,author,author-admin,author-1,paged-2,author-paged-2,ajax_fade,page_not_loaded,,qode_grid_1300,qode_popup_menu_push_text_top,qode-content-sidebar-responsive,qode-theme-ver-10.0,wpb-js-composer js-comp-ver-4.12.1,vc_responsive

Author: Shawn Harry

The below can be accomplished using DHCP options 66 & 160. For the purposes of testing one phone though a manual configuration may be preferable. Under the Provision Server tab the following server address must be entered. Enter “[YourIPAddress]/phoneservice/configfiles” as the server address. Server type must...

This article is applicaple to Office 365 only. EG Skype for Business Online with no hybrid or premise connectivity. The following technet wiki was used to understand the configuration: https://social.technet.microsoft.com/wiki/contents/articles/34339.skype-for-business-online-enable-your-tenant-for-modern-authentication.aspx Per service state of modern authentication by default for Office 365: •    Skype for Business Online - OFF...

Symptom: The Front End service would not start due to incorrectly placed certificates in the Trusted Root container. This script https://gallery.technet.microsoft.com/LyncSkype4B-Certificate-81944851 was used to check the certificate containers and two root certificates were found incorrectly placed in the Trusted Root container. Example output:- Resolution: The below registry...

To resolve the Poodle vulnerability and harden the Edge Server download and install the following tool from Nartac Software https://www.nartac.com/Products/IISCrypto/Download After installing select ‘best practices’ and apply the suggested fixes. The keys will be written to the following path: “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control \SecurityProviders\SCHANNEL\Protocols” Browse to Qualys SSLs checker and scan the Edge...

Summary: After initiating a successful failover of the Central Management Store and Pool failback of the CMS failed. The topology reported the CMS as being homed on the primary pool, but the Get-CsManagementStoreReplicationStatus –CentralManagementStoreStatus cmdlet reported the CMS as still being on the backup pool....