Although all of my staff laptops are members of an Active Directory domain and are managed by Group Policy, I do not manage wireless profiles on those devices using a group policy. The staff member who uses each laptop actually signs into the device using a local account, not a domain account. This means I can use a local administrator account on the affected machines to delete the faulty profile and then import an "all user" profile for the same SSID. School laptops that are used by students do have wi-fi managed through group policy (primarily to prevent them from connecting to cell phone hotspots as a way to bypass the school firewall). However, I have never experienced this issue on those laptops. After doing some experimenting over the last few weeks, I think the issue can be avoided if I join the device to wi-fi at the right time during setup. 1. Install a (non-domain) image onto the device over ethernet using MDT. 2. Connect to wi-fi using the local administrator account. 3. Join the laptop to the domain (over wi-fi). 4. Create the local account for the end-user. If the device is domain-joined with MDT as part of sysprep or domain-joined over ethernet after setup has finished and THEN connected to wi-fi, the resulting wireless profile will be "per user", but will not exhibit any issues. If the local user account is created and that account is used to join wi-fi, then not only will the wireless profile be "per user", but the wi-fi connection will drop whenever a running task owned by 'SYSTEM', 'LOCAL SERVICE', or 'NETWORK SERVICE' attempts to access something over the network.
... View more
