Description
This issue was solved and closed, but I and a separate commenter seem to be experiencing it again as of now.
[20:40] Current domain is set to 'workgroup'. Time to join the domain!
[20:40] My hostname is WIN10
[20:40] Joining the domain...
[20:40] First, set DNS to DC to join the domain...
__GENUS : 2
__CLASS : __PARAMETERS
__SUPERCLASS :
__DYNASTY : __PARAMETERS
__RELPATH :
__PROPERTY_COUNT : 1
__DERIVATION : {}
__SERVER :
__NAMESPACE :
__PATH :
ReturnValue : 0
PSComputerName :
__GENUS : 2
__CLASS : __PARAMETERS
__SUPERCLASS :
__DYNASTY : __PARAMETERS
__RELPATH :
__PROPERTY_COUNT : 1
__DERIVATION : {}
__SERVER :
__NAMESPACE :
__PATH :
ReturnValue : 0
PSComputerName :
[20:40] Now join the domain...
[20:40] Adding Win10 to the domain. Sometimes this step times out. If that happens, just run 'vagrant reload win10 --provision'
[20:40] Disabling Windows Updates and Windows Module Services
Stderr from the command:
powershell.exe : Add-Computer : Computer 'win10' failed to join domain 'windomain.local' from its current
+ CategoryInfo : NotSpecified: (Add-Computer : ...om its current :String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
workgroup 'WORKGROUP' with following error message: The specified domain either does not exist or
could not be contacted.
At C:\vagrant\scripts\join-domain.ps1:42 char:3
+ Add-Computer -DomainName "windomain.local" -credential $DomainCred ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (win10:String) [Add-Computer], InvalidOperationEx
ception
+ FullyQualifiedErrorId : FailToJoinDomainFromWorkgroup,Microsoft.PowerShell.Commands.AddComp
uterCommand
have tried:
vagrant reload win10 --provision