Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1051
  • Last Modified:

Invalid homemta is preventing mail from Exchange 2k3 to 5.5 in same site

I have 700 users with an invalid homemta entry in AD. This was probably caused by a failed first attempt to bring in Exchange 2003 several months ago OR a failed uninstall of one of the 5.5 servers.  (WHAT A MESS)

I followed the Exchange setups /removeorg documentation to remove the original 2k3 install but it seems to have 'missed' the whacked MTA entries.

NOTE: If I copy a valid homemta to a user account, mail flows perfectly well between 5.5 and 2k3 and back.

Is there anyway to 'bulk' copy the correct MTA into these users?

OR BETTER YET.....

Is there anyway to get 5.5 to tell the ADC what the correct MTA entry should be?

Thanks Much,

Brian
0
bhubert
Asked:
bhubert
  • 7
  • 6
1 Solution
 
kristinawCommented:
Brian,

a vbscript could easily 'bulk' update the homemta value, especially if the value will be the same for all users.

are all your users in the same OU?

kris.
0
 
kristinawCommented:
Brian,

Here's a litte vbscript that will update this attribute for you. Change the strhomeMTA value to match what you need it to be, (watch the linewrap, it should all be on one line!), change the OU to match the OU your users are in, then take the ' out of the 'objUser.setInfo line to make the changes stick.

This script assumes all users are located in the SAME OU, specified in the strOU line (if there are any OU's under that OU, no changes will be effected).

Let me know if you have any questions.



strhomeMTA      = "CN=Microsoft MTA,CN=MAIL1,CN=Servers,CN=SITENAME,CN=Administrative Groups,CN=Your Group,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=COM"

strOU                  = "LDAP://OU=YourUsers,DC=domain,DC=com"
Set objOU           = GetObject(strOU)

For Each objUser In objOU
      'wscript.Echo objUser.homeMTA
      objUser.homeMTA = strhomeMTA
      'objUser.setInfo
Next
0
 
bhubertAuthor Commented:
They are in different OU's.  Which makes this VB Script a little hairy.

I still wish I coule have the ADC rebuild these the right way.

If I could check for the presence of "DEL:4d4366" in the homemta field before it is replaced, I could run the script on the whole domain. The homemta field has an improperly deleted MTA there right now and installing the ADC didn't overwrite the MTA with a valid one.

The incorrect MTA string is:
CN=Microsoft MTA\
DEL:4d436681-af5f-42f1-b026-8c8fac50f466,CN=Deleted Objects,CN=Configuration,DC=eastlyme,DC=com

The correct MTA string is:
CN=Microsoft MTA,CN=HSMAIL1,CN=Servers,CN=EASTLYMESCHOOLS,CN=Administrative Groups,CN=ELPS,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=eastlyme,DC=com
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
kristinawCommented:
if you have the same mta for all the users in the domain, then why not just run it against the entire domain?

kris.
0
 
bhubertAuthor Commented:
BTW!!!!!!!!!!
The incorrect MTA string sometimes appears w/ different char's right after the CN=Microsoft MTA\  sometimes its a pipe and a 0A etc etc.

b
0
 
bhubertAuthor Commented:
sorry, there are two different Exchange 5.5 servers and consequently two different homemta

where is the stupid find/replace button in ADSI edit ;-)
0
 
kristinawCommented:
can you try completely removing the homemta attribute for someone and see if mail delivery works?

if that works you can simply wipe the attribute from all your users.

kris.
0
 
bhubertAuthor Commented:
Tried wiping the homemta for all users and the ADC put it back correctly!!!

What would the VB script be to search for all users in an OU and set homeMTA to <not set> so that the ADC can set it correctly?

B
0
 
bhubertAuthor Commented:
btw,

i have never run a vbscript to do anything before so a FAQ on how to run one would be grand....
0
 
kristinawCommented:
it will have to wait til tomorrow, that type of script is a little more complex.

later,
kris.
0
 
kristinawCommented:
good morning:)

so when you wipe out the homemta everything gets set correctly?

can you give me some idea of your ou structure? is it terribly complex?

kris.
0
 
bhubertAuthor Commented:
Don't bother writing the code. I am still uncovering the 'bodies' buried on this network from the last IT guys/gals. I don't want to use a script on this AD!!!

I have a couple of flying monkies going through 530 mailboxes and deleting the homeMTA attribute. I'll buy the beers.

To sum up for the next poor person that has this issue:
1. homeMTA was whacked because of failed ADC installation
2. the /removeorg switch didn't remove bad homeMTA data
3. install of ADC didn't 'refresh' data
4. if you delet the homeMTA data and re-synch the ADC connectors the correct MTA data is put in homeMTA field
5. a find/replace feature added to ADSI edit would rule!!!! (i would have been tempted to use it)

Thanks KristinaW. I have never posted a question here before, I'll make sure that you have all the points you can for this one. I am certain your script would have worked and your advice to reset the homeMTA and resynch ADC was perfect.

Brian
0
 
kristinawCommented:
Brian,

glad you got it fixed! don't let this discourage you from upgrading though, you'll like 2003.

Kris.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now