Showing posts with label Configuration and Deployment. Show all posts
Showing posts with label Configuration and Deployment. Show all posts

Saturday, May 21, 2011

WebApplication Permission Policy in SharePoint 2010

After long time I found some time today to share my new experience in my new organisation. Since last 10 weeks I was working on my 1st ever SharePoint implementations assessment assignment. And ad on to that it was for SharePoint 2010.

My Assignment included to set up or to be precise suggest the Architecture for implementation of SharePoint 2010.

One of the requirement from the client is real time. They were planning to make their intranet portal available on extranet users as well. But they want the restriction on some of the confidential documents when same user accessing the portal from extranet.

Requirement: User A is a exist as a Store Manager in AD. He should be able to access the document on portal only when he is accessing it from store or say from Intranet. At the same time when User A is trying to access the same document on portal from Home through extranet the document should not be accessible to him. 

Myth:It can be achieved by using (1) Audiance Target (2) Creating different group for Intranet and Extranet.

Solution: I would say option (2) is half true. But My Document library is having a permission only for Intranet Group. Now when user A who is a part of both Intranet & Extranet Group how SharePoint will know when User A is accessing the portal from Extranet or Intranet?

Answer to this is Web Application Permission Policy in SharePoint 2010.

Step1: Create portal http://myportal for "Intranet Zone"
Step2: Go to Central Admin and Extend "http://myportal" for "Extranet Zone"
Step3: Select the created "http://myportal" and select Permission Policy from the "Ribbon" on the top.
Step4: Create new policy for "Deny" and add Intranet AD group to that, which will prevent the site to be accessed for the defined group in the Deny Policy.

Now when User A is accessing the portal from extranet and entered the site, SharePoint knows that User A is accessing the portal as a part of Extranet AD Group and not allowed him to access the Document Library which is only having an access to Intranet Group users.

Feel free to write to me for any help on this...and click here and here to know more on how to set up site permission policy.

Sunday, May 16, 2010

Search Crawling Stops or The parameter is incorrect in sharepoint search

This is one of the worst problem I came across. :(

I don't blame Microsoft for this, but I can say a wrong governance model is the reason for this.

Problem: My client complaint that a new item added on the site is not comes under a search result since last few days. I spent lot of a time to find out the real cause. When I have gone through the Search Crawling log an error is found saying "The parameter is incorrect in sharepoint search". When I checked for all the other sites on the farm all are working fine with search and none of the site has given such error at the time of crawling. That has increased my curiosity.

After spending a full day at last I found a reason and its a cause for small party ;), thanks to Mattias Lindberg

Solution: The reason which stops the crawling for the site is the user we have added in the site are more than 5000 in a particular group instead of adding an AD Group.

I am just copying the workaroung given by Mattias below.

Our solution was to require sites with over 1500 members to use an AD group for keeping track of membership, as recommended by the KB for SPS 2003. One disadvantage with this approach is that you must maintain membership by updating the AD group so you can no longer request membership using SharePoint standard dialogs.

Probably an article is wriiten for SPS 2003 but infect it is applied to MOSS 2007 as well.

Set Domains for People Picker in SharePoint

I am currently working with one of the retail client where we have one requirement as below.

Client is having 4 different domains set for their different group of companies.
1) abc, 2) def, 3) uvw and 4) xyz.
Now client doesn't want a users from domain "uvw" to search by anyone (including site admin) in people picker.

Solution:
I have found a very good article by Joel Oleson @ set propery for people picker

you can use a command as "stsadm.exe -o setproperty -url http://server:port -pn "peoplepicker-searchadforests" -pv "forest:foo.corp.com;domain:bar.foo.corp.com", LoginName, Password"

Tuesday, July 7, 2009

SharePoint Farm Configuration and Deployment

This series of articles which I have found on SharePointMagazine, that provides guidelines and instructions of how to plan, build and configure SharePoint farm across organizations. Current practices are based on the different of SharePoint projects and can be used as step-by-step instructions helping to configure proper baseline for SharePoint farms.

Part 1 – Architecture and Logical Planning
Part 2 – Installation
Part 3 – Development Environment
Part 4 – Backup and Recovery Strategy
Part 5 – Virtualization
Part 6 – Post Deployment

Friday, June 26, 2009

Recommended SQL disk size for MOSS-2007

Few days back I started working on a new project for one of the client.
The current environment they have is having a lots of probelme and is kind of a mess. We decide to improve their current environment. And the first challenge comes up is to convience their DBA Team for the sizzing of the SQL Server for MOSS. Thanks to cleverworkarounds, we got a very good artilce.
This article helps us to make the decesions on Disk and I/O Sizing for MOSS2007. Read Part-1 & Part-2