none
Anyone ever faced any issues in FIM 2010 after servers moved to TLS 1.1 or TLS 1.2? RRS feed

  • Question

  • Hi All,

    Just wanted to check if anyone ever came across any issues when FIM 2010 servers were updated to use TLS 1.1 or TLS 1.2?

    Thank you in adavance.

    Best Regards,

    Rajan Shrivastava

    Tuesday, February 9, 2016 7:15 PM

All replies

  • Hi,

    it depends on what OS and settings your clients, if any , and servers are running.

    see also here http://blogs.msdn.com/b/kaushal/archive/2011/10/02/support-for-ssl-tls-protocols-on-windows.aspx.

    Hope that helps,

    Lutz

    Monday, February 15, 2016 2:43 PM
  • TLS protocol and FIM / MIM.

    Depends on the feature. Anything which relies on OLEDB will not work. This includes Portal and Service installs, upgrades; and the SQL MA.

    For the Portal installs TLS 1.0, 1.1 need to be temporarily enabled, then can be disabled afterwards.

    Currently the SQL MA will not work.

    There are two bugs opened against this behavior. As of 8/28/2018 the bugs are not resolved, but will be very soon.

    As far as other functionality, there are separate SQL upgrades to support TLS 1.2, search for SQL TLS 1.2. On the FIM or MIM server make certain of the Native client being used and make sure to upgrade that client. It is easiest to choose to 'upgrade all' when running the SQL update. Functionality can be tested by creating a UDL and testing Native Client connectivity to SQL. I will repost to this thread when the bugs are resolved.

    Wednesday, August 29, 2018 4:38 PM
  • TLS protocol and FIM / MIM.

    Depends on the feature. Anything which relies on OLEDB will not work. This includes Portal and Service installs, upgrades; and the SQL MA.

    For the Portal installs TLS 1.0, 1.1 need to be temporarily enabled, then can be disabled afterwards.

    Currently the SQL MA will not work.

    There are two bugs opened against this behavior. As of 8/28/2018 the bugs are not resolved, but will be very soon.

    As far as other functionality, there are separate SQL upgrades to support TLS 1.2, search for SQL TLS 1.2. On the FIM or MIM server make certain of the Native client being used and make sure to upgrade that client. It is easiest to choose to 'upgrade all' when running the SQL update. Functionality can be tested by creating a UDL and testing Native Client connectivity to SQL. I will repost to this thread when the bugs are resolved.

    Thanks for the information you have provided. As you haven't updated this  to say that the bug reports have been resolved, I just want to ask if there are any updates. 

    Are there any requirements, e.g., service packs for FIM 2010 itself, which will need to be applied? We have an RTM version which was set up left at that level.

    Thanks for the link about SQL. Our SQL is behind the requirements.

    Thursday, February 21, 2019 2:17 AM