Search the web
Sign In
New User? Sign Up
sharepoint · Discussion list for Microsoft Sharepoint Portal Server
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Message search is now enhanced, find messages faster. Take it for a spin.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
My Sites running on it's own web application..,   Message List  
Reply | Forward Message #14541 of 14579 |
RE: [sharepoint] My Sites running on it's own web application..,

Typically you'd do this with a "host header" site running on port 80.
There isn't really a good way to get a friendly URL on an alternate port
without involving some sort of URL re-writing proxy like ISA.



Bryan Hart | Technical Consultant | Solanite Consulting, Inc.



From: sharepoint@yahoogroups.com [mailto:sharepoint@yahoogroups.com] On
Behalf Of celts340520
Sent: Monday, June 15, 2009 2:10 PM
To: sharepoint@yahoogroups.com
Subject: [sharepoint] My Sites running on it's own web application..,








Hello, we'll soon be rolling out My Sites to the masses at our company.

When initially setting up SharePoint we configured My Sites to run on
its own web app (as well as its own iis web site and app pool on port
83).

This generated a URL with the port number, 83, included.

What I'm trying to do is give a My Sites web application in SharePoint
running on port 83 (also currently on its own iis site and app pool) a
more user friendly URL - i.e. the port number 83 doesn't show - when
users browse their My Sites page and all subsequent pages underneath it.

We definitely want to keep My Sites on its own SharePoint 2007 Web
Application for performance and administrative purposes.

Is this an acceptable method to display a more user friendly URL...

We created a C-name record in DNS that resolves mysitestest to the ip of
our dev Moss server.

When creating our SSP we made My Sites its own web application using a
newly created IIS site and app pool on port 83.

We'll call the My Sites web app http://servername:83/

The primary Web app is http://servername on port 80.

The AAM I create for the My Sites web app is http://mysitestest (note:
no port specified in the AAM)

After this when I go into the edit shared service provider properties
page (My Site Location URL) or the My Site Settings page (Personal site
provider) within the SSP Admin page I see the My Sites Location URL
listed as http://mysitesdev:80/

Is this approach acceptable? Could it cause any potential issues?

Cheers





[Non-text portions of this message have been removed]




Thu Jul 9, 2009 12:01 am

w3bgeek
Offline Offline
Send Email Send Email

Forward
Message #14541 of 14579 |
Expand Messages Author Sort by Date

Hello, we'll soon be rolling out My Sites to the masses at our company. When initially setting up SharePoint we configured My Sites to run on its own web app...
celts340520
Offline Send Email
Jul 8, 2009
11:26 pm

Typically you'd do this with a "host header" site running on port 80. There isn't really a good way to get a friendly URL on an alternate port without...
Bryan Hart
w3bgeek
Offline Send Email
Jul 9, 2009
12:02 am

Bryan, Would a DNS redirect work for this using the cname? I can't remember if that would still want a port 80. BTW...over the last year I have learned a ton...
Kris Pahel
kris.pahel
Offline Send Email
Jul 15, 2009
3:24 am

DNS only handles the IP address - you need either a host header (which allows you to run more than 1 IIS site on port 80) or something that will do a port...
Bryan Hart
w3bgeek
Offline Send Email
Jul 15, 2009
4:08 am
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help