Kevin Remde's IT Pro Weblog
IT Pro Resources
TechNet EventsMicrosoft Security Response CenterTechNet IT Manager Community HubMicrosoft Virtual AcademyKevin’s Evaluation Download Center
IT Pro Evangelist Blogs
Blain Barton Blain Barton's Blog@BlainBar
Brian LewisMy Thoughts on IT...@BrianLewis_
Dan Stolts IT Pro Guru Blog@ITProGuru
Jennelle Crothers TechBunny@jkc137
Keith MayerIT Pros ROCK!@KeithMayer
Kevin Remde Full of I.T.@KevinRemde
Matt Hester Matthew Hester's WebLog@MatthewHester
Tommy PattersonVirtually Cloud 9@Tommy_Patterson
Yung Chou Yung Chou on Hybrid Cloud@YungChou
I have another question related to the DJOIN command:
For those of you who don’t know what an “Offline Domain Join” is or what the DJOIN.EXE command does, please refer to my blog post from the other week on the subject. In a nutshell, Windows Server 2008 R2 and Windows 7 contain a tool (djoin.exe) that allows you pre-populate AD with a computer account, and then at a later time connect that computer to the domain without having to have the domain actually available at the time.
Which leads to this pretty good question that Mark asks: Why not just use the NETDOM JOIN command?
The answer really has to do with the key benefit that an Offline Domain Join provides: The ability to do it OFFLINE. For the NETDOM JOIN command to work, your machine has to be able to communicate with a domain controller. Not so with DJOIN.EXE.
What do you think?
I think for some of us, the idea of joining a computer to the domain when the domain is not available is still something we have a hard time wrapping our brains around. I know I have that issue ;-)
Can't beat how handy that would be though.