Skip to main content

Install Wireless Networking on Server 2008 R2

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.

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
Sai,

I do not have one of those in stock. You are going to need to contact the manufacture for installation instructions.
Anonymous said…
helpfull :D thx

Popular posts from this blog

How to list all the AD LDS instances on a server

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.

How to run GPResult on a remote client with PowerShell

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.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the