"Can't find the specified file" when trying to rename a folder.
I have a Windows Server 2012 R2 terminal server (we'll call it TERM01) on which we need access to a shared drive from another source (in this proof of concept case \\FileServer\test$) in order to redirect the documents folder. The fileserver with the network share is also a Windows Server 2012 R2 server. The folder redirection has been configured in a GPO with a scope that affects members of a security group (rdp-users). Each time I log into TERM01 with a regular user who is a member a that security group, the folder redirection portion of the GPO fails. I believe I have determined the cause of the failure. In testing access to the share, I connected directly to the UNC path that is used by the GPO and I am able to establish a connection. I can successfully create a new folder so long as I do not change the name. If I give the new folder any name other than New Folder or if I try to rename the folder after the fact, I get the error “Can’t find the specified file” as seen in the image below. This situation only occurs if the new folder on the remote share is created while logged into the TERM01 server only. When I log into another server, TERM02 also a Windows Server 2012 R2 terminal server, the folder redirection does not fail and my profile folder, ladleyb, is created as seen image below also. When I go into the ladleyb folder, I can create files with any name I choose but the folders will still only allow the default name. The effective NTFS permissions indicate that I have full control over the files and folders that I create and I can delete anything I create as well. Both servers are in the same OU in Active Directory and the same GPO applies to both systems. McAfee HIPs software is installed on both TERM01 and TERM02 if that makes a difference.
FolderRenameFailure.jpg
FolderRenameFailure.jpg
Brian B
The question has been flagged to bring it to the attention of more Experts. Meanwhile, does disabling the anti-virus make any difference? The error message sounds misleading. Usually these types of problems say the file can't be modified or is in use. Saying it can't be found also makes it sound like the folder has already been renamed. After the new folder has been created via TERM01, can you look at it/rename it from elsewhere?
ASKER
I just tested the creation of a folder on the shared drive from TERM01 which still produced the failure. I was able to log into the file server and rename the folder that was created from the test. Back on TERM01, I can see the new folder name and I tried to create a subfolder under it which also fails as does another rename attempt from TERM01.
Disabling the Antivirus is not a viable option as this system needs to stay protected while users are on it.
Thanks for the suggestion,
Brian L
Disabling the Antivirus is not a viable option as this system needs to stay protected while users are on it.
Thanks for the suggestion,
Brian L
I know disabling AV is not a long term option, but I would suggest you try it as a temporary test. Just to rule it out.
We have the exact same problem with an terminal server enviroment.
Cannot change foler or file names from the TS, not even with an admin account.
Found that it started around 19-10, same day the rollup 10-2017 was installed.. KB4041693
I suspect the update to be the issue, but can't find anything about this on the MS forums.
@Brian: Do you have the update installed?
Cannot change foler or file names from the TS, not even with an admin account.
Found that it started around 19-10, same day the rollup 10-2017 was installed.. KB4041693
I suspect the update to be the issue, but can't find anything about this on the MS forums.
@Brian: Do you have the update installed?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@Mark B, I do not see the update that you referenced having been installed on the terminal server. I also deleted those registry keys that you suggested. I had previously removed them while trying to lock down the server. Deleting them again has no effect after a reboot of the server.
To add further information after troubleshooting, it has come to my attention that no accounts, not even administrators, have the ability to create folders on the terminal servers local drives either while logged into the terminal server. If I access the C$ share on the terminal server from a remote system, I can create folders with any name. The problem is definitely isolated to logged in users on the terminal server.
To add further information after troubleshooting, it has come to my attention that no accounts, not even administrators, have the ability to create folders on the terminal servers local drives either while logged into the terminal server. If I access the C$ share on the terminal server from a remote system, I can create folders with any name. The problem is definitely isolated to logged in users on the terminal server.
Then a process on the Terminal Server is actively inhibiting those operations. It cannot be related to security (NTFS permissions).
ASKER
Many postings claim that deleting or renaming the following registry keys and rebooting fixed their problem:
HKLM\Software\Microsoft\Wi
{2112AB0A-C86A-4ffe-A368-0
{491E922F-5643-4af4-A7EB-4
{7b0db17d-9cd2-4a93-9733-4
{A302545D-DEFF-464b-ABE8-6
{A990AE9F-A03B-4e80-94BC-9
This did not resolve the issue in my case. I also renamed the same keys under the HKLM\Software\Wow6432Node\
Any other suggestions would be helpful. My client would rather not go through the hassle of creating a new VM and configuring everything all over again.
HKLM\Software\Microsoft\Wi
{2112AB0A-C86A-4ffe-A368-0
{491E922F-5643-4af4-A7EB-4
{7b0db17d-9cd2-4a93-9733-4
{A302545D-DEFF-464b-ABE8-6
{A990AE9F-A03B-4e80-94BC-9
This did not resolve the issue in my case. I also renamed the same keys under the HKLM\Software\Wow6432Node\
Any other suggestions would be helpful. My client would rather not go through the hassle of creating a new VM and configuring everything all over again.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The only other suggested solutions were incomplete. Additional steps were required to provide a complete solution.