I'm so sorry if this question is very basic but I'm very new to SharePoint. I only explored SharePoint Office 365 (SharePoint Online) so I'm not familiar with the server-side of it. I'm using SharePoint 2010. I've installed it in a server along with SQL Server 2008 R2 (so this server is the SharePoint server and the database server). I've configured it as a standalone (which is I'm not sure if right). I have another server for Active Directory Users and the SharePoint/Database server is a member of it's domain. How can I add users from Active Directory to be able to access the Central Administration and the site I'm going to build with the SharePoint/Database server? Please help me as I'm a beginner here. Thanks a lot in advance!
Login using the user which you used to install the Sharepoint 2010.
It will become your System Account . Then add other AD users to the CA site. and provide them appropriate permissions as per your requirements
Also add ad users to the site collection administrators for the other site you want to access .
Add them as a Site collection administrators for that site from Central administration
then log into that site :- goto site actions > site setting > People and Group
Here you can add the users in a group from AD users and provide them appropriate permissions
Related
I did a deep search over internet and watched videos. There is nowhere that I could find how to make Sharepoint 2010 accesible from internet using SBS 2011.
What could be the steps to do this?
i.e : sharepoint 2010 is running properly on intranet. But the users want to reach it from home as well. And we are using SBS 2011 including Active Directory. How will these users reach sharepoint from home or not only from intranet?
Would you direct me ?
I guess best solution is to provide VPN access to users. - future proof and you don't have to tweak any thing to the server. Its cheaper as well considering the cost and they will have seamless integration to AD
Next since you have already have AD configured ( it depends on how it has been setup) you could have additional ADFS configuration to authorise users.
See if you can upgrade to Windows Server 2012 essentials which gives more power than SBS 11 in terms of Claims authentication
Finally, you have to use Claim Based Authentication for the authentication and DNS routing etc which you might have seen on the videos.
Finally, you have cloud think Azure as well as an option.
Although I haven't configured SBS 2011 for SharePoint extranet, It appears to be same like windows 2008 server (slim down one) according to MSDN which should not affect your requirement. Apart from licensing... ( check this).
I have tried to configure alternate access mappings in my SharePoint 2010 which is installed in WorkGroup Windows Server 2008 R2 server but could not make it work.
Here are my steps.
Go to Central Administration-> Manage Web Application.
Select a web application and extend it.
Provide the my12server.com in the host header and leave other default values as it is. I changed the zone to Extranet.
Click Ok.
After sometime, it creates Web Application in SharePoint and Web Site in IIS.
I have changed my hosts file by adding entry
192.168.1.11 my12server.com
Browse the new extended. It asks for credential. Supplied the correct credential but nothing got display. Just a blank page.
Note: I have however successfully extended web application when the SharePoint 2010 is in domain machine.
Please advice me.
Thanks
Prakash
SharePoint is designed to work in domain environments only. In other words, you cannot expect to run it on an underlying Windows Server which joined into a workgroup and expect full functionality. Although there are blog posts around describing installation in a workgroup environment (or, better to say, using local accounts), I wouldn't recommend wasting time with such a mode of operation.
Furthermore, it doesn't make sense to extend a web application just for the sake of providing another hostname. Extending web applications multiple times is mostly useful when you need different authentication providers for each of them. In your simple case you can just configure multiple Alternate Access Mapping records for a single web application.
I am trying to install sharepoint 2010 foundation. I want to have farm content database on a different machine which is not on a domain, but in a workgroup.
When I do a server farm installation, on 'specify database settings' screen, it asks for a domain account. The problem is that my db machine is not on a domain. Is there any way to install sharepoint with this requirement.
The short answer is no, I don't believe you can. You can get away with installing SharePoint 2010 as a single-server standalone configuration in a workgroup, using local accounts for services. To add other servers to form a multiple-server farm, you need a domain environment.
The most straight forward way to do this is have a second server acting as a domain controller and have both servers in their own network. You could try having SHarePoint, SQL and DC all running on the same server, but this might be too much for one server to handle.
What are the required steps to properly allow domain users access to reports via the Reporting Services web site?
What I've tried:
Added users through Reporting Services site (i.e. http://servername/Reports)
Given users access through SQL Management Studio
Result:
users are continuously prompted by the browser for their credentials and can't log in
I don't know why I didn't think of this before but I:
Added desired domain users to the "SQLServer2005ReportServerUser*$InstanceName*" group on the Windows 2008 machine running SQL Server Reporting Services
Added users to specific roles through reporting services web site (http://servername/reports)
AND now users are able to access the reporting services site!
I've been dealing with this exact issue recently. I still don't know the answer, but I think that at least part of it is to add the users to SSRS-specific groups (create them if needed through the SSRS Configuration manager).
Problem:
No access to internal sites after new Instance of SQL was installed on MS SQL Server
Description:
I've got a WSS 3.0 installed on the W2K3 Sever.
Originally, there was only one Instance of MS SQL (MSDE) for Backupexec (bkupexec). Later, we installed WSS 3.0 and instead of installing the new instance of SQL we installed on the same instance (bkupexec). So, at some point all the DBs from Backupexec and DBs from WSS were all together within the same SQL instance.
After we noticed this we wanted to split those two into two separate instances: bcupexec and sharepoint. First, I have done a backup of all DBs within backupexec instance. Then, I installed new SQL Instance and called it Sharepoint and tried to restore all WSS DBs into the new SQL instance. Once that was done I check references in IIS so Content and Config would point into the new instance. But since then no go.
I can access Admin site from within IIS and from the browser. I cannot access any internal WSS sites. It asks for the authentication. All I am using is Windows authentication. Account is in AD.
As I am new to WSS I will be greateful for all suggestions and possible fixes.
If you have changed where the content DB's are located for your site collections you will need to detach and re-attach them using the SharePoint Central Admin.
Navigate to Application Management and switch to the application you're concerned about. Click "Content Databases" under the heading SharePoint Web Application Management. From here you can click "Remove content databse" and hit OK.
This will not remove the physical database from SQL, it will simply disassociate the database with that web application. You can then Add a content database from within the manage content databases screen and type the name of the database you wish to associate the application with.
If the permissions issues persist, ensure that Anonymous access is enabled for the application and that appropriate service account permissions are enabled for the DB's from within SQL and SharePoint.
Not sure this will help, but give this a try...
In central administration make sure you check on the site collection administrator for your site collections and make sure you are using that user.
In IIS Manager, check to make sure that user has access to the IIS web site.