locked
WSS 3.0 SharePoint Central Admin doesn't work when joined to domain RRS feed

  • Question

  • I've got a TFS 2010 installation that uses WSS 3.0 on a 64-bit Server 2008 SP2.  When not joined to our domain, I can use Cental Admin to add site collection admins, and everything else that you would expect.  However, after joining the server to our domain, none of the link function any more.  For example, clicking on site actions to get the the page to add site collection administrators does nothing.  Also, none of the site collection administrators are displayed when accessing the Site Collection Administrators page, under Application Management.

    Beyond a doubt, this is a permissions issue since all these features are available when the server is not joined to the domain. 

    Backgroud:  When joining systems to the domain, some GPOs that are pushed down the forest tree really tighten up security on the systems.  I am unable to add anything to the trusted or local intranet sites in IE security, as one of the GPOs locks this out, even to

     

    So, my question is: what permissions have to be set for these links to function correctly whether the system is joined to the domain or not?

    I would be just as happy trying the stsadm to add to the site collection administrators, if the commands were better documented, or better examples were available.  (permissions issues may still keep this form working)

    example:

    stsadm.exe -o setapppassword -password (password key)

    What password key should be used?  any pass phrase desired or the password for the service account that WSS is running under? or somethign else?

    stsadm.exe -o adduser -url (URL) -userlogin Domain\Username -useremail (user's email address) -role (Site_Group_Name) -siteadmin

    In this example, what is the URL?  the URL for the SharePoint Central Admin site?

    What is Site_Group_Name?

     

     

    Monday, April 25, 2011 6:27 PM

Answers

All replies

  • I've got a TFS 2010 installation that uses WSS 3.0 on a 64-bit Server 2008 SP2.  When not joined to our domain, I can use Cental Admin to add site collection admins, and everything else that you would expect.  However, after joining the server to our domain, none of the link function any more.  For example, clicking on site actions to get the the page to add site collection administrators does nothing.  Also, none of the site collection administrators are displayed when accessing the Site Collection Administrators page, under Application Management.

    Beyond a doubt, this is a permissions issue since all these features are available when the server is not joined to the domain. 

    Backgroud:  When joining systems to the domain, some GPOs that are pushed down the forest tree really tighten up security on the systems.  I am unable to add anything to the trusted or local intranet sites in IE security, as one of the GPOs locks this out, even to

     

    So, my question is: what permissions have to be set for these links to function correctly whether the system is joined to the domain or not?

    I would be just as happy trying the stsadm to add to the site collection administrators, if the commands were better documented, or better examples were available.  (permissions issues may still keep this form working)

    example:

    stsadm.exe -o setapppassword -password (password key)

    What password key should be used?  any pass phrase desired or the password for the service account that WSS is running under? or somethign else?

    stsadm.exe -o adduser -url (URL) -userlogin Domain\Username -useremail (user's email address) -role (Site_Group_Name) -siteadmin

    In this example, what is the URL?  the URL for the SharePoint Central Admin site?

    What is Site_Group_Name?

     

     

     

    • Moved by Mike Walsh FIN Monday, April 25, 2011 7:00 PM This post starts with "I've got a TFS 2010 installation" so clearly this is extremely relevent to this post. (From:SharePoint - Setup, Upgrade, Administration and Operation (pre-SharePoint 2010))
    • Merged by Vicky SongMicrosoft employee Tuesday, April 26, 2011 7:59 AM duplicate
    Monday, April 25, 2011 6:27 PM
  • @Mike, I have consulted our Microsoft SharePoint support engineer. He has confirmed that it is a SharePoint issue.

    Hello MMGFLA,

    Thanks for your post. I am afraid it is not the appropriate forum to deal with your issue. I am moving it to the SharePoint forum.

    Thanks,


    Vicky Song [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Tuesday, April 26, 2011 8:30 AM
  • Hi,

    Thanks to share your post.

    For the issue, please check that you have made the SharePoint server a member server of the new domain. And set up the service account rights, SQL permissions update the service account, please follow this article for the detailed information:

    http://blogs.technet.com/b/sushrao1/archive/2011/03/17/sharepoint-migrating-sharepoint-server-from-one-domain-to-another.aspx.

    And here is the usage of the STSADM:

    http://technet.microsoft.com/en-us/library/cc262643(office.12).aspx.

    Hope this could help you!

    Leo

    • Marked as answer by Emir Liu Thursday, May 5, 2011 10:10 AM
    Thursday, April 28, 2011 8:32 AM