Question Locked

Windows server 2003 Group Policy

0 helpful
21 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm using Windows server 2003 and i've got Group policy program and i've added my Policy to my Domain ( Home.local ) And for some reason the policys will only take affect on the server computer.

I've used the command gpupdate /force i've logged off logged back on restarted infact but for some reason it won't work!

Any ideas?

21 replies

by ic-it

Usually the easiest way to deploy the policies is to attach it to a specific OU with those computers in it.

You have joined the other computers to the Domain (I hope).
Also insure that the policies are not blocked on the OU.

by cooljase

Yes they are connected to the domain and the profiles reside on the server along with there files i've got everything perfect.

Not sure what you mean by the OU as i'm very new to server 2003

by ic-it

An OU (Organizational Unit) is a container for seperating different functional Units, computers, or users.
In a Domain environment you normally do not want certain Group Policies to apply to all users, all computers, and/or your server(s).
There is a default container called computers. You could remove your server from that container and link the Group Policy to it (provided the other computers are listed there.
If you have not done so, download and install the 2003 server admin pack and GPMC (Group Policy Management Console).
Use the AD Users and Computers mmc to easily view those objects.

by david.baines

This is a tool in the group policy management consol that enables you to test your policies to see if they run clean or fail. They also usually tell you why they failed, indicating where the problem lies.

Usually with group policies, the problems lie with permissions sopmewhere along the line..

You have to ensure that the security filtering INCLUDES the computer you are running the policy from, and also the group your user is a member of is included in the filters...

This can all be found in the group policy management console, on the "Scope" tab.

Dave

by cooljase

I'll give the scope tab ago any more details you can give me to make this a little bit easyer?

EDIT: The admin pack installed fine

What do i do now guys?

EDIT Again: I've checked the scope and all the nesscary users are in there, i notice that when i log in using Administrator on a Work station the plolicy works! But i'm confused as why it does not work for the rest!

by downrighttired

Probably one of the more confusing issues w/ GP when your starting...
Basically User configurations will be applied individually when that user logs on. So these should be applied to users (theyll have no effect on computers). If its only applying to your admin account it could be that youve applied the policy to the wrong OU or your users ou is blocking it. In active directory users and computers create a new organizational unit. Move the users you want to affect into that OU then apply your policy to that ou and try it. just a thought.

O and just to finish the inital thought, computer configurations will apply to the whole computer its linked to, as well as all the users that happen to use that computer. These policies are applied before you logon, as apposed to user configurations which are applied second, after the user logs on. hope that helps....

by ic-it

On this tab, in the lower section, what does it have under Security Filtering? It should be the users, groups, or computers that the policy is applied to.

by cooljase

Thanks for that, i've got the GPMC but not this admin pack i'll download and install it and have a fiddle around with it.

I do remember seeing a tutorial online about setting certian groups (admins) so the policy does NOT apply again to do with the premissions

by cooljase

Before i comment on what you've said i'll give everyone an update so far

The group policy applies to The Administrator on Windows XP + VISTA
And the Group policy applies to everyone on vista but for some reason not on XP!

Regards the grouping, i already have set up one called Home Users and it's in there but it's not picking it up for XP

by ic-it

Add Authenticated users to the scope.
On the domain Administrator and local administrators block inheritance.

by tokunbo007

hello all,

Pls why is this happening: Im using Windows 2003 Standard Server edition. Domain controller is installed/set up. Fine. A client PC is joined into the domain. Fine. I can see the client PC name in the servers 'Computers' tab. I can see the domain controller(DC) in the 'my network places' of the client PC.

I create a user/pass on the DC and at first I can loginto/join the domain from the client PC. Fine.

Then I observed that policies I create on the D.Controller are not applied to the Client PC/User created.

I also discovered that I can still log-in into the client PC using the same 'users' username/password which I created on the DC, even with the client PC disconnected(LAN disconnected) from the network....as if that username/pass were created directly on the PC. I saw the username listed in the Documents and settings of the CLient PC. I believe this is not how things are supposed to work..as in i shouldnt be able to loginto the client PC (domain) using the user/pass on the DC if the client is disconnected from the network.

Why is this happening. Is it that the client is not properly joined...or theres something else i havent done.

by cooljase

Hey, go post your own question and dont hijack mine!

IMPROVEMENTS:

I've found out it was to do with the DNS why the group policy was not 100% working!

I pointed the DNS towards my server and the policy worked which is great only problem is pointing the DNS towards my server has nocked out the internet for those computers

Server DNS: 192.168.0.3
Router(Internet): 192.168.0.1

by downrighttired

dont you hate that!
I had the same issue when I set up my first profesional domain(CG IT helped me solve it > http://tinyurl.com/2ps5p5).
Heres the thing,
you did the right thing to point all your hosts to your DC. Now what you need to do is make sure your domain controller forwards all domain names it cant resolve to an external dns server. see this MKB > http://support.microsoft.com/kb/825036/en-us

basically you want to make sure, first of all, the your domain controller points to itself and only itself as the dns server (set this manually in network settings).
Then go into your DNS mngmt console. Right click your server and go to properties. Go to the forwarders tab. The only thing you should see in here is in the first box "All other DNS domains". If its set like that good, leave it. Now go to the root hints tab and there should be a list of servers.
Provided you dont have forwarders set, and your domain controller is looking to itself for DNS resolution; your DC will use this list to resolve all internet domain names.
I think.....

by ic-it

DownRightTired has it right. DNS Forwarding.
Another option would be to turn off DNS on the server and allow the Router to handle the resolution.

by cooljase

How can i make it do that?

I don't think you can have 2 DNS's

At the moment the Server is plugged into the router but i think it's ment to be The Internet is plugged into the Router and then the server gives out the net if you get me?

by downrighttired

sorry i edited my last post to include more info, see if it helps.
And no, sorry i dont quite get what your asking??

by ic-it

You will do ok with the forwarding.
The only advantage to using the router to do the DNS is that you may want the other computers to still have internet access should you be "learning" on the server, or shutting it down for any reasons.

Basically you would need to turn OFF DNS and DHCP on the server.
On the router you would set it to use DHCP (assign a static IP for the server) and set the scope to exclude the server.
The Gateway would be the router and DNS as set from your ISP.

by downrighttired

sorry i thought you were asking me.
Hes right though if for whatever reason you shut down the DC you will lose internet access on your host pcs.
As a backup option you could go to the "Alternate Configuration" tab of each pcs TCP/IP settings and set your router as both the Gateway and the DNS server. This way if your DC is down you SHOULD still be able to connect, although Ive never actually tested this.

by cooljase

Oh god theres so much to do just to get Internet access and have a group policy in action at the same time! *screams*

This discussion is closed to new replies.