I set up a test Sharepoint 2007 Server before I set up a test AD Server to add it to. Based on what I read I did this backwards and if I would have set it up the other way around Sharepoint would use AD by default.
Is there a way I can change the configuration so this Sharepoint server will authenticate against the domain?
I did some searches in the configuration as well as SO and Google and couldn't come up with anything obvious.
Thanks!
You'll have to move your server into the new AD domain. Optionally you can change all the accounts that are used by SharePoint services to domain accounts, see http://support.microsoft.com/kb/934838. SharePoint will continue to work with local accounts though.
For any user rights assignment you did using local server accounts you can run the command: stsadm -o migrateuser to migrate user accounts from local\user to domain\user.
Related
I am working on a task where I need to run SSRS and SharePoint on different servers, but right now, SSRS is working in integrated mode. Is it possible to configure a remote SSRS instance in integrated mode with a sharepoint instance ?
I stand under correction, however, I believe you could use the SharePoint SSRS web-part component and as long as the user executing the request (Your service account on SharePoint) has access to the database it should work.
Ensure that the AD user that is running the SharePoint front-end has access to the database (read / execute) - can be added to a group that has access to the database, or
give the user exclusive access to the database <- not the recommended solution
I have a farm solution wsp which I want to add and deploy on a client's SharePoint farm.
Now I don't have remote access to this SharePoint machine but do have full admin rights to its central admin and related site collection, and can open the central admin and all sites through my machine.
Now as per my knowledge a farm solution is added to the SharePoint farm and not to the site collection, but I could not find any screen in central admin from which I can add my solution.
This is the case with both SharePoint 2010 and SharePoint 2013 servers.
What are the possibilities?
Basically, it sounds like you need to add and deploy a farm solution only using central admin? I don't think that is possible. If you look step one from MSDN
Adding: A solution package is added by a farm administrator to the farm's solution store, which is in the farm's configuration database. This is done either with the SharePoint Management Shell (or with the object model). It cannot be done in Central Administration.
You can't do this through web interface.
If you have full admin rights - you can use Remote PowerShell. But this require some setup on server. You can read this article about this: http://blog.incworx.com/blog/nik-brendlers-blog/administer-your-sharepoint-farm-remotely-with-powershell
Somebody knows how to change the user account and authentication method sharepoint uses to connect to its content database?
It is now setup to connect using Windows Integrated Authentication but I want to change that to a local user account.
Is it even possible to do this?
Thanks in advance
SharePoint supports both types of authentication in SQL Server:
Windows authentication (the default and preferred choice) - windows credentials are used to authenticate against the SQL server. SharePoint uses IIS which runs sites in an application pool worker process. You can change the credentials for a Web application pool here:
Central Administration > Operations > Service Accounts
SQL authentication - a username/password combination is created and stored in SQL server. When you create a content database you can choose SQL authentication and then provide the username/password (which you have already created in SQL). If you want to change the auth type of an existing database, you can detach it by checking the remove option on the database settings page (it removes the database from SharePoint but does not delete the actual data). Then you can re-attach the existing database and choose a different auth type. You can manage content databases here:
Central Administration > Application Management > Content Databases
you can do it by extending webapplication
The below links will helps you
http://weblog.vb-tech.com/nick/archive/2006/06/14/1617.aspx
http://www.codeproject.com/KB/sharepoint/moss_enableforms.aspx
We're trying to setup an internet facing WSS 3.0 site without Active Directory. We have a single WFE and a single SQL Server (2005). The WFE will be outside our DMZ.
We've successfully created the Central Admin site with a local admin account on the WFE and a separate account on the SQL server for the database, but we're stuck on setting up the WSS search capability.
I couldn't seem to get things to work when using Central Admin to start the WSS Search service. I'm thinking I'll need to use stsadm -spsearch to set up the WSS search manually, rather than using the menus in Central Admin.
Does anyone have any tips and/or resources they recommend?
You want to setup your WSS3 site using Forms Based AUthentication, with an ASP.Net SQL Membership Provider and backend database.
Microsoft have a very nice guide on MSDN.
I followed this guide when attempting something similar. This explains how to allow forms based and AD authentication on the same site but you could just follow the parts that explain how to setup forms based.
This also includes changing the web.config file for central administration so that it can access the SQL database used to store users for forms based authentication.
It is very easy to follow.
We're looking for the same... rather we have a separate AD for our DMZ, however, for the extranet, would like to use it without AD accounts. May I ask what you've come up with so far?
Have seen posts talking about local machine accounts, but we do have 2 app servers and realize the maintenance involved to keep them in sync if we use local machine acounts. Swore I saw a 3rd party tool that would allow user's to be added into their own db and managed through their web-part/portal but can't seem to find it now.
Is it possible to create a user with permissions of both a local administrator and NETWORK SERVICE?
I've got a Sharepoint timer job which runs stsadm for which it needs local administrator permissions. On the other hand temer jobs are also used by other services which need NETWORK SERVICE permissions and those to sets of permissions only overlap, so I need a user with the "sum" of the permissions to run OWSTIMER under.
(I know that most of the operations you can perform with stsadm sharepoint administration API can be used, by in my case it is the operation which moves a site collection between content databases for which there seems to be no API equivalent).
I recommend always using domain accounts - SharePoint works best on servers connected to an Active Directory server. For production environments a best practice is using a least privilege account. I always create the following domain account dedicated to SharePoint services:
DOM\spservice
You do not need to grant any special privileges to this account as SharePoint will automatically do this for you when you specify the account during setup.
I can't help you with the user permissions (Lars hit the important points), but I wanted to share some information that may be of use.
You mentioned that you're trying to move site collections between content databases and haven't found an API the can be leveraged. Have you looked into SharePoint's Content Deployment API (also know as the PRIME API) to see if it can assist? The types of which I'm speaking are located in the Microsoft.SharePoint.Deployment namespace, and they provide you with mechanisms to export (via SPExport) site collections as CAB files and then import them (via SPImport).
SharePoint leverages types in this namespace for its own content deployment paths and jobs (in MOSS); it's also the API that is leveraged by the STSADM.EXE executable for export (STSADM.EXE -o export) and complementary import operations. For that matter, it's also used by SharePoint Designer for it's site "backup" and "restore" operations.
For an example of how this API can be leveraged, check out the SharePoint Content Deployment Wizard tool on CodePlex (http://www.codeplex.com/SPDeploymentWizard).
I hope this gives you a potential alternative to shelling out to a command line in your timer job!