GPP drive mapping issues on Windows 8

[penfold]

I'm looking at replacing the our logon scripts for mapping Drives with GPP which work fine on Windows 7 but with Windows 8 it throws up an odd error. Most drives map OK but we have a couple that when you first log on it shows the drive but when you try to access it it throws up an error which indicates the network path was not found. However, if you wait a little you can then access the drive ok. I assume this is something to do with logging on too quickly but I can't see where the problem is as this is only apparent for 2 out of 6 of the networked drives.

 

Anyone else come across this before?

[psydii]

I'm looking at replacing the our logon scripts for mapping Drives with GPP which work fine on Windows 7 but with Windows 8 it throws up an odd error. Most drives map OK but we have a couple that when you first log on it shows the drive but when you try to access it it throws up an error which indicates the network path was not found. However, if you wait a little you can then access the drive ok. I assume this is something to do with logging on too quickly but I can't see where the problem is as this is only apparent for 2 out of 6 of the networked drives.

 

Anyone else come across this before?

 

Have you installed the enterprise hotfix rollup etc?

 

EDIT:Windows 8 D'oh.

Edited August 23, 2013 by psydii

[penfold]

I tried that but it says it is already installed. Strange thing to me is that it almost looks like it is still processing some mapped drive settings which is why it produces the error but other mapped drives to the same server are fine.

[psydii]

I tried that but it says it is already installed. Strange thing to me is that it almost looks like it is still processing some mapped drive settings which is why it produces the error but other mapped drives to the same server are fine.

 

Does this happen on a clean machine that has not been logged into before?

 

Check the offline files log to see if there are any clues in there

[psydii]

Does this happen on a clean machine that has not been logged into before?

 

Check the offline files log to see if there are any clues in there

 

Also are the maple drives to different shares and different servers?

[psydii]

Right after you log on what does the following command report?

netstat –noa

Edited August 23, 2013 by psydii

[penfold]

The mapped drives are actually a DFS route but other drives are showing up ok. There is an Warning Event ID 1112 which indicates "..group policy drive maps was unable to apply one or more settings because changes must be processed before system startup or user login. The System will wait for Group Policy processing to finish completely before the next startup or logon from this user..."

 

I assume this is what is causing the problem with drive mappings. It does map the drives, but there seems to be a delay & sometimes requires you to access a different mapped drive before it will allow you to access the problem drive. When clicking on the mapped drive it gives an error that it is trying to connect to a location that is unavailable.

[psydii]

Group Policy Drive maps was unable to apply one or more settings.

 

Also have you got this installed:

Windows 8 and Windows Server 2012 update rollup: February 2013

[JayPeg]

Change you're GPP for the Drive Map to the following:

 

Action Update

Reconnect Disabled

 

Can't recall the exact reason why but it doesn't seem to like any other settings.

[penfold]

Sorry, for not coming back sooner. I think some of the issues may have been from rogue scripts trying to map drives also. I have now moved solely over to GPP for drive mappings for a test user group and it seems to be mapping fine. I just need to sort out our DFS names and ensure that I've gone through all the scripts for mapping drives before I fully move staff over to GPP.