This post is migrated from previous hosting provider. There are still some issues with old posts. Please make a comment on this post with any issues.

Give your SharePoint 2010 custom Application Proxy Groups pretty names

Tags: SharePoint 2010

SharePoint 2010 allows you to configure your Service Application in Application Proxy Groups. By default all Service Applications ends up in the Default Proxy Group, named default. This Proxy Group is used by all Web Applications unless otherwise specified. Sometimes there is need to create specific Proxy Groups for different Web Applications, the reasons may vary but often it is a result of having different service offerings. For instance you would like to have different Managed Metadata Service Applications for different Web Applications.

Service ConnectionsCustom Proxy Groups can be created in the user interface (Central Administration) and is automatically created once you customize the Service Connections for a Web Application. To create a Custom Proxy group for a Web Applications you go to Central Administration and select the Web Application you would like to configure and then choose Service Connections in the Ribbon. A modal dialog window with all available Service Applications appear, this dialog contains a drop down in the top where you choose Proxy Group. This drop down contains two values by default; default and [custom]. To create a custom Proxy Group for the Web Application you just select the [custom] option and then select the service applications to use.

No pretty names

When you start to create a number of custom Proxy Groups it might be hard to differentiate them from each other. The name [custom] doesn't mean anything, but that it's custom.

Instead I prefer to name these custom Proxy Groups into something meaningful. Unfortunately you cannot create named Proxy Groups in the user interface and have to revert to PowerShell. But it's a really simple PowerShell cmdlet to do this:

New-SPServiceApplicationProxyGroup -Name "Extranet Service Group"

This simple command creates a named custom Application Proxy Group, in this case Extranet Service Group. Now when configuring Service Applications for a Web Application this new Proxy Group will appear in the drop down:

Man, this is pretty!

A far better alternative, don't you agree?


  • Anders Rask said

    And when you created those new proxy groups, you can assign them to your web application using -ServiceApplicationProxyGroup <spserviceapplicationproxygrouppipebind> You can also move SA's into new proxygroups using Add-SPServiceApplicationProxyGroupMember cmdlet. Like so: Get-SPServiceApplicationProxy | Foreach-Object {Add-SPServiceApplicationProxyGroupMember (Get-SPServiceApplicationProxyGroup -default) -Member $_} For more granular control just filter out using Where-Object cmdlet.</spserviceapplicationproxygrouppipebind>

  • Confused said

    When i use this command i cannot add anythign to it through the UI. All the boxes are grayed out, and it wont let me add anything to it. So looks like you have to use powershell to add the apps into the proxy group.

  • Men Moncler Coats Army Green said

    In jail felt place coowners Keashia manley, Sometimes referred to as Sharon engender, 49, Via the 8300 neighborhood of Wildbriar and thus Shaday Williams, 19, Within 4000 section of actively playing the game back link, In Shreveport. Both would be arranged to gaol to achieve bogusing and buying tag words and moreover against the law using art logos.

Comments have been disabled for this content.

About Wictor...

Wictor Wilén is the Nordic Digital Workplace Lead working at Avanade. Wictor has achieved the Microsoft Certified Architect (MCA) - SharePoint 2010, Microsoft Certified Solutions Master (MCSM) - SharePoint  and Microsoft Certified Master (MCM) - SharePoint 2010 certifications. He has also been awarded Microsoft Most Valuable Professional (MVP) for seven consecutive years.

And a word from our sponsors...