New User - email not binding to account

[Guest]

When adding a new user to active directory, his/her email address is not being bound to their username and they are not being added to the global address list. RUS (recipient update service) is running normally and no errors are showing up in the event viewer. The user is able to log into the domain normally, however when they attempt to create an Outlook profile this error occurs: "The name could not be matched to a name in the address list"
Any help on why the email address is not being bound to the username would be greatly appreciated. Thanks!

 

[Cary Shultz [A.D. MVP]]

MT,

How much time are you giving it? I worked previously in a two site
environment and it would sometimes take 90 minutes for this to happen!
BTW - I changed the default Intersite replication from 180 to 90 minutes.
Does this apply to you? If just in one site, does it work after 15 minutes?
I have seen this as well.

Or, does it just not work? Even a day later?

Cary

When adding a new user to active directory, his/her email address is not

being bound to their username and they are not being added to the global
address list. RUS (recipient update service) is running normally and no
errors are showing up in the event viewer. The user is able to log into the
domain normally, however when they attempt to create an Outlook profile this
error occurs: "The name could not be matched to a name in the address list".

Any help on why the email address is not being bound to the username would

be greatly appreciated. Thanks!

 

[Guest]

Thanks Cary. Still not working a day later. Just one site. This actually worked fine/immediately a couple weeks ago and for the last year since the domain was set up. I am unaware of any policy or other kinds of changes on the domain, although obviously something must have changed. The only thing I could possibly think of was we added an ADSI linked server to our SQL Server to pull names from Active Directory into a SQL table. Here was the syntax we used in the SQL Query Analyzer:
sp_addlinkedserver 'ADSI', 'Active Directory Services 2.5', 'ADSDSOObject', 'adsdatasource'
GO
SELECT * FROM OpenQuery( ADSI,'<LDAP://DC=Microsoft,DC=com>;(&(objectCategory=Person)(objectClass=user));name, adspath;subtree')
GO

Could that have done anything? Thanks for the help!

 

[Cary Shultz [A.D. MVP]]

MT,

Do not know about the SQL. Do not know why / how that would affect anything
but I am not that familiar with SQL ( yet!! ). It *should* not necessarily
affect Exchange.

Check two things:

In the ESM open up the Recipients folder and then inside the Recipient
Update Server folder ( left pane ) there will be two entries ( right pane ):
the RUS for the domain and the RUS for the enterprise. Right click the one
for the domain and select 'Update Now'. Does this resolve it? If not, do
the same for the Enterprise. Does that do anything? If not, right click
again and select the 'Rebuild' option.

In the ESM open up the SERVERS folder ( inside the Administrative Groups -
First Administrative Group ) and select the Exchange Server in question.
Actually, right click and select Properties. Then, go to the Directory
Access tab. There should be an entry for the Configuration Domain
Controller at the top followed by an entry for each DC and then an entry for
each GC. All these correct?

This is where I would start!

HTH,

Cary

Thanks Cary. Still not working a day later. Just one site. This actually

worked fine/immediately a couple weeks ago and for the last year since the
domain was set up. I am unaware of any policy or other kinds of changes on
the domain, although obviously something must have changed. The only thing I
could possibly think of was we added an ADSI linked server to our SQL Server
to pull names from Active Directory into a SQL table. Here was the syntax
we used in the SQL Query Analyzer:

sp_addlinkedserver 'ADSI', 'Active Directory Services 2.5',

'ADSDSOObject', 'adsdatasource'