![]() This is only an issue using the powershell specific cmdlet to map the drive. 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. 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. Could be related to certain programs, like Teams or OneNote. 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. Unfortunately, it doesnt get applied consistently. We use the update option and dont use the user context option. Select File from the menu bar and click on Run new task. Map drive group policy Preferences not applying consistently Hi everyone, We deployed Several drive via GPP. Right-click on explorer.exe and select End task > End process. ![]() To do so, Press Ctrl + Shift + Escape to open the Task Manager. ![]() You can temporarily resolve this issue by restarting Windows Explorer. I'm at a complete loss as to why this is an issue. Explorer will not show the mappings until restart. So, you can’t see the mapped drive on File explorer. 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. If I end process for Explorer.exe and re-run it, then it would show and use the new mappings. ![]() You can save the network path in Z and use it in your scripts as a path but users need the mapping in File Explorer. Even documentation in Microsoft Docs is wrong. 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. All the answers saying you should use -Persistent or/and -Scope Global are wrong in scenario when you want to see the drive in File explorer. While it was working there was a strange bug where it would only work if I pasted the code directly into powershell. I'm using Remove-SMBMapping and New-SMBMapping. I'm writing a script to remap drives to new paths (file server migration), and I had everything working. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |