Is it safe to just delete the 2 entries that are in the "gatewayproxy" attribute for the Recipient Update Service? I noticed that the other 2 RUS items don't have any gatewayproxy entries. Further to part 2, can I just delete the bad RUS item? I kind of think that it should be linked to our exchange server in our other site.
By the way, this configuration is the same at the other site. Active Directory is controlled on DC 1 at our site, not theirs so I have a feeling that AD replication between the 2 sites is configured incorrectly.
This all really came about because we had a 3rd party IT managing our organization and they are gone now so we are finding their mistakes. Thank you for your help. I just need to know what to do with bad RUS 3. Do I delete the entry or change it to reflect our exchange info at our other site? This article is purely mend to educate and free to share to whom so ever. Exchnage Server Simplifying Messaging Services.
Share this if you like: Twitter Facebook. Like this: Like Loading Category: Exchnage Server Blog Archives.
Blog Statistics in Google search. Scott in reply to rsmudliar Post : 4. I just need to know what to do with bad RUS 3. Do I delete the entry or change it to reflect our exchange info at our other site? Scott in reply to scohunter.
Post : 5. Post : 6. Post : 7. Since your Topology is not so big. And one domain RUS is enough to process the request. DRUS is required in every site where exchange is installed. If you make them point to remote domain then there will be a problem generating proxy address. Post : 8. We have 1 domain and it is spread across 2 site. California and Montana. So do we really only need the 1 Enterprise RUS entry?
Any other comments are appreciated.
0コメント