Un-Extend and Re-Extend a Web Application

To update the URL or IIS bindings of a Web application, you must unextend and re-extend the Web application, and reconfigure alternate access mapping URLs or IIS Web site bindings.

Unextending and re-extending a Web application
If you need to change your IIS bindings, unextend the Web application from the zone that the Web application has been extended into (without deleting the Web application), and then re-extend the Web application into the same zone. Consider trying these migration procedures in a test environment before deploying them in a production environment.

Unextend the Web application from the zone by using the Remove SharePoint from IIS Web site link on the Central Administration Application Management page, as described in the following procedure:

Unextend a Web application1.On the SharePoint Central Administration Web site, on the Application Management page, in the SharePoint Web Application Management section, click Remove SharePoint from IIS Web site.

2.On the Web Application menu, click Change Web Application.

3.On the Select Web Application page, click the Web application you want to unextend.

4.In the Select IIS Web site and zone to remove list, click the IIS Web site and zone you want to remove. Because a Web application can be extended in up to five zones, make sure you select the correct IIS Web site and zone.

5.In the Delete IIS Web sites section, click Yes if the IIS Web site is only hosting SharePoint Products and Technologies content. If the IIS Web site is hosting other content, you might not want to delete the Web site. In that case, click No.

6.Click OK. This action does not delete the Web application, nor does it delete the content databases of the Web application.

After you have unextended the Web application, you can re-extend the Web application to the same zone, using your updated bindings.

Re-extend a Web application1.On the SharePoint Central Administration Web site, on the Application Management page, in the SharePoint Web Application Management section, click Create or extend Web application.

2.On the Create or Extend Web Application page, in the Adding a SharePoint Web Application section, click Extend an existing Web application.

3.On the Extend Web Application to Another IIS Web Site page, on the Web Application menu, click Change Web Application.

4.On the Select Web Application page, click the Web application you want to extend.

5.In the IIS Web Site section, if you have already created an IIS Web site with the appropriate bindings for Office SharePoint Server to use, click the Use an existing IIS Web site option and select the IIS Web site from the list. Otherwise, click the Create a new IIS Web site option.

6.In the Port, Host Header, and Use Secure Sockets Layer (SSL) fields, type the IIS bindings you want to use.

7.In the Load Balanced URL section, in the URL field, type the URL that end users will use to locate this Web application. If you are using a load balancer or reverse proxy, this is the URL of the load balancer or reverse proxy.

8.In the Load Balanced URL section, in the Zone list, click the zone that you previously selected.

9.Click OK.

Additional steps for updating a Web application URL and IIS bindings

To complete the process of updating a Web application URL or IIS bindings, you need to perform the additional steps listed in this section, after you have re-extended the web application into the same zone.
  Update the alternate access mapping URLs for the zone

If you are using a load balancer or a reverse proxy, make sure that your internal URLs are updated in alternate access mappings to reflect the new IIS bindings. In addition, you need to update your load balancer rules, or your reverse proxy rules, to align with the new IIS bindings.

Comments

Post a Comment

Popular posts from this blog

Activating a SharePoint Feature on Multiple Sites or Site Collections using PowerShell

I need to either activate or even deactivate certain features on multiple site collections. So the below script will allow you to do this.. First step create a text file in the below format, you only need to define the URL for each Site collection or site. SiteURL http://sharepointsuresh/sites/site1 http://sharepointsuresh/sites/site2 http://sharepointsuresh/sites/site3 http://sharepointsuresh/sites/site4 http://sharepointsuresh/sites/site5 http://sharepointsuresh/sites/site6 You can list all features installed on your sites by using the following PowerShell: Get-SPFeature | Sort -Property Scope,DisplayName | FT -GroupBy Scope DisplayName,Id Then use the below PowerShell Script: $SiteList = Import-Csv Sites.txt ForEach ($item in $SiteList) {             If ($item -ne $null)             {                 Write-Host "Activated Branding Feature for: $($item.SiteURL)" -...
Read more

Managed Path with WildCard and Explicit Inclusion

I thought to put an article on Managed Paths in SharePoint covering their use with Explicit Inclusion and Wildcard Inclusion and also how to use them in Real World scenarios So let’s see what Managed Path is Managed Path: By default when we create Site Collections inside a Web Application in SharePoint they are created with the URL “http://servername:portnumber/site”.  But if we want to have a specific URL other than “/site” we need to create Managed Path. So as an example if we want to create Site Collections for IT and HR Dept and want to have URL's like “http://servername:portnumber/IT” and “http://servername:portnumber/HR” we can do with the help of Managed Paths. Managed Path helps to have site collection with the URL other than “/site”. Managed Path can be created in Central Administration in Application Management under SharePoint Web Application Management. When we create Managed Path either we can select Explicit Inclusion or Wildcard Inclusion. So let’s see what ...
Read more

List All SharePoint 2010 PowerShell Commands

Use this PowerShell command to output a list of all cmdlets that are found within the SharePoint 2010 namespace: Get-Command –PSSnapin “Microsoft.SharePoint.PowerShell” | format-table name > C:\SP2010_PowerShell_Commands.txt If you would like a little more detail, then try this one: Get-Command –PSSnapin “Microsoft.SharePoint.PowerShell” | select name, definition | format-list > C:\SP2010_PowerShell_Commands.txt
Read more