ADMX drive mapping issue
We have a customer with 12 drive mappings pushed via Intune Import ADMX. We uploaded the admx for windows and the admx for the drivemappings. In the configuration created one policy with al the driveletters configured and pushed this to every device in the environment. Al worked great, untill we changed one drive letter from X to Z i remembered correctly and changed the path to a folder deeper in the folder three. Then it was pushed to everyone and people got issues with the drivermappings. Only 2 or 3 driveletters were showing in file explorer. When you want to add the drive letter via the wizard you can see all the paths to the different drive letters are there. Adding them via that way is not possible. We checked all the settings, like persistent drive mappings, enable linkedeconnections, setting all the drives to not configured, Create separate policy for every driveletter, removed the admx in intune and uploaded again, but nothing is working. currently using a custom script via our minitoring system to get it working again. I have used the ADMX by many customers and never have had these issues. Also opened a microsoft case but they couldn't get it fixed. Only way is a fresh install of the device. But 150 devices is a bit to much time consuming for us and the customer. Love to hear how i can solve this issue.New-SMBMapping not showing in Explorer until Explorer process is closed/restarted
I'm writing a script to remap drives to new paths (file server migration), and I had everything working. I'm using Remove-SMBMapping and New-SMBMapping. While it was working there was a strange bug where it would only work if I pasted the code directly into powershell. But if I called the .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. If I end process for Explorer.exe and re-run it, then it would show and use the new mappings. I just ignored this at the time. 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. I'm at a complete loss as to why this is an issue. It occurs in both Powershell 7 as well as Windows Powershell 5.1. Does anyone have a clue as to what is happening here? FWIW I know that drives mapped in the standard UAC user context are not visible to admin contexts and vice versa. That is not the issue here. This is all under the same user context. No elevated admin sessions are at play. In fact, if it were this, restarting Explorer would have no affect. Also this is an issue whether -persistent $true is used or not. Finally, 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. This is only an issue using the powershell specific cmdlet to map the drive.
Map Home-Directory attribute UNC path for locally connected azure-ad joined shared devices.
We have an on-premises Active Directory (AD) environment connected to Azure AD via AD Connect. We’ve successfully joined our devices to Azure AD using Azure AD Join (MEJ) through Autopilot. We also, using Passthrough Authentication (PTA) for Authentication and we have 3 PTA agents (Including AAD Connect) on-premises. Now, we want to grant users access to an on-premises file share (File server) while they are physically connected to the local network at the office. Each user has an individual Home Drive (H:) defined in their On-premises "Home-Directory attribute" (HomeDirectory), and we want to make this H drive accessible for any users who sign-in to a locally connected shared AADJ devices at the office (We don't want these H drives to be available for remote users). Our shared AADJ devices currently have access to on-premises share files when they’re locally connected at the office, but they don’t have access to user's home drive now. In summary, we want to map Home-Directory attribute UNC path for locally connected azure-ad joined shared devices for any individual users who sign in to these devices.
Group Policy Objects - Drive Mapping with Passwords
Struggling to Map a Drive to an external source with a Username and Password through GPO. We are using SIMs as our MIS in school and use certain reporting features that require a mapped drive to the LAs Server, in legacy GPO you could map a drive with a username and password using the CPassword Attribute - but due to being a "known security risk" this was removed by Microsoft. Our users are restricted and have locked down profiles so dont have permission to map the drive themselves using the username and password and because of CPassword Attribute being removed from GPO we cannot map the drive? Any help in doing this through GPO?
