Adding a wireless profile (batch file or registry entry)?

[Lowdown]

I work at a local K-12 school district and I was wondering if there is a easier way to add a lot of our laptops to a new wireless profile/SSID. With how we setting up our new SSID is with it being a non-broadcasted SSID so you have to go into the Windows Zero Wireless configurations on each computer and enter in the SSID, what network type it is and the password for the wirless network. I was wondering if there was any way to make a .bat file or a .reg file so that we can easily send and run the file on the computer without manually entering in all the information. If not I understand this will just save a lot of time in the long run and we can still make sure only the computers that are part of the district get the new information in the file. All of our systems are Windows XP SP3.

[IrfanL]

Before you implement such solution, did you evaluated the security risks it may cause. Just imaging what will happen if someone got hold of this batch or script file!!!

[Lowdown]

I completely understand what you are getting at here but can you see why I am looking for a way to add them a little faster. When this goes into effect there will be at least 200 laptops that I will need to change the SSID info. Anybody with some ideas?

[tdogg21]

I completely understand what you are getting at here but can you see why I am looking for a way to add them a little faster. When this goes into effect there will be at least 200 laptops that I will need to change the SSID info. Anybody with some ideas?

did you ever find a solution?? i have the same issue.

[TurboTuna]

Hiding the SSID is pointless, and only gives you more problems as you've found out.

anyone can open something like Kismet and see your SSID in seconds.

[+BudMan MVC]

^ Exactly -- there is NO security reason to not broadcast your SSID.. What your wanting to hide it from the 97 year old senile grandma across the street?

It is uttterly pointless to not broadcast the SSID.. It does not increase your security one bit. And as you can see its clearly a going to cause you logistics issues. Plus other to be honest is more of a security issue then broadcasting it -- see MS article!

Here is some good info on it

http://blogs.technet.com/steriley/archive/...less-ssids.aspx

Myth vs. reality: Wireless SSIDs

Here is a MS Article on it.

http://technet.microsoft.com/en-us/library/bb726942.aspx

Non-broadcast Wireless Networks with Microsoft Windows

I would HIGHLY suggest you read both of these. Tasty tidbits from the MS article.

"Unlike broadcast networks, wireless clients running Windows XP with Service Pack 2 or Windows Server? 2003 with Service Pack 1 that are configured to connect to non-broadcast networksare constantly disclosing the SSID of those networks, even when those networks are not in range.>"

Therefore,using non-broadcast networks compromises the privacy of the wireless network configuration of a Windows XP or Windows Server 2003-based wireless client> because it is periodically disclosing its set of preferred non-broadcast wireless networks.

This behavior is worse for enterprise wireless networks because of the number of wireless clients that are periodically advertising the non-broadcast network name. For example, an enterprise wireless network consists of 20 wireless APs and 500 wireless laptops. If the wireless APs are configured to broadcast, each wireless AP would periodically advertise the enterprise’s wireless network name, but only within the range of the wireless APs. If the wireless APs are configured as non-broadcast, each of the 500Windows XP or Windows Server 2003-based laptops would periodically advertise the enterprise’s wireless network name,regardless of their location (in the office, at a wireless hotspot, or at home)>.>

For these reasons,it is highly recommended that you do not use non-broadcast wireless networks>. Instead,configure your wireless networks as broadcast and use the authentication and encryption security features of your wireless network hardware and Windows to protect your wireless network, rather than relying on non-broadcast behavior.>

I am curious who actually suggested that you not broadcast it? Nobody that actually works in Wireless Security would suggest this!!