Yes, the x-forwarded-for was added via PowerShell. The screenshot above is validation of the setting being present.
Your suggestion to upgrade one's IIS version, that is an entire OS upgrade. That is a much bigger ask/change than we are trying to do. We are trying to figure out why some Win2012r2 servers are properly doing the x-forwarded-for in our environment, and some other Win2012r2 servers (same OS, same IIS version) do not log when that x-forwarded-for is added.
Is there a ticket or some way to track it? Or some way for the Microsoft team to reach out to me?
Yes, the x-forwarded-for was added via PowerShell. The screenshot above is validation of the setting being present.
Your suggestion to upgrade one's IIS version, that is an entire OS upgrade. That is a much bigger ask/change than we are trying to do. We are trying to figure out why some Win2012r2 servers are properly doing the x-forwarded-for in our environment, and some other Win2012r2 servers (same OS, same IIS version) do not log when that x-forwarded-for is added.