Transferring a sharepoint installation to another port / URL

Question

We installed Windows Search Server Express on one of our servers, which apparently runs on top of sharepoint.

Sharepoint was installed on port 80, where our "normal" intranet works. When I turn off the intranet and launch the sharepoint site, everything will work as intended. The intranet is connected in many places, it would be a pain to move it, so I'm trying to move the sharepoint to another “place” (hoping that this is less pain), or another port, or as a virtual directory under the main site.

Firstly, when I make any of these changes, it cannot access the root of the intranet. Not sure what he is looking for there, but ok, I give "Network service" (acocunt for the application pool "Sharepoint 80" works under) to access the root of the intranet. This takes me one step further, I'm at a standstill:

When I move the Sharepoint site to another port, it complains that it cannot find default.aspx (it is not there, but it is also not needed when working on port 80)

When I transfer it to a subfolder of an existing site and try to open global.asax in a browser, ti tells me that this extension is prohibited, although the "Application Configuration" - as far as I understand - is the same as for the Sharepoint site, and allows GET, HEAD , POST, DEBUG for .asax.

Any suggestions?

Answer 1

Sharepoint sites should be able to run on any port - if you go to Sharepoint Central Admin and create or delete web applications without problems.

Do you intend to work heterogeneously with Sharepoint and your regular site like on port 80? I know that you can create a web application at 80 and then not have a root site collection (Sharepoint applications consist of a web application that runs on a specific port and any number of site collections in it, each of which has its own directory path and may contain lists, libraries, other collections of sites, etc.), just creating one on the other way, but I don’t know exactly how it will work together with an existing website on the same port - maybe this not very good. Again, you can create and delete site collections from the main SharePoint administration page, which is associated with your Administration list on your server. I would try to do it first, as if it worked this easily.

Are Windows Search Server Express related to Sharepoint's own search engines? If so, you may find that it will be launched using some objects of the common service provider that even Sharepoint does not expect that they will work in the same port as the sites to which it provides services.

Answer 2

Even better would be to create a different alias (cname) in your DNS for your server, just set a different host header for each website.

for example, in DNS, your machine might be called "intranet." Create an alias for this machine named "sharepoint"

In IIS, create a new site for sharepoint and set the host header for this site to "sharepoint.domain.com", where domain.com is your domain.

Do the same for the intranet website, but set the host header to "intranet.domain.com"

This way, your users do not need to use a different port in the url.

Answer 3

Thanks! I found this option on the sharepoint administration website.

I am adding this answer to describe in detail the steps I have taken - perhaps they are useful to someone else.

On the sharepoint administration website (runs flawlessly on a different port), I selected "create or extend web applications" and then "expand an existing web application."

There, from the drop-down “web application”, “change web application” opens a pop-up window with available web applications. The search engine was installed as "Sharepoint 80", so I chose this.

Then I selected Create New IIS Website with a new name and a new port. All other options looked great by default.

Clicking OK will create a new website in IIS that has been configured correctly. it does not work through the server IP address ( http://192.xxx:8080 ), only using the server name - but this is normal with me :)

I still had to make some changes with permissions, but a full crawl is done, and I can find several documents already. Hooray!

Answer 4

It is much easier when you first create a backup of your site, and then create a new site with the central administrator with a new port number, and then restore the backup (overwrite)