One of the things I get involved with at work is sorting auto-deployment of wireless profiles via Group Policy. In the past this has been great for configuring WPA/TKIP wireless profiles which are fine for most situations. However, most implementations of 802.11n require either no encryption or WPA2 before the advanced features of ‘n’ (eg. high speeds) are available.
Microsoft Server 2003 doesn’t support WPA2 in Group Policy, despite the fact it’s in XP Service Pack 3, and Windows Server 2008. It is also supported in Windows XP Service Pack 2 with update kb893357. After a lot of faffing around various forums it turns out there is a workaround to implement WPA2 in GPO on Server 2003.
Updating Active Directory for Group Policy Enhancements
Described in http://technet.microsoft.com/en-gb/library/bb727029.aspx
. This is just a howto so I won’t go into detail, just how to get it done.
Copy the file 802.11Schema.ldf onto the Active Directory server (the content of this file is listed at the end of this post in plaintext which you can cut n paste into a file if the link fails. Open command prompt and run the following command on AD Server:
C:\ldifde -i -v -k -f 802.11Schema.ldf -c DC=X [Distinguished_Name_of_domain_controller]
It should respond that 6 items have been updated. That’s it for the Server.
Group Policy Update from Vista PC or Server 2008
Join the PC to the domain if not already on it. Log onto the PC as Domain Admin if possible.
Start, Run ‘gpmc.msc’ – If it’s not installed you need to install Microsoft Remote Server Administration Tools for Windows Vista (KB941314)
After the MRSAT have been installed you need to enable them: Go to Control Panel, Programs and Features, Turn Windows features on and off, Enable Tools.
From Group Policy Management you should now be able to select the Wireless Policy under:
Computer Config, Policies, Windows Settings, Security Settings, Wireless Network Policies, edit ‘XP’ policy, select Preferred Networks, and enter or edit the network profile. Change the authentication type to WPA2 and encryption to AES.
The following is the content of the ldf file, you should just be able to download the file above though.
# -----------------------------------------------------------------------
# Copyright (c) 2006 Microsoft Corporation
#
# MODULE: 802.11Schema.ldf
# -----------------------------------------------------------------------
# ———————————————————————–
# define schemas for these attributes:
#ms-net-ieee-80211-GP-PolicyGUID
#ms-net-ieee-80211-GP-PolicyData
#ms-net-ieee-80211-GP-PolicyReserved
# ———————————————————————–
dn: CN=ms-net-ieee-80211-GP-PolicyGUID,CN=Schema,CN=Configuration,DC=X
changetype: ntdsSchemaAdd
objectClass: attributeSchema
ldapDisplayName: ms-net-ieee-80211-GP-PolicyGUID
adminDisplayName: ms-net-ieee-80211-GP-PolicyGUID
adminDescription: This attribute contains a GUID which identifies a specific 802.11 group policy object on the domain.
attributeId: 1.2.840.113556.1.4.1951
attributeSyntax: 2.5.5.12
omSyntax: 64
isSingleValued: TRUE
systemOnly: FALSE
searchFlags: 0
rangeUpper: 64
schemaIdGuid:: YnBpNa8ei0SsHjiOC+T97g==
showInAdvancedViewOnly: TRUE
systemFlags: 16
dn: CN=ms-net-ieee-80211-GP-PolicyData,CN=Schema,CN=Configuration,DC=X
changetype: ntdsSchemaAdd
objectClass: attributeSchema
ldapDisplayName: ms-net-ieee-80211-GP-PolicyData
adminDisplayName: ms-net-ieee-80211-GP-PolicyData
adminDescription: This attribute contains all of the settings and data which comprise a group policy configuration for 802.11 wireless networks.
attributeId: 1.2.840.113556.1.4.1952
attributeSyntax: 2.5.5.12
omSyntax: 64
isSingleValued: TRUE
systemOnly: FALSE
searchFlags: 0
rangeUpper: 4194304
schemaIdGuid:: pZUUnHZNjkaZHhQzsKZ4VQ==
showInAdvancedViewOnly: TRUE
systemFlags: 16
dn: CN=ms-net-ieee-80211-GP-PolicyReserved,CN=Schema,CN=Configuration,DC=X
changetype: ntdsSchemaAdd
objectClass: attributeSchema
ldapDisplayName: ms-net-ieee-80211-GP-PolicyReserved
adminDisplayName: ms-net-ieee-80211-GP-PolicyReserved
adminDescription: Reserved for future use
attributeId: 1.2.840.113556.1.4.1953
attributeSyntax: 2.5.5.10
omSyntax: 4
isSingleValued: TRUE
systemOnly: FALSE
searchFlags: 0
rangeUpper: 4194304
schemaIdGuid:: LsZpD44I9U+lOukjzsB8Cg==
showInAdvancedViewOnly: TRUE
systemFlags: 16
# ———————————————————————–
# Reload the schema cache to pick up altered classes and attributes
# ———————————————————————–
dn:
changetype: ntdsSchemaModify
add: schemaUpdateNow
schemaUpdateNow: 1
-
# ———————————————————————–
# define schemas for the parent class:
#ms-net-ieee-80211-GroupPolicy
# ———————————————————————–
dn: CN=ms-net-ieee-80211-GroupPolicy,CN=Schema,CN=Configuration,DC=X
changetype: ntdsSchemaAdd
objectClass: classSchema
ldapDisplayName: ms-net-ieee-80211-GroupPolicy
adminDisplayName: ms-net-ieee-80211-GroupPolicy
adminDescription: This class represents an 802.11 wireless network group policy object. This class contains identifiers and configuration data relevant to an 802.11 wireless network.
governsId: 1.2.840.113556.1.5.251
objectClassCategory: 1
rdnAttId: 2.5.4.3
subClassOf: 2.5.6.0
systemMayContain: 1.2.840.113556.1.4.1953
systemMayContain: 1.2.840.113556.1.4.1952
systemMayContain: 1.2.840.113556.1.4.1951
systemPossSuperiors: 1.2.840.113556.1.3.30
systemPossSuperiors: 1.2.840.113556.1.3.23
systemPossSuperiors: 2.5.6.6
schemaIdGuid:: Yxi4HCK4eUOeol/3vcY4bQ==
defaultSecurityDescriptor: D:(A;;RPWPCRCCDCLCLORCWOWDSDDTSW;;;DA)(A;;RPWPCRCCDCLCLORCWOWDSDDTSW;;;SY)(A;;RPLCLORC;;;AU)
showInAdvancedViewOnly: TRUE
defaultHidingValue: TRUE
systemOnly: FALSE
defaultObjectCategory: CN=ms-net-ieee-80211-GroupPolicy,CN=Schema,CN=Configuration,DC=X
systemFlags: 16
# ———————————————————————–
# Reload the schema cache to pick up altered classes and attributes
# ———————————————————————–
dn:
changetype: ntdsSchemaModify
add: schemaUpdateNow
schemaUpdateNow: 1
-


by guest
02 Jun 2009 at 22:56
Have been getting this error:Entry DN: CN=ms-net-ieee-80211-GP-PolicyGUID,CN=Schema,CN=Configuration,DC=Firets0,DC=FIRENOW,DC=NET
14: Object does not exist, entry skipped
Entry DN: CN=ms-net-ieee-80211-GroupPolicy,CN=Schema,CN=Configuration,DC=FIRENOW,DC=NET
Add error on line 80: Unwilling To Perform
The server side error is “Schema update failed: attribute in may-contain does not exist.”
An error has occurred in the program
Thanks for your time, Michael
by Darren
23 Jun 2009 at 17:45
Hi Michael,
No idea, but the error you’re getting is mentioned at Microsoft under kb276382 with the following explanation. Give their suggestions a go, I can’t be any more help as I never encountered this error.
by mlc9
21 Jul 2009 at 14:14
I’ve apparently updated the Active Directory schema successfully on a Win 2K3 server, as I received the 6 separate “success” command line entries. But, I still do not see WPA2 as an option in the drop down box of the wireless group policy. Thoughts? Does the Win 2K3 domain controller require a restart after this?
by Darren
16 Aug 2009 at 22:48
mlc9 – I didn’t think it needed the restart, but it might be a good idea anyway, it’s quite a fundamental change. Post if that fixes things.
by Nel
26 Aug 2009 at 16:50
Hi there, I’m having the same issue! I did this yesterday afternoon and let everything propogate overnight and upon discovering I still couldn’t access wpa2 I gave the server a reboot but to no avail.
if anyone has any ideas they would be greatly appreciated! Thanks.
by Jari
03 Sep 2009 at 09:00
Hello there
I had the same issue. Booting the server did not help. The only solution was to install a Vista Domain machine and run the management of the Active Directory GPO from it. Now the WPA2 and AES config was there! Thanks a lot!!
by Darren
04 Sep 2009 at 07:20
I don’t know if I made it clear but the GPO updates do have to be made from either a Vista or Server 2008 machine. Glad the info helped anyway.
by David
17 Sep 2009 at 02:12
The item that tripped me up was that while I am an Enterprise Admin and Domain admin, etc, I was not a “Schema Admin.” Adding myself to that group (and logging back in) made things work much better.
Also, while you say “[Distinguished_Name_of_domain_controller]“, I believe you mean “[Distinguished_Name_of_domain]“. Pointing to a specific controller was not effective.
Lastly, it might be worth adding a sample of a distinguished name. I haven’t done AD stuff in a long time, and trying to dig this back out was more effort than I want to admit.
by Darren
18 Sep 2009 at 19:54
It’s a good point – I don’t tend to get involved in AD stuff unless absolutely necessary, I’ll update the article when I get a moment. You’d think that a Domain Admin would have permissions for schema updates!? Thanks for the feedback.
by Stewart
29 Dec 2009 at 14:40
Thanks for the Schema Admin tip
Pingback
by WPA2 missing from policy
15 Dec 2009 at 12:27
[...] I believe you can do it by integrating an update into the 2003 schema. [...]
by MCP
18 Jan 2010 at 05:51
Very Poor Documentation of providing a solution. Sorry, Its not documented properly.