Log on script for Group Policy in server 2008

Attempting to set up a group policy log in script to map drives.

Currently the users are having the drives mapped but we are wanting to change to a global policy.

In server 2003 there is no group policy (right click on the group OU and see it in 2008 and not in 2003)

In server 2008 the logon bat file works on the local machine and in the Active Directory Profile. But only some of the drives are mapped in the Group Policy Management.

Any further details needed, suggestion, guidance would be greatly appreciated.


Thank you,
ascentsysAsked:
Who is Participating?
 
ascentsysConnect With a Mentor Author Commented:
Changed the local path to domain path instead of C:sysvol... of the location of the script .. found this on http://www.youtube.com/watch?v=5E34QVxdcGQ
0
 
tmoore1962Commented:
It sounds like you have both a 2003 and 2008 DC in your network.  It is highly possible your domain wasn't prepped correctly when the 2008 DC was added.  That would be why the GP only shows up in the 08, see this link about installing a 08 DC in 2003 domain:
http://www.netometer.com/video/tutorials/windows-dc-2008-add-upgrade/
You can do a 'set' command from a dos prompt to see which DC the workstation used to logon,  do the drives map correctly when the 08 is the logged on server?  Since the policy doesn't show up in AD on the 03 system then when authenticating to that server the policy won't map the drives
0
 
ascentsysAuthor Commented:
I have verified that the local machine is set to the log and is logged to the 08 server and does have DC.

The logon.bat is set on the 08 server in the path \Windows\SYSVOL\domain\scripts and the GOP is pointed to that same path. Six drives do not map. Eight drives do map. I have verified sharing and of course that folders and names exsist and match the script.

Further advise?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
DonNetwork AdministratorCommented:
0
 
ascentsysAuthor Commented:
Didn't match for the set up in my AD

Neither solutions worked found the solution myself
0
 
DonNetwork AdministratorCommented:
Didn't match for the set up in my AD

How's that ??

Neither solutions worked found the solution myself

And what would that be ?
0
 
ascentsysAuthor Commented:
I apologize and I realize all of us are busy. I remember I had to set my policy as the first policy and then enabled and forced. I will come back later and give further details
0
 
ascentsysAuthor Commented:
Found solution on google
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.