Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
OK, So active directory, PDC + WHS = NO RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    I have active directory, and a domain controller on my home network for one reason...

     

    I do software development for enterprise level applications, message queue software, IBM's and Microsoft's REQUIRE DNS, active directory, domain controller functionality for installation for persistent cross machine messaging.

     

    It seems I need to choose between WHS or my work. Any ideas?

    Saturday, October 6, 2007 9:37 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    WHS works fine with domain joined machines, and can exist on the same subnet/network as a domain.

     

    So--I don't see why you can't do this.  I have to say this statement is partly hearsay--I've VPN'd to and from from the domain to my WHS, but haven't actually had it in the office physically.

     

    So--you can use WHS in a Domain network, but it can't be a DC and it can't join the domain.

    Saturday, October 6, 2007 9:42 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    WHS works fine with domain joined machines, and can exist on the same subnet/network as a domain.

     

    So--I don't see why you can't do this.  I have to say this statement is partly hearsay--I've VPN'd to and from from the domain to my WHS, but haven't actually had it in the office physically.

     

    So--you can use WHS in a Domain network, but it can't be a DC and it can't join the domain.

    Saturday, October 6, 2007 9:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Bill is correct; WHS can't be joined to a domain, because it's built on a version of Small Business Server and that would violate the SBS EULA (which requires that a SBS machine be PDC). And you can't make it a domain controller itself because that may break the WHS security model. But it can co-exist on the same network as a domain controller, and can back up domain-connected PCs.

    Saturday, October 6, 2007 10:09 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

     

    You seem to be stating the the WHS license module will only kick in if it is JOINED to a domain, and will not kick in sitting on a subnet that has a domain controller in it and the broadcast messages flying by?

     

    I guess this begs the question why functionality to be a domain controller exisits or is allowed to exist on the WHS machine? And why the ability to join a domain exisits/can exist on the WHS machine?

     

     

     

    Saturday, October 6, 2007 10:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
     Ken Warren wrote:

    Bill is correct; WHS can't be joined to a domain, because it's built on a version of Small Business Server and that would violate the SBS EULA (which requires that a SBS machine be PDC). And you can't make it a domain controller itself because that may break the WHS security model. But it can co-exist on the same network as a domain controller, and can back up domain-connected PCs.

     

    This clarifies much.

     

    WHS is a PDC, correct?

     

    Can machines that are already members of a different domain be full fledged WHS clients or are they required to join the WHS's domain for that functionality?

     

    (and sorry for being so late to the party)

    Saturday, October 6, 2007 10:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    As I said, WHS can't join a domain, or be the PDC in a domain. So no AD at all, for your server. It functions as a standalone server. But you can enroll a domain PC as a WHS client and back it up just fine. It doesn't interfere in any way with the domain that PC is already joined to.

    Saturday, October 6, 2007 11:09 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

     Walkie wrote:
    I guess this begs the question why functionality to be a domain controller exisits or is allowed to exist on the WHS machine? And why the ability to join a domain exisits/can exist on the WHS machine?
    WHS was built on a version of Windows Server 2003/SBS. As a result it has the usual licensing restrictions that a SBS machine has. That's where the license module comes in: a SBS server can't be joined to a domain other than as the PDC.

     

    The functionality is probably still there because it was easier to leave it in place; that way WHS can do a complete OS install from a pre-built and validated image. The ability to join a domain is part of every Windows-based machine; it's turned off in home SKUs of desktop OSes, but it can be turned back on with registry edits. Because this is a server OS, and because it will normally be used in a headless configuration by people who won't be logging in to the server itself, jsut connecting and administering it through the WHS Console application, the team probably felt there was nothing to be gained from trying to remove the functionality. Plus, future plans (which I must point out I'm not privy to Smile ) could potentially require AD, and taking it out would cause double the work.

    Saturday, October 6, 2007 11:17 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Evening,

    In fact, if you hunt around, there are instances of people backing up their SBS info TO the WHS, one example I was reading, was backing up the odd's & sod's that you might not want backing up through the SBS backups.

     

    Colin

    Sunday, October 7, 2007 4:38 PM