1. Starting in Central Administration, under Application Management, click on the Manage web applications.
2. Make sure you select the site you want to enable anonymous access and click on the Authentication Providers icon.
3. On the Authentication Providers pop-up window click on the Default zone.
4. Under Edit Authentication, check Enable anonymous access and click Save.
5. Going back to Web Application Management click on the Anonymous Policy icon.
6. Under Anonymous Access Restrictions select your Zone and set the Permissions to None – No policy and click Save.
7. Now, web application will allow anonymous access to be set. So, navigate to your top level site collection for the web application. Click the Site Actions > Site Settings. Under Users and Permissions click Site permissions.
8. Under Permission Tools, click Anonymous Access icon and set the permissions to Entire Web site and click OK.
That’s all, folks! If you followed these steps properly you should have now Anonymous Access enabled.
SharePoint Admin Responsibilities:
- Managing and checking the overall server health and functionality.
- Monitoring SharePoint disk space usage through the built-in SharePoint reports for each site collection.
- Managing SharePoint permissions.
- Analyzing and reporting upon SharePoint usage and activity.
- Moving/copying sites.
- Supporting network load balancing needs and ensuring its correct operation (NLB).
- Regular review of the events and messages reported in Event Viewer and Performance Monitor.
- Regular review, clean-up, management and configuration of SharePoint accounts and sites. This portion of the role will work closely with an Active Directory administrator if they are separated.
- Regularly analyzing SharePoint content and storage.
- Monitoring SharePoint trends (e.g. site usage and growth, disk space usage and growth).
- Setting up alerts and enforcing policies.
- Regularly auditing your SharePoint environment.
- Identifying and reporting governance violations.
- Checking for operating system, SQL Server and SharePoint patches and cumulative updates.
Difference between SharePoint Architect and SharePoint Admin
The following article is taken from http://gunakuppusamy.wordpress.com it was very useful to me. I am just exposing his knowledge to outer world
Please note that there are different types of SharePoint Architects roles for bigger enterprise
SharePoint Information Architect,
SharePoint Infrastructure Architect,
SharePoint Solutions Architect.
Many of us are having hard time to differentiate the responsibilities between SharePoint Architect and SharePoint Admin.
I agree that some the responsibilities will overlap (Of course, I did mention below on shared responsibilities) but Architect / Admin are two different roles.
In my perception, SharePoint Architect can perform Admin role but NOT the other way around. You will find out “WHY” when you finished reading this blog.
Please feel free to comment if you want me add / update the responsibilities.
SharePoint Architect
1. Define the Physical Architecture / Logical Architecture / Capacity planning and make sure that it’s scalable.
2. Define the Architecture for Globally Distributed Systems (Strategy for Regional Based Farm and the communication between Central and Regional Farms)
3. Define the integration architecture for SharePoint to integrate with various disparate systems (SAP / Finance systems etc.,)
4. Define the Information Architecture / Taxonomy and clearly define Taxonomy Term Store for the whole Enterprise
5. Participate in Architectural Peer Review activities with other Groups (DBA / AD / Legal Team etc.,)
6. Define the Service Applications Architecture and make sure that there is NO SPoF (Single Point of Failure)
7. Work with CxO and Program Managers to define the architecture and design the solutions to address business needs and opportunities (Basically, Architect should be Trusted Advisor for leadership team)
8. Responsible for Mentoring SharePoint Admin and Development Team. Should have good relationships with Key Vendors and closely work with them to understand their offerings and roadmaps.
9. Implement best practices and Governance procedures for SharePoint custom solutions
10.Conduct a PoC (Proof of Concept) for MCA (Mission Critical Applications). Lead the development of SharePoint components (web parts, application pages, page layouts, etc.) for enterprise scale Portal, ECM, and Collaboration solutions
11.Define the CCD (Custom Code Deployment) processes (Dev -> Test -> Staging -> Production). Most of the time, He / She needs to prepares ADS (Automated Deployment Script)
12.Understanding of multiple access and authentication models such as NTLM, Kerberos, Claims-based, ADFS, SSL, card services, TMG, UAG, etc.
13.Lead and facilitate information gathering sessions to validate business cases, gather and document business and functional objectives
14.Define project deliverable standards and ensure quality of customer deliverables and alignment to industry best practices
15.Define the Detailed Disaster Recovery strategy which aligns into Enterprise DR strategy
SharePoint Admin
1. Knowledge of Windows Server Environments: Windows Servers, IIS, SQL and Client Server Environments/Web Applications and Knowledge of Enterprise Networks and configurations: TCP/IP, Load Balancing, Failover
2. Knowledge of SharePoint 2007 and 2010 farms: SharePoint Server roles, SharePoint installation, configuration and administration, Central Administration management, PowerShell administration modules
3. Monitoring Server Health and closely monitor event logs / ULS logs for any critical errors. Delegate the troubleshooting of the issues to development team if custom codes have caused the issues
4. Planning and implementation of Service Packs and Cumulative Updates of SharePoint Foundation and SharePoint server
5. Performing site and data migration tasks between cross farms, sites, & site objects.
6. Creating and maintaining documentation for SharePoint infrastructures, deployments, and service specifications
7. Provide direction to lead the customer and development team on where configuration changes can be made to utilize “Out of the Box” functionality instead of code customizations
8. Basic development knowledge of SharePoint Designer, InfoPath form and Dashboard Designer
9. Responsible for providing Enterprise feature such as Excel Services and InfoPath services (Add Trusted File Locations, Upload administrator-approved form template etc.,)
10.Collaborate with Infrastructure and DBA groups on backup/recovery operations and disaster recovery testing related to SharePoint implementation.
11.Work with developers to deploy custom applications and solutions to production and pre-production environments
12.Perform common SharePoint Power User functionality in order to create solutions that solve a business need and provide value
13.Responsible for managing Service applications, create web applications, site collections
14.Responsible to install and configure Antivirus product and define Real time scan settings and Manual scan and scheduled scan settings
15.Responsible for monitoring various SharePoint Timer jobs and recycle them when necessary
16.Responsible for configuring AAM (Alternate Access Maaping) and Managing Farm features / soultions
Shared Responsibilities
1.Create a SharePoint 2010 Configuration document that takes into account software configuration, service accounts, IP addresses, host names, and the service application topology
2.Assists in solving technical and performance problems within the technical infrastructure
3.Define and enforce security rules at the farm and site collection levels
4.Install and configure third-party tools and/or Web parts for evaluation
5.Define user training and orientation plans and prepare training materials
6.An installation guide that includes information about server builds (for the operating system, disk configuration, and so on)
7.Performs disaster recovery operations as required.
Enable Audience Targeting in SharePoint 2010
The following steps will teach you how to enalbe audience targeting in sharepoint 2010.
Step 1. Create two users in Active Directory which names are “test1″ and “test2″.
Step 2. Log in SharePoint site with the administrator.
Step3. Go to Site Settings>Site collection features, start the “SharePoint Server Publishing Infrastructure” feature, then go to “Site collection navigation” to check if “Enable audience targeting” is selected.
Step 4. Go to Site Settings>Site Permission>Create Group, create a group named “testinggroup” whose permission level is Full control, then add “test1″ to this group.
Step 5. Go to Settings>Site Permission >Grant permissions, create a user named “test2″ whose permission level is Full control.
Step 6. Now let me take our product BoostSolutions Password Reset web part as an example. In the web part zone click Edit web part. In the Advanced section of the web part tool pane add the “testinggroup” into the Target Audiences box and click OK.
Step 7. Log in SharePoint with “test1″ and “test 2″ respectively. You will see the difference as below.
When you log in SharePoint with “test1″, you will see the Password Reset web part, and when you log in SharePoint with “test2″, you will not see the web part. This shows we have set the target audience successfully.
How to Setup Load Balance in SharePoint 2010 Farm
Web front end servers
A web server that handles web page requests from users, processes the request and returns the data.They process HTTP/S traffic and relies on Internet Information Server (IIS) to provide much of the web server ‘stack’
In a farm there can be multiple Web Front End (WFE) servers and a Network Load Balancer (NLB) will distribute requests between them. This is the primary method of scaling in SharePoint – as the number of users grows you add more WFE servers.
Is also used to add redundancy – If a WFE fails the NLB can distribute requests to other WFE’s.
1 Add a WFE server to the current SharePoint Farm. (One has existed in the farm)
2 Add the feature Network Balancing and configure the cluster.
3 Create an entry in the DNS for the cluster.
Assume one WFE server has been added to your SharePoint farm, now let’s add another one.
1. Install SharePoint in another WFE Server and enter the configuration wizard, connect to an existing server farm.
2. Click Next then type database server name, click Retrieve Database Names and select the farm configuration database.
3. Click Next and input the passphrase which you have specified when you first install the SharePoint Farm.
4. Click the Advanced Settings and Select User this machine to host the web site.
5. Click OK to finish the configurations.
6. Now install the feature NLB(Network Load Balancing) in the two WFE(web front end) SharePoint servers.
7. Configure NLB and create a cluster, Go to Start>Administrative Tools>Network Load Balancing Manager.
8. Right-click Network Balancing node and select New Cluster.
9.Connect to one host and add the cluster IP address.
10.Select Multicast, the default is Unicast.
11. You can define the port rule, but I leave the default here.
12.Add the other WFE server to the cluster.
13. Type the host name that to be part of the new cluster.
14.Set the priority to be 2.
15. Click Next, complete the configuration.
16.Create an entry in DNS for the cluster.
17117
17. Set the binding for the site.
18. Modify Alternate Access Mapping for the default site collection from http://spb10wfe1 to http://cluster.
Now it’s great, all configuration has completed, and you can access you site by the URL http://cluster.
sharepoint2013admin 