Windows 10: Domain PC keeps forgetting hidden domain network

Hey, everyone.I have a customer here who's PC recently decided to stop remembering the network information for our domain wifi network. No other employees have reported this problem. Here in I'll relay what we've observed and actions taken to rectify it. I am with the IT department here and am 5+ years experienced with running face to face with nonsense MS problems at this company and working with end user Windows troubleshooting for several years before being here not my first rodeo. Observed For reference: This is on Windows 10 professional with presumably the latest updates not checked

:)

 

Domain PC keeps forgetting hidden domain network

Hey, everyone.

I have a customer here who's PC recently decided to stop remembering the network information for our domain wifi network. No other employees have reported this problem. Here in I'll relay what we've observed and actions taken to rectify it. I am with the IT department here and am 5+ years experienced with running face to face with nonsense MS problems at this company and working with end user Windows troubleshooting for several years before being here (not my first rodeo).



Observed

For reference: This is on Windows 10 professional with presumably the latest updates (not checked)

In windows > taskbar > network icon

left click > choose hidden network >

Type in name in all caps to as I understand it to be case sensitive

type the password correctly

discoverable on network > yes

Before this point, if we went into known wifi networks and forgot the last reference to this network, we'd get a new network hereby referred to as NETWORK. Now if we disconnect from it by toggling to LAN, disabling the wifi device or some other means (possibly), NETWORK is now gone.

If we add it back as done before (not forgetting it), you'll then be on NETWORK 2 and connected with NETWORK below it not connected. This can presumably be repeated ad infintum as I saw with NETWORK 3, NETWORK 2, NETWORK.



- -- --- -- -

Attempted solutions



We tried forgetting the wifi device drivers in device manager (DM) then refreshing to reinstall. Additionally, I tried forgetting multiple network devices in DM just in case (such as the LAN device) and then refreshing to let windows reinstall them once more. Some restarts were made, but I cannot pin down at what intervals at this point, though restarts have occurred over time while working on this.

Additionally, efforts were made with this below site and their solutions.

SOLVED: Windows 10 Will Not Save WiFi Password - Appuals.com

I even tried adding the NETWORK as I have done successfully many times in the classical Set up a Connection or Network > Manually connect to a wireless network, whereby I fill out the boxes below correctly

for ref

NETWORK

WPA2-Personal

AES

Key *****

check both for start automatically and connect even if not broadcasting



No change. In desperation, I asked this employee, fairly competent on her own, to try the built in windows diagnostic tool (desperate times). She came back with a report that it was not fixed and perinate data regarding the network entries.

Profile: NETWORK
SSID: NETWORK
SSID length: 7
Connection mode: Infra
Security: Yes
Set by group policy: No
Connected even if network is not broadcasting: No
Connectable: Yes

Aha, right!? a big NO there for even if not broadcasting, but I know what I set.

The question: Why has Windows started ignoring this critical parameter and how to I force it to do so, or otherwise, how do I fix this problem?

Thank you for reading. I'll be pinning this to my desktop, bookmark bar, and ticket for daily updates (This isn't going to be a dead end found 5 years later). I have tried searching online but dead ends and non solutions were only found.

 

UnattendedJoin error: failed to find the domain data (0x6e)

Thanks for the suggestion! I don't want to add a domain account, as this is a generic unattended install that will be used for all company machines. Do you think it's possible that the computer would join the domain if, instead of using UnattendedJoin in specialize, I used your steps but left out the specific account?

The other thing I was thinking was to use a generic account to allow the domain join during the specialize step. I added a machine password in the UnattendedJoin component, and instead of getting the error listed above, I got an authentication error, which makes me think I could probably do a secure join instead of the unsecure join.

Thoughts?

 

Raising the windows domain and forest issues?


hi,

I run a domain that was all 2003 r2 servers. I recently upgraded all my domain controllers to windows 2012 r2.
That went off without any problems.. Our trust relationships had no issues also.

My first step was to raise the Domain and Forest levels past 2003 to 2008. This went off without a hitch.
These are the features for raising the levels to 2008:

• Features and benefits include all default Active Directory features, all features from the Windows Server 2003 domain functional level, plus:
• Read-Only Domain Controllers – Allows implementation of domain controllers that only host read-only copy of NTDS database.
• Advanced Encryption Services – (AES 128 and 256) support for the Kerberos protocol.
• Distributed File System Replication (DFSR) – Allows SYSVOL to replicate using DFSR instead of older File Replication Service (FRS). It provides more robust and detailed replication of SYSVOL contents.

Forest Level Windows Server 2008

• Features and benefits include all of the features that are available at the Windows Server 2003 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2008 domain functional level by default.

My next step is to raise the domain and forest to 2008 r2, then 2012, and finally 2012 r2. I have been trying to find out exactly what I could expect from raising the Domain and Forest for each step.

The step involving 2008 r2 seems relatively a non issue. But getting the couple of new features seem very nice

Domain Level Windows Server 2008 R2

• All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus 2 new features

Forest Level Windows Server 2008 R2

• All of the features that are available at the Windows Server 2003 forest functional level, plus the following features:

• Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. <== New Feature very cool
• All domains subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default.

Here is my big concerns for the next raising of domain and forest to 2012.

Forest Level Windows Server 2012:

• All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features.
• All domains subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.

Domain Level Windows Server 2012 R2: <=====Need to investigate more and why this post

• DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer:

• Authenticate with NTLM authentication <==============(what issues may arise)
• Use DES or RC4 cipher suites in Kerberos pre-authentication
• Be delegated with unconstrained or constrained delegation
• Renew user tickets (TGTs) beyond the initial 4-hour lifetime

Will this affect my exchange anywhere users with remote access authenticating either clear of NTLM???
and what would/may not to work properly day 1 when I raise the domain and forest to 2012. I cant really find anyone that can answer a straight question.

Has anyone gone through this? what problems did you have, if any , if a lot???

Any thoughts and suggestions will be much appreciated??

thanks


- - - Updated - - -

One more point... I am not sure if I posted this to the correct forum.. So if I was wrong and it should be in a different one..
PLEASE LET ME KNOW