Create a DWORD entry named EnableLinkedConnections with a value of 1. This is only an issue using the powershell specific cmdlet to map the drive. Navigate to this key: HKEYLOCALMACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem. In fact, if it were this, restarting Explorer would have no affect.Īlso this is an issue whether -persistent $true is used or not.įinally, if I just simply use native Windows cmd prompt command "Net Use" to map the drive, even within the Powershell console, everything works as expected. It occurs in both Powershell 7 as well as Windows Powershell 5.1.ĭoes anyone have a clue as to what is happening here?įWIW I know that drives mapped in the standard UAC user context are not visible to admin contexts and vice versa. I'm at a complete loss as to why this is an issue. If your organization has not requested network drive mapping and would like it to be enabled, refer to How to save files to a network location from Blackbaud. One of the indicators of this issue is the appearance of error 0x80070043 whenever the desktop user tries to connect on a network drive. Well now I'm doing some more testing, now no matter what I do, when using New-SMBMapping in any way, Explorer refuses to see the drive (even new mappings) while the system does see the correct drives via cmdline. Method 1: Delete Your Current Network Drive and Remap One of the most common scenarios where users can’t map a network drive in Windows 10 is when they update from v1909 to v2004. ![]() If I end process for Explorer.exe and re-run it, then it would show and use the new mappings. ps1 script file, the drive mappings would change (as verified by NET USE from the command line), Explorer continued to show and use the old drive mappings. Fix: A registry entry modification can be. Notwithstanding how ridiculous it is that running. ![]() While it was working there was a strange bug where it would only work if I pasted the code directly into powershell. Also the Not seeing network locations when Run as Administrator is checked issue is reported in Windows 10. This is because the mapped drives were created under a login different from the administrator login. ![]() I'm using Remove-SMBMapping and New-SMBMapping. The primary reason for mapped network drives not showing in all folders is because all the folders are hidden in the NAS and other drives. I'm writing a script to remap drives to new paths (file server migration), and I had everything working.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |