{"id":36,"date":"2009-10-19T21:25:57","date_gmt":"2009-10-20T03:25:57","guid":{"rendered":"http:\/\/blog.escarra.org\/?p=36"},"modified":"2016-07-20T08:23:28","modified_gmt":"2016-07-20T14:23:28","slug":"wpa-enterprise-server-setup","status":"publish","type":"post","link":"https:\/\/blog.escarra.org\/?p=36","title":{"rendered":"WPA Enterprise – Server Setup"},"content":{"rendered":"

So it has been a little over three months since I last posted, and having left off before starting to explain a simple WPA Enterprise implementation, I will now continue.<\/p>\n

I’ll assume you already have a Domain Controller setup with a Certification Authority, and Internet Authentication Service, since that will be the key around authenticating our users and computers.<\/p>\n

<\/p>\n

So, let’s start with setting up our AD. We’ll create two security groups, one for authenticating computers, and another for authenticating users against the wireless network. We can add our Computer objects and User objects from AD to the respective groups.<\/p>\n

\"Screen<\/a><\/p>\n

Next, we’ll configure IAS Policies. Open the Internet Authentication Service console, then right click on Remote Access Policies<\/strong> and click on New Remote Policy<\/strong>.<\/p>\n

We can use the Wizard, as it asks the right questions to get this working quick.<\/p>\n