Comments on: Windows wireless configuruation script http://itknowledgeexchange.techtarget.com/itanswers/windows-wireless-configuruation-script/ Sun, 19 May 2013 00:45:31 +0000 hourly 1 By: danieldainty http://itknowledgeexchange.techtarget.com/itanswers/windows-wireless-configuruation-script/#comment-79742 danieldainty Wed, 28 Jul 2010 14:33:14 +0000 #comment-79742 Better late than never, eh?

http://innovit-education.co.uk/blogs/daniel-dainty/116-scripting-windows-xp-wireless-configuration

]]> By: suzuhara http://itknowledgeexchange.techtarget.com/itanswers/windows-wireless-configuruation-script/#comment-58953 suzuhara Wed, 31 Dec 2008 17:05:07 +0000 #comment-58953 Hi,

At first, KarlG’s solution sounds like a good idea but when you get to think about it, you realise that you should never use it. Mac addresses can be so easily faked and you can sniff an unencrypted wireless network so easily that anyone with a computer could connect to your network.

MAC addresses should never be used for security, they could be used to determine which ssid they belong to (considering your access-point supports multiple ssid and vlans) but NEVER use it to prevent people from connecting to your network by itself as that can be circumvented in less than 10 seconds by people with little to no knowledge.

as for the original question, I still haven’t found that answer myself, we are still rolling out ssid by re-imaging the computers (when there are a lot) which is not convenient at all or just manually giving them.

]]>