Wireless LAN Service Overview
Updated: May 9, 2012
Applies To: Windows Server 2012
The Wireless LAN service is a feature in Windows Server® 2012 that you can use to enable the wireless WLAN AutoConfig service, and to configure the WLAN AutoConfig service for automatic startup. Once enabled, the WLAN AutoConfig service dynamically selects which wireless network the computer automatically connects to, and configures the necessary settings on the wireless network adapter. This includes automatically selecting and connecting to a more preferred wireless network when one becomes available.
In Windows Server® 2008, installing the Wireless LAN Service server feature did not require restarting the computer. The restart was added in Windows Server 2012 to support the Windows Connection Manager service. The Windows Connection Manager service runs in an svchost.exe process which is already running when the Wireless LAN Service feature is installed, which is why a restart is required. Additionally, to start the WAL AutoConfig service requires an additional step, which is explained in the following procedure.
To enable the Wireless LAN Service
In Server Manager Dashboard, click Manage, and then click Add Roles and Features. The Add Roles and Features Wizard opens.
Click Next. In Select installation type, select Role-based or feature-based installation, and then click Next.
In Select destination server, enable Select a server from the server pool, and in Server Pool, select the server for which you want to enable the Wireless LAN Service, and then click Next.
In Select server roles, click Next.
In Select Server features, in Features, select Wireless LAN Service, and then click Next.
The computer must be restarted to complete the installation of the Wireless LAN Service. Regardless of whether you select the option to automatically restart the computer after adding the Wireless LAN Service, or you manually restart the computer after adding the wireless LAN service, after the computer restarts, the Wireless LAN Service (WLAN AutoConfig) does not automatically start. You can verify this behavior as follows:
You can start the WLAN AutoConfig service, and resolve the service startup configuration in one of two ways: