RPC OVER HTTPS Connectivity...

[Roy T]

HI Everyone,

I have implemented a third party high availability solution for Exchange
2003 SP2 Backend servers. The name of the third party application is called
"WANSxxC XOSOxT".

I have setup Exchange Front-end at my environment, along with RPC over HTTPS
at the front end.

The third party software works fine and redirect all user mailboxes to
Standby Exchange Backend Servers during the Primary/Active Backend
failure(system completely offline), without any re-configuration at the
client end(through update DNS and all Exchange attributes in the LDAP for all
users).

Since there is no system backup on Primary/Active Backend Server, we have to
reinstall the server with the same name to allow the third party software to
failback all mailboxes after reinstallation of the Active Backend Server.

However, when we delete the Exchange Backend Server from Exchange System
Manager, all RPC over HTTPS connection to the Exchange Front End failed.

It seems it failed to find the failed active server, which is offline for
couple of days already. We think it is because it is no longer listed as
part of Exchange organisation and Front End server fails identify it even the
DNS record is redirected to Standby server.

I am wondering how can we make RPC over HTTPS work to avoid re-configure
outlook for hundreds of users.

If anyone can share their experience, it would be much appreciated!

Thanks

Roy

[Roy T]

The software is CA WANSync XOsoft...

[Roy T]

Hi Everyone,

After further study, I found the cause is the rpcproxy registry is removed
automatically on the Front-End Server.

HKLM\Software\Microsoft\Rpc\RpcProxy

Once the Active server is removed, either manually or through uninstall, the
Front-End will remove the Active Server information from this registry and
result in RPC Over HTTPS failure.

How can we temporarily prevent it from updating automatically? It seems it
will update itself either periodically or after restarting Exchange SA
service.

Thanks in advance.

Roy

[Roy T]

According to Microsoft, the registry value is updated either if ExchangeSA
service is restarted or depends on HTTPFEPollingInterval....

However, it is less prefer to depends on the HTTPFEPollingInterval settings,
as you never know when do you need to reboot the server..

http://technet.microsoft.com/en-us/library/aa997759(EXCHG.65).aspx

It would be nice if we can trick ExchangeSA service on Front End server and
let it think the failed server still exist or not updating the ValidPorts
Registry Value

Thanks

Roy