Domain Joining using WMIC command with a batch file

Farhan Siddiqui

5/24/24, 10:05 AM

With a batch I was able to successfully join Office Systems on domain but for some reason a few are stuck and I did try the same command with changing fjoinoptions=2 and 3 but still unable to get them on domain.

wmic computersystem where name="%computername%" call joindomainorworkgroup AccountOU="OU=lab;DC=ABClab;DC=local" fjoinoptions=2 name="ABClab.local" username="ABClab\administrator" Password="@@@@@@@"

My question is there any way to force join domain?

Also I found out that any system that hits on AD server, A pointer (PTR) is created which needs to be deleted first before retrying force join?

147

0 + 1

domain-name-system

active-directory

wmic

Greg Askew

5/24/24, 10:49 AM

This would require the domain join log file to pursue. It is located in: %windir%\debug\Netsetup.log. https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/troubleshoot-errors-join-computer-to-domain . There must also be testing performed, to determine how the domain join performs using a more traditional method, such as the graphical interface or the Add-Computer PowerShell cmdlet. https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/add-computer?view=powershell-5.1

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Domain Joining using WMIC command with a batch file

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.