Discussion Locked

Default Domain Policy GPO not working.

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a basic new installation W2K server with AD, created a Domain User & a Domain Local Group, put my user in the group, went into Default Domain Policy & edited it as follows: User Configuration - Windows Settings - Scripts - Logon properties, Browsed & Added a batch file that simply maps a network share. Added my group to the security list of the Default Domain Policy & made sure the READ & APPLY GROUP POLICY permissions were ticked. My user has rights to the shared folder being mapped by the login script. User is in the default Users folder/container. Any ideas on why the script doesn't run? I works if I assign it directly to each individual user (selecting the user - Properties - Profile - Logon Script & entering the batch filename). Please help.

2 replies

by usvirus01

check the event viewer of the user machine after a fresh system start, probably there might be some syntactical error in the batch file. Make sure the batch file is stored in the location:
\\somedomain.com\sysvol\somedomain.com\Policies\{31B2F340-016D-11D2-945F-xxxxx00000xxx}\USER\Scripts\Logon

by farayi

Thanx usvirus01. Sorry I've not been able to respond to your reply due to other pressing commitments. I checked everything & it's all as you suggested. What I've now discovered was that if I put the IP address of the W2K server as the client's DNS server, the policy works, but then the client cannot access internet because that particular W2K server is not the DNS server for the internet. I'm new to W2K as you can guess. Can someone try & explain to me what's going on here? Are policies tied-inwith DNS. I've been trying to learn W2K DNS server on the side, and that's proving to be a nightmare too. Please don't laugh, help, I'm sure you were all once in the dark too.

This discussion is closed to new replies.