4 replies to this topic

[bguy_1986]

We recently upgraded our domain to 2008 R2 finally from 2003. Somewhere inbetween it broke our Wireless Network Settings GPO (we are assuming moving to 2008, or 2008 r2 domain broke it {can't think of any other changes}). We recreated the whole policy and it still pushes nothing out. We are kind of at a loss. We don't have anything in the event logs on the clients. I was comparing the Local Group Policy Editor to the server group policy and noticed it doesn't contain some of the settings that the server has. I doubt this is the problem but would just like somebody to confirm that this is correct or if anybody else has any ideas. As far as I can tell, all our other group policy settings are getting pushed out correctly.

[TPreston]

_{Use WPA 2 Enterprise, If you have a NPS server you can use it to authenticate domain users using their windows accounts ie they don't need to enter a password}

[bguy_1986]

TPreston, on 08 October 2012 - 17:35, said:

_{Use WPA 2 Enterprise, If you have a NPS server you can use it to authenticate domain users using their windows accounts ie they don't need to enter a password}

We have the policy all set up, it just won't go down to the clients... We've even tried importing a profile, and that won't even apply to the client computers.

[+sc302]

local policies are different than server policies. you will have many more server policies than local policies. to see what policies are being ran, you need to check the resultant set of policies. You can do this by running rsop.msc

also you can check to see what policies are being applied and ignored by running gpresult /r at a command prompt.


These two tools are what is needed to successfully see what the client is doing with policies, what is being grabbed, what is being ignored, and what is actually being applied and what policy is applying it. You say it isn't being applied, have you checked to verify that the groups/users you wish to apply this to exist. You are also in computer configuration, you do understand that that policy does not apply to people, it applies to computers. You force that policy to apply to users and it will not apply because users are not computers.

[bguy_1986]

We figured it out.... Not sure how it happened, but we had another policy with blank wireless settings overwriting our wireless policy.

sc302, on 08 October 2012 - 19:23, said:

local policies are different than server policies. you will have many more server policies than local policies. to see what policies are being ran, you need to check the resultant set of policies. You can do this by running rsop.msc

also you can check to see what policies are being applied and ignored by running gpresult /r at a command prompt. These two tools are what is needed to successfully see what the client is doing with policies, what is being grabbed, what is being ignored, and what is actually being applied and what policy is applying it.

rsop.msc is what we used to discover our problem. Thanks!