Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Renaming a Web App

  Asked By: Scottie    Date: Mar 11    Category: Sharepoint    Views: 2147

Is it possible to rename a web app?

The reason I am asking is that I would like to simplify the URL used to
access the web app. I will use some redirect technique if I need to, but
I was wondering if there was an stsadm command to do it, or some other
method.

During initial web app creation I used the default (though I changed the
port number) and ended up with the //servername:port/ as the URL. Our
server naming conventions make the server name look like nonsense to the
average user. As you can see in my sig block I work at Aberdeen Test
Center and would like the URL to show as //atcsp/

Am I missing something obvious? (that has already happened to me once
today, none of my timers were working and I was looking everywhere for
the difficult answers, ended up being the sharepoint timer service on
the server wasn't started....)

Share: 

 

6 Answers Found

 
Answer #1    Answered By: Janell Camacho     Answered On: Mar 11

My first recommendation would be alternate access mapping (AAM).

 
Answer #2    Answered By: Julia Washington     Answered On: Mar 11

Yes, you need to add an Alternate Access Mapping. If you no longer want to
access by the old URL, then you can just change the default  Public Mapping.
Don't forget to add a DNS entry if needed, and a host header in IIS.

 
Answer #3    Answered By: Shashwat Takle     Answered On: Mar 11

When you use Alternate Access Mapping, do you need to use reverse proxy
publishing? I found this page:

technet.microsoft.com/en-us/library/cc288609.aspx

and followed the instructions skipping the reverse proxy. (it is
questionable if we would be allowed to do reverse proxy from a security
standpoint)

so I went into AAM and set it to my web  app, then edited the public URL
for that web app. Added the new URL to the Custom field and saved it.

Then I went into "Create or Extend Web App" and extended the web app,
set the port to the same port as the original web app, and set the URL
to the new URL. Then saved it. Did an iisreset.

In the end, no love. I am realitively sure that the URL I want has been
successfully added to the local DNS (the guy that does it is out this
week but we have been trying to get this to work  for a while now.)

 
Answer #4    Answered By: Aastha Acharya     Answered On: Mar 11

If you extend and map a Web application, the AAM is created automatically. If
not using a reverse proxy, then you just need an AAM for each URL you want to
access a give Web app.

Lastly, I always ping.exe the FQDN to verify DNS. Make sure you have an IIS Host
Header for the site as well as AAM.

 
Answer #5    Answered By: Glenda Roth     Answered On: Mar 11

It did end up being the fact that it wasn't listed in DNS.

Once in DNS the AAM began working  like a charm.

 
Didn't find what you were looking for? Find more on Renaming a Web App Or get search suggestion and latest updates.




Tagged: