• Home
  • Articles
    • Office 365
    • Exchange
    • Skype for Business (Lync)
    • Active Directory
    • Windows
    • Sharepoint
    • Joomla
    • Linux
    • Other
    • Blackberry
  • Project: Nagios Monitoring
    • First steps
    • NSCP installation
    • Scripts
    • FAQs
  • Links
  • Home
  • About
  • Imprint
Toggle navigation
Admin Enclave
  • Home
  • Articles
    • Office 365
    • Exchange
    • Skype for Business (Lync)
    • Active Directory
    • Windows
    • Sharepoint
    • Joomla
    • Linux
    • Other
    • Blackberry
  • Project: Nagios Monitoring
    • First steps
    • NSCP installation
    • Scripts
    • FAQs
  • Links
Home
/
Articles
/
Office 365
/
Data-Articles
/
Website Articles
/
Articles
/
Sharepoint
/
Disabling TLS 1.0 on Microsoft Sharepoint

Disabling TLS 1.0 on Microsoft Sharepoint

Bastian W.Feb 07, 2017Articles \ Sharepoint

Abstract: This short howto goes true the steps to disable TLS 1.0 (and therefore leave only TLS 1.1 and TLS 1.2 activated) on an Microsoft SharePoint Server.

As the payment Card Industry Security Standards Council (PCI SSC) recently announced that TLS 1.0 will be no longer secure (in PCI 3.1) after 2018-06-30 it is now the right time to consider some updates on the affected environments.

Disabling TLS 1.0 on Windows Server 2012 R2 / 2008 R2 is quite easy via the following registry entry (as outlined here):

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server]
"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000

However as you might have already disabled SSL 2.0 and 3.0 you would end up in having no protocols enabled. So make sure that TLS 1.1 and TLS 1.2 are enabled via:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001

Note: ffffffff is the same as 00000001

 

Then you need to do an OS reboot and you are almost fine.

To check if that is working as expected you can run an NMAP against the port 443 (assuming you have an IIS webserver installed or against the RDP port 3389) as mentioned here.

BUT that will start to cause all kind of connection issues. So this howto will drive true some of them and outline the solutions in order to fix the connection issues. Feel free to comment this article and I will update it if needed.

 

RDP & Windows 2008 R2

As RDP used TLS 1.0 out for the box you might lock out yourself from the Windows 2008 R2 server as KB 3080079 might be missing as documented by Microsoft here. Once installed this point should be covered.

The GUI and the GPO might still show TLS 1.0 this is a known bug as mentioned here.

Make also sure you are using Remote Desktop Protocol (RDP) 8.0 (or better 8.1 as outlined in KB KB2830477) on your Windows 7 PC as mentioned here.

 

https & Internet Explorer 10 / Internet Explorer 11

If you disable TLS 1.0 it might be you break any https connection towards the https website hosted on the Windows Server 2012 R2 / 2008 R2. No https website will be working when you use the Internet Explorer. However solving that one is quite easy. Simply enable TLS 1.1 and TLS 1.2 in the browser and you should be fine. Depending on your OS there is also no action needed per default (see below).

Windows 7 & Internet Explorer 11: TLS 1.1 and TLS 1.2 are enabled per default

Windows 8 & Internet Explorer 10: TLS 1.0 and TLS 1.2 are disabled per default

Windows 10 & Internet Explorer 11: TLS 1.1 and TLS 1.2 are enabled per default

You can control these settings via GPO or via Registry keys (The example below will enable TLS 1.0, 1.1 and 1.2 and disable SSL 2.0 and 3.0):

Windows Registry Editor Version 5.00[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"SecureProtocols"=dword:00000a80
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings]
"SecureProtocols"=dword:00000a80

 

3rd party application which used the SCHANNEL implementation in the Windows OS

Some 3rd party application (e.g. FTP Software) might use the build in SCHANNEL (aka Secure Channel) implementation in the Microsoft Windows OS. To ensure they can still connect to your Windows Server you need to enable TLS 1.1 and TLS 1.2 on the Windows OS where the 3rd party application is installed one. Enabling TLS 1.1 and TLS 1.2 is quite easy and can be done via the following registry key (as outlined here):

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client]
"DisabledByDefault"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]
"DisabledByDefault"=dword:00000000

