problem after AD Prep creating mail enabled contacts?
This past week I went through the procedure to prepare AD for Exchange 2010. I ran step 1 to /PrepareLegacyExchangePermissions. One thing I noticed today is when I create a new Contact in AD and I "Create an Exchange e-mail address" and give it a new SMTP address it doesn't seem to take. We are still on Exchange 2003. Has anyone heard of this issue after preparing AD?
October 20th, 2010 8:02pm

Hi, AFAIK there should be no issue but for result I would like to ask you that have you followed this article from Microsoft ? http://technet.microsoft.com/en-us/library/bb125224.aspx Regards. Shafaquat Ali.M.C.I.T.P Exchange 2007/2010, M.C.I.T.P Windows Server 2008, M.C.T.S OCS Server 2007 R2, URL: http://blog.WhatDoUC.net Phone: +923008210320
Free Windows Admin Tool Kit Click here and download it now
October 21st, 2010 12:55am

Do you get any error message? or smtp address is not stamping at all?Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|
October 21st, 2010 7:33am

Yes.
Free Windows Admin Tool Kit Click here and download it now
October 21st, 2010 11:56am

It doesn't stamp the object at all with the SMTP address or a x.400 address, thus it doesn't appear in the GAL either. The interesting thing is when an end user types in the SMTP address for the outside user in Outlook it seems to detect the object, but it bounces. I don't know if the bounce was because when I first created the AD contact I had a typo in the address or what as I can't see any email entries in the properties of the contact, but Outlook seems to detect it somehow. Weird. Because this is causing people problems with the bounces I've deleted the contact from AD. I've tried creating 4 different contacts and none of them are getting stamped with an address. I've actually gone ahead and opened a Microsoft incident with support.
October 21st, 2010 12:09pm

Update: Issue seems to be with contacts or new user object creation so it seems to be an issue with the RUS on the root domain. it seems I can create objects and they get stamped ok on the other domains. At the time I didn't think to try a user objuect, or a contact on another domain. Microsoft support is having me restart the system attendant this evening on the one Exchange server that the RUS is pointing at.
Free Windows Admin Tool Kit Click here and download it now
October 21st, 2010 5:44pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics