Skip to main content

Install Wireless Networking on Server 2008 R2

By
Recently I installed a couple of new servers in my test lab.  They had both wired and wireless NICs installed on them.  I configured the wired NIC without any issues.  The wireless takes a few extra steps.
To get wireless functionality on a server, you need to enable the Wireless feature.
On your Server 2008 R2 server, open Server Manager.  You can do this in your Administrative Tools or by clicking the icon in the quick launch bar image.

Once the Server Manager has open, click Features.

With Features open, click Add Features to the right.

Once the Select Features window opens scroll to the bottom of the list and check that feature called Wireless LAN Service.

Click Next
image

Click Install.

Click Close.

Close Server Manager.

Click Start.

Right click Network and select Properties.

In the upper right corner of the Network and Sharing Center, click Change Adapter Settings.

If your wireless adapter is Disabled, right click it and select Enable.

Right click your wireless adapter can click Connect/Disconnect.
image

Select your wireless network and continue the configuration according to the security policy of your organization.
Labels:

Comments

Unknown said…
Right. But how to get going with DWA-525 Dlink wireless network adapter on a Server 2008 R2 machine?

Sai Narayana
India
April 23, 2011 at 11:21 PM
Jason Yoder, MCT said…
Sai,

I do not have one of those in stock. You are going to need to contact the manufacture for installation instructions.
April 25, 2011 at 6:00 AM
Anonymous said…
helpfull :D thx
March 22, 2012 at 12:50 AM
Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more