So the profile server isn't able to do anything either.
I can get into the folder, but if I try to go to a sub folder, I don't (as a domain admin) suddenly have access. The users have a roaming profile that's saved to the fileserver upon logoff. I can sometimes see the ProfileImagePath is to a temp folder. If I check regedit under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList, I don't see a. The only way I've found to fix it is to reboot the Terminal server. I have no way of knowing if they are logging off (despite continued re-education) or if they are just disconnecting, leaving the session to be interrupted Several users across two different terminal servers are being forced into using a temporary profile.
I have been searching the internet for 2 days now but found nu solution. When I create the rdcb database beforehand and try to connect to it by creating a dataset via odbc data resources, this works without problems.
#Remote desktop server 2016 not mapping local drives driver#
I have also tried with the latest odbc driver using this string:ĭRIVER=ODBC Driver 17 for SQL Server SERVER=servername\instance Trusted_Connection=Yes APP=Remote Desktop Services Connection Broker DATABASE=rdcb This is my connection string:ĭRIVER=SQL Server Native Client 11.0 SERVER=servername\instance Trusted_Connection=Yes APP=Remote Desktop Services Connection Broker DATABASE=rdcb When I try to enable HA on the connection broker, it says the database is not available. The servers are in the same subnet and firewall settings are OK. I installed the SQL server native clientġ1 on the CB server. Created a login in SQL server for this group and gave it the db creator role. I created an AD security group and added the CB server to it. One of these instances needs to contain the connection broker HA database. I have a SQL server 2017 which has multiple named instances, no default instance. I'm setting up an new RDS environment consisting of a server with the connection broker, rdweb and licensing role and 1 session host.
(A device which does not exist was specified.)ĥ) The IO operation at logical block address 0x24ea0 for Disk 4 (PDO name: \Device\00000131) was retried.įor issue 1 i've looked at the KB and checked several other posts, using diskpart to look at the uniqueid, they are all different.ģ, 4 and 5 I could do with some advice please. Corruption may occur in VolumeId: \\?\Volume, DeviceName: \Device\HarddiskVolume27. Go to Microsoft's support website () and search for KB2983588 to resolve the issue.Ģ) An error was detected on device \Device\Harddisk4\DR24 during a paging operation.Ĥ) The system failed to flush data to the transaction log. Upon investigation, we're noticing the following errors.ġ) Disk 4 has the same disk identifiers as one or more disks connected to the system. The system became completely unresponsive. Running a test RDS2019 server with UserProfile disks hosted on an RDSbroker share on 2016.Įverything was fine but since the weekend, logging new users onto this server caused a black screen.