Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, February 1, 2019 2:57 PM
I make the new GPO's for Build 1809 right now and i can't get rid of the random hardware adresses settings under network & internet wi-fi.
I think that this feature is not really usable for enterprise and sccm managed enviroments. Does anybody know how to prevent users from activation it?
All replies (7)
Wednesday, February 27, 2019 6:26 AM âś…Answered
Hi Zoe
I've created a Powershell Script that is applied as a Shutdown Script. It disable the Hotspot 2.0 function too. It's not how it should be but better than nothing.
#Disable Random Mac Adresse
Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\WlanSvc\Interfaces | where {$_.Property -like "RandomMacState*"} | Set-ItemProperty -name RandomMacState -Value ([byte[]](0x00,0x00,0x00,0x00))
#Disable Hotspot 2.0
if (((Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\WlanSvc\ | where {$_.Property -like "OsuRegistrationStatus*"}).Property) -eq "OsuRegistrationStatus"){
Set-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\WlanSvc\AnqpCache -name OsuRegistrationStatus -Value "0"
}
else{
New-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\WlanSvc\AnqpCache -name OsuRegistrationStatus -PropertyType DWord -Value "0"
}
Friday, February 1, 2019 7:54 PM
Are you referring to MAC Address?
Monday, February 4, 2019 7:33 AM
Hi,
Thanks for posting in the forum.
You may make a GPO to change the registry value.
1) Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WlanSvc\Interfaces
2) Find the interface that contains the key: RandomMacState (for me, it was: {EDA8D522-F34B-49A5-8F13-AD4F59F9DD5F})
3) Change RandomMacState from 01 00 00 00 to 00 00 00 00
For your reference:
Services Tips Blog Contact Fix Endless Reboot After Enabling Random Hardware Addresses for Wifi on Windows 10
Regards,
Zoe
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, February 4, 2019 10:12 AM
Hello Zoe,
Thanks for your reply.
The way over the registry as you describe is no solution for me. We have more than 20 different hardware types. We certainly can't manage that anymore.
From my point of view there are various security relevant settings in 1809 (aswell as in previous builds) that can not really be hardened by admx.
Always having to go through the registry is more like a McGyver workaround than professional client management.
Regards,
Nicolas
Monday, February 4, 2019 3:31 PM
Yes im trying to stop the possibility of activating this feature
Wednesday, February 6, 2019 6:04 AM
Hi,
Thanks for your update and sorry for all the inconvenience.
We've performed a lot of research but, unfortunately, we have not found any workaround available.
You may visit the Feedback Hub app to send suggestions to help Microsoft improve your Windows experience.
For your reference:
Send feedback to Microsoft with the Feedback Hub app
Your understanding and cooperation is appreciated.
Regards,
Zoe
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, February 28, 2019 2:10 AM
Hi,
Glad to know that you've found the solution.
Would you please mark it as answer? This may help other community members find the helpful reply quickly.
Thank you for your understanding and support.
Regards,
Zoe
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].