Could it possibly be a mixup of mapping the drives from normal and/or elevated permissioned windows?
As crazy as it sounds, I've seen weird behavior like that when there is a mixed consistency of mappings on x64 systems. AFAICT, its usually born of mapping drives from the command prompt. To clear it, I have to go through and remove the mappings from both normal and elevated CMD windows. I have not been able to intentionally replicate the issue consistently, but I've encountered it enough times for it to be in my thought process. -- Espi On Mon, Aug 1, 2016 at 11:09 AM, Bill Humphries <[email protected]> wrote: > Hi all, > > > > I’m trying to solve a weird issue on one laptop for a client. There are > several drives mapped using GPO on a 2008r2 domain. As expected, most > laptops show a red x over mapped drives when off the company network. They > enable VPN and then have access. > > > > I have one system (win7 64 bit) that when the user logs in away from > corporate network, the mapped drives do not appear. I tried running > gpupdate /force after enabling VPN without success ...but understand that > probably wouldn’t work anyway because drive maps in GPO typically only > happen at logon. > > > > I tried creating a bat file to net use the drive mappings so that the user > could run this after turning on the vpn. This fails with an already in use > error. Because of the error, I went to look at the screen where you > manually map a drive. And the error is correct. All of the drive letters > we use show as mapped to the correct UNC path. But the mapped drives do > not show up in explorer and explorer doesn’t recognize the drive letters as > valid location if you enter the drive letter in the address bar. > > > > Anyone have any insight as to why this laptop hates me? > > > > Thanks. > > > > Bill > > >
