Tag Info

Hot answers tagged

23

When you extend a SharePoint web application, you are telling SharePoint to go to IIS and create a new site, but SharePoint will use it to show the same content. You would normally do that to support different security, authentication and URLs between an Internet site, Intranet and Extranet, for example. When you add a host header it is equivalent to going ...


8

What you're looking for is the host named site collection, which enables you to assign a unique DNS name to site collections. Or alternatively create an AAM for existing Site collection to achieve it. For example, you can address them as http://hr.mycompany.com or http://sales.mycompany.com. The sample PowerShell code creates a new web application listing ...


7

Rather than trying to modify IIS directly, I think it is better to do this in SharePoint Central Administration if you can, particularly if you have more than one web front-end server. To change the URL of your SharePoint try this: Go to Central Administration/Manage Web Applications and select the Web Application. Click on the drop-down on the Delete ...


5

As a rule of thumb you can say that every URL that ends up in the browser address bar anywhere should be a public URL, therefore a separate zone has to be created. As a good practice, each zone should have its own separate IIS website so you can configure different IIS-related settings like host headers, SSL certificates etc. The public URL is what's being ...


5

This can be achieved by Extending each of the web applications instead of specifying AAMs only. The steps from where you are now would be: On each web app, remove the AAMs leaving the default one only On ISS Remove IIS bindings for the deleted AAMs on each of the SharePoint servers for the respective web sites On Central Administration => Manage Web ...


4

As a Best Practice, you never want to reference your SharePoint installation using the machine name so you are on the right track. Add "portal.mysp.test" to your DNS Add "portal.mysp.test" as the name of your Default or Intranet zone in SharePoint You might need to also add "portal.mysp.test" as a host header to your SharePoint web application in IIS. ...


4

Here's a couple of options for you: In Central Admin, go to your Search Service Application (Content SSA if you use FAST Search for SharePoint) then navigate to Server Name Mappings and create one. Set the "Address in index" field value to your Extended zone url (the one configured to be crawled in the content source) and set the "Address in search ...


4

If you want to set different port to your application, first go to IIS -> your site -> bindings -> add binding for new port. Then: Go to Central Administration -> Application management -> Configure alternate access mappings -> Add Internal URLs -> here set your alternative name. Also, remember to configure your DNS service or hosts file, so browser is ...


4

You can disable the http binding in your IIS. Open the site and have a look on the right side under "Actions" you will find "Bindings". Allow only the 443 binding with a valid certificate for your site and remove the 80 port binding ;) If you do this then users will not be able to reach anything with http anymore for this site. You can use the Rewrite ...


3

I think the problem is most likely that you are running SSL on a non-standard port. I believe the search crawler will only crawl SSL on standard port 443. Are you using Kerberos or NTLM for authentication?


3

Extend your existing web application to a new port ( CA > Application Mgmt > Extend an existing web application > apply new port and/or host header). You can then delete the old web application using CA. hth Anders Rask


3

Maybe it's the problem with DisableLoopBack. http://support.microsoft.com/kb/896861/en-us


3

This is a difficult topic to describe in words only. I recommend you take a look at this link which I think does a great job of illustrating how to manage host headers, alt access mappings, and even ssl if applicable. ...


3

You can achieve this using Host Named Site Collections. From TechNet Microsoft SharePoint Foundation 2010 supports both path-based and host-named site collections. The primary difference between path-based and host-named site collections is that all path-based site collections in a Web application share the same host name (DNS name), and each ...


3

Okay. finally, I found a article and it helped me right away... http://www.howtogeek.com/howto/vmware/allow-access-to-a-vmware-virtual-machinenat-from-another-computer/ Went to "Virtual Network Editor" from my host computer (found under VMWare menu) Change the IP address for the NAT subnet ip to 192.168.10.0 Followed the article above for more on NAT ...


3

We finally figured out the problem with this one. We had given Full Read permissions to NT AUTHORITY\Authenticated Users for All zones in User Policy of the web applications in question. I am not sure of the reason for giving this. We removed it. Then, a full crawl fixed the issue. Thanks!


3

If the web application is set to use a specific port, you will be bound to that port even with a host header. So simply put, if you want to have http://intranet.domainname.com then you have to have the web application available on port 80. Using host headers you can have lots of unique names available on the same server, so there really is no reason not ...


3

You can achieve this using Alternate Access Mapping: On the Alternate Access Mappings page (Central Administration), click Edit Public URLs. If the mapping collection that you want to modify is not specified, then choose one. In the Alternate Access Mapping Collection section, click Change alternate access mapping collection on the Alternate Access ...


3

When you extend a SharePoint web application, you are telling SharePoint to go to IIS and create a new site, but SharePoint will use it to show the same content. You would normally do that to support different security, authentication and URLs between an Internet site, Intranet and Extranet, for example. When you add a host header it is equivalent to going ...


3

Here are the steps: make sure you have valid DNS entry for Local.xyz.com, A record entry for the DNS. Service Account(domain Account) required which will run the App Pool of new Web App. Now login on the Central Admin with Farm Admin account go to Central Admin > Application Management > Manage web Application > from Ribbon Select New Fill this form with ...


3

Do not use a redirect. Set your AAM to only https://, and then use the URL rewite module in IIS to rewrite http requests to https. There are guides (http://pcfromdc.blogspot.com/2013/10/how-to-redirect-from-http-to-https-with.html) out there to use the GUI, but I find editing the web.config file be easiest. Install the URL Rewrite module for IIS and then ...


2

you could try the following: using(SPSite site = new SPSite(SPContext.Current.Site.Zone, SPContext.Current.Site.ID)) { //your code }


2

I think an important thing to point out here is that this is completely unsupported by Microsoft. One of the key issues is that you are changing something other than the host portion of the URL (because the modified URL does not end in "/sub1"), and Alternate Access Mappings (AAM) are not designed for this kind of scenario. The result is that you will have ...


2

You are missing nothing, profile images for some reason (bug) do not obey AAMs. You could try to fix with HttpModule or jQuery, but i'm just waiting for SP1


2

If you stay on the same server I think that using AAMs is the easy solution. Just set the AAM and any hostheader bindings you still need in IIS. SharePoint should take care of the term store depencies although I am not 100% sure of this. If you are concerned about hardcoded URLs, just make a redirect that points to your new domain for the old domain in ...


2

The easiest way to think of it is this: An extended web application is merley an additional IIS web site pointing to the same content. This web site will have a new folder under inetpub\wss\virtualdirectories with the default files within (including web.config) This means that the extended web application will share the majority of settings with the ...


2

hmm it shouldnt be necessary to extend the web app. Normally you can define what you want by adding a new AAM. Extending zones is usually if you need seperate security context (extranet) or specific authentication (eg for indexing). What exactly isnt working with the correct urls? I can recommend the following ressources on AAM: ...


2

Are the external zone just an alternate access mapping (AAM) or is it an extended web app (new zone) with other authentification?


2

@tcv, yes I read your post. Search itself likes the default zone with NTLM permissions. It will work with kerberos and SSL, but you'll save your self alot of TS time, just using 80/NTLM. Search will "mostly" work with an extended app, but you will lose things like the default scopes (this site, this list), etc. You can still search those, but only from ...



Only top voted, non community-wiki answers of a minimum length are eligible