In our Server 2003 domain, my login script that uses the IFMEMBER command to look at group membership to map drives does not always work.
We have 3 servers acting as DC's
During login, the XP client will see the login script. One of the first lines is the script is to show the list of groups that user is a part of
net use M: \\%DomainController%\NETLOGON /persistent:no
echo Setting Drive Mappings ...
This ALWAYS show the local groups, but intermittently does not read which domain group the user is a member of. When this happens, the rest of the session doesn't get set properly.
Sometimes, the user just logs off and back on and it works. Sometimes, they have to logoff and back on more than once until the domain is recognized. I've found that if they restart their computer it will find the domain the next time it boots up.
When I map the drives using the net use command, I have /persistent:no at the end each time.
My Win2k workstations do not have this problem.
Key Steps I've taken
1) net config server /autodisconnect:-1 command run on my DC's
2) Name space registry entry deleted on the workstations
3) Enabled the Group Policy entry to 'Always wait for the network at computer startup and logon'
I know I can see the Domain Controller because the script is running, but it doesn't seem to be communicating properly with the AD to determine group membership.