Archive for April, 2010

SharePoint 2010 – Role of the App Server

by Cory Peters on April 29, 2010 in Blog with 4 Comments

Previously in SharePoint 2007 a common SharePoint environment looked something like:

  • Web Front End Server
  • Application / Index Server
  • Database Server

Now when we said “Application Server” that usually meant things like Central Administration and Search but really didn’t mean a whole lot because while we wanted to isolate additional services to this box, SharePoint didn’t give us that level of control.

Enter SharePoint 2010… Continue reading →

SharePoint 2010 and SQL Server 2008 R2 are now RTM!

by Cory Peters on April 25, 2010 in Blog with No comments

SharePoint 2010 is now available for download on MSDN (as of last week). For those lucky MSDN subscribers go pick up your copy and start planning your upgrades/implementations today!

Also, Todd Klindt has pointed out on his blog that SQL Server 2008 R2 is available for a 180 day trial. Hopefully that will be long enough for it to be released on MSDN. Let’s hope that we can upgrade it to the full version once we all have keys! Here’s the direct link to the SQL Server 2008 R2 download page.

SharePoint – Limited Access – What is it?

by Cory Peters on April 24, 2010 in Blog with 5 Comments

This has been around for a while but since I still get questions about it from clients I figured I would post an explanation that may be a little more visual that other explanations.

When you start customizing security on your SharePoint sites by breaking inheritance at different levels you may start to see your nice clean permission lists be infiltrated by “Limited Access”. MSDN explains the “Limited Access” permission level as:

Allows access to shared resources in the Web site so users can access an item within the site. Designed to be combined with fine-grained permissions to give users access to a specific list, document library, item, or document, without giving users access to the entire site. Cannot be customized or deleted.

Let’s look at a scenario: Continue reading →