• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 418
  • Last Modified:

HOMEMTA of user accounts after Exchange 2003 install into 5.5 site

Regarding this question
http://www.experts-exchange.com/Networking/Email_Groupware/Exchange_Server/Q_21637747.html?query=The+user+is+mailbox+enabled+and+contains+no+home-mta&clearTAFilter=true#15334574

Will it cause me any problems to leave this alone?  We are going to be migrating all our mailboxes to Exchange 2003 in the coming weeks.  Will leaving this warning alone and not doing anything about it cause any problems with functionality or anything at all?  IS this something I really need to fix?

Thanks
0
MCPJoe
Asked:
MCPJoe
  • 9
  • 7
1 Solution
 
VahikCommented:
do u get this warning?? if u do u will have problem with ur emails specially when
sending internal emails....
It is easy to fix this problem for moved users...just use ADModify and change the value of those attributes to  a correct one...or u can do it through ADSiedit...one at a  time...
0
 
MCPJoeAuthor Commented:
Can you send me specific instructions on how to use ADModify to set this value?  Would I just sent this value on each user account in AD to whatever exchange server their mailboxes are on?  I've never run into this before, so I have no experience fixing it.

Thanks
0
 
VahikCommented:
sure...
this how i will take care of ur problemmm
1- Create a test user in exchange 2003 server
2-Using ADSIedit check users attributes for homeMDB and homeMTA....write it
down ..."remember attribute names are case sensetive"...
3-do a google search and download ADModify....
4-go to the installation folder and click on ADModify.exe
5-choose modify attributes option
6- in the domain list drop down option choose DC bla bla
7-in the domain controller drop down option choose or write the FQDN
8- in the show only option ONLY CHOOSE users and then click on the GREEN ARROW
9-expand ur domain and choose the test USER U CREATED
10- click add to the list
11- in the list hilite it and click next...
12-choose the CUSTOME option
13-check MAKE CUSTOMIZED bla bla
14- in the name of the attribute write homeMDB
15- for the value write "null"
16- press go....u should get a success story BOX
17- go back in ADSI edit and see if the value for homeMDB has been cleared...
18- if so come back and go through the steps and this time for the homeMDB attribute write what u copied in step 2...
check ADSIedit and see if the value is back ....
happy with ur TEST???? if u are then u know what to do next....
and have a happy EASTER
0
Technology Partners: 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!

 
VahikCommented:
REMEMBER values and names are CASE SENSETIVE..........
0
 
MCPJoeAuthor Commented:
So what if I have users on 5 Exchange servers, 4 exchange 5.5 servers and 1 exchange 2003 server?  Do I need to do them in batches, users on one server at a time?  

Thanks
0
 
VahikCommented:
u use this tool when u move users over to 2003....usually u have nothing to worry about....u can check the moved users attributes for the attributes that we are talking about...it is always a good prractice to create a test user....then move users over ...and take a moved user and check his or her attributes against a test user and see if anything major sticks out....if so then u can use ADModify to chenge or even add new attributes and values....
as far as moving users are concerend (in ur situation) move users per server....
first move one test user from 5.5.....check email transfer betwwen the test user
and users on 5.5 and 2003....if u see no problem then move all the users from
one server.....test again......and move to the next server.....
this business is all about testing and retesting...one step at a time....
0
 
MCPJoeAuthor Commented:
I haven't moved any users from Exchange 5.5 to Exchange 2003 yet.  I created some new test accounts directly on the Exchange 2003 server.  I saw the above errors in the exdeploy logs before any users were created on Exchange 2003.  My next problem is now I"m getting "the bookmark is invalid" when trying to view the address list from a new outlook profile created for a new user on exchange 2003.  So these two issues are my only battles at this point.

Thanks
0
 
MCPJoeAuthor Commented:
Is there a chance that the problem I mentioned originally will be fixed on its own as I moved mailboxes to Exchange 2003?  
0
 
VahikCommented:
this problem that u talk about does not happen on all the MOVES...first move and see if that is ur problem...a move takes care of all the changes neccessary to a users attributes authomatically(including outlook profile redirection).....well it is suppose to.....and hope fully urs will be trouble free....and most are....and u should start worring after a move and after a problem is reported.....so all u can do is be prepared...which u are...
as i said create a test user on 5.5 and move the user.....and check and recheck...
wait a day or two ...test....like sending emails and checking free\bussy owa...if satisfied ...move the rest.....
what u are trying to do requires a lota patience  steady hand preperation and knowledge....
0
 
VahikCommented:
MCPjoe is this ur first major migration??? well u have nothing to worry about...
u got to see the stab wounds on my back from all the failed migrations i went through....but u say wounds??? yah...i got them from CEOs chasing me out buldings
after a failed migration..hahahhahahahaah...hey kido just trying to cheer u up....
it happens and will happen even to the best of us...as i said all u can do is to do ur HOMEWORK and be ready....
0
 
MCPJoeAuthor Commented:
Its not the first migration I've done, but by far the most complex and largest I've worked on.  So far I haven't had any major issues, only these two small issues left to resolve.  I consider this a successful installation, and just need to do a bit more tweaking.  Now that I have Exchange 2003, the rest of my migration is much easier.  Do you have any tips on fixing the errors with the offline address list generation?  I've done some digging, but didn't see any different in the attributes Microsoft says to check in Adsiedit.  I also looked at GC issues, but I turned on medium logging for Exchange and see successful calls to the GC.  The event id is 9126.  
0
 
VahikCommented:
well that is one of the problems with migration....u can delete and recreate offline address list (make sure to use a diffrent name for offline address list when deleting and recreating)...and then rebuilt...and then ask ur users to delete their OST files and resync again...make sure outlook is working fine and all the data is available in the outlook before u ask them to receate OST files again and make sure not all the users try resync all at the same time....
u cab try rebuilt first....if that did not solve ur problem then u can try recreate...if that did not solve ur problem u can try recreating OST files ......
what is ur problem with GCs???
0
 
MCPJoeAuthor Commented:
I just installed SP2 for Exchange 2003, now the logging says it can't communicate with AD specifically with a GC.  However, I see in the event logs it connects successfully to a GC to perform other operations, so I'm not sure why the SA has problems for OAB generation.
0
 
MCPJoeAuthor Commented:
Ok, so now I have everything worked out except I'm getting NDRs when sending mail to Exchange 5.5 users from Exchange 2003 mailboxes.  I think its related to the issue I opened this question about.  I am going to call Microsoft for further help fixing this.  
0
 
MCPJoeAuthor Commented:
Ok, my issue now is that the homeMTA and HomeMDB attributes for all AD users is missing.  I have NOT moved any real users accounts to Exchange 2003, all of my production users are connected to mailboxes on 4 Exchange 5.5 servers.  I think my problem sending mail to Exchange 5.5 users is caused by the homeMTA and homeMDB attribute being missing from AD users attributes.  Exchange 2003 doesn't see them as mail enabled users.  

My question is, how can I populate this value correctly, since I have 4 Exchange 5.5 servers, just setting it to a single value won't work for everyone.  Is there another value I can change that will auto populate this?

Thanks
0
 
MCPJoeAuthor Commented:
All fixed, I used admodify to fix the problem with the attributes.  That fixed my issue.  
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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