Search This Blog

Friday, August 5, 2016

Two words about Lync Reverse Proxy requirements

Reverse proxy can provide

SSL pass-through - RP just passes HTTPS traffic without really changing it

SSL offload - HTTPS traffic is terminated at RP and then passed to internal host in HTTP.

SSL bridging - HTTPS is terminated at RP, proxy have a chance to read unecrypted traffic, then it would opn new HTTPS stream to internal server.

First and third methods are supported by Lync, but not SSL offload.

The prefered and less painful method is  SSL Bridging. You should use a public certificate on RP and a private one in Lync.

Tuesday, August 2, 2016

Upgrade Microsoft ATA 1.5 to 1.6

https://docs.microsoft.com/en-us/advanced-threat-analytics/understand-explore/ata-update-1.6-migration-guide

1. Check if you have at least 10GB free space
2. Stop ATA and expand disk to get 10 GB free
3. Take checkpoint
4. Run ATA_1.6_Update
5. Accept and it will update .NET to 4.6.1 and ask to reboot, go for it.
6. After reboot update will continue.
7. At the end update will propose to launch ATA https://url/configuration
8. Download gateway package, copy ZIP to all gateways
9. Run setup and it will update .NET first
10. As in case of main server after restart setup will continue and will update gateway.










Recertification to MCSE Communication 70-384 - plan

https://www.microsoft.com/en-us/learning/exam-70-384.aspx

Good news - no Exchange integration, No Skype for Business, no Lync online, no migration at least in the plan.

Bad news - two exams combined -  core and voice. Too much of a persistent chat, heavy DRP/HA,

SharePoint 2010 The search service stopped the filter daemon because it was consuming too many resources


Problem:

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Server Search
Date:          02.08.2016 10:56:52
Event ID:      30
Task Category: Gatherer
Level:         Warning
Keywords:    
User:          x
Computer:   x  
Description:
The search service stopped the filter daemon because it was consuming too many resources. A new daemon will automatically be started, and no user action is required.

Potential solution:

http://blogs.developpeur.org/fabrice69/archive/2012/12/28/sharepoint-d-tails-de-la-configuration-du-moteur-de-recherche-pour-les-documents-pdf.aspx


https://gallery.technet.microsoft.com/office/Improve-SharePoint-Search-9b964682