Showing posts from November, 2013

Default Value for Secure Store Implementation Field

When you import a BDC model into Central Administration in SharePoint 2013, you often need to configure it to use a Secure Store Target Application. This is straightforward to an extent: Browse the external systems in your BDC service application. Click through to the settings of the external system that corresponds to your BDC model. Select an appropriate Authentication Mode for your Secure Store Target Application ( Impersonate Windows Identity or Impersonate Custom Identity ). Provide the target application ID for your secure store target application. The tricky bit is that SharePoint expects you to provide a value for Secure Store Implementation . If you've changed the authentication mode from User's Identity or BDC Identity, this field will be blank: What you actually need to type in this Secure Store Implementation field is the fully-qualified type name for the secure store provider. Unless you've built your own secure store provider (i

Adding Active Directory OU Members to a SharePoint 2013 Group

Over the last few months we've been busy writing the SharePoint 2013 developer courseware for Microsoft (check out 20488B and 20489B ). That hasn't left much time for blogging, so I plan to write a few quick posts on some of the more tricky things we had to figure out along the way. First up: how to use PowerShell to import a bunch of users from an Active Directory OU into SharePoint and add them to a group. The script below does the following: It adds a new group named Finance Members to the specified site. It links the group to the site as the associated members group. It grants the Contribute permission level to the group. It gets all the members of the Managers OU from Active Directory. It adds each AD user to the Finance Members group. # Variables $siteUrl = "" $groupName = "Finance Members" $groupDescription = "Members of this group can contribute to the Finance site." # Load the SharePoint PowerShe