So I recently caught out an employee who snuck their Xbox into work for some console gaming during the holidays.. He connected it to our LAN, and the switch notified me of the "illegal device". This is courtesy of 802.1x on the ports, authenticating client PC's based on their Machine AD account (only), and in this case, his xbox wasn't on my AD and fired a security alert. The look on his face certainly compensated my effort in walking to one of the factories in hot weather to bust him.
So this got me wondering.. I always have headaches with people attaching their mobile phones and iPads to the company WiFi using their AD User account. I have a guest network for them to use, but it's rate limited and people sook that they can't run netflix well on their phones during lunch. So I am constantly having to police it.
Why the hell aren't I using the Machine AD account for WiFi authentication?
It's the same AD, the same RADIUS servers, virtually the same config as the wired network.. I even deploy the WiFi profiles via Group Policy (with AD User Only authentication). I'd just have to make up a laptop group, dump the laptops in, change the RADIUS server to look in the new group instead of Authenticated Users and update the GPO. But for some reason, be it lazy convention or some unknown wisdom, everywhere I have had anything to do with WiFi & AD uses AD user accounts (until they gotten big enough to warrant installing certificate infrastructure to support EAP-TLS).
Looked at doing this for WiFi years ago and it was a real PITA. Ended up using a UTM to achieve the same thing. Also useful for blocking streaming, social media and other sites during work hours and automatically unblocking during the lunch period. Keeps the staff happy.