Re: SBS 2003 w/ 2nd Exchange/OWA Server
- From: "Ken Sheppard" <ksheppard31@xxxxxxxxxxx>
- Date: Mon, 19 May 2008 09:17:26 -0400
Thanks for your reply and suggestion, Terence.
Will I make this redirect on the existing SBS IIS? From your suggestion, the users would still use RWW (I know it's not supported following TP install) and when clicking on the RWW OWA link, their requests would be internally redirected to the new Exchange OWA IIS.
Ken
"Terence Liu [MSFT]" <v-terliu@xxxxxxxxxxxxxxxxxxxx> wrote in message news:gFjggEYuIHA.1784@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello Ken,
Thank you for posting here. Let's also thank Cris for the input.
According to your description, I understand that you move the OWA from SBS
to another Exchange server, and you want to make the RWW page link to the
new OWA location. If I have misunderstood the problem, please don't
hesitate to let me know.
Based on my research, we unable to modify the RWW page link to not SBS
server. This is hard code of the RWW. I agree with Cris, we need to train
the users to use the direct OWA URL to access it.
As you are paining to convert the SBS to standard windows server, the users
will no longer to use RWW. Therefore train the use to use direct OWA URL is
necessary for you.
However, we can use the IIS web site redirect function to work around this
issue:
1. Start the Microsoft Management Console (MMC) IIS snap-in.
2. Right-click Default Web Site -> Exchange, click Properties on the
shortcut menu, and then click the Home Directory tab.
3. Under When connecting to this resource, the content should come from,
click A redirection to a URL.
4. In the Redirect to box, type your new OWA URL.
5. Under The client will be sent to, click The exact URL entered above.
6. Stop and start the Default Web Site.
Note: This is just a work around based on my knowledge, I'm not guaranty it
is work fine on your network.
I hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Terence Liu (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Ken Sheppard" <ksheppard31@xxxxxxxxxxx>
| References: <0387C4D2-3DB6-4843-B09E-39F7EC522B66@xxxxxxxxxxxxx>
<OHOPgY2tIHA.4376@xxxxxxxxxxxxxxxxxxxx>
<0EEE8DB0-6302-4C6F-8CA4-D37B96315B89@xxxxxxxxxxxxx>
<eRbWFo3tIHA.672@xxxxxxxxxxxxxxxxxxxx>
| In-Reply-To: <eRbWFo3tIHA.672@xxxxxxxxxxxxxxxxxxxx>
| Subject: Re: SBS 2003 w/ 2nd Exchange/OWA Server
| Date: Fri, 16 May 2008 14:17:27 -0400
| Lines: 284
| Message-ID: <004CE467-0535-4625-A724-D2D983E670D2@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: multipart/alternative;
| boundary="----=_NextPart_000_0012_01C8B75F.91D85870"
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
| X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18000
| X-MS-CommunityGroup-PostID: {004CE467-0535-4625-A724-D2D983E670D2}
| X-MS-CommunityGroup-ThreadID: 0387C4D2-3DB6-4843-B09E-39F7EC522B66
| X-MS-CommunityGroup-ParentID: 10F5642D-4C25-4E21-A55E-DC2C575A3AC1
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:108090
| NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Thanks for your reply, Chris.
| I certainly know about manually creating the mailboxes. And we've
purchased the necessary Transition Packs, CALs, Windows/Exchange CALs, a
new Dell PE 2950, new switches, patch cables... It's an investment firm
that has the money and needs the performance. We have a very complex
Public Folder store that's about 30Gb and another 75 mailbox users that is
about 25Gb. The SBS box was an end-of-life Dell PE 2600 that's 5+ years
old. We considered a Swing to new hardware, but that didn't address our 75
user limit. Lots of thought and planning went into the Exchange purchase
and I truly believe that a dedicated twin Quadcore Zeon with 4Gb of RAM and
15k RPM SAS drives will serve us well.
| Any thoughts on my question as to OWA links in RWW?
| Ken
| "Cris Hanna [SBS-MVP]" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxx> wrote in
message news:eRbWFo3tIHA.672@xxxxxxxxxxxxxxxxxxxxxxx
| Ken
| Just out of curiousity, given the cost of a separate windows server
license, the separate Exchange license and all those Exchange Cals, and the
hardware, and time, what is the benefit you expect from this separate
Exchange server?
| BTW, you do know you will have to create mailboxes manually as the Add
User Wizard won't do that for you now.
| -- | Cris Hanna [SBS-MVP]
| -------------------------------------------------
| Microsoft MVPs
| Independent Experts (MVPs do not work for MS)
| Real World Answers
| ---------------------------------------------------------
| Please do not contact me directly regarding issues
| "Ken Sheppard" <ksheppard31@xxxxxxxxxxx> wrote in message
news:0EEE8DB0-6302-4C6F-8CA4-D37B96315B89@xxxxxxxxxxxxxxxx
| Thanks for your reply, Larry.
| I am using ISA 2004 on SBS and I have published the new Exchange OWA,
which
| works to https://domain/exchange. However, most of my users have
gotten
| used to RWW because it contains links to virtually everything like
OWA and
| computers. I was hoping to continue the use of RWW and simply modify
the
| link in the RWW page from the old SBS OWA to the new OWA.
| Ken
| "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer(at)mis-wizards(dot)com>
wrote in
| message news:OHOPgY2tIHA.4376@xxxxxxxxxxxxxxxxxxxxxxx
| > Hi Ken:
| >
| > Port forward the OWA port that you are using from the
router/firewall to
| > the new server. Train the users to use OWA without RWW, directly
to the
| > new server.
| >
| > Lots of articles on the net about what ports to use and how to
configure
| > firewalls. You should speak to or review the literature for your
specific
| > device.
| >
| > -- | > Larry
| >
| > Please post the resolution to
| > your issue so that all can benefit.
| >
| >
| > "Ken Sheppard" <ksheppard31@xxxxxxxxxxx> wrote in message
| > news:0387C4D2-3DB6-4843-B09E-39F7EC522B66@xxxxxxxxxxxxxxxx
| >> I'm running SBS 2003 Premium w/SP2. I have just added a dedicated
| >> Exchange 2003 server running on a member Windows 2003 R2 server.
The
| >> Exchange 2003 installation simply joined the existing Exchange
| >> orginization on my SBS box. I have successfully moved my mailboxes
and
| >> Public Folders via replication. I've also completed OWA setup on
the new
| >> server with SSL. I have not removed the existing Exchange server
on SBS
| >> and I probably will leave it for several of the Exchange roles,
but SMTP
| >> is setup for the users on the new Exchange server.
| >>
| >> I'm now trying to modify the SBS RWW page to point users to the
new OWA
| >> server instead of the SBS OWA server. On the RWW page, there's
the link
| >> to SBS OWA with "Read my company e-mail" and it points to
loadOWA.aspx.
| >> I have found that Web.config on SBS contains this data. The
loadOWA.aspx
| >> file doesn't seem to contain a pure link to
https://servername/exchange.
| >>
| >> How can I point the RWW page to my new OWA and not the old SBS OWA?
| >>
| >> Thanks for any help.
| >>
| >> Ken
| >
| >
|
.
- Follow-Ups:
- Re: SBS 2003 w/ 2nd Exchange/OWA Server
- From: Terence Liu [MSFT]
- Re: SBS 2003 w/ 2nd Exchange/OWA Server
- References:
- SBS 2003 w/ 2nd Exchange/OWA Server
- From: Ken Sheppard
- Re: SBS 2003 w/ 2nd Exchange/OWA Server
- From: Larry Struckmeyer [SBS-MVP]
- Re: SBS 2003 w/ 2nd Exchange/OWA Server
- From: Ken Sheppard
- Re: SBS 2003 w/ 2nd Exchange/OWA Server
- From: Cris Hanna [SBS-MVP]
- Re: SBS 2003 w/ 2nd Exchange/OWA Server
- From: Terence Liu [MSFT]
- SBS 2003 w/ 2nd Exchange/OWA Server
- Prev by Date: Re: SBS Clients Licences
- Next by Date: Re: adding w2k8 to SBS'03R2 domain failes
- Previous by thread: Re: SBS 2003 w/ 2nd Exchange/OWA Server
- Next by thread: Re: SBS 2003 w/ 2nd Exchange/OWA Server
- Index(es):
Relevant Pages
|
Loading