After an OS reboot TLS 1.1 and TLS 1.2 would be accessible for clients. Keep noted that Windows Vista do not support TLS 1.1 or TLS 1.2 (as written here).

 

Microsoft Office running on Windows 7

You might think that enabling TLS 1.1 in the regestry as mentioned above would be enough for MS Office however that's not the case. Microsoft Office makes use of WinHTTP (Windows HTTP Services) which required some special settings. So for Windows 7 you need to do some additional tweaks (see here or here):

Windows 7 64bit OS:

1.) Install KB3 140245

2.) Add the following registry keys (to enable TLS 1.1 & TLS 1.2; and disable TLS 1.0):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000a00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000a00

3.) reboot the OS

 

Windows 7 32bit OS:

1.) Install KB 3140245

2.) Add the following registry keys (to enable TLS 1.1 & TLS 1.2):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000a00

3.) reboot the OS

 

Microsoft Office running on Windows 8.1 / 10

For Windows 8.1 or Windows 10 Microsoft already enabled TLS 1.1 and TLS 1.2 for WinHTTP-based applications by default. So you do not need to do any changes here.

 

Microsoft Office running on Windows Vista

Windows Vista do not support TLS 1.1 or TLS 1.2 (as written here) so you need to replace this OS fully.

 

Note:

While you are already improving the environment you should also replace the SHA1 SSL certificate used to one with SHA2.

 

Comments (1)

Paul
Paul
  1. about 2 years ago
  2. #412
This comment was minimized by the moderator on the site

FWIW, disabling TLS 1.0 on SP 2010 will break the search service. It appears that it doesn't instantly die by doing it, but once it does you will not be able to re-provision a search service application until tls1.0 is re-enabled on both the app...

FWIW, disabling TLS 1.0 on SP 2010 will break the search service. It appears that it doesn't instantly die by doing it, but once it does you will not be able to re-provision a search service application until tls1.0 is re-enabled on both the app server and sql server.

Read More
  1. Reply
There are no comments posted here yet

Leave your comments

  1. Posting comment as a guest.

Abstract: This short howto goes true the steps to disable TLS 1.0 (and therefore leave only TLS 1.1 and TLS 1.2 activated) on an Microsoft SharePoint Server.

As the payment Card Industry Security Standards Council (PCI SSC) recently announced that TLS 1.0 will be no longer secure (in PCI 3.1) after 2018-06-30 it is now the right time to consider some updates on the affected environments.

Disabling TLS 1.0 on Windows Server 2012 R2 / 2008 R2 is quite easy via the following registry entry (as outlined here):

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server]
"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000

However as you might have already disabled SSL 2.0 and 3.0 you would end up in having no protocols enabled. So make sure that TLS 1.1 and TLS 1.2 are enabled via:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001

Note: ffffffff is the same as 00000001

 

Then you need to do an OS reboot and you are almost fine.

To check if that is working as expected you can run an NMAP against the port 443 (assuming you have an IIS webserver installed or against the RDP port 3389) as mentioned here.

BUT that will start to cause all kind of connection issues. So this howto will drive true some of them and outline the solutions in order to fix the connection issues. Feel free to comment this article and I will update it if needed.

 

RDP & Windows 2008 R2

As RDP used TLS 1.0 out for the box you might lock out yourself from the Windows 2008 R2 server as KB 3080079 might be missing as documented by Microsoft here. Once installed this point should be covered.

The GUI and the GPO might still show TLS 1.0 this is a known bug as mentioned here.

Make also sure you are using Remote Desktop Protocol (RDP) 8.0 (or better 8.1 as outlined in KB KB2830477) on your Windows 7 PC as mentioned here.

 

https & Internet Explorer 10 / Internet Explorer 11

If you disable TLS 1.0 it might be you break any https connection towards the https website hosted on the Windows Server 2012 R2 / 2008 R2. No https website will be working when you use the Internet Explorer. However solving that one is quite easy. Simply enable TLS 1.1 and TLS 1.2 in the browser and you should be fine. Depending on your OS there is also no action needed per default (see below).

