Hot answers tagged alternate-access-mapping
14
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 ...
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
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 ...
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
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 ...
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
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
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
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 ...
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
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
@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 ...
2
There is actually a pretty simple solution. Merely have your DNS folks whip up a new DNS entry (like http://sharepoint07.domain.com - note the 07 in there), point that to your current 07 server and then add that as the URL for one of your Zones in your Alternate Access Mappings( I.E. Intranet/Internet/Extranet/Custom).
When the migration happens, ...
2
Try set it up as follows (ripped from our internal documentation - and assign the self signed cert described above)
Setup Alternate Access Mappings
Open SharePoint 2010 Central Administration
Click Application management
Click Configure alternate access mappings under Web Applications
Click Edit Public URLs (this is on the blue menu bar)
For Alternative ...
2
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 ...
2
It sounds as though you understand the concept of Web app extension so there isn't too much I can add really.
Something that hasn't been mentioned is the fact that extension creates an additional IIS site. You may wish to configure this site in a different manner to the original, e.g. configure an SSL certificate for access over the Internet or change ...
2
The behavior is normal as the AAM doesn't know about your redirect, therefore the Workflow engine is not able to populate the proper Url. You should either use a Reverse'Proxy (e.g. ForeFront TMG, ISA 2006 ) that could automatically change your HTTP to HTTPS or Extend the Web Application to use HTTPS too.
Besides you can make also enable the "Configure ...
2
I think there can be several sources of the problem, if you URL stops working
something is wrong with your DNS server
someone changed IIS bindings
someone changed mappings in Central Administration
About the IIS settings, look into Bindings of your website. Right-click on website and choose Edit bindings. Also go to Central Administration > Application ...
2
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 ...
2
You could achieve this in many ways it all depends on your infrastructure capabilities, here is my take:
Extend you existing application on a HOST-HEADER based web
application - that would create a new IIS web site too, and you
would need to use port 80.
Use a reverse-proxy such as ForeFront TMG, ISA 2006 or any other that could be configured to forward ...
2
If you extend a web application in SharePoint, a new IIS website will be created. That's one of the purposes of extending: to allow a different configuration.
The necessary bindings will be configured and maintained for you by SharePoint itself, on all servers in the farm. If you make manual changes to these settings, you'll have to do this on all servers. ...
2
Don't use SSL (https) whenever specifying your content sources in SharePoint search.
Also, the second error just means that users and services are using the http://servername url to access to the site. It's more of a warning than an error. I constantly see that on my farm, but I ignore it.
1
You should not hardcode a URL into your code. In most cases you can access the context your component is in and can therefore access the objects without a specific hardcoded URL. If you are writing a program that runs outside of SharePoint, and therefore the context must be provided, you should add a configuration section/file of some sort to allow you to ...
1
OK, there's a lot going on here. Let see if I get it.
When you search from a site collection search box (when it doesn't work) do you end up in a search center or the default search page? Is your site collection setup to use the search center? Technically, the search center has one set of web parts for results, regardless of where the request comes from ...
1
A web.config setting was found to be responsible for this case.
I don't have the full details, but apparently changing the session state from InProc to SQLServer solved the problem.
You can read more about using ASP.Net Session State with SharePoint here:
http://blogs.msdn.com/b/markarend/archive/2010/05/27/using-session-state-in-sharepoint-2010.aspx
1
It depends on how you are exposing this externally. You will probably need to setup your AAMs like so (using foo.com as the FQDN example)
Default
http://mysite
Internet
https://mysite.foo.com
Extranet
https://mysite.foo.com
Load you SSL certificate compatible (like a wildcard cert of *.foo.com) for https://mysite.foo.com into IIS and assign the ...
Only top voted, non community-wiki answers of a minimum length are eligible
