Hi,
I think it would be more to the CLASS information in the Transparent Login script then the Windows Server version.
Especially when you are creating a Transparent Login Script for the SQL Server, I have experienced many times that the CLASS value that I captured turns out to be different when it fails. The script did not change so I know the CLASS value changed with the SQL Studio, possibly some updates to the product changes this value.
So I had to modify the Login Script to be more tolerant to those changes.
Following is my original script named "MS SSMS 17".
You can see [CLASS:WindowsForm10.COMBOBOX.app.0.1974537_r44_ad1;INSTANCE:3]
This value "0.1974537_r44_ad1" from the SSMS product keeps changing and breaks the PAM Transparent Login.
To solve this problem I used "REGEXCLASS" instead of static "CLASS".
Below is the new script I created.
As you can see from below screenshot, the script will be able to detect the input fields even when those values change.
Hope this helps with your Transparent Login.
Regards,
Kim