We have a resource domain (single domain/forest) in place that is used primarily for locked down systems like lab machines, kiosks, etc. We are in the process of uplifting the domain with new Windows 2019 DCs replacing the 2008 R2 DCs (DFL and FFL still 2008 R2 currently).
This is an inherited domain, and I *think* the issue is with the domain name being created with an underscore in the name: _resource.local - just looking for confirmation or if something else could be causing this issue.
The AD management tools work fine, but we are seeing errors with the PowerShell for AD. While the old DCs are around, they have been demoted and we don't know if this happened with them unfortunately. When you launch Active Directory Module for PowerShell, it returns this error below. Manually typing import-module ActiveDirectory succeeds without error.
import-module : Attempting to perform the InitializeDefaultDrives operation on the 'ActiveDirectory' provider failed.
At line:1 char:1
+ import-module ActiveDirectory
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (Microsoft.Activ...ActiveDirectory:ProviderInfo) [Import-Module], Prov
iderInvocationException
+ FullyQualifiedErrorId : InitializeDefaultDrivesException,Microsoft.PowerShell.Commands.ImportModuleCommand
However, trying to run any AD cmdlet returns an error like this one below:
Get-ADDomain : Invalid URI: The server name 'DC20._RESOURCE.LOCAL' could not be parsed. You might need to enable
internationalized domain name support for class System.Uri. See help of class System.Uri for more details.
At line:1 char:1
+ Get-ADDomain
+ ~~~~~~~~~~~~
+ CategoryInfo : InvalidType: (_RESOURCE:ADDomain) [Get-ADDomain], UriFormatException
+ FullyQualifiedErrorId : ActiveDirectoryCmdlet:System.UriFormatException,Microsoft.ActiveDirectory.Management.Com
mands.GetADDomain