The people picker, allows users to assign tasks to users in AD. This is a useful, but what do you do if you have multiple clients or user groups who shouldn’t see each other.
Enter the Filtering People Picker for the entire collection.
People Picker Filters: http://technet.microsoft.com/en-us/library/gg602075.aspx
People Picker is configured at the zone level for a farm by using the Stsadm setproperty operation. By configuring the settings for the control, you can filter and restrict the results that are displayed when a user searches for a user, group, or claim. Those settings will apply to every site within the site collection.
Restrict users to pick from a specific OU: stsadm -o setsiteuseraccountdirectorypath -path<Valid OU name>–url<Web application URL>
Restrict users to pick from only users within the collection: stsadm -o setproperty –pn peoplepicker-onlysearchwithinsitecollection –pv yes –url<Web application URL>
** this is ideal either you have access to the collection our you don’t.
To meet the requirement of limiting users to only co workers would need be its one collection. While this approach introduces many collections (one for each client/ instance) it’s not an untenable situation nor will it reach any limits.
SharePoint Boundaries: http://sdrv.ms/S9ive2
250,000 per site collection
You can create a very large total number of Web sites by nesting the subsites, For example: a shallow hierarchy with 100 sites, each with 1,000 subsites, is a total 100,000 Web sites, or a deep hierarchy with 100 sites, each 10 levels deep also containing a total of 100,000 Web sites.
The maximum recommended number of sites and subsites is 250,000 sites. Note that Web deletion can have significant impact on the Site’s availability, access to the site and subsites will be limited during the time of Web deletion. Also high concurrency of subsite creation might fail beyond a certain pace
Site Collection Size
100 GB per site collection
A site collection should not exceed 100 GB unless it is the only site collection in the database.
Certain site collection actions, such as site collection backup/restore or Move-SPSite, cause large Microsoft SQL Server® operations which can have performance impact or fail if other Site collections are active in the same database.
300 per Web application
With 300 content databases per Web application, end user operations such as navigating to the site or site collections are not affected. But admin operations such as creating a new site collection will experience performance degradation. It is also suggested to user PowerShell to manage the Web application when a significant number of Content databases is present
This entry explains one way to deal with double booking. The explained SharePoint Designer procedure is not bullet proof, but by extending it, it could easily be made to be.
This procedure will check to see if the conference book is already booked and if it is, an email is sent to the creator of the list item stating that the conference room is booked.
- Set up a workflow so that each time a calendar item is saved the workflow runs.
- Create a condition to check the start date of the current item <Start Time> is greater than a start time of other items in the list.
Start Time contains Date and time
- Create a sub condition to check the start date of the current item <Start Time> is less than a start time of other items in the list.
Now we have identified if the current saved item’s <Start Time>, is in between other items. AKA a double booking.
- An email should be sent if there is a double booking. What should be done is a further condition to only send the email if the item is created. This can be done by comparing the created and modified dates.
The whole step should look something like this:
One point to be made with adding in a double booking check process. Be careful of what you ask for. If you add a hard and fast rule, it will have to work in every time. Often (particularly when humans are involved) this is not possible. E.g: The owner of the firm books the conference room and out ranks all over booking. Be pragmatic.
Microsoft’s IIS has a feature called (Simple Object Access Protocol) SOAP. Which allows a user to connect to a web service over https/https with an authenticated AD User/group. This connection transfers XML data between computers such as your SharePoint server. If the web service allows it, you can control what data is selected and displayed on your page.
In SharePoint this can be done in SharePoint Designer in data sources. all without a .net developer!!!!!
SharePoint web services Link
The event was well attended with over 200 attendees
My presentation is here:
Excellent straight, non MS techie speak, of how to develop applications in SP2010.
Wish I found this article 2 months ago.
I’m speaking on SharePoint Designer 2010…It’s one hell of an improvement on 2007
Click here to register
SharePoint Saturday Philly meeting details:
Date: May 8, 2010
Time: 8:00am – 5:00pm
Location: DeVry Campus
1140 Virginia Drive
Fort Washington, PA 19034
Office Winter Games Winners Microsoft announced the winners of the Office Winter Games contest. The Office team is sending bloggers Amber Borowski Johnson and Dylan Derryberry to report live from the Games as members of the credentialed press. The idea is to show how Office 2010 can be used in a variety of settings – on the PC, phone and in the browser – to share information and get work done.
Excerpt from SharePointConnections
The site: Link
The nice 2010 features that I like are: Images with their loading effects.
Silverlight web part
The search is very Bing like
And works in Firefox!!!
How much of this is customized, I don’t know.