Re: Upgraded to Exch2003, OWA2003, but experience is slow
From: Marlon Brown (marlon_brownj_at_hotmail.com)
Date: 01/25/05
- Next message: Marlon Brown: "How to access myowa as http://webmail/company.com"
- Previous message: frier: "Re: Autoarchive Settings"
- In reply to: Marlon Brown: "Upgraded to Exch2003, OWA2003, but experience is slow"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 24 Jan 2005 22:37:33 -0800
I applied Exch2003 to front-end and now that works.
"Marlon Brown" <marlon_brownj@hotmail.com> wrote in message
news:uuFJRrpAFHA.2156@TK2MSFTNGP10.phx.gbl...
> I've setup a two node Exch2003 cluster. I still have Exch2000 running in
> co-existence with the new Exch2003 system.
>
> THen I create a new mailbox on the new Exch2003 cluster back-end servers.
>
> Via OWA, I logon with newUserAccount and I see the OWA 2003 interface.
> However, it comes slow and it doesn't finalize all the grapics. I try to
> send an e-mail, but I click "New" and nothing appears. Something is not
> working right.
>
> Any idea of what could it be ?
>
> I did not configure the steps below outlined the Exch2003 Deployment
> guide:
>
> Creating the HTTP Virtual Servers in Exchange System Manager
> When you create an Exchange Virtual Server, during the installation of the
> System Attendant resource, Exchange creates an HTTP virtual server
> resource. To configure a front-end server to use a clustered back-end
> server, you must create additional HTTP virtual servers on each Exchange
> Virtual Server that is a part of the clustered back-end servers.
>
> You must create one Exchange HTTP virtual server for each front-end
> namespace. For example, if contoso.com hosts Exchange Server 2003 for both
> tailspintoys.com and wingtiptoys.com, three virtual servers are
> necessary-the default virtual server, a virtual server for
> tailspintoys.com, and a virtual server for wingtiptoys.com. This
> configuration provides maximum flexibility in determining which resources
> are available to each hosted company.
>
> The following steps must be repeated for each Exchange Virtual Server in
> the cluster.
>
> To create an HTTP virtual server
> 1.
> In Exchange System Manager, in the console tree, expand Servers,
> expand the server that you want to configure as a back-end server, and
> then expand Protocols.
>
> 2.
> Right-click HTTP, point to New, and then click HTTP Virtual Server.
>
> 3.
> In Properties, in the Name box, type the name of your front-end
> server.
>
> 4.
> Next to the IP Address list, click Advanced.
>
> 5.
> In Advanced, under Identities, select the default entry, and then
> click Modify.
>
> 6.
> In Identification, in the IP address list, select the IP address of
> this Exchange Virtual Server (the back-end server). This IP address must
> match the IP address resource value you previously configured for the
> back-end server (Figure 7.9).
>
>
>
> Figure 7.9 The Identification dialog box
>
> 7.
> In the Host name box, type the host header of the front-end server.
> This is the name by which the clients access the front-end server. The
> host header for the Exchange Virtual Server must map to the host header on
> the front-end server.
>
> Note :
>
> Client requests to the front-end server use a specific host, such as
> http://mail.contoso.com. A virtual server on the front-end must have the
> "mail.contoso.com" host header configured. The front-end server then
> proxies the request to the back-end server, which must also have the host
> header configured on a virtual server.
>
> 8.
> Verify that TCP port is set to 80, and then click OK.
>
> 9.
> In Advanced, if you want to add an additional identity, click Add, and
> perform Steps 6 through 8 again.
>
> Note :
>
> Consider adding several identities to the virtual server that list
> all the ways that a user might access the front-end server. For example,
> if a front-end server is used both internally and externally, consider
> listing both a host name and a fully qualified domain name, such as "mail"
> for internal access and "mail.contoso.com" for external access.
>
> 10.
> In Advanced, click OK twice to create the new HTTP virtual server.
>
>
> Creating Virtual Directories to Match the Directories Configured on the
> Front-End Server
> After you create the HTTP virtual server, you must add virtual directories
> to match those configured on the front-end server. A typical Exchange
> installation contains virtual directories called Exchange and Public. In
> Exchange System Manager, virtual directories of HTTP virtual servers
> appear as child objects of the HTTP virtual server.
>
> To create virtual directories on the back-end server
> 1.
> In Exchange System Manager, in the console tree, expand Servers,
> expand the server that you want to configure as a back-end server, expand
> Protocols, and then expand HTTP.
>
> 2.
> Right-click <HTTP Virtual Server Name> (where HTTP Virtual Server Name
> is the name of the HTTP virtual server you created in "Creating the HTTP
> Virtual Servers in Exchange System Manager" earlier in this section),
> point to New, and then click Virtual Directory.
>
> 3.
> In Properties, in the Name box, type Exchange.
>
> 4.
> Under Exchange Path, the Mailboxes for SMTP domain option is selected
> by default. Keep this setting, because users use the Exchange virtual
> directory to access their Exchange mailboxes. Click OK to create the first
> virtual directory.
>
> 5.
> In the console tree, right-click <HTTP Virtual Server Name> again
> (where HTTP Virtual Server Name is the name of the HTTP virtual server you
> created in "Creating the HTTP Virtual Servers in Exchange System Manager"
> earlier in this section), point to New, and then click Virtual Directory.
>
> 6.
> In Properties, in the Name box, type Public.
>
> 7.
> Under Exchange Path, click Public folder, and then click Modify.
>
> 8.
> In Public Folder Selection, double-click Public Folders. After a few
> seconds, Exchange resolves the public folder's server name and appends it
> to the name of the Public Folders container (Figure 7.10).
>
>
>
>
- Next message: Marlon Brown: "How to access myowa as http://webmail/company.com"
- Previous message: frier: "Re: Autoarchive Settings"
- In reply to: Marlon Brown: "Upgraded to Exch2003, OWA2003, but experience is slow"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
