A Windows Server CAL is required when a user or device is directly or indirectly accessing Windows Server. A Remote Desktop Service (RDS) CAL is also required for users that need to access programs or the full desktop remotely using Remote Desktop Services (RDSs). Both Windows Server CAL (user or device) and RDS CAL (user or device) are required for remote desktop access. RDS CALs contain a product key for activation. As an exception to these rules, up to two users or devices may access the server software, only for server administration purposes, without requiring either a RDS CAL or a Windows Server CAL.
In this scenario, the correct date and time are displayed in the remote desktop session. However, the Control Panel item cannot retrieve the client session's time zone information. Therefore, the time zone information is set to "unknown" in the remote desktop session. Additionally, the applications (for example, Microsoft Dynamics NAV or an application that is built based on the Java rt.jar source) that rely on the GetDynamicTimeZoneInformation API stop working.
This issue occurs because the GetDynamicTimeZoneInformation API does not redirect time zone information. In a remote desktop session, when time zone information is requested to be redirected, the system calls the older GetTimeZoneInformation API. The GetDynamicTimeZoneInformation API cannot return the time zone information in the remote desktop session. Therefore, the applications that use the GetDynamicTimeZoneInformation API may fail.Note The GetDynamicTimeZoneInformation API is introduced in Windows Vista. It is available in Windows Vista, Windows Server 2008, or a later version of Windows.For more information about the GetDynamicTimeZoneInformation API, go to the following Microsoft website:
With the recent launch of XenDesktop 5.6 Feature Pack (FP) 1 Citrix released a great feature known as the Remote PC. The Remote PC feature allows end-users to access their laptops/desktops on any device (Tablets, Mobile Phones or even other remote laptop and desktop) and anywhere (in the office, home and road). Citrix launched this feature for enterprises that are yet not ready to move into VDI mode and this solution allows end-users to continue using their desktop/laptop devices. The device that will be accessing the office desktop/laptop will require Citrix Receive to be installed beforehand.
So, my knowledge on Remote desktop services is not so good, but I managed to get it up and running last year, it's been working just fine for eight months. Now today no Remote desktop users can login. Console sessions are working fine though. I checked and the licensing is okay, no errors. But users trying to login are logged in the security log such:
To narrow it down I followed this tip to get logging running in the netlogon.log-file -US/1001bb80-c490-4ec6-828a-9090588c570c/cannot-remote-desktop-into-windows-2008-server-eventid-4625?forum=winserverTS
I have no clue why this apparently got changed - or other thing made this not to work. But unselecting the "network level authentication for remote-desktop services" for the server worked. Now everyone can access.
I've windows 10 anniversery edition. I'm trying to connect remote windows server 2008 64 bit edition. After some time Remote desktop gives me error "Because Of Error in Data encryption this session will end.". I don't understand what does it mean. Before connection was working fine. I've changed the setting in Kaspersky AV "Do not scan encrypted connections". But it doesn't help. I've not tested any other solution.
I was able to connect to my RDS 2012R2 using the built-in win 10 remote desktop connection via the web interface without problems until the desktop was upgrade to built 14393.187. Now I receive the error message "Your Computer can't connect to the gateway server"
After the upgrade I browser to my RDS and click on the remote desktop connection icon as normal and then I receive a new window that asks for my password, I have double logon so this is not unexpected, the look of the window is new however.
Our desktop appliances are often deployed in remote locations where flexible connectivity is essential. The expansion bay on the XGS 116, 126, and 136 models provides the option to add a 3G/4G module to your appliance. The module can be securely mounted and is then managed from your Sophos Firewall console.
Since the issue has started I have removed the expansion cabinet, updated all sessions hosts to current windows updates and added two more hosts for a total of 14. I have removed all nonessential GPOs, double checked and set session timeouts in both the collection session settings and GPO, Attempted to set keep alive in RDS GPO settings to 1. I have around 15-20 users using 1 remote app on these hosts during daytime business hours.
When users connect to the remote desktop service, ie they connect via rds.domain.com - they initially get the wildcard certificate, but when they are then directed to the individual remote desktop servers, they get an error because they then receive the self signed cert for the servers - rds1.int.domain.com and rds2.int.domain.com.
ManageEngine satisfies this requirement too, it has a free tool called Free Windows Admin Tools which contains 15 free tools that helps you deal with all windows management issues, right from remote troubleshooting to remotely shutting down and restarting your user systems. 2b1af7f3a8