dtooth71
asked on
RPC-HTTP configuration
i am currently in the process of swing migration of server 2003/exchange2003 standard (both currently on a DC) to a server 2003/exchange2003 standard (member server). on server1(old) i have configured RPC-HTTP and has been and is working just fine. in an effort to configure server2(new) i would like to set it up prior to the entire mailbox move. then i will test with my mailbox and another test box i moved to the new server. to test i plan to move the NAT entry from the old to the new(temporarily as i know this will stop mail flow) however i am not sure if having two RPC-HTTP setting up at the same time will cause conflict, which i do not want to do. experience comments on this configuration???
I am using Simons link here http://www.amset.info/exchange/rpc-http-server.asp. I have configured the GUI to set the backend server( there is no front end, however this is how i have my current setting and it works) the registry DC registry changes - all senerios and the Seperate Exchange server and domain controller configuration registry setting. i believe i have everything here correct.
I am using Simons link here http://www.amset.info/exchange/rpc-http-server.asp. I have configured the GUI to set the backend server( there is no front end, however this is how i have my current setting and it works) the registry DC registry changes - all senerios and the Seperate Exchange server and domain controller configuration registry setting. i believe i have everything here correct.
ASKER
this is not a front-end, backend server configuration/ i just did not know if setting up this configuration with one i place will cause issues? becasue i have to put entries on my DC and the member server Exchange now as currently the exchange box is a dc.
I understand better, let me paraphrase for clarity.
You are adding a stand-alone (non DC) Exchange server to your domain (this will not be a Front-End/Back-End environment). Your current Exchange Server is a DC and is configured as a single RPC over HTTPS server. If you configure RPC over HTTPS on your stand-alone Exchange server, will this cause any problems with the current flow of RPC over HTTPS traffic?
Am I on the right track?
-saige-
You are adding a stand-alone (non DC) Exchange server to your domain (this will not be a Front-End/Back-End environment). Your current Exchange Server is a DC and is configured as a single RPC over HTTPS server. If you configure RPC over HTTPS on your stand-alone Exchange server, will this cause any problems with the current flow of RPC over HTTPS traffic?
Am I on the right track?
-saige-
ASKER
that is absolutely correct.
This would pose an interesting situation. My gut want's to say that as long as you have configured the DC to have the port in the registry for the second server that this should not present a problem. Imma have to think on this for a bit.
-saige-
-saige-
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
then i will implement the settings. if i can bring my certificate ofvger form the other server then that is ok.
i need to test externally for my users. what do you suggest?
i need to test externally for my users. what do you suggest?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
When the client request comes in, and the LDAP authentication is made, your Front-End server would recieve information as to which Back-End (or HOME) server to send the request to.
-saige-