Hi Supun,
Windows Server 2022 support on the middleware server was added with UPD22.
Windows Server 2025 support has not yet been announced.

Best regards.

Hi Ben,

Thank you for the confirmation.

Is there a Shared Benchmarking Document, which I could refer to when this is available?

I cannot check this in current Tech document because that link is internal.

Best Regards,

Supun

Hi Supun,

I am not aware of this information being publicly available for IFS Applications 10.
I verified the details from an internal SharePoint page managed by IFS R&D.
If you require updated details you can always open a support ticket.

FYI: For IFS Cloud the information is available via the documentation.

Best regards -- Ben

Hi Ben,

Thank You,

I will create a Ticket as you suggested to get an update later.

Thanks again for the Link you provided for the Cloud version.

Best Regards,

Supun

Please check also this topic and attached documents:

Thank you for sharing.

hello, we recently had an issue with WinServer 2025 and IFS being operative. 

Here I will share what we faced during start of system and what was the root cause of that. 

When trying to open IFS application on Windows Server 2025, the following error may occur: 

Details show following information: 
 

Ifs.Fnd.FndSystemException: Unexpected error while calling server method ClientApplication/IdentifyCurrentUser 

   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync, Boolean integrationGateway) 

   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(String intface, String operation, Object requestBody, Object responseBody, FndRequestContext requestContext, Boolean forcedSync, Boolean integrationGateway) 

   at Ifs.Fnd.AccessProvider.Interactive.FndLoginDialog.AuthenticateCredentials(FndLoginCredentials loginCreds) ---> Ifs.Fnd.FndSystemException: 500 

   at Ifs.Fnd.AccessProvider.FndConnection.CallGetResponse(String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Byte[] requestHeaderBytes, Byte[] requestBodyBytes, FndApfAsyncInvoke asyncInvokeHandle, Boolean integrationGateway) 

   at Ifs.Fnd.AccessProvider.FndConnection.InvokeGetResponse(String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Byte[] requestHeaderBytes, Byte[] requestBodyBytes, Boolean& abandoned, Boolean forcedSync, Boolean integrationGateway) 

   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync, Boolean inteturn off grationGateway) 

   --- End of inner exception stack trace --- 

Solution: 

1. Open Server Manager 

2. Go to Local Server and turn off IE Enhanced Security Configuration: 
    

As a result application opens without problem: 

Explanation: 

This change lower some of security settings for Internet Explorer which is most common cause of this error: 
 

Technical Case Summary: IFS Applications 10 Connection Failure (HTTP 500)

🔎 TL;DR

HTTP 500 during IFS IEE login was caused by IE Enhanced Security Configuration (IE ESC) blocking credential/token transmission.
✅ Resolved by disabling IE ESC for Administrators.

1. Problem Description

An HTTP 500 (Internal Server Error) occurred when launching IFS Enterprise Explorer (IEE) on a specific Windows Server.

The application (deployed via ClickOnce) started correctly but failed during the authentication phase.

📌 Error Stack Trace

!--scriptorstartfragment-->

Ifs.Fnd.FndSystemException: Unexpected error while calling server method ClientApplication/IdentifyCurrentUser

   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(...)

   ...

   ---> Ifs.Fnd.FndSystemException: 500

   at Ifs.Fnd.AccessProvider.FndConnection.CallGetResponse(...)

!--scriptorendfragment-->

🔍 Diagnostic Context

• ✅ Scope: Issue isolated to a single Windows Server
• ✅ User Validation: Same AD user could log in from another identical server
• ✅ IFS Availability: No server-side issues (IFS / DB working fine)
• ✅ Network & SSL:
  • IFS landing page loaded correctly
  • SSL certificate (*.cedo.com) trusted

👉 Initial conclusion: problem is local (OS / security layer), not IFS backend

2. Root Cause Analysis

The issue was caused by IE Enhanced Security Configuration (IE ESC) being enabled with a restrictive policy.

🔬 Key Difference Identified

| IE ESC status | Disabled / relaxed | Strictly enabled |

💡 Technical Insight

Even though Internet Explorer is deprecated:

• WinINet engine + IE security policies are still used by .NET apps
• IFS Enterprise Explorer relies on this layer for HTTP communication

👉 With IE ESC enabled:

• security level = very restrictive

• blocked:

• credential flow

• authentication token exchange

👉 Result:

• IdentifyCurrentUser call fails
• server drops request

• returns generic HTTP 500

3. Resolution

✅ Fix: Disable IE ESC for Administrators

🛠 Step-by-Step

1. Open Server Manager
2. Go to Local Server
3. Locate:

• IE Enhanced Security Configuration (On)

1. Click and set:

• ✅ Off (for Administrators)

1. Restart IFS Enterprise Explorer

✅ Outcome

• Authentication restored
• IFS IEE launched successfully
• Full access to PROD environment confirmed
   

  💬 Key Takeaway

  👉 Even modern enterprise apps (like IFS IEE) can still depend on legacy Windows components

  👉 If you see:

• HTTP 500 on login
• IdentifyCurrentUser failure
• issue only on one server

• ✅ Always check IE ESC / WinINet security policies first