You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
We can see that the installer is for Windows 10 however a partner reported that they're trying to use Scalus on Windows server too. They reported that when they use Scalus on Server 2016 or 2019 then the main mstsc window is shown with the filled username but and empty target address field. This behavior can be reproduced by manually removing the full address property from a proper rdp file then opened by mstsc.
The URL generated by the SPP portal looks good.
I could reproduce the same with Scalus on Windows Server 2019, so my conclusion is that for some reason Scalus cannot populate the full address property.
If we wish to make Scalus work Windows Server too, please look into this problem.
Thank you!
Viktor
The text was updated successfully, but these errors were encountered:
Hi,
We can see that the installer is for Windows 10 however a partner reported that they're trying to use Scalus on Windows server too. They reported that when they use Scalus on Server 2016 or 2019 then the main mstsc window is shown with the filled username but and empty target address field. This behavior can be reproduced by manually removing the full address property from a proper rdp file then opened by mstsc.
The URL generated by the SPP portal looks good.
I could reproduce the same with Scalus on Windows Server 2019, so my conclusion is that for some reason Scalus cannot populate the full address property.
If we wish to make Scalus work Windows Server too, please look into this problem.
Thank you!
Viktor
The text was updated successfully, but these errors were encountered: