If this happens again, try opening the document in Microsoft Word.” “Sorry, there was a problem and we can’t open this document. When opening an attachment in OWA I do see the OOS environment, it tries to open a document and then generates this error: Installed Windows 2016, installed prerequisite software, configured an SSL certificate, installed Office Online Server and created a new Office Web Apps farm.Īfter testing the and configured the organization configuration everything must be good. I did this in the past and blogged about it (Install Office Online Server 2016) so I thought it should not be a big deal. AADConnect wizard Azure AD Connect TLS 1.2 Windows 2019įor a current project I am working with Exchange 2019 and for OWA we want to implement Office Online Server. You can add | out-null to each command to suppress the console outputĪfter running these commands, Azure AD Connect was installed as expected. New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -name 'DisabledByDefault' -value 0 -PropertyType 'DWord' -Force New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -name 'Enabled' -value '1' -PropertyType 'DWord' -Force New-Item 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -Force New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server' -name 'DisabledByDefault' -value 0 -PropertyType 'DWord' -Force New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server' -name 'Enabled' -value '1' -PropertyType 'DWord' New-Item 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server' -Force New-ItemProperty -path 'HKLM:\SOFTWARE\Microsoft\.NETFramework\v9' -name 'SchUseStrongCrypto' -value '1' -PropertyType 'DWord' -Force New-ItemProperty -path 'HKLM:\SOFTWARE\Microsoft\.NETFramework\v9' -name 'SystemDefaultTlsVersions' -value '1' -PropertyType 'DWord' -Force New-ItemProperty -path 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v9' -name 'SchUseStrongCrypto' -value '1' -PropertyType 'DWord' -Force New-ItemProperty -path 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v9' -name 'SystemDefaultTlsVersions' -value '1' -PropertyType 'DWord' -Force To easiest way to get these on your server is by using the following PowerShell commands: New-Item 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v9' -Force "SystemDefaultTlsVersions"=dword:00000001 Luckily it’s not that difficult to enable TLS 1.2 on a Windows 2019 server (although I am wondering why this is not enabled by default) by using the following registry keys: After configuring TLS 1.2, please run AADConnect Wizard to continue with installation and configuration. Please refer to this document to learn more about the steps you need to take to enable TLS 1.2 on your server. This installation requires TLS 1.2, but it was not enabled on the server. After starting I got the following error message: Or better, I wanted to upgrade an existing Azure AD Connect version 1.x server to version 2.x. So, I installed a brand-new Windows 2019 server where I wanted to install Azure AD Connect version 2.x.
0 Comments
Leave a Reply. |