![]() ![]() ![]() Rebooting the server when this problem occurs is not an option since there are other users logged on to this remote desktop server, who have not yet encountered this problem. ![]() When the session is redirected we get the following output on "whoami" and "set": C:\Windows\System32>whoamiĪgain, I replaced the domain and user name. There are no handles on the users NTUSER.DAT file when he is not logged on, so no other process is locking the file in the background - it first gets opened / used when the user logs on to the server via RDP. For example, a Windows Server 2016 RDS license. The second time that device connects, as long as the license server is activated and there are available RDS CALs, the license server issues a permanent RDS Per Device CAL. The issue is solved after the server is rebooted and all users can login just fine until this happens again. When you use the Per Device model, a temporary license is issued the first time a device connects to the RD Session Host. All output on this screenshot is regarding the same user. This is fixed in RLM v11.1BL1 Fix affects: server. I have added a screenshot of the ProcMon Output and blurred user names and IP-adresses for privacy reasons. If a windows server is shut down, it loses information about any roamed licenses. Whenever this happens we can observe a sharing violation on NTUSER.DAT on User loggon. From time to time, no specific shedule identifiable, a user session will be redirected to a temporary profile. Having searched the Microsoft site I can only find references to temporary licenses that expire after 90 days, we have been running this combination of servers for over six months so I am at a los as to. We have a Windows 2012 R2 RDS running as a virtual machine. Recently a couple of users have been receiving pop-ups at login telling them their temporary terminal services license will expire in x days. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |