Hello
My farm topology is as follows:
- one web front server
- one app server
- SQL DB server
- Office Web Apps server
I created a new web application to host an intranet site on the app server. Content is already in there. The url is something like http://sp-app/. I also created my sites web app at http://sp-app:100 as well. Now we want to have a nice meaningful url, let's say http://companyintranet.com.
 
QUESTIONS:
1. How do I configure the alternate access mappings?
2. When I create a new DNS entry do I point it to the IP of the web front end or the app server? I want to make sure the web front end handles all web related traffic.
Thanks

• Edited by The Profiler 10 hours 7 minutes ago

1. Configure AAMs

2. Web front end, yep.

• Edited by Keith Work 10 hours 2 minutes ago

First, you mentioned that web application http://sp-app has been created on app server. Please make sure "Microsoft SharePoint Foudation web application" service is started n WFE through Central Admin -> Services on server -> (Choose WFE Server). Also validate site is available in IIS of WFE.

Extending your web application http://sp-app to http://companyintranet.com would be recommended solution.

1.Go to Central administration > Manage web application
2.Select your web application(http://sp-app)
3.Click EXTEND and enter the information for port(Eg. 80) you want to use, DONT FORGET to enter the host header, otherwise you have to do some extra task. For host header you can put the user friendly address. For example, enter companyintranet.com as host header.
4. Click ok and its done.

Second, the best idea shoud be using load balancer if your organization/setup allows. Since you asked single WFE to handle all request, create DNS entry for WFE server.

Thanks guys -

Ripon, would I add the load balancer for both WFE and APP server? I would have to enable the "Microsoft SharePoint Foudation web application" service on the APP server as well so that the app server also acts as a WFE. I thought it would be better to leave the WFE on its own and let the app server handle the rest. It's a small farm so we don't need crazy performance right now.

Ripon, questions about extending the app.

1. If I extend the app using a URL and then company decides to change the URL would I have to delete the extended web app and recreate it? Is this a one time deal?

2. Is there a way to enter the DNS entry without having to extend the web app which would allow you flexibility in updating that DNS entry (URL) later?

Thanks

1. You can go and delete the extended web app if you don't need it.

2. You don't need to extend the web app for setting url to http://companyintranet.com if you don't want users to see http://sp-app at all. You should go to CA-> Application Management -> Alternate access Mappings. Select the web app as http://sp-app. Then set the public url as http://companyintranet.com. Also update the bindings in associated web site in the IIS on wfe server to reflect the same.

Extension is recommended only for scenarios if you want your users to use more than one url or use different authentication policy for different set of users etc.

Hope this