Jump to content
|Topic||Stats||Last action by|
|Gunman killed after shooting 2 officers at Minnesota city hall||
|Xbox One features coming with the Windows 10 upgrade||
|Windows 10 Technical Preview||
|Perhaps some users need to check out the definition of accessibility? (Windows feedback catagories)||
|X-Fi Titanium and Build 9926||
Posted 08 October 2012 - 17:19
Posted 08 October 2012 - 17:35
Posted 08 October 2012 - 18:51
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.
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
Posted 08 October 2012 - 19:23
Posted 08 October 2012 - 19:26
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.