ERROR 1104: C:\USERS
This is in your Group Policy Management Editor under User Configuration, and then Preferences, Windows Settings, Drive Maps.
Type in the location example: \\server\sharename and change to Update
Do not set it as replace;
Replace used to be the recommended practice pre Win8.1/Win10/Server2012r2, Microsoft changed how it behaves without much documentation on it.
The symptoms were completely random errors popping up with no realtion to each other.
Exit out and try the same steps again and it should work without problems.
It would only impact individual users on the RD server, not all users at the same time (so when their group policy happened to be refreshing causing the mapped drive to briefly disconnect and then reconnect).
And there was zero packet loss or other network issues.
1) Browse to bro folder and find ‘Config.fpw’ file. Open with notepad and make sure it reads as below:
Test for a day or so… if no changes, then continue with
2) We would like to suggest Googling ‘turn off background refresh of group policy’
3) Google ‘Configure keep-alive connection intervall’
4) Increase Ram on your server(s)
5) In Utilities – Define Your Company Information – Software Directories tab. Please change the folder location using the numbering system to the next sequential number. Having tremendously full folders may create a hug lag on your network, thus creating a disconnect to the server.
6) The picture below is a suggested solution. This was a fix for a power broker customer.
(Disclaimer: This has not been tested by the Power Broker support team, this is just a suggested solution.)
Go into Control Panel – Power Options. Next to Balanced (Recommended), click on ‘Change Plan Settings’. From the drop down that says ‘Put the computer to sleep’, choose Never.
‘Speed up’ Suggestion
If users are reporting a speed issue from workstations connecting from a mapped drive taking 8 seconds to load the software login screen. Once the registry was changed on the server, the screen then changed from 8 to 2 seconds.
– Add the three highlighted with Edit, New, Dward Values.
HKEY_LOCAL_MACHINE and locate System\CurrentControlSet\Services|Lanmanworkstation\Parameters
The issue has been resolved. It appears that our SysAdmin enabled “Digitally Sign Communications” for SMB protocol which is disabled by default except on Domain Controllers.
We had to add the following to our Group Policy to have this remediated:
Windows Settings->Security Settings->Local Policies/Security Options->Microsoft Network Client->Policy:
Microsoft network client: Digitally sign communications (always) – Disabled
Microsoft network client: Digitally sign communications (if server agrees) – Disabled
Windows Settings->Security Settings->Local Policies/Security Options->Microsoft Network Server->Policy:
Microsoft network server: Digitally sign communications (always) – Disabled
Microsoft network server: Digitally sign communications (if server agrees) – Disabled