Group Policy Pref - Mapped Drives Not Applying to One User


hi all,

i’m new list, please excuse etiquette slip ups.  

have 3 users @ site. machines running windows xp service pack 3 , have client side extensions installed. created group policy map default drives using gp user preferences.

each of drives set "update".

example of policy created xml follows:
<drive clsid="{935d1b74-9cb8-4e3c-9914-7dd559b7a417}" name="h:" status="h:"
image="2" changed="2009-11-25 05:13:58"
uid="{8a44d2f4-aae5-4f43-aeec-d36f08ea619c}" desc="maps users h drive
servername\users$\%username%" bypasserrors="1"><properties action="u"
thisdrive="nochange" alldrives="nochange" username=""
path="\\servername\users$\%username%" label="home (servername)"
persistent="1" useletter="1" letter="h"/></drive>

,

<drive clsid="{935d1b74-9cb8-4e3c-9914-7dd559b7a417}" name="j:" status="j:"
image="0" changed="2009-11-30 03:52:58"
uid="{535cd462-a45d-4363-ada1-2316d5ecc703}" desc="maps j drive users
\\servername\apps" bypasserrors="1"><properties action="c"
thisdrive="nochange" alldrives="nochange" username=""
path="\\servername\apps" label="apps (servername)" persistent="1"
useletter="1" letter="j"/></drive>


group policy applied ou site. 
3 users in same ou.
3 users in same “xxsitecode users” group.

2 of users log pc , mapped drives no issue, 1 user doesn’t.
there no other login scripts , user has no manually mapped drives.
have h drive mapped using profile field in ad object temp measure. every 90 mins other manually mapped drives removed policy.
don’t use roaming profiles

trouble shoot have tried
-    reinstalling client side extensions
-    re-joining pc domain
-    running gpupdate command prompt see if event logs generated (none are)
-    manually mapping drives make sure there network access etc – can manually map them/he can access them.
-    creating user new account, when logs in using account gets mapped drives on pc’s
-    getting user log different pc, when doesn’t drives – it’s not machine or profile
-    manually checking security on user object in ad against 1 of users gets drives mapped

i'm sure gp fine because works 2 other users , testing isolates user account issue.

policy i’m having issues xxxx mapped drives/ printers

have posted issue on tech net gp discussion groups page, haven’t had replies.

suggestions appreciated.
simone

hi again simone,

how under settings tab generated resultant set of policy? did see if drive showed under preferences section? guess i'm mulling on nagging feeling profile level mapping of h: coming after policy preferences mapping.

with respect policy preferences change referring earlier, thinking might try:

- adding additional drive mapping same policy you've been using other users, alternative letter,
- using wmi targetting under common tab target additional drive troubled user, doesn't apply else,
- making sure setting ends appearing within rsop data through double-checking gpmc (since rsop.msc won't this).

here's illustrations of how i'd have set temporary additional drive mapping (i'm hoping these come through okay).

user configuration / drive mapping general properties tab (http://7mgp6a.bay.livefilestore.com/y1pwjudvsuvylv3tc1c2rd_opojmtoxljkihnflhuttnsyogxiwobfbvfwp2ubwrdb8v6va0bow8dtsfdsbmku9xcgr7qkj-h51/gpmc_pref_drivegeneral.png)




common tab configuration (http://public.bay.livefilestore.com/y1pbl7lbhybz1vey3dblw_yrleglrxrii8ytsvyit1wblo5lxndtzpyu-vate3c6h9_tluawbov2hysjo4a0-6jwg/gpmc_pref_drivecommon.png)




targetting properties (http://public.bay.livefilestore.com/y1p-qkmccvku03axvhdpoiq_nybodkzm-yqrr3efnpnr6jvtne-llujdtdxc-wr_l7nxtyaygsdhoq9l3juml19yq/gpmc_pref_drivecommon_targetting.png)




needless user in last picture user, not poor little guest account!

cheers,
lain


Windows Server  >  Group Policy



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS