Details of the scenario you tried and the problem that is occurring
I am using DSC to setup a lab server including ADDS, ADCS and ADFS on a single machine. Setting up the ADFS throws an error after the first reboot during the teststage. It complains about an unkown NetBIOS name and seems to use the domain name as a query, which fails.
Verbose logs showing the problem
Set completes with a couple of warnings.
LCM: [ Start Resource ] [[WindowsFeature]ADFSInstall] "},
LCM: [ Start Test ] [[WindowsFeature]ADFSInstall] "},
[[WindowsFeature]ADFSInstall] The operation 'Get-WindowsFeature' started: ADFS-Federation"},
[[WindowsFeature]ADFSInstall] The operation 'Get-WindowsFeature' succeeded: ADFS-Federation"},
LCM: [ End Test ] [[WindowsFeature]ADFSInstall] in 0.2190 seconds."},
LCM: [ Skip Set ] [[WindowsFeature]ADFSInstall] "},
LCM: [ End Resource ] [[WindowsFeature]ADFSInstall] "},
LCM: [ Start Resource ] [[AdfsFarm]ADFSLab] "},
LCM: [ Start Test ] [[AdfsFarm]ADFSLab] "},
[[AdfsFarm]ADFSLab] Testing 'adfs.lab.local'. (FRM002)"},
[[AdfsFarm]ADFSLab] Getting 'adfs.lab.local'. (FRM001)"},
[[AdfsFarm]ADFSLab] 'adfs.lab.local' is absent but should be present. (FRM007)"},
LCM: [ End Test ] [[AdfsFarm]ADFSLab] in 0.0630 seconds."},
LCM: [ Start Set ] [[AdfsFarm]ADFSLab] "},
[[AdfsFarm]ADFSLab] Setting 'adfs.lab.local'. (FRM003)"},
[[AdfsFarm]ADFSLab] Getting 'adfs.lab.local'. (FRM001)"},
[[AdfsFarm]ADFSLab] Installing 'adfs.lab.local'. (FRM004)"},
[[AdfsFarm]ADFSLab] A machine restart is required to complete ADFS service configuration. For more information, see: http://go.microsoft.com/fwlink/?LinkId=798725"},
[[AdfsFarm]ADFSLab] The SSL certificate subject alternative names do not support host name 'certauth.adfs.lab.local'. Configuring certificate authentication binding on port '49443' and hostname 'adfs.lab.local'."},
[[AdfsFarm]ADFSLab] The SSL certificate does not contain all UPN suffix values that exist in the enterprise. Users with UPN suffix values not represented in the certificate will not be able to Workplace-Join their devices. For more information, see http://go.microsoft.com/fwlink/?LinkId=311954."},
[[AdfsFarm]ADFSLab] 'adfs.lab.local' has been installed successfully. A reboot is now required. (FRM005)"},
LCM: [ End Set ] [[AdfsFarm]ADFSLab] in 26.4210 seconds."},
LCM: [ End Resource ] [[AdfsFarm]ADFSLab] "},
[] A reboot is scheduled to progress further. Configuration will be continued after the reboot."},
[] A reboot is scheduled to progress further. Configuration will be continued after the reboot."},
[] Consistency check completed."}
After reboot it picks up but fails the test and exits.
"type": "verbose", "message": "[WIN-I0BA3HA4226]: LCM: [ Start Resource ] [[AdfsFarm]ADFSLab] "},
"type": "verbose", "message": "[WIN-I0BA3HA4226]: LCM: [ Start Test ] [[AdfsFarm]ADFSLab] "},
"type": "verbose", "message": "[WIN-I0BA3HA4226]: [[AdfsFarm]ADFSLab] Testing 'adfs.lab.local'. (FRM002)"},
"type": "verbose", "message": "[WIN-I0BA3HA4226]: [[AdfsFarm]ADFSLab] Getting 'adfs.lab.local'. (FRM001)"},
"type": "verbose", "message": "[WIN-I0BA3HA4226]: LCM: [ End Test ] [[AdfsFarm]ADFSLab] in 1.0000 seconds."},
"type": "error", "message": "PowerShell DSC resource MSFT_AdfsFarm failed to execute Test-TargetResource functionality with error message: The Active Directory NetBIOS name is unknown. (ADFSCOMMON0018)\r\nParameter name: lab.local "},
Suggested solution to the issue
I am very new to DSC and have not found any hint on how the NetBIOS name is acquired in this instance. The Parameter name it shows i the actual domain lab.local, the NetBIOS name would be lab. I cannot rule out that I made a configuration mistake.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
Details of the scenario you tried and the problem that is occurring
I am using DSC to setup a lab server including ADDS, ADCS and ADFS on a single machine. Setting up the ADFS throws an error after the first reboot during the teststage. It complains about an unkown NetBIOS name and seems to use the domain name as a query, which fails.
Verbose logs showing the problem
Set completes with a couple of warnings.
After reboot it picks up but fails the test and exits.
Suggested solution to the issue
I am very new to DSC and have not found any hint on how the NetBIOS name is acquired in this instance. The Parameter name it shows i the actual domain lab.local, the NetBIOS name would be lab. I cannot rule out that I made a configuration mistake.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
Version and build of PowerShell the target node is running
Version of the DSC module that was used
1.3.2