Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
How do you create an account for the user "System" or group "Administrators" on WHS? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    OK, so WHS isn't aimed at mega Active Directory enterprises ... it's aimed at LAN-Locked WORKGROUPS ... people who don't have an Active Directory in their house ... Yes?

    So how do we create a share (an account) on WHS that is accessible by an RDN like System or Administrators?

    If WHS can only create a share for .jpg's and .mp3's for "Sam and Jane" ... but can't create a share to support files for "System" or "Administrators" ... well the only thing it is good for is to support HP's photo-printer division.

    More explicitly ... how do I create a share, accessible only by the workgroup user "System", where we can place site/home log files, mail-spool files, and other sorts of simple text files that are used by the home/SOHO?

    Or should we just toss WHS and continue to use one of the sites XP systems to serve files and backup the PCs?

    Portland'ers are much smarter than Redmond'ers
    Friday, February 27, 2009 9:26 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Windows Home Server is designed to support the needs of home users, not businesses. As such, it can't be joined to a domain, and you can't run DCPROMO to make it a domain controller.

     

    In order to support an AD user id, you would create a user on the home server which matches (exactly) the login name of the AD user, and match the passwords between the two. Note: if your AD implementation has a system policy that requires passwords to be changed regularly, you will have to sync the password on the home server separately, since the home server can't participate in the domain. You will not be able to add an AD group to your home server, or (probably, though I haven't tried) a "system" ID in AD.

     

    To allow (or deny) any given user that your home server knows about access to a share, you can set that user's access to shares using the WHS Console.


    I'm not on the WHS team, I just post a lot. :)
    Friday, February 27, 2009 2:12 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Logon to your WHS locally or using Remote Desktop, create shared folder outside WHS shares (preferrably also outside storage pool, use C partition or separate disk not added to storage pool), right click and set appropriate rights.

    Also please have a look at the WHS technical briefs, links on this page
    Saturday, February 28, 2009 1:43 AM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Windows Home Server is designed to support the needs of home users, not businesses. As such, it can't be joined to a domain, and you can't run DCPROMO to make it a domain controller.

     

    In order to support an AD user id, you would create a user on the home server which matches (exactly) the login name of the AD user, and match the passwords between the two. Note: if your AD implementation has a system policy that requires passwords to be changed regularly, you will have to sync the password on the home server separately, since the home server can't participate in the domain. You will not be able to add an AD group to your home server, or (probably, though I haven't tried) a "system" ID in AD.

     

    To allow (or deny) any given user that your home server knows about access to a share, you can set that user's access to shares using the WHS Console.


    I'm not on the WHS team, I just post a lot. :)
    Friday, February 27, 2009 2:12 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Logon to your WHS locally or using Remote Desktop, create shared folder outside WHS shares (preferrably also outside storage pool, use C partition or separate disk not added to storage pool), right click and set appropriate rights.

    Also please have a look at the WHS technical briefs, links on this page
    Saturday, February 28, 2009 1:43 AM
    Moderator