• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 670
  • Last Modified:

WPA2 option not available in Group Policy Object Editor

I have deployed a 802.1x wireless solution for our laptops.  This is all up and running with WPA.

I'd like to implement WPA2.  I can configure the XP Clients manually to use WPA2 and this connects and works.  

However, in Group Polocy Object Editor on our 2003 Server, I edit our wireless group policy object, go into
Computer Settings > Windows Settings > Security Settings > Wireless Network (IEE 802.11) Policies
and edit our Wireless Policy from there.

When I do this within the wireless properties the options for 'Wireless Network Key' only provides the following Network Authentication Types.

-Open, -Shared- WPA or -WPA-PSK,   there is no option shown to WPA2.  My initial thought is that we need an updated ADM template but I have been unable to find one.

Any ideas?
Thanks in advance.
0
nationalschool
Asked:
nationalschool
  • 2
1 Solution
 
Darr247Commented:
You should be able to customize your ADM files as needed, though some changes are really 'Preferences' rather than 'Policy'. i.e. you set the default at logon with a GPO, but the user is still able to change it during the session if there's nowhere in policy to lock down that setting.

See http://www.petri.co.il/adding_new_administrative_templates_to_gpo.htm
0
 
nationalschoolAuthor Commented:
We managed to do it from a 2008 box in the end, connecting in to the 2003 DC that had the policy on .  (note the 2008 server wasn't actually a DC).  A shame Microsoft haven't made it easier but it works now.

Thanks.
0
 
nationalschoolAuthor Commented:
Also, looks if so you could do this by making your own custom ADM.  All OK now.
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now