Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Windows home server, active directory and new release RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello


    I check the forum and it appears WHS cannot be a domain controler (no active directory functionnality available or limited to several days). I suppose it's because Microsoft do not want that Entreprise use WHS instead of Windows 203 server !!!!!


    But I'm a part of the home user who have several PC (with Microsoft OS) linked by network. I think WHS is a good product BUT I really find stupid to block the native "active directory" functionnality as WHS is based on Windows 2003 server.


    Does anybody know how to activate the function (for a long time) ?
    Could we buy an add-on which allow this activation ?
    Do you have any information about a futur new release of WHS ?

    Thanks
      Thierry
    Thursday, March 12, 2009 9:11 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    If you read the End User License Agreement, you will see that joining your Windows Home Server to a domain or promoting your server to be a domain controller is prohibited. This is mostly because Microsoft doesn't see a lot of benefit in AD for the average user of WHS, but also partially (I'm sure) revenue protection as you suggest.

    If you join your server to a domain, it will (after 1 week) start rebooting every hour because it's licensing requirements don't permit it to be a member of a domain. If you promote it to a domain controller, you may break core Windows Home Server functionality, which all assumes that the server is part of a workgroup.

    As for future versions of the product, Microsoft has not announced any features for future versions, so there's nothing I could tell you there. 
    I'm not on the WHS team, I just post a lot. :)
    Thursday, March 12, 2009 9:51 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    If you read the End User License Agreement, you will see that joining your Windows Home Server to a domain or promoting your server to be a domain controller is prohibited. This is mostly because Microsoft doesn't see a lot of benefit in AD for the average user of WHS, but also partially (I'm sure) revenue protection as you suggest.

    If you join your server to a domain, it will (after 1 week) start rebooting every hour because it's licensing requirements don't permit it to be a member of a domain. If you promote it to a domain controller, you may break core Windows Home Server functionality, which all assumes that the server is part of a workgroup.

    As for future versions of the product, Microsoft has not announced any features for future versions, so there's nothing I could tell you there. 
    I'm not on the WHS team, I just post a lot. :)
    Thursday, March 12, 2009 9:51 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Microsoft has not officially released information about what will be in the next version of Home Server.  I will say stay tuned.  You're not the only one with these questions.
    Thursday, March 12, 2009 9:52 PM