Re: Transitioning RPC-HTTP setup from back-end only to front-end / back-end setup

Tech-Archive recommends: Fix windows errors by optimizing your registry

What is FBA and how do I tell if it is enabled on the back end server?

"Nuevo" <imaneophyte@xxxxxxxxx> wrote in message
news:OnSZIqdSGHA.424@xxxxxxxxxxxxxxxxxxxxxxx
I've done it a number of times. The FE server will certainly connect to
the BE but it won't affect any connections to the Backend as it is being
completely bypassed. One other thing from a testing perspective is that
you can't have FBA enabled on the BE if it is enabled on the FE. Once
again this will only affect people connecting through the FE.

Nue
"Kevin Wilkins" <kwilkins@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OnmnpfdSGHA.1236@xxxxxxxxxxxxxxxxxxxxxxx
Thanks. Are you sure that bringing up a front end server will not cause
any problems with the existing Outlook connections directly to the back
end server?

Anyone have any examples of someone who has successfully made this
transition?

Kevin


"Nuevo" <imaneophyte@xxxxxxxxx> wrote in message
news:%23dt75WdSGHA.2176@xxxxxxxxxxxxxxxxxxxxxxx
I think you understand the process clearly enough based on your
description and I have not seen any documentation which covers this
scenario. My only recommendation for the cutover would be to modify NAT
at the firewall level rather than make IP address changes in DNS. This
will avoid the latency associated with the TTL on your DNS records.

Nue
"Kevin Wilkins" <kwilkins@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:u%23xiOOdSGHA.776@xxxxxxxxxxxxxxxxxxxxxxx
My company is currently using RPC over HTTP on a single server using
the No Front End Server scenario.
http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3RPCHTTPDep/48d6d03d-64c2-470f-9561-6de9003effe4.mspx

The current server is getting overused and performance is degrading so
we are bringing up a second Exchange 2003 back-end server. My
understanding is that we now also need an Exchange 2003 front-end
server as well. I have both of the new servers configured, with
Exchange installed and part of the Exchange organization. I have a few
questions about the next steps.

If I configure the new server as a front-end server for testing will
that make any changes to the existing back-end server that is currently
handling the RPC-HTTP and OWA connections? My plan would be to do
initial testing using a different URL on the new front-end server and
then later migrate the existing URL and certificate from the current
back-end only server. I know that front end servers will dynamically
update when a back end server is added and I'm just concerned that if
the back-end server might update someting when a front-end server is
added so users can no longer connect to it directly.

I have not found any documentation on making this transition from
back-end only to front-end back end setup. Technet gives instructions
titled "How to Deploy RPC over HTTP for the First Time on Exchange
Server 2003 SP1 (Front-End/Back-End Scenario)" but we are not deploying
RPC over HTTP for the first time, we want to transition an existing
setup.
http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3RPCHTTPDep/48d6d03d-64c2-470f-9561-6de9003effe4.mspx?mfr=true
Can anyone point me to any documentation that covers our scenario?

Thanks,
Kevin









.

Relevant Pages

  • Re: SBS 2003 IIS BASED SERVICES FAIL INTERMITTENTLY
    ... If I read your post correctly, you have a switch where the SBS ... Run DHCP server on your SBS, and set all client machine nics to dynamic. ... Once you have your nics configured, run the Connect to the Internet wizard, ... QUESTION1 - what is REFUSING CONNECTIONS? ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... So far everything is good and now I'm just monitoring my exchange. ... get the SMTP service to stop hanging in the first place. ... won't have dead connections. ... work for now until I put into production new server hardware with sbs 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... You really should go through the steps I posted and get the SMTP service to stop hanging in the first place. ... You'll be happier, you won't be clubbing your server every day with a kill script, and you won't have dead connections. ... You do *not* need to restart the server, ...
    (microsoft.public.windows.server.sbs)
  • Access 2007->SQL Server2005 "connection was forcibly closed",GNE 1
    ... I have a very big problem connecting an SQL ... changing number of clients using the SQL Server with this frontend at the ... connection pooling or if these connections are separated connections). ...
    (microsoft.public.sqlserver.connect)
  • Re: Reducing load for LAMP app?
    ... MySQL: as much as possible, he keeps query results in RAM, but ... His hoster says that Apache server is under significant load. ... Using apc is pretty much transparent, but memcached will require modifying your database abstraction layer using the memcached functions. ... With persistent connections, you must have the maximum number of connections *ever* required allocated *all of the time* - even if no one is using your server. ...
    (comp.lang.php)