SharePoint Blog - René Hézser

Anmelden  RSS Feed RSS Feed
Startet die Suche

Archive

Kategorien

Links

Andere Blogs



Add to Technorati Favorites

Jul 292010

List members of SharePoint Groups

Every SharePoint group has a setting to prevent users, who are not members of the group, to see who actually is a member. This setting works great when you use a browser to access the group. The setting can be configured on the property page of every SharePoint group.

2010-07-29 14h36_21

As you can see, you’ll get a message telling you that you may not see the members of that particular group.

2010-07-29 14h39_52

Now comes the interesting part.

If you use the SharePoint build-in web service to access this information, you’ll get it even if you are not a member of that particular group! The web service you’ll have to use is UserGroup (http://msdn.microsoft.com/en-us/library/ms772647%28office.12%29.aspx).

On the left side, you can see the request for a user with the login name DOMAIN\user. The response we get from a web service request to http://sharepointurl/_vti_bin/usergroup.asmx is on the right side. It responds with the user as member of the group, even if the group settings should prevent this. We should not see any member.

2010-07-29 14h53_17

This fact was tested on a Microsoft Office SharePoint Server 2007 with SP2 and CU from this year (can’t remember which one). And if you would like to know with what tool I made the web service test, it is “soapUI” from http://sourceforge.net/projects/soapui/files.

Conclusion:

Even if you prevent users from seeing group members in SharePoint, you can’t be sure they can’t access this information on another way. I’ve not tests accessing this information with the object model, because if it works with a simple web service query, that’s enough for me to see the group memberships are not safe.


Published: 7/29/2010  5:46 PM | 0  Comments | 0  Links to this post
Tagged as: SharePoint

Jul 162010

CKS:EBE 3.0-Enhanced Blog Edition 3.0

Like many other blogs running SharePoint, my blog uses the EBE to add more functionality to the default SharePoint blog.

And since I am one of the developers of the EBE 3.0, I’m glad that we announce the release of the next release. Version 3 brings along many new features and improvements of already implemented features.

New Features
*Ability to theme wiki pages
*Ability to export post to PDF
*Localization (French, Spanish)
*Technorati Links from post categories
*Ability to bookmark post with Twitter
*Centralized Theming - Ability to create a theme library at the root and allow sub blog sites to use the common theme library.
*The ability to add an XML feed control
*Logging of pingbacks and trackback errors to SharePoint Logs directory
*Support of feature stapling
*Preliminary SharePoint 2010 Beta 3 compatible (with web.config edits)
*EBE caching and performance validation
*Performance increases for page loads less than <3 sec
Note: Some features are specific to certain themes

Enhancements
*Caching enhancements
*Added caching to XML controls
*Added enhanced XSL caching
*Ability to exclude the EBE HttpModule from specific paths
*Auto-Discovery for Live Writer metaweblog api
*Tweaks and enhancements to all themes
*Ability to sign-in after denied access to system pages
*Posts with future date are now hidden from posts list
*Browser title now matches post titles
*Comments are not added if they are spam

Read the release notes here: http://cks.codeplex.com/releases/view/28520


Published: 7/16/2010  12:06 PM | 1  Comment | 0  Links to this post
Tagged as: CKS EBE, CodePlex, SharePoint, Development

Jul 142010

How To install SharePoint 2010 prerequisites automatically

Don’t leave if you read “Powershell” and think “Oh my. Why does it take Powershell to do this?”. Powershell is easy to use and a great tool for this task.

This post is about installing all required components that are needed for a SharePoint 2010 installation (Hardware and software requirements (SharePoint Server 2010)).

So what are we going to to?

  1. Download required software
  2. Create a Powershell script to install the requirements
  3. Install required software

Download required software

The advantage of downloading the required components prior installing SharePoint is, that we can use the downloaded bits on many servers. The size of all these components is about 387 MB. So even if you have a fast internet connection, it might be worth downloading them.

A Powershell script for downloading all required software can be downloaded here: http://autospinstaller.codeplex.com/releases/view/44442

When you start the script, it will ask where you want the downloaded files to be saved.

 image

I’ve copied the content of the SharePoint 2010 Installation bits to a local folder. e.g. C:\Install\SP2010Bits

Then the folder for would be c:\Install\SP2010Bits\PrerequisiteInstallerFiles

Create a Powershell script to install the requirements

A Powershell script in the Rootfolder of the SharePoint bits will install the required software. Create a new file “c:\Install\SP2010Bits\InstallPrerequisites.ps1”. The content of the file would be

# get current folder
$folder = Get-Location
# install requirements
Start-Process "$folder\PrerequisiteInstaller.exe" -Wait -ArgumentList "/unattended `
	/SQLNCli:`"$folder\PrerequisiteInstallerFiles\sqlncli.msi`" `
	/ChartControl:`"$folder\PrerequisiteInstallerFiles\MSChart.exe`" `
	/NETFX35SP1:`"$folder\PrerequisiteInstallerFiles\dotnetfx35.exe`" `
	/PowerShell:`"$folder\PrerequisiteInstallerFiles\Windows6.0-KB968930-x64.msu`" `
	/KB976394:`"$folder\PrerequisiteInstallerFiles\Windows6.0-KB976394-x64.msu`" `
	/KB976462:`"$folder\PrerequisiteInstallerFiles\Windows6.1-KB976462-v2-x64.msu`" `
	/IDFX:`"$folder\PrerequisiteInstallerFiles\Windows6.0-KB974405-x64.msu`" `
	/IDFXR2:`"$folder\PrerequisiteInstallerFiles\Windows6.1-KB974405-x64.msu`" `
	/Sync:`"$folder\PrerequisiteInstallerFiles\Synchronization.msi`" `
	/FilterPack:`"$folder\PrerequisiteInstallerFiles\FilterPack\FilterPack.msi`" `
	/ADOMD:`"$folder\PrerequisiteInstallerFiles\SQLSERVER2008_ASADOMD10.msi`" `
	/ReportingServices:`"$folder\PrerequisiteInstallerFiles\rsSharePoint.msi`" `
	/Speech:`"$folder\PrerequisiteInstallerFiles\SpeechPlatformRuntime.msi`" `
	/SpeechLPK:`"$folder\PrerequisiteInstallerFiles\MSSpeech_SR_en-US_TELE.msi`""

So you have the SharePoint 2010 Bits in a folder. In the same folder is the install script, and in a subfolder “PrerequisiteInstallerFiles” all requirements.

image

Install required software

Just run the script from within Powershell :-)

image

Now you are ready to install SharePoint 2010.

If you get an exception like this, set the execution policy “Set-ExecutionPolicy RemoteSigned“ in a Powershell window.

File C:\install\SP2010Bits\InstallPrerequisites.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details.
At line:1 char:27
+ .\InstallPrerequisites.ps1 <<<<
    + CategoryInfo          : NotSpecified: (:) [], PSSecurityException
    + FullyQualifiedErrorId : RuntimeException


Published: 7/14/2010  8:26 AM | 1  Comment | 1  Links to this post
Tagged as: SharePoint, Powershell

Jul 112010

SQL Reporting Services 2008 R2 and SharePoint

Did you know that the latest SSRS have a build-in support for SharePoint lists as DataSource?

image

So if you need arguments to update to SQL 2008 R2, this is one :-)


Published: 7/11/2010  11:05 AM | 1  Comment | 0  Links to this post
Tagged as: Reporting Services, SharePoint, SQL Server