Sharepoint Foundation 2010 Service Accounts Problems
I have no choice but to install SharePoint Foundation 2010 and SQLExpress 2008 r2 on my domain controller because I have only one server. I know this isn't recommended, but that it can be done.
I have run into all sorts of problems and warnings with my service accounts running on "built in" accounts and having too much privileges. A classic symptom of this problem is that when I log into Central admin as the Domain and Sharepoint Admin (same account), it shows up as "Service Account".
My local administrator account is named "administrator". My domain or network administrator is also named "administrator". SharePoint seems to default to the local administrator account which could be causing some of these problems.
I have completely uninstalled SQLExpress 2008 r2 and SharePoint Foundation. I did forget to remove the site collections from SP before uninstallation, but I don't think that will be a problem as I have also removed SQLExpress.
I want to do this the right way this time.
1) Do i need to remove the entire SQL folder under program files? Last time I didn't, it couldn't create Sharepoint_config.mdb because it said it already existed.
2) What is the right way to set my Farm Administrator account and the service accounts given I am running this on the domain controller itself? The Sharepoint defaults don't seem to work right, probably because it doesn't expect to be on a domain controller. In the past, I have created regular user accounts on the domain and used these for the various services except for Farm Management, but it still gave me warnings, even when I removed these accounts from the built in users group and they were only in the domain users group.
3) Do I need to also remove any SharePoint application pools before re installing?
The Sharepoint default choices just never seem to work right like they should.
4) Is there any sort of definitive guide as to what to do when installing SQL and SP on the domain controller?
I have run into all sorts of problems and warnings with my service accounts running on "built in" accounts and having too much privileges. A classic symptom of this problem is that when I log into Central admin as the Domain and Sharepoint Admin (same account), it shows up as "Service Account".
My local administrator account is named "administrator". My domain or network administrator is also named "administrator". SharePoint seems to default to the local administrator account which could be causing some of these problems.
I have completely uninstalled SQLExpress 2008 r2 and SharePoint Foundation. I did forget to remove the site collections from SP before uninstallation, but I don't think that will be a problem as I have also removed SQLExpress.
I want to do this the right way this time.
1) Do i need to remove the entire SQL folder under program files? Last time I didn't, it couldn't create Sharepoint_config.mdb because it said it already existed.
2) What is the right way to set my Farm Administrator account and the service accounts given I am running this on the domain controller itself? The Sharepoint defaults don't seem to work right, probably because it doesn't expect to be on a domain controller. In the past, I have created regular user accounts on the domain and used these for the various services except for Farm Management, but it still gave me warnings, even when I removed these accounts from the built in users group and they were only in the domain users group.
3) Do I need to also remove any SharePoint application pools before re installing?
The Sharepoint default choices just never seem to work right like they should.
4) Is there any sort of definitive guide as to what to do when installing SQL and SP on the domain controller?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER