I think Joe was trying to stop the group policy that runs a login script
from taking effect for these users to test out that there wasn't a
conflict happening.

 

Joe, this seems to be a long standing problem with Windows, and we've
certainly had this problem for several years. Every now and then Windows
will fail to map the users home drive correctly if its been specified on
the profile tab. Our googling efforts showed quite a few others having
the issue from way back in 2003, and it doesn't appear to have been
fixed since then as someone reported that it still does it on 2008
(though with a 2003 domain level) .

 

Check out this thread for starters:
http://forums.techarena.in/windows-xp-support/923771.htm

 

We resorted to using login scripts to map the drive, this seems to be
more consistent. Would be interested to know what you find out, as we
haven't revisited this one in a while. 

 

 

From: Ken Schaefer [mailto:[EMAIL PROTECTED] 
Sent: 26 November 2008 05:57
To: NT System Admin Issues
Subject: RE: Group policy question

 

FWIW, this isn't being done through Group Policy AFAIK - you are setting
a property on the user's AD object, not creating a Group Policy Object
that is downloaded and applied on the user's machine.

 

Cheers

Ken

 

From: Joe Heaton [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, 26 November 2008 4:30 AM
To: NT System Admin Issues
Subject: Group policy question

 

Is it possible to add exclusions to a group policy?  I'm having an issue
with some people getting their personal home drives mapped.  When I
started here, this was done with a login script to a manually created,
shared folder.  I've always believed that if the tool is provided, you
should use it, so I would like these drives mapped through ADUC, using
the Profile tab.  However, when I do this, the user will intermittently
not have their home drive mapped at all.  I haven't changed all users
over to the new way, as I need to unshared their home directory, copy
the current contents to a temp location, delete the current folder and
allow AD to recreate it with the proper rights.  But I have been doing
this for all the new employees.  It just so happens that these new
employees are the ones with the issues, so I would like to exclude them
from the GPO that does the old login script, to see if the problem goes
away.

 

Joe Heaton 
 
=== 
STEMCOR CONFIDENTIALITY AND DISCLAIMER NOTICE 
This e-mail is intended only for the addressees named in it. The contents 
should not be disclosed to any other person nor copies taken. Any views or 
opinions presented are solely those of the sender and do not necessarily 
represent those of Stemcor unless otherwise specifically stated. Stemcor does 
not accept legal responsibility for the contents of this message nor 
responsibility for any change made to it after it was sent by the original 
sender. You are advised to carry out a virus check before opening any 
attachment as Stemcor does not accept liability for any damage sustained as a 
result of any software viruses. You should be aware that Stemcor reserves the 
right to read incoming and outgoing emails. 
===

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to