Score:0

My network profile is showing as private instead of domain profile after installing Active Directory DNS on Windows Server 2019 VMware Workstation

my flag

After installing Active Directory and DNS role on VMware Workstation with domain "mylab.local". I used NAT switch on my VM and my IpV4 settings are

enter image description here

After installation my current network profile was showing as mylab.local enter image description here

However after restarting my VM my network profile changes to private and Domain profile is not available to switch.

enter image description here

> Get-NetConnectionProfile
Name             : Network
InterfaceAlias   : Ethernet0
InterfaceIndex   : 14
NetworkCategory  : Private
IPv4Connectivity : Internet 
Score:0
my flag

Actually Several users have reported this problem with Windows Server 2019 Some links to the solution are Solution from microsoft

First check if restarting the Network Location Awareness service fixes the issue?. enter image description here

If yes then for permanen fix I followed the suggestion and made below registry change to my Server 2019 we need to add this registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters

Add a DWORD parameter :AlwaysExpectDomainController

Set value to:1

Note: This registry key alters the behavior when NLA retries domain detection.

enter image description here

It fixed the problem for me!

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.