Drive Map Preference - Windows 7

[zenful6219]

I am using the Drive Mapping preference to map three network drives to DFS shares. On Windows XP computers, the drives are mapping to drive letters and a folder is created on the Desktop for each, but, on Windows 7 Pro computers, only 2 map properly. The third preference creates a folder on the Desktop, but will not map a drive letter. In the Event Viewer, I get the following:

The user 'S:' preference item in the '<GPO name and GUID>' Group Policy object did not apply because it failed with error code '0x80070035 The network path was not found.' This error was suppressed.

Nothing is connected to S: and I don't understand why it happens only on Windows 7 computers. I hope someone can suggest a fix.

[drbayer]

I have found that under some circumstances in Win7 you need to specify "run in logged on user's security context" for mapped drives & printers if they are not universally accessible. If it tries to map using the administrator or system context, it doesn't necessarily have access to the network resource if you have UAC enabled.

[jeremym]

I would bet if you tried to manually connect, you would encounter the same problem. This appears to be a common issue with a common error code that's NOT specific to GP.

[Ook]

I'm not sure if this is the same thing, but we've often seen these kinds of problems when redirecting My Documents (etc) to network drives - when users then run software installers using elevated rights, the administrator account can't find the My Docs folder anymore because it can't see/use the network drive.

We've solved this by adding an "Enable Linked Connections" registry key which basically links the your account and the admin account together (just for access to network shares):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLinkedConnections"=dword:00000001

Also see KB article 937624 for more info!

[zenful6219]

I would bet if you tried to manually connect, you would encounter the same problem. This appears to be a common issue with a common error code that's NOT specific to GP.

When we manually connect, we have no problem.

[zenful6219]

I'm not sure if this is the same thing, but we've often seen these kinds of problems when redirecting My Documents (etc) to network drives - when users then run software installers using elevated rights, the administrator account can't find the My Docs folder anymore because it can't see/use the network drive.

We've solved this by adding an "Enable Linked Connections" registry key which basically links the your account and the admin account together (just for access to network shares):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLinkedConnections"=dword:00000001

Also see KB article 937624 for more info!

I tried the Enable Linked Connections reg key, but it made no difference.