Q: Should I use Group Policy to configure WiFi in my company?

A: Yes. You should use Group Policy to fully configure the WiFi settings for all domain-joined company systems. Doing so gives your clients predictable network access, simplifies complex WiFi configurations, and helps to prevent users from unwittingly connecting to unsecure or malicious networks. You can also use Local Security Policy for non-domain environments and to configure initial Windows images before they receive Group Policy.

At a minimum, consider using Group Policy for these tasks:

  • Restricting all new networks to the Public network profile, to ensure that Windows Firewall is enabled and file sharing is disabled
  • Specifying authorized corporate wireless networks and assigning them to the Domain network profile
  • Disabling Internet Connection Sharing to prevent unauthorized clients from using corporate resources as a network bridge

There are too many settings to list in this brief FAQ, but these are a good starting point. You should examine all policy options to determine the best configuration for your WiFi users.

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• The Microsoft
Technology Roadmap
• Office 365 Implementation
• Hyper-V Optimizing
• Windows 8 Deployment
and much more!

Come See Paul Thurrott & Rod Trent in Person!

Early Registration Now Open

Upcoming Training

Mastering SharePoint 2013: Succeeding, Not Just Surviving

Building on the success of the “Mastering SharePoint 2010” seminars, the presenters have updated the content to cover the latest and greatest SharePoint product: SharePoint 2013. While SharePoint 2013 is relatively new on the marketplace, the presenters have been working with SharePoint 2013 for well over a year, and have implemented it with a number of clients in production environments.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.