We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

removing HT role in exchange 2007

Winstink
Winstink asked
on
Medium Priority
587 Views
Last Modified: 2012-08-14
Admittedly, my exchange organization is a tad screwed up.  

I am planning on removing the HT role on two of my three exchange 2007 servers.   I found the technet article explaining how to do that. I  have a few questions.

1) do I need to do anything to prepare the organization for this?  Like clean up any queues or something like that.

2)I have Update rollups installed on both machines.  I just need to use Add/remove programs to remove the rolls, correct?

3)  the environment I want is so that mail comes and goes through one server, yet people can check their mail through OWA and Activesync from two servers.  Is this going to solve that?  Is that even possible?

4) Is there anything I need to do to the servers after removing the HT role?

5) Is there anything else I should be worried about?  I'm just a little gun shy on this and don't want to screw up things any more than they are.  

thank you.
Comment
Watch Question

Commented:
Why do you need to remove the HT? Having more than 1 is good for performance and resiliency.

You can just uninstall the role easily from the cmd line in the exchange setup or service pack source files with:
Setup.com /mode:uninstall /roles:HT

Author

Commented:
well maybe you can help me.  I have three exchange servers.  one is going to be decommissioned.  (all sorts of problems with it).  It seems as though mail is routing through the one that is being decommissioned, and not being scanned by any spam filter.  It also seems as though mail gets stuck sometimes in local loop connector (it was before, but I seemed to have fixed that).  

What I want is for mail to come through one server so it gets scanned by the spam filter and routed out appropriately, and won't get stuck in a local loop when sending out.  How do I accomplish this?  

Commented:
First stop the transport service on the faulty server and verify mail flow still works.

Receive connectors are per Exchange server whereas Send Connectors are used by all.

If inbound Internet mail is going to the faulty server then you need to change your firewall/router to forward port 25 to one your other HT servers where you have an anonymous auth receive connector configured...

Author

Commented:
Gosh you are right.  my firewall is pointing to the faulty server.  When I change the configuration to point to the good server, mail gets rejected:

Delivery to the following recipient failed permanently:

 

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 530 530 5.7.1 Client was not authenticated (state 13).


I tried restarting the transport service, but no dice.  So I pointed mail back to faulty server for now.  
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Commented:
Thanks for the points

Author

Commented:
thanks for the help!
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.