first drive map doesn't work (sorry for yet another thread on this)


i've searched around day before deciding start thread on topic. no matter how configure gpp drive maps, first 1 not map. i've gone far having drive maps map same share, of them map first one. config replace, reconnect not checked (as i'm using replace), have label set, run in logged-on user's sec context checked, remove item when it's no longer applied checked, , item level target that evaluates a single group membership. have "always wait network @ computer startup , logon" enabled, "process if group policy objects have not changed" enabled, , "startup policy processing wait time" enabled , set 20 seconds. 20 seconds else not currently being applied or in picture. i've removed , still have issue.

with said, i'll continue discussions using current setup of 2x drive maps attempt map same share different drive letters , labels. drive map works #2. i'm using win7 x64 vm , snapshots test (uac disabled). same results test user in local admin group , not in local admin group. gpresult \h blah.html shows 'result: failure (error code: 0x800704d0)' drive map #1, , event viewer shows event id 4098 "the user 'r:' preference item in 'mygpo {67b83735-09a2-48db-a16b-d0b6667f1e0a}' group policy object did not apply because failed error code '0x800704d0 network location cannot reached. information network troubleshooting, see windows help.' error suppressed."

how possible, both drive maps #1 , #2 mapping same share? did start out #1 , #2 mapping different shares, still same results where #2 works.

order label letter
#1 cs1 r
#2 cs2 s



so, dns issue. don't understand why though. file share presented through dfs (namespace: \\shares\divisions, folder dcs, folder target fs01.contoso.com). access share, users browse \\shares.contoso.com\divisions\dcs. restate, successful in mapping manually users drive maps not working. these users successful in resolving fs01.contoso.com via nslookup. users successful in leaving out dfs , manually mapping \\fs01.contoso.com\dcs. fs01.contoso.com file system 01 on our nas. noticed other file systems did work via gpp drive maps had dns entry fs02.denver.contoso.com. inconsistency human error, no other reason. changing dns record fs01 fs01.contoso.com fs01.denver.contoso.com , updating folder target in dfs fs01.denver.contoso.com fixed them problem. 



Windows Server  >  Group Policy



Comments

Popular posts from this blog

CRL Revocation always failed

0x300000d errors in Microsoft Remote Desktop client

Failed to query the results of bpa xpath