Windows 7 & Internet Explorer 11: TLS 1.1 and TLS 1.2 are enabled per default

Windows 8 & Internet Explorer 10: TLS 1.0 and TLS 1.2 are disabled per default

Windows 10 & Internet Explorer 11: TLS 1.1 and TLS 1.2 are enabled per default

You can control these settings via GPO or via Registry keys (The example below will enable TLS 1.0, 1.1 and 1.2 and disable SSL 2.0 and 3.0):

Windows Registry Editor Version 5.00[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"SecureProtocols"=dword:00000a80
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings]
"SecureProtocols"=dword:00000a80

 

3rd party application which used the SCHANNEL implementation in the Windows OS

Some 3rd party application (e.g. FTP Software) might use the build in SCHANNEL (aka Secure Channel) implementation in the Microsoft Windows OS. To ensure they can still connect to your Windows Server you need to enable TLS 1.1 and TLS 1.2 on the Windows OS where the 3rd party application is installed one. Enabling TLS 1.1 and TLS 1.2 is quite easy and can be done via the following registry key (as outlined here):

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client]
"DisabledByDefault"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]
"DisabledByDefault"=dword:00000000

After an OS reboot TLS 1.1 and TLS 1.2 would be accessible for clients. Keep noted that Windows Vista do not support TLS 1.1 or TLS 1.2 (as written here).

 

Microsoft Office running on Windows 7

You might think that enabling TLS 1.1 in the regestry as mentioned above would be enough for MS Office however that's not the case. Microsoft Office makes use of WinHTTP (Windows HTTP Services) which required some special settings. So for Windows 7 you need to do some additional tweaks (see here or here):

Windows 7 64bit OS:

1.) Install KB3 140245

2.) Add the following registry keys (to enable TLS 1.1 & TLS 1.2; and disable TLS 1.0):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000a00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000a00

3.) reboot the OS

 

Windows 7 32bit OS:

1.) Install KB 3140245

2.) Add the following registry keys (to enable TLS 1.1 & TLS 1.2):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000a00

3.) reboot the OS

 

Microsoft Office running on Windows 8.1 / 10

For Windows 8.1 or Windows 10 Microsoft already enabled TLS 1.1 and TLS 1.2 for WinHTTP-based applications by default. So you do not need to do any changes here.

 

Microsoft Office running on Windows Vista

Windows Vista do not support TLS 1.1 or TLS 1.2 (as written here) so you need to replace this OS fully.

 

Note:

While you are already improving the environment you should also replace the SHA1 SSL certificate used to one with SHA2.

 

Comments (1)

Paul
Paul
  1. about 2 years ago
  2. #412
This comment was minimized by the moderator on the site

FWIW, disabling TLS 1.0 on SP 2010 will break the search service. It appears that it doesn't instantly die by doing it, but once it does you will not be able to re-provision a search service application until tls1.0 is re-enabled on both the app...

FWIW, disabling TLS 1.0 on SP 2010 will break the search service. It appears that it doesn't instantly die by doing it, but once it does you will not be able to re-provision a search service application until tls1.0 is re-enabled on both the app server and sql server.

Read More
  1. Reply
There are no comments posted here yet

Leave your comments

  1. Posting comment as a guest.
Attachments (0 / 3)
Share Your Location

2017 - MS SharepointHardening20162013Sharepoint

Follow me on Twitter

Recent Posts

  • How to connect a Osram On/Off Plug with Phoscon/deCONZ

    Friday, 20 March 2020
  • Update TPM Firmware on Windows 10 1909

    Saturday, 15 February 2020
  • Switch your PC from BIOS to UEFI

    Tuesday, 07 January 2020
  • WLAN 6 (AX) released

    Monday, 23 September 2019
  • Use deCONZ to perform an OTA firmware update of OSRAM devices

    Saturday, 23 March 2019

Tags

Exchange 20162016 - MS ExchangeServer 2015Hardening2016 - MS Skype for Business Server 2017 - MS WindowsWindows Server 2012Windows2017 - MS ExchangeExchange 20132016 - MS Windows2013Exchange2017 - MS Skype for Business Server 2016 - MS SharepointRaspberry PiMicrosoftOpenHABHomeMatic2017 - MS Sharepoint

Archive

      • How to connect a Osram On/Off Plug with Phoscon/deCONZ
      • Update TPM Firmware on Windows 10 1909
      • Upgrade the BIOS from an ReadyNAS device
      • Switch your PC from BIOS to UEFI
      • WLAN 6 (AX) released
      • [ReSolved] Get-MailboxRestoreRequest matches multiple entries and couldn´t be performed
      • Use deCONZ to perform an OTA firmware update of OSRAM devices
      • Remove the Transparent Data Encryption (TDE) from a SQL DB
      • Install OpenHAB 2.4.x on Raspberry Pi (on Debian 9 - Stretch)
      • Windows 10 Driver for HP EliteBook 2570p Notebook-PC
      • Windows 10 Driver for HP EliteBook 850 G1 Notebook
      • Windows 10 Driver for HP EliteBook 8570p Notebook
      • Windows 10 Driver for IBM Thinkpad T560 Notebook
      • Windows 10 Driver for HP EliteBook 850 G5 Notebook
      • Windows 10 Driver for Lenovo T560 Notebook
      • Add an additional Sharepoint Admin to every Site Collection via Powershell
      • Do not install .NET Framework 4.7.2 on Exchange Servers yet
      • [Resolved] Unable to Migrate User to O365 due to "Target user 'XYZ' already has a primary mailbox"
      • Migrate SharePoint Elements to SharePoint Online
      • Microsoft Exchange OU picker is empty when creating new user or group
      • Exchange Online Powershell failed to connect when using MFA
      • Move-DatabasePath caused a "WMI exception occurred on server XY: Quota violation"
      • Privacy Policy
      • D:\AdvancedDataGovernanceLogs created on Exchange 2016
      • After May 2018 security update "An authentication error occurred" using RDP
      • Find out which .NET Framework version is installed
      • Install OpenHAB 2.0.x on Raspberry Pi (on Debian 9 - Stretch)
      • Convert a *.pfx certificate into *.pem
      • Changing last modified and creation date or time via PowerShell
      • Multidimensional arrays in Powershell
      • HowTo create an Enterprise Wiki on SharePoint Online
      • Attention: Microsoft Office 365 will disable support for TLS 1.0 and 1.1
      • [RESOLVED] Graphics Card issue when installing BlueStacks inside VMWare
      • How to create a pkcs12 file with a ordered certificate chain?
      • Publish an S/Mime certificate to AD via Powershell
      • [RESOLVED] iOS accounts needs permission to access resources in your organization that only an admin can grant
      • [RESOLVED] Exchange 2016 CU X failed to install error 1619
      • Headless Raspberry Pi WLAN Configuration
      • How to remove all partitions on an USB stick / SD card
      • How to generate a notifications once Handbreak finished its current work?
      • Enable TLS 1.1 and TLS 1.2 as a default secure protocols in WinHTTP
      • Security Hardening: Upgrade Diffie-Hellman Prime to 2048 bit on Windows Server
      • Change a SSL Certificate on Windows Server 2012 R2 Web Application Proxy
      • Add Windows Updates to a Windows 7 SP1 image
      • When using Import-Module you got an unblock file error
      • [Resolved] Exchange admin got the error "User profile cannot be loaded" when using RDP
      • Google Chrome browser to deprecate trust in existing Symantec-issued certificates
      • [RESOLVED] Error ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY when using Google Chome and OWA
      • Cumulative Update 6 for Exchange Server 2016 released
      • Windows Phone 8.1 will reach EOL on the 2017-07-11
      • .NET Framework 4.7.* and Microsoft Exchange Server
      • Disable weak cipher (e.g. 3DES, SSLv3, MD5, ...) suites in Java
      • [RESOLVED] "Could not find stored procedure" after installing SfB Server Updates
      • [RESOLVED] None of the network adapters are bound to the netmon driver.
      • [Resolved] No connectivity with any of Web Conferencing Edge Servers - Event 41026
      • Raspberry Pi - Connect to multiple wireless networks (WLAN) automatically
      • From 0 to Raspberry Pi (start with Raspberry Pi)
      • [RESOLVED] Exchange 2016 IIS not usable after installation from CU5
      • Microsoft Exchange 2007 reached end of life today
      • .NET Framework 4.7 released but not yet supported on Exchange 2016
      • .NET Framework 4.7 released but not yet supported on Skype for Business
      • Using Quest ActiveRoles Management Shell to add/update all users from a OU inside an AD group
      • [RESOLVED] Can´t install Office Web Apps Server because it requires .NET 4.5
      • Cumulative Update 5 for Exchange Server 2016 released
      • Using the Skype for Business device update service
      • Enable XA transactions on Microsoft SQL 2012
      • [RESOLVED] The Open Procedure for service XXX in DLL "C:\Windows\System32\XXX.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code
      • WES7 is crashing on VMWare Workstation
      • WES7 / WES8 OS deployment issue on VMWare Workstation
      • [RESOLVED] Growing amount of missing disk space on Microsoft Exchange
      • Disabling TLS 1.0 on Microsoft Sharepoint
      • Reset the content index on an MS Exchange DAG environment
      • Deploy the Statistics Manager for Skype for Business Server
      • HowTo add own formats to the TinyMCE Editor in Joomla?
      • Create a Kerberos authentication account in Skype for Business
      • Hardening Microsoft Exchange 2016 Server
      • Hardening Microsoft SharePoint 2016 Server
      • Hardening Microsoft Skype for Business Server
      • [Workaround] "Screen presenting isn't supported with this contact" with SfB MAC
      • [RESOLVED] Black or frozen screen during screensharing in Skype for Business 2016
      • Exchange Windows OS Hardening: Disable SSL 2.0/3.0 & PCT 1.0 & weak ciphers
      • SfB Windows OS Hardening: Disable SSL 2.0/3.0 & PCT 1.0 & weak ciphers
      • SharePoint Windows OS Hardening: Disable SSL 2.0/3.0 & PCT 1.0 & weak ciphers
      • Configure https for Windows Remote Management (WinRM) on Windows 2012 R2
      • Configure https for Windows Remote Management (WinRM) on Windows 2012 R2
      • Configure https for Windows Remote Management (WinRM) on Windows 2012 R2
      • Hardening Skype for Business Server
      • [RESOLVED] You do not have the permission to send the message on behalf of the specified user
      • Copy Windows Installation DVD to ISO
      • [RESOLVED] The remote certificate is invalid according to the validation procedure.
      • Prevent that the Skype for Business client will open when the user click on an meeting URL
      • Test GroupPolicy (*.admx templates) locally without AD
      • Implementing the Skype for Business Call Quality Dashboard
      • Configure / Finetune the Microsoft Exchange search / indexing feature
      • Disable content indexing on all DBs on an Exchange DAG
      • HowTo: create Search Sharepoint 2013 Foundation Application via Powershell
      • Migrate from Exchange 2010 to Exchange 2016
      • Enable TLS 1.2 on Windows 2012 R2
      • Download Skype for Business for MAC
      • [RESOLVED] Exchange 2013/2016 hub transport Mail.que file large in size
      • How to get only a subset from a 2 GB big logfile?
      • Add the Internet Explorer 11 and Updates to a Windows 7 SP1 image
      • [RESOLVED] MSExchange Mailbox Replication error 1006 (database doesn't exist)
      • Nagios Core 3.x installation guide on Debian 8.x (Jessie)
      • Move Exchange 2010/2013 user to Exchange 2016
      • [RESOLVED]: "Whole calendar" greyed out when publishing a calendar via Outlook on a webdav server
      • SfB Windows OS Hardening: Disable the "X-AspNet-Version" header
      • Exchange Windows OS Hardening: Disable the "X-AspNet-Version" header
      • SharePoint Windows OS Hardening: Disable the "X-AspNet-Version" header
      • Powershell: Clean (Remove) all completed Exchange Mailbox move requests
      • HP Data Protector isn´t able to browse an Exchange 2016 DAG
      • Powershell: Get a list from all Exchange users, where the latest logon time is older then 270 days
      • Usefull links
      • Hardening Microsoft Exchange 2013 Server
      • [Solution] Skype for Business Error: This message wan´t send to Firstname LastName
      • Step-By-Step: Configuring Office Online Server with Skype for Business
      • Troubleshooting connection issues from users migrated from Exchange 2010 to Exchange 2013/2016
      • Skype for Business Server DB update needed after patch management
      • How to check the progress of the ‘Shrink Database’ task in SQL Server 2012
      • Build an MS Exchange Throttling Policy to remove inactive mobile device partnerships
      • Exchange Windows OS Hardening: Disable NTFS 8 Dot 3
      • SfB Windows OS Hardening: Disable NTFS 8 Dot 3
      • SharePoint Windows OS Hardening: Disable NTFS 8 Dot 3
      • Windows OS Hardening: Disable NTFS 8 Dot 3
      • [RESOLVED] Centralized Logging Service Agent Error while moving cache files to network share.
      • [RESOLVED] MS Web Application Proxy used with SfB caused a Error 502
      • Manage the SSL certificate on Exchange 2016 via Powershell
      • [RESOLVED] How to fix damaged or corrupt Health Mailbox on Exchange 2016
      • [RESOLVED] "The client and server cannot communicate, because they do not possess a common algorithm"
      • Homematic IP Schalt und Steckdose mit CCU 2 verbinden / anlernen
      • Exchange 2010 to Exchange 2016 Co-Existence migration OWA redirect not working
      • Factory reset HomeMatic IP devices
      • Factory reset / Werksreset von HomeMatic IP Geräten
      • Pairing / Using Homematic IP Pluggable Switch and Meter with an CCU2
      • [Resolved] A Skype for business user isn´t able to join meeting via invitation link
      • Installation von BluePy auf dem Raspberry Pi
      • Install BluePy on Raspberry Pi
      • Released: Microsoft Exchange 2016 CU 2
      • Install OpenHAB 1.x on Raspberry Pi
      • Installieren von OpenHAB 1.x auf dem Raspberry Pi
      • Rebalance Mailbox Databases in an Exchange Server DAG via TaskManager
      • Fix a failed and suspended content index state on MS Exchange
      • Howto send an email using telnet
      • Hardening Windows Server (Basic Steps)
      • [RESOLVED] No DNS servers could be retrieved from network adapter 00000000-0000-0000-0000-000000000000
      • [RESOLVED] Setup can't use the domain controller because it belongs to Active Directory site
      • Use MS Web Application Proxy as reverse proxy (and ADFS) with Skype for business
      • [RESOLVED] Error message 0x80094004 when completing a certification request on IIS
      • [RESOLVED] Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.
      • Get all Exchange user inclusive details from a list of AD groups
Admin Enclave

The Admin enclave delivers the latest news, quick tips, useful tricks, and in-depth tutorials for IT pros working with IT solutions (e.g. Microsoft Sharepoint, Microsoft Exchange, Microsoft Skype for Business, Joomla, ...).

Follow Us

Recent Posts

  • How to connect a Osram On/Off Plug with Phoscon/deCONZ

    Friday, 20 March 2020
  • Update TPM Firmware on Windows 10 1909

    Saturday, 15 February 2020
  • Switch your PC from BIOS to UEFI

    Tuesday, 07 January 2020
  • WLAN 6 (AX) released

    Monday, 23 September 2019
  • Use deCONZ to perform an OTA firmware update of OSRAM devices

    Saturday, 23 March 2019

Popular Posts

  • How to fix “The program can’t start because MSVCR110.dll is missing from your computer.” error on Windows

    Sunday, 07 April 2013
  • [RESOLVED] You do not have the permission to send the message on behalf of the specified user

    Wednesday, 16 November 2016
  • [RESOLVED] Exchange 2013/2016 hub transport Mail.que file large in size

    Thursday, 13 October 2016
  • [RESOLVED] The Open Procedure for service XXX in DLL "C:\Windows\System32\XXX.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code

    Wednesday, 08 March 2017
  • [RESOLVED] "The client and server cannot communicate, because they do not possess a common algorithm"

    Wednesday, 13 July 2016
© 2012 - 2021 admin-enclave.com | Disclaimer | Privacy Policy | Imprint | Articles